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

Limitations of Veritas Storage Management for Oracle
Following are the limitations of HP Storage Management for Oracle 5.0:
• DBDST Limitations With Non-English Filenames and Placement Class Names
DBDST does not work with non-English database filenames or non-English placement class
names, because of limitations in the VxFS Dynamic Storage Tiering and VxVM volume tags.
VxFS Dynamic Storage Tiering does not support placement of non-English filenames, and
VxVM volume tag feature does not support non-English volume tag names.
• Spaces in Container Path Names are not Supported
This release does not support spaces in the container path names.
• Checkpoint Policies Cannot be Started From the GUI.
• Internet Explorer Security Setting Required for Web GUI
The security setting in the Internet Explorer browser must be set to Medium or Lower for
the VEA Web GUI run to properly.
• Storage Checkpoint Limitations
— You cannot create a clone database using a mounted Storage Checkpoint.
— You must enter the dbed_update command after upgrading to Veritas Storage
Management 5.0 for Oracle from a previous release. This enables 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 enter the
dbed_update command before you 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
While cloning an Oracle instance using the dbed_clonedb or dbed_vmclonedb command,
the ORACLE_SID of the cloned database cannot contain more than eight characters. If the
ORACLE_SID is more than eight characters, the error (ERROR V-81-5713) is displayed.
• Database FlashSnap Limitations
— The Database FlashSnap feature does not support RAID-5 volumes.
— To clone a database using the Database FlashSnap feature, the Oracle database must
have at least one mandatory archive destination. Otherwise, the dbed_vmchecksnap
command displays the following 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.
The following example illustrates 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];
Limitations of Veritas Storage Management for Oracle 13