HP Storage Management for Oracle 5.0 Release Notes HP-UX 11i v3 HP Part Number: 5992-1953 Published: May 2008 Edition: 1.
© Copyright 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................5 Intended Audience.................................................................................................................................5 Document Organization.........................................................................................................................5 Typographic Conventions.....................................................
List of Tables 1-1 1-2 1-3 4 Enhanced SMO Commands.........................................................................................................10 Storage Management for Oracle Bundle.......................................................................................10 Features enabled by the SMO licenses..........................................................................................
About This Document This document discusses the most recent product information pertaining to HP Storage Management for Oracle (SMO) 5.0, which is supported on systems running HP-UX 11i v3. It also discusses product licenses, limitations, system requirements, compatibility with previous product versions, and known problems with SMO 5.0. Intended Audience This document is intended for system administrators who install and configure UNIX® systems with the Veritas suite of products.
This website contains the following documents: • • • • • • • • • • • • • • Veritas 5.0 Installation Guide Veritas File System 5.0 Release Notes Veritas File System 5.0 Administrator’s Guide Veritas Volume Manager 5.0 Release Notes Veritas Volume Manager 5.0 Administrator’s Guide Veritas Volume Manager 5.0 Troubleshooting Guide Veritas Volume Manager 5.0 Migration Guide Veritas Enterprise Administrator User's Guide Veritas Storage Foundation 5.
Include the document title, manufacturing part number and any comment, error found, or suggestions for improvement you have concerning this document. Also, include information on what we did right, so that we can incorporate it into other documents.
1 HP Storage Management for Oracle (SMO) 5.0 Release Notes This chapter discusses new features, licenses, system requirements, compatibility with previous releases, and known problems with HP Storage Management for Oracle 5.0 which is supported on systems running HP-UX 11i v3.
• Enhanced Command-Line Interface (CLI) commands Table 1–1 lists the enhanced HP Storage Management for Oracle CLI commands. Table 1-1 Enhanced SMO Commands • Command Description dbed_clonedb To specify the modified initialization parameters (contained in pfile_modification_file) for the clone. dbed_vmclonedb To specify the modified initialization parameters (contained in pfile_modification_file) for the clone.
Table 1-3 Features enabled by the SMO licenses. (continued) Feature SMO Standard T2789CB SMO Enterprise — T2790CB File Change Log Yes • Logs file system activity for fast incremental backup and auditing Yes Yes Yes DMAPI - a VxFS interface that enables Hierarchical Yes Storage Management (HSM). Also known as XDSM.
Table 1-3 Features enabled by the SMO licenses. (continued) 12 Feature SMO Standard T2789CB SMO Enterprise — T2790CB Oracle SmartSync Support which improves Oracle runtime and recovery performance with mirrored volumes and enables raw volume configuration.
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.
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 software "VRTSdbms3.VXDBMS,l=/opt,r=3.0.244.0" is not in the correct state (AVAILABLE, INSTALLED, or CONFIGURED). You will need to recopy, reinstall or configure this software before operating on software that depends on it. The corequisite "VRTSdbms3.VXDBMS,l=/opt,r=3.0.244.0" for fileset "VRTSdbed.DBED,l=/,r=5.0.31.0" cannot be successfully resolved. ERROR: The dependencies for fileset "VRTSdbed.DBED,l=/,r=5.0.31.0" cannot be resolved (see previous lines). * The software "VRTSdbms3.
• Problem When an SFCFS file system is not mounted, it is possible that the fsck operation of the snapshot will take longer than the usual time to complete, depending on the I/O activity at the time of the snapshot. Workaround When taking a snapshot of an SFCFS file system, ensure that at least one of the volumes defined in the command line is mounted on the cluster master. • Problem Mount operation can cause inconsistencies in snapshots.
ORA-00600: internal error code, arguments: [2662]... Workaround Do not use the pre-existing tempfile. Instead either take a backup of the tempfile with the rest of the database or remove the tempfile and recreate it once the database is open. • Problem In an HA environment, after successfully taking a snapshot and cloning the database on the same host where the primary node is running, if a node failover occurs then the dbed_vmclonedb -o umount command does not work.
NOTE: The pfile of the primary instance is saved at the time of snapshot creation. If you attempt to clone the database using that snapshot you will be using the saved pfile and not the current file. Therefore, you must create a new snapshot so that the clone will use an updated pfile. For more information on special characters that must be either placed within quotes or escaped when using a pfile, see the Oracle Reference Manual.
• Problem Database editions utilities randomly fail to execute even if the required database files reside on VxFS. The following error will be displayed: ERROR V-81-3012 One or more files reside on non-VxFS file systems or devices. Workaround Restart the vxdbd daemon using following commands: /opt/VRTS/bin/vxdbdctrl stop /opt/VRTS/bin/vxdbdctrl start Verify that no other Database editions utility is running while restarting the vxdbd daemon.
/home/mytestdb, an error message is displayed because the repository already has a snaplan with the name A. Workaround Remove one of the snapplans or use different names for the snapplans. • Problem The checkpoint object in the HP Storage Management for Oracle GUI (SMO GUI) does not display the correct size (in blocks) of the checkpoint. This size is not updated even after rescanning the checkpoints in the GUI.
• Problem Creating an online checkpoint for a database that has only the DB_RECOVERY_FILE_DEST set as an archive log destination causes a warning message to be printed from the checkpoint creation command. The message states that a clone cannot be created from this checkpoint. If the dbed_clonedb command is run subsequently using this checkpoint, database recovery fails with an Oracle error.
SFORA dbed_vmsnap ERROR V-81-6518 Could not find snapplan'snap_plan' in repository. /opt/VRTSdbed/bin/dbed_vmsnap[21]: test: argument expected. Workaround Ensure that the name of the snapplan is that of one that exists and re-run the dbed_vmsnap command. • Problem Changing the communication port number in /etc/vx/vxdbed/admin.properties requires resetting the file permission. Workaround If you change the communication port number in /etc/vx/vxdbed/admin.
• Problem You can click the Quota tab for the Storage Checkpoint available from the GUI. However, if the file system and the Storage Checkpoint are on a version earlier than Disk Layout Version 6, the unknown error code 4646 is displayed. Workaround To display Storage Checkpoints Quotas from the GUI for Disk Layout Version 5 and later, complete the following steps: 1. 2. 3. • Using Veritas File System 3.5, create a file system. Upgrade to Veritas File System 5.0.
*5992-1953* Printed in the US
