Removing dbed_vmsnap or dbed_vmclonedb Changes (if a failure occurs) Using dbed_vmsnapundo
If the dbed_vmsnap or dbed_vmclonedb command fails during an operation, you can use dbed_vmsnapundo to restore the system to the SNAPREADY state.
If dbed_vmsnap failed, dbed_vmsnapundo imports the disk group and tries to snapback the data volumes. If dbed_vmclonedb failed, dbed_vmsnapundo will deport the disk group again.
Prerequisites
- The dbed_vmsnapundo command must be run as the Oracle database administrator.
Usage Notes
- You can only run the dbed_vmsnapundo command if there is an error using dbed_vmsnap or dbed_vmclonedb.
- You must use the dbed_vmsnapundo command from the same host as the failed dbed_vmsnap or dbed_vmclonedb command.
- This command does not interact with the user.
- By default, dbed_vmsnapundo uses the last snaplog on the system. The snaplog provides essential information, such as the snapplan.
- If a dbed_vmclonedb failure occurs before the VxDBA repository is mounted, dbed_vmsnapundo will not work. The repository must be mounted so dbed_vmsnapundo can find the snapplan.
- This command may not be able to undo all failures. If you are unable to recover the data volumes, contact the system administrator for help.
- The snaplog file stored in the /etc/vx/vxdba/ORACLE_SID/snapplan/log directory may help the system administrator troubleshoot the problem.
- See the dbed_vmsnapundo(1M) manual page for more information.
Options
-S
|
Specifies the ORACLE_SID, which is the name of the Oracle database, for which a snapshot image will be created.
|
-f snapplan
|
Indicates the name of the snapplan that you are creating.
|
-l snaplog
|
Specifies the snaplog file name.
|
-o new_sid
|
Indicates the ORACLE_SID used for the snapshot image. Use this option if the dbed_vmclonedb command failed.
|
To remove changes caused by a dbed_vmsnap failure
Use the dbed_vmsnapundo command as follows:
# dbed_vmsnapundo -S ORACLE_SID
If dbed_vmsnapundo is able to remove the changes, you will see the following output:
snaplog file is
/etc/vx/vxdba/PROD/snapplan/log/snapplan1.log.20020404135145.
snapback is done
If dbed_vmsnapundo is unable to remove the changes, you will see the following output:
snaplog file is
/etc/vx/vxdba/PROD/snapplan/log/snapplan1.log.20020403150537.
Nothing to undo.
Please run dbed_vmsnap -o resync again.
To remove changes caused by a dbed_vmclonedb failure
Use the dbed_vmsnapundo command as follows:
# dbed_vmsnapundo -o new_sid=new_sid
|
