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

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.
Workaround
Fix the issue that caused the failover to the other node, and then fail back to the fixed node.
• Problem
The file fragmentation check in qio_convertdbfiles may report errors when run on
multi-volume file systems. This issue also causes the dbed_checkconfig command to fail
with an error if run on a database which uses one or more multi-volume file systems.
Workaround
These errors are harmless and may be safely ignored. The method used to determine
fragmentation in qio_convertdbfiles has been deprecated. The preferred way to check
and resolve file or file system fragmentation is by using the fsadm tool. For more information
on using the fsadm tool, see the Veritas File System Administrator's Guide.
• Problem
If HP Storage Management for Oracle and Veritas Storage Foundation Cluster File System
are installed on the same machine, do not use the installer to remove only one of the two
products.
Workaround
You must uninstall the HP Storage Foundation for Oracle packages manually if you want
to uninstall the product.
If HP Storage Management for Oracle and Veritas Storage Foundation Cluster File System
are installed on the same machine and you are upgrading both products, use the installer
to upgrade Veritas Storage Foundation Cluster File System first. Then, use the installer to
upgrade HP Storage Management for Oracle. If the second upgrade fails, remove the HP
Storage Foundation for Oracle packages, then run the installer to upgrade HP Storage
Management for Oracle.
• Problem
If you are running the dbed_vmclonedb -p or the dbed_clonedb -p command, the
pfile modification will fail if there is an unquoted or unescaped special character in the
pfile of the primary instance. The following error is displayed:
SFORA pfile_mod ERROR V-81-5781 Parse error in file
/oracle/dbs/(pfile_name). line 6: .
SFORA dbed_vmclonedb WARNING V-81-5788 Pfile modification
failed. Clone instance (CLONE SID) may not start.
Workaround
To avoid this issue, make sure all special characters in the pfile of the primary instance
are either placed within quotes or escaped.
Known Problems And Workarounds 17