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

• 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.
• Problem
Performing the reverse_resync_abort operation may display an error message similar
to the following:
VXDBA_PRODUCT vxckptadm ERROR V-81-7100 /usr/sbin/mount -F vxfs
-o ckpt=SNAP_1193314118,ro
/dev/vx/dsk/flashdg48/datavol:SNAP_1193314118 /tmp/dbed_BA
A001066/snap_data9r2
VXDBA_PRODUCT vxckptadm ERROR V-81-7100 UX:vxfs mount: ERROR:
V-3-24706: /dev/vx/dsk/flashdg48/datavol:SNAP_1193314118 no such
device or filesystem on it missing one or more devices
VXDBA_PRODUCT vxckptadm ERROR V-81-4576 Could not mount Storage
Checkpoint SNAP_1193314118 on /snap_data9r2.
VXDBA_PRODUCT vxckptadm ERROR V-81-4569 Could not mount Storage
Checkpoint SNAP_1193314118.
VXDBA_PRODUCT vxckptadm ERROR V-81-4562 Storage Rollback failed.
SFORA dbed_vmsnap ERROR V-81-3016 Could not roll back the entire
database.
Despite this message, the reverse_resync_abort operation is complete and you must
complete the resynchronization after this operation.
Workaround
To avoid this error, restart the vxdbd daemon after the reverse_resync_begin operation
using the following commands:
/opt/VRTS/bin/vxdbdctrl stop
/opt/VRTS/bin/vxdbdctrl start
• Problem
If dbed_vmchecksnap is run with the -h option, and /oracle/ora9i/ is set as the home
instead of /oracle/ora9i (without the forward slash), an error message is displayed.
Workaround
Ensure that / is not added at the end.
• Problem
A snapplan is in a state where dbed_vmchecksnap -o remove does not remove the
snapplan entry from the repository.
Workaround
You can remove the snapplan by forcing a snapshot and then resyncing. Later, use the
dbed_vmchecksnap -o command to remove the snapplan entry from the repository.
• Problem
If two snapplans are created with the same name but with different paths, an error message
is displayed indicating that the snapplan already exists. For example, if a snapplan by name
‘A’ is created on /home/proddb directory, and if you try to create another snaplan 'A' in
Known Problems And Workarounds 19