HP Storage Management for Oracle 5.0.1 Release Notes, HP-UX 11i v3, First Edition, November 2009

• Java GUI interface for all Storage Foundation for Oracle features
• Mapping-related functions, such as ORAMAP, vxstorage_stats, and dbed_analyzer,
for all versions of Oracle
Limitations of HP Storage Management for Oracle
Following are the limitations of HP Storage Management for Oracle 5.0.1:
• The qiomkfile and odmmkfile commands must be run as a privileged user
The qiomkfile and odmmkfile commands must be run as a privileged user. This behavior
has changed from the previous releases where these commands could be run by any user.
• Differing locales produce unintelligible characters in the GUI
The GUI does not support Oracle users having a locale different than the superuser's locale.
The GUI displays unintelligible characters if the Storage Foundation for Database (SFDB)
repository server starts with a locale that is different from the Oracle user locale (client).
• Certain features stop working after a Global Cluster failover
Certain Storage Foundation for Oracle features do not work correctly after a Global Cluster
(GCO) Failover. In 5.0.1, the SFDB repository and tools do not manage virtual hostnames
correctly in a Global Cluster environment. The SFDB repository does not correctly adjust to
the secondary host after the failover.
Features such as Storage Checkpoint, Database FlashSnap, the scheduler, and Database
Dynamic Storage Tiering (DBDST) do not run normally after a failover. However, features
such as Oracle Disk Manager (ODM), Quick I/O, and Concurrent I/O (CIO) continue to work
after a failover. This issue will be fixed in a future release.
• Avoid using UNIX VEA through PC-based UNIX emulators
You must use the Windows VEA client instead of running the UNIX VEA client through
emulators because problems could arise while displaying deep mapping topology in PC-based
UNIX emulators, such as Exceed.
• Disk layouts Version 5 and earlier do not display Storage Checkpoint quotas in the GUI
If you click the Quota tab for the Storage Checkpoint available through the GUI, you will
notice an error if the file system and the Storage Checkpoint are on a version prior to the
Disk Layout Version 6.
To display Storage Checkpoints Quotas using the GUI (for Disk Layout Version 5 and earlier),
complete the following steps:
1. Create a file system using Veritas File System 3.5.
2. Upgrade to Veritas File System 5.0.1 but do not upgrade the file system.
3. Create a checkpoint and then click the Quota tab accessible in the GUI.
• Veritas Enterprise Administrator Limitations
The following are Veritas Enterprise Administrator (VEA) limitations:
— VEA does not display tablespace information when the v$table column names are
changed using the SQL*Plus profile facility. Usually, VEA displays the tablespace
information when the SQL*Plus profile settings are used in login.sql to change
column names in reports.
— VEA may display certain system fonts incorrectly. Japanese characters may not be
properly displayed when you select the non-default font for the VEA GUI.
10 HP Storage Management for Oracle (SMO) 5.0.1 Release Notes