HP Storage Management for Oracle 5.0.1 Release Notes

reverse_resync_begin
dbed_vmsnap started at 2007-12-28 12:02:42
SFORA dbed_vmsnap WARNING V-81-5725 After reverse_resync_commit
is performed, you need to recreate the Authentication Password
File using the ORAPWD utility.
SFORA dbed_vmsnap ERROR V-81-4882 An error occurred while
reconfiguring Oracle instance 'sfora'.
SFORA dbed_vmsnap ERROR V-81-4881 Log file is at
/tmp/dbed_vmclonedb.12313/nomount.log.
SFORA dbed_vmsnap ERROR V-81-4918 Database sfora has not been
correctly recovered.
SFORA dbed_vmsnap ERROR V-81-4881 Log file is at
/tmp/dbed_vmclonedb.12313/recover.log.
Workaround
The reverse_resync operation for a database created with OMF is not supported in the
5.0.1 release.
There is no workaround for this issue.
• Problem
If a clone database operation is performed for an offline checkpoint, the dbed_clonedb
command executes successfully and the database is cloned properly. However, the alert log
for the clone database displays the following errors:
Errors in file /oracle/11g/diag/rdbms/cl6/cl6/trace/cl6_ora_21133.trc:
ORA-00367: checksum error in log file header
ORA-00318: log 1 of thread 1, expected file size 1024 doesn't match 1024
ORA-00312: online log 1 thread 1: '/tmp/cl6/datavol/FLAS11r1/redo01.log'
Workaround
These errors are harmless and can be ignored.
• Problem
While creating a checkpoint clone, the following error message may be displayed:
Error V-40-49408-1
An unexpected error occurred
Even though this error message is displayed, the clone operation completes in the
background. A rescan in the GUI displays the appropriate objects.
Workaround
In the SOFTWARE\VERITAS\VRTSobc\pal33\Agents\__defaults section in the /etc/
vx/isis/Registry file, add the following key:
[REG_INT] "USE_RT_TIMEOUT" = 0;
• The dbed_clonedb -o restartdb command fails after the database group switches
to a second node with spfile.
In Storage Foundation for Oracle High Availability, you can run the restartdb command
for a checkpoint clone database only on the node on which you have created the clone.
• Problem
Checkpoint rollback corrupts Oracle database when upgrading from Oracle 9i to Oracle 10g
If an Oracle 9i database is upgraded to Oracle 10g, and at a later point in time the database
is rolled back to the Oracle 9i environment, then the recovery procedure for 9i logs following
error in the alert log file:
ORA-00600: internal error code, arguments: [2662]..."
This bug has been documented by Oracle as bug number 2216823.
Workaround
Known Problems And Workarounds 13