Skip to Main Content

Hardware

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

SAM-QFS 5.3 What Works With What

Brad Blasing - Oracle-OracleJun 23 2015 — edited Jun 30 2015

SAM-QFS 5.3 What Works With What

(Revision 1.5)

April 20, 2015

1. Introduction

SAM-QFS is an integrated hierarchical storage manager (HSM) and storage area network (SAN) file system. SAM is the HSM storage and archive management component. QFS is the SAN scalable high performance file system component. SAM-QFS also has integrated disk volume management and tape volume management. QFS also has a write once, read many times (WORM) file system capability. QFS can be used independently of SAM when just a file system is needed. SAM requires QFS and cannot be used independently of QFS. This "What Works With What" covers the specifics of what works with SAM-QFS.

This What Works With What (WWWW or W4) covers the following products:

  • SAM-QFS 5.3
  • QFS 5.3

The build level for the base 5.3 release is 5.3.2.The build level for the base 5.3-01 patch is 5.3.9.The build level for the base 5.3-02 patch is 5.3.14.The build level for the base 5.3-03 patch is 5.3.18.

2. Supported Products, Configurations, And Features

The following products, configurations, and features are supported with SAM-QFS and QFS.

2.1 Hardware Products

  • All Sun SPARC (64 bit) architecture servers and workstations.
  • All Sun x64 (64 bit) AMD architecture servers and workstations.
  • All Sun x64 (64 bit) Intel architecture servers and workstations.
  • All Sun x86 (32 bit) Intel architecture servers are only supported as Shared QFS clients.
  • All Fujitsu Prime Power SPARC servers.
  • All Sun SCSI, FC, and iSCSI protocols.
  • All Sun SCSI and FC HBAs.
  • All Sun FC switches.
  • All Sun RAID disk arrays (includes StorageTek RAID disk arrays).
  • All Sun hard disk drives (includes the X4500).
  • The tape libraries and tape drives listed at:
    SAM-QFS Tape Library and Drive Support
  • All non-Sun HBAs and switches supported by Sun (includes HBAs and switches listed in the Interop and PreQual Tools as well as via the Get To Yes program).
  • All non-Sun RAID disk arrays supported by Sun (includes RAID disk arrays listed in the Interop and PreQual Tools as well as via the Get To Yes program).

2.2 Software Products

  • Oracle Solaris Operating Systems: See section 4.1 below for certified versions
  • Linux Operating Systems: See section 4.2 below for certified versions
  • ZFS Volume Manager (ZVOLs)
  • Solaris Volume Manager (SVM)
  • Solaris Volume Manager (SVM) OBAN cluster capability with Solaris Cluster
  • Veritas Volume Manager (VxVM) with stand-alone SAM-QFS
  • NFS V4 (without delegation for shared file systems)
  • NFS V3
  • SAMBA
  • All StorageTek ACSLS releases through 8.2
  • Solaris Cluster HA-QFS
  • Solaris Cluster HA-SAM (SAM failover). It is only supported in a two host active/passive configuration. There are several configuration restrictions regarding this feature and the SAM Administration Guide should be read prior to using this feature.
  • Solaris Cluster HA-NFS with HA-SAM.  NFS v3 and v4 were tested.  NFS file systems must be exported from the current SAM-QFS MDS.  Minimum code levels for using HA-NFS with HA-SAM are Solaris 11.1 SRU 19.6 and SAM-QFS 5.3.
  • Solaris Cluster HA-Oracle
  • Solaris Cluster Scalable (Shared) QFS with Oracle Real Application Cluster (Oracle RAC)
  • IBM Tivoli SANergy with a Solaris SPARC server. IBM Tivoli SANergy file sharing software may be used to support hosts running different operating systems (heterogeneous support). This software is not supported with Solaris x64 servers, however. This software is now supported by Sun Support Services with IBM serving as backline support.

2.3 Configurations

  • Solaris mixed architecture (SPARC with x64) Shared QFS configurations requires use of EFI disk labels.
  • Shared QFS should be implemented using a private or dedicated ethernet switched network for metadata transmission. Performance problems can occur if this network is not private.
  • For Shared QFS configurations of 10 hosts (nodes) or greater it is recommended that applications not be run on the metadata server to provide more predictable client performance.
  • Sun StorageTek Enterprise Backup to a SAM-QFS file system.
  • Veritas NetBackup to a SAM-QFS file system.
  • Clients outside of Solaris Cluster in Solaris Cluster configurations. This includes clients of mixed architectures (SPARC with x64). This capability is only supported with the ma file system type.

2.4 Virtualization Configurations

  • Zones (containers). Only one non-global zone per file system is supported. There are several configuration restrictions regarding this feature and the QFS Administration Guide should be read prior to using this feature. For Solaris Cluster, Oracle RAC is supported in a Zone Cluster.
  • Oracle VM Server for SPARC (previously known as Sun Logical Domains, or LDOMs) is supported with SAM-QFS, with the following restrictions:
    - Minimum of 4 cores assigned to the domain.
    - Suggested minimum of 24GB of RAM.
    - SAM-QFS MDS must boot from a physical device, and therefore it must have at least 1 PCI root complex.
    - Disk I/O virtualization is not supported for LUNs which are used in a QFS file system.
    - Network virtualization is supported.
    - Tape devices must be attached via non-virtualized PCI slots attached to the SAM-QFS MDS server.
    - QFS clients may boot from a virtualized disk, however they still need a PCI root complex to access file system devices via PCI controllers (FC or SAS etc.)
  • For Solaris Cluster, virtual storage devices used by Shared QFS must be backed by whole SCSI FC LUN disk arrays, and must not be shared with any other guest domain on the same server; virtualized partial LUN disk arrays are not supported.

2.5 Feature Limitations

  • If running SAM with Shared QFS, SAM must be run on the metadata server.
  • A version 1 file system cannot be upgraded to a version 2 file system.
  • SAM-Remote servers and clients must be running the same revision level of SAM-QFS.
  • Remote disk archiving servers and clients must be running the same revision level of SAM-QFS.
  • Shared QFS clients must be running within one software revision of the Shared QFS metadata server. So if the Shared QFS metadata server is at revision level "N", the Shared QFS clients must be at revision level N or N-1. (Note that a Shared QFS client will be at revision level N+1 only when performing the first step of a rolling upgrade where the potential metadata server is upgraded.)
  • Multi-reader servers and clients must be running the same revision of SAM-QFS or QFS software.
  • Mixed architecture (SPARC with x64) metadata servers are not supported for failover purposes.
  • Mixed architecture (SPARC with x64) multi-reader configurations are not supported.
  • Online shrink. Online shrink is only supported for V2A ma file systems. Online shrink now includes support for Solaris Cluster.
  • NFSv4 ACL's supported on Solaris 11 only.

3. Unsupported Products, Configurations, And Features

The following products, configurations, and features are not currently supported with SAM-QFS and QFS.

3.1 Unsupported Software Products

  • Sun StorageTek Enterprise Backup of a SAM file system
  • Veritas NetBackup of a SAM file system
  • Instant Image (II)
  • Sun StorageTek Network Data Replicator (SNDR)
  • NFS V4 delegations with Shared QFS
  • CIFS (Common Internet File System) - Ephemeral ID's are not supported. All Windows identities must have an explicit idmap entry (either directory or name map based)

3.2 Unsupported Configurations

  • Solaris regular zones with Solaris Cluster
  • Solaris Cluster HA-SAM with clients outside of Solaris Cluster

3.3 Unsupported Features

  • Segmented files on a shared file system
  • Memory mapped segmented files
  • Mixed architecture (SPARC with x64) metadata server failover
  • Mixed architecture (SPARC with x64) multi-reader
  • The Linux Shared QFS client doesn't support:
    - access control lists (ACLs)
    - quotas
    - being used as a NFS or Samba server
    - sam-aio driver
    - SAM-QFS Manager (GUI)
    - 32 bit kernels on x64 systems
    - forced unmount (umount -f)
    - mdadm path failover

4. Certified Products And Configurations

The following products and configurations were certified (tested) for SAM-QFS and QFS:

4.1 SAM and QFS

  • Oracle Solaris 11 (base 11.0 release)
  • Oracle Solaris 11.1 (requires SAM-QFS 5.3-01 patch)
  • Oracle Solaris 11.2 (requires SAM-QFS 5.3-03 patch)
  • Oracle Solaris 10 10/08 or later updates of Solaris 10
  • The tape libraries and tape drives listed at:
    SAM-QFS Tape Library and Drive Support

4.2 Linux Shared QFS Clients

The following versions of Linux were certified for Sun x64 64 bit architecture systems:

  • Oracle Linux 5.6 (2.6.18-238.0.0.0.1.el5 kernel)
  • Oracle Enterprise Linux 5.4 (2.6.18-164.0.0.0.1.el5 kernel)
  • RedHat 5.6 SMP RHEL AS and ES (via OL 5.6)
  • RedHat 5.4 SMP RHEL AS and ES (via OEL 5.4)
  • RedHat 4.5 (2.6.9-55.ELsmp x86_64 kernel) SMP RHEL AS and ES
  • SUSE 11 Service Pack 1 (2.6.32.12-0.7-default kernel) SMP SLES
  • SUSE 10 Service Pack 3 (2.6.16.60-0.54.5-smp kernel) SMP SLES
  • SUSE 10 Service Pack 2 (2.6.16.60-0.21-smp x86_64 kernel) SMP SLES
  • SUSE 9 Service Pack 4 (2.6.5-7.308 x86_64 kernel) SMP SLES

4.2.1 Linux I/O Channel (Path) Failover

Device mapper path failover was tested with RedHat 4, SUSE 10, and SUSE 9 and is supported.mdadm path failover is not supported. This is due to its use of a superblock at the end of each disk slice that Solaris is unaware of.

4.3 Oracle Database

4.3.1 HA-Oracle

The following versions of HA-Oracle were certified with QFS and Solaris Cluster:

  • SPARC Oracle 11g Release 2 (11.2.0.3, 11.2.0.4 also supported)
  • SPARC Oracle 10g Release 2 (10.2.0.5)
  • x64 Oracle 11g Release 2 (11.2.0.3)
  • x64 Oracle 10g Release 2 (10.2.0.5)

4.3.2 Oracle Real Application Cluster (Oracle RAC)

The following versions of Oracle RAC were certified with Shared QFS and Solaris Cluster:

  • SPARC Oracle 11g Release 2 (11.2.0.3, 11.2.0.4 also supported)
  • SPARC Oracle 10g Release 2 (10.2.0.5)
  • x64 Oracle 11g Release 2 (11.2.0.3)
  • x64 Oracle 10g Release 2 (10.2.0.5)

4.3.3 Oracle Solaris Cluster

The following versions of OSC were certified with Shared QFS:

  • OSC 3.3 U1 with Solaris 10
  • OSC 4.0 with Solaris 11.0
  • OSC 4.1 with Solaris 11.1  (SAM-QFS 5.3-01 or a later patch is required for Solaris 11.1)
  • Clusters configured with Solaris Cluster should all be at the same major level of Solaris.

5. Uncertified Products And Configurations

The following products were not certified or tested with SAM-QFS and QFS and thus the potential exists that a customer may have problems with them:

  • Sun StorageTek Enterprise Backup of a QFS file system
  • Veritas NetBackup of a QFS file system
  • Veritas Cluster Services (VCS)
  • Veritas Cluster Volume Manager (VCVM)
  • Sun StorageTek Resource Management Suite
  • Sun StorADE
  • Any other Solaris Cluster agent with shared QFS configuration that hasn't been previously listed as supported
  • HA-NFS with HA-SAM with code levels less than Solaris 11.1 SRU 19.6 or SAM-QFS 5.3.

Note that backup of QFS file system data should work. Backup products may not be aware of all of the QFS metadata extended attribute information, however, and this should be taken into account when backing up a QFS file system.

Comments

MWaseem

Dear Sir,

         @"Michael Ferrante-Oracle" is below tweet regarding forms 19c.

20190529_095233.jpg

Dan Andro-Oracle
Answer

Hello,

There won't be a 19c version, the version will be called 12.2.1.4. No official release date has been established.

Regards,

Dan

Marked as Answer by MWaseem · Sep 27 2020
bkmcdaniel

Dan,

There is a lot of confusion, speculation, and misinformation concerning the future of Oracle Forms and associated products. It would be nice if Michael or someone could provide an updated roadmap, MOS document, etc. Even our sales reps and support coordinators have conflicting information.

In 2018, Michael gave a presentation which contained a "Forms Road Map" slide (timeline) that showed "19.1.0.0 Patch Update" targeted for CY19. While that presentation contained the usual warning/disclaimer that the product was for information purposes only, is not a commitment, etc., etc., etc. However, a tweet by Michael also showed a success screen for Fusion Middleware / Forms Services 19.1.0.0.

Regardless of the actual version number attached to the final product, it would be nice to have some details available as to what we can expect to see. Not every organization is capable of applying the next product update without planning, scrutiny, etc. Throw in a timeline (i.e. 1 year to end of support after update) and things get stressful for absolutely everyone involved (i.e. "developer crunch"). A little information here can be a big help for project planning, software life cycle planning, resource management, etc.

  1. According to the Lifetime Support Policy, Oracle Forms and Reports is supported until August 2022 / August 2025. However all other documentation, release notes, roadmaps, articles, presentations, etc. state that Reports is deprecated, 12.2.1.3 is the planned terminal release, reports not to be included with the next version, etc. and that BI Publisher (which a RUL is included with the WLS/Forms license) is the recommended replacement.
    1. Will 12.2.1.4/19.x continue to offer support for Oracle Reports?
    2. Will 12.2.1.4/19.x offer an installation option for BI Publisher or will it remain a separate download?
  2. It has been stated that there are technical reasons that Oracle Forms 12.2.1.3 cannot be used with the newer releases of Java.
    1. Will 12.2.1.4/19.x continue to support Java 8?
    2. Will 12.2.1.4/19.x support Java 11 (the LTS release)?
    3. Will 12.2.1.4/19.x support both?
  3. Will Forms 12.2.1.4/19.x continue to support JWS or will it be FSAL only? Obviously if there is no support for Java 8, it will have to be FSAL only.
  4. Is the upgrade from 12.2.1.3 to 12.2.1.4/19.x the same as previous "upgrades" or will it be simpler (i.e. more like a true patch)? I understand that things are more complicated due to the underlying WebLogic and FMW Infrastructure.
  5. Not specific to Forms, but an easier path to relocate the WebLogic repository would be nice. There are MOS documents on how to do this but there is a lot of room for error. So, if you could put in an enhancement request that'd be great! Probably 90% of our WLS installations are specifically for OFR.

I know Oracle, like many other companies, has a policy on what can and cannot be said on unreleased products. This is understandable, but it sure would be nice to be able to set management expectations and to be able to prepare them for changes on the horizon.

Holger.Lehmann

I think you'll have to be patient and wait :-)

CY19 is there and even more we don't know :-)

Let OOW come or KScope and perhaps .....

@"bkmcdaniel", let me start with this.  I have been working with Oracle and specifically the Forms product for a very long time.  In that time, neither I or anyone else with the authority to say anything about the Forms product have ever said that Forms was not planned to continue on forward.  We may have encouraged users to consider newer technologies when appropriate, but never was it said that the product was at the end of its life.  So there should be no "confusion, speculation, and misinformation", as you've stated, if you are listening to those with authority to comment.  Problems start when you (the community of product users) take comments from a third party who are trying to sell you something as gospel or manipulate you for some other purpose.  I have been in a Product Management role for a long time.  In that time, I have done nothing but provide roadmap information and generally good news about the product.  So it is unclear how anyone could be confused.

Regarding "Reports", Oracle previously announced the product as being deprecated.  This does not necessarily mean it won't be delivered any longer nor does it mean you are no longer entitled to support.  It means that Oracle is planning to end its life at some future time and you should not be banking on it being available in the future.  It also means that no new updates will be added to it.  It will basically be frozen in time beginning with 12.2.1.3.  So if Oracle decides to ship it with the next release or any release in the future, likely it would be just like it was in 12.2.1.3, except for changes required to make it compatible with the infrastructure and framework that hosts it.  It may (but may not) also include bug fixes that were deemed critical to include.  So yes, considering a move to BI-Publisher is likely a good idea if your organization is making significant changes to its current reports and expects to create new ones in the future.  That said, Reports 12.2.1.3, like most of the products in the FMW 12.2.1 family are entitled to support based on the published support dates.  At this time, there are no plans to change that.  So you can choose to remain on Reports for some time, but I would not wait until Aug 2022 (or Extended Support - Aug 2025) to start discussing what you should be doing next.  Such discussions should have already started.  Note that BI-Publisher is available on-premise, but is also available in Oracle Cloud (Oracle Analytics Cloud).  This could be a good match for Oracle Forms in Cloud, which you can do today using Oracle Cloud Infrastructure (OCI- Compute).

Regarding your other comments/questions, beyond what I've said here, i can't say much more.  However, what I can say is that some of your desires are being planned for a future release.  Exactly which release I cannot say.  Also, with regard to continuing support of JWS or removing it from Forms, we have no plans to remove any functionality from Forms while related dependencies are still available and supported.  So in the case of JWS, which is planned to be available to Oracle customers who are using supported products (e.g. Forms 12.2.1.x), you should have some kind of JWS support at least until 2025 (and possibly longer).  FSAL will be the preferred configuration, although JWS is planned to continue being supported for the foreseeable future, as mentioned.

My recommendation is that if you have a product question (regardless which product or its vendor), you should reach out to someone of authority related to the product owner/vendor.  Offer very limited faith in social media and unsubstantiated rumors not communicated by those with authority to comment.

A more official statement can be found in MyOracleSupport Note 2009262.1

It all sounds like mostly good news to me...

bkmcdaniel

In that time, neither I or anyone else with the authority to say anything about the Forms product have ever said that Forms was not planned to continue on forward.

There was no question or concern with that. Oracle has clearly stated that they remain committed to this product. As I stated in my post, the "confusion, speculation, and misinformation concerning the future of Oracle Forms and associated products." As you can see from my post, this mainly hinges on topics such as Java, Reports, and the things that are used in conjunction with Forms itself.

When it comes to Reports, I understand that it is deprecated, at the terminal release, and we shouldn't expect to see new features. To me, I would consider this to be a risk and will continue to be a risk until it is eliminated from our environment. To my management, they see "supported until August 2022." What my management does not understand is what "supported" means when it comes to Oracle products. It means I can submit an SR, it does not guarantee that it will be available with or work with later products. We ran into a similar situation years ago where a security fix was only available in OHS 11.1.1.9, could we upgrade the included OHS 11.1.1.7 with OFR 11.1.2.2? No (Doc ID 1373061.1). But our product was supported. Sure, we could submit an SR to request version compatibility, backport, etc. Such requests are often painful and lengthily to get a resolution. The whole 12.2.1, 12.2.1.1, 12.2.1.2, and 12.2.1.3 has been somewhat similar... technically, according to the Lifetime Support Policy, these are still supported. According to the Error Correction policy, that is a different story (Doc ID 1933372.1). I understand that this is the same process used elsewhere with Oracle - the 12.2/18c/19c database is another prime example of how the support policy says one thing but other documents are needed to get all the other details required to put together the big picture.

Again, my goal is to try and set expectations and keep management informed. MOS documents, statements of direction, and whitepapers are often vague and subject to change without notice (or details of what changed). I don't want my organization to be in a situation where they are planning to be done by X date, only to have a security situation that requires a patch/update specific to a particular version that is sans features still being used. When we ask such questions of our Oracle reps (sales or otherwise) we receive conflicting information from them or information that contradicts published documents. That's why the questions are put here, to hopefully get as much information as possible from those of authority, like you.

I'm in a situation where I cannot provide the information to management to get them to prioritize certain change. Yet, if something occurs and we need to make a move by a certain date, I will be the one to catch management's ire for not providing them the information to raise the priority. Damned either way. All I can do is ask questions, and if something occurs, have the documentation available to show that I tried and hope that is enough.

Well kudos to you for doing your homework.  I wish you would/could encourage others to do the same. 

Regarding Java, we (Forms) are doing everything within our internal boundaries to ensure that the changes in Java do not impact our customers' ability to run their Forms applications.  This was one reason for creating the Forms Standalone Launcher (FSAL).  If we find ways to improve it or even an alternative, we will consider that as well.  Going forward we will be considering improvements to FSAL that will hopefully make it easier to use and administer.  We are also looking into supporting newer Java versions although exactly which is to be determined.  Likely we would only support the LTS (Long Term Support) releases.  Also, we likely will not support the use of OpenJDK.  Only the Oracle builds would be certified.

For Reports, as I mentioned I see no immediate issue with getting support for using it assuming you are using the latest version (currently 12.2.1.3).  However, as time passes (especially after 12.2.1.4 releases), you may find it more difficult to get bugs fixed unless they are clearly critical.  That said, your definition of "critical" and Oracle's may differ and it is Oracle that will get the last word.  As for compatibility with other products, like my comments related to the use of Java with Forms, we are doing everything we can to ensure that Forms and Reports continue to offer direct integration (i.e. through RUN_REPORT_OBJECT). This should not be an issue for 12.2.1.4, but after that is still unknown.

I mentioned BI-Publisher above.  Don't forget that Forms 12.2.1.x introduced integration with BI-Publisher similar to the integration with Reports.  Check out the Forms 12c New Features Guide for more information about it and more.  You can find that doc and other Forms 12c specific papers here:

https://www.oracle.com/technetwork/developer-tools/forms/documentation/techlisting12c-2855390.html

1 - 7

Post Details