Veritas Storage Foundation for Oracle 5.0 Release Notes, First Edition

• Storage Checkpoint Limitations
— You cannot create a clone database using a mounted Storage Checkpoint.
— You must run the dbed_update command after upgrading to Veritas Storage
Foundation 5.0 for Oracle from a previous release. This will allow you to roll back to a
Storage Checkpoint that was created prior to this release.
— If you create an Oracle instance using the spfile option, you must run the
dbed_update command before you can successfully perform any Storage Checkpoint
or Database FlashSnap functions.
— Storage Checkpoint operations are currently not supported for databases cloned with
Database FlashSnap.
• Clone Database ORACLE_SID Character Limit
When cloning an Oracle instance using the dbed_clonedb or dbed_vmclonedb command,
the ORACLE_SID of the cloned database can be only eight characters or less. You will receive
an error (ERROR V-81-5713) if the ORACLE_SID is more than eight characters.
• Database FlashSnap Limitations
— The Database FlashSnap feature does not support RAID-5 volumes.
— When cloning a database using the Database FlashSnap feature, the Oracle database
must have at least one mandatory archive destination, otherwise dbed_vmchecksnap
results in this error message:
SFORA dbed_vmchecksnap ERROR V-81-5677 Could not find a mandatory,
primary and valid archive destination fordatabase PROD.
Please review the LOG_ARCHIVE_DEST_n parameters and check
v$archive_dest.
This example shows how to establish a mandatory archive destination using SQL*Plus:
alter system set log_archive_dest_1 =
'LOCATION=/ora_mnt/oracle/oradata/PROD/archivelogs
MANDATORY [REOPEN]' [scope=both];
For more information about Oracle parameters for archiving redo logs, refer to
appropriate 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
— Because Oracle Disk Manager uses the Quick I/O driver to perform asynchronous I/O,
do not turn off the Quick I/O mount option. 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 your system to panic. To avoid a system panic, ensure the following:
◦ If you are using Oracle Disk Manager, do not enable Cached Quick I/O on your
file system.
◦ If you are converting from Quick I/O to Oracle Disk Manager, make sure you
disable Cached Quick I/O.
System Requirement
This section discusses the supported Oracle and HP-UX versions, and mandatory patches.
Supported Oracle and HP-UX Combinations
Table 1-3 lists the supported Oracle and HP-UX combinations:
System Requirement 13