HP Storage Management for Oracle 5.0 Release Notes, HP-UX 11i v3, First Edition, May 2008

For more information about Oracle parameters for archiving redo logs, see the relevant
Oracle documentation.
— Existing snapshot plexes created using the vxassist command are not supported. A
combination of snapshot plexes created using the vxassist and vxsnap commands
is also not supported.
• Oracle Disk Manager Limitations
— You must not turn off the Quick I/O mount option, because Oracle Disk Manager uses
the Quick I/O driver to perform asynchronous I/O. The default option is the correct
option to use.
— Using Oracle Disk Manager with Cached Quick I/O enabled is not supported and may
cause a system panic. To avoid a system panic, ensure the following:
◦ If you are using Oracle Disk Manager, you must not enable Cached Quick I/O on
your file system.
◦ If you are converting Quick I/O to Oracle Disk Manager, ensure that Cached Quick
I/O is disabled.
System Requirements
This section discusses the supported Oracle and HP-UX versions, and required patches.
Supported Oracle and HP-UX Combinations
Oracle 10gR2 and Oracle 11gR1 are supported in non-clustered environments.
Patch Requirements
For information on the list of required and recommended patches for SMO 5.0, see the Veritas
5.0 Installation Guide HP-UX 11i v3.
Compatibility With Earlier Versions
Support for Oracle 9.2.0.3 or later is available and there is no compatibility issues with earlier
versions of Oracle.
Known Problems And Workarounds
Following are the known problems in SMO 5.0:
• Problem
After an update of SMO bundle that contain the VRTSdbms3 package from 5.0 on HP-UX
11i v2 to 5.0 on HP-UX 11i v3, the DBMS server cannot be restarted. The following error
messages are printed in the swm and swagent logs:
ERROR: Could not start DBMS server instance. Please check error.
ERROR: Return code: 2
ERROR: Installation has failed!
* Running "configure" script for product "VRTSdbms3". failed with 3
errors.
ERROR: The "configure" script for "VRTSdbms3" failed (exit code "1"). The
script location was
"/var/adm/sw/products/VRTSdbms3.2/pfiles/configure".
In addition to these errors during an update, errors are also seen at the time of swverify
operation for VRTSdbed, VRTSdbcom and ASFO* products. You are advised to ignore these
error messages as they are being reported for dependencies that these products define on
VRTSdbms3 which does not appear to be in the right state after an update. Following is a
sample of these error messages:
14 HP Storage Management for Oracle (SMO) 5.0 Release Notes