Oracle and IM fail to start after a disk image is restored on IM
The last several lines of the Alert_adva.log file will look like the following:
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Wed May 08 23:19:19 2013
alter database open
ORA-1113 signalled during: alter database open...
The log file is in:
SV5.0 and earlier: c:\oracle\admin\ADVA\bdump\alert_adva.log
SV5.1 and up: C:\oracle\diag\rdbms\adva\adva\trace\alert_adva.logSymptoms:
There is no way to recover and instance that has an ORA-1113 error if a "consistent" backup is not available. A consistent backup is one where all volumes that have Oracle instance files on them were backed up at the same time. If a consistent backup was made then ensure all the volumes were properly restored. If a consistent image backup is not available, then an IM Backup or hsBar backup should be used to restore the IM back to the time these backups were made. If neither of these are available, the the Oracle Instance must be recreated.
Warning: Prior to Windows XP, disk imaging software (like Ghost and Acronis) had to be run "off-line" to make disk image backups. These off-line backups were guaranteed to be consistent if all the drives containing Oracle files were done at the same time (without a reboot in between). As of XP, Windows provides a feature to allow the "snapshot" of a volume. With this feature came the ability to do "on-line" disk image backups.
The on-line disk image backups present potential catastrophic problems for backups made of IMs that have an Oracle Instance with files on multiple volumes. As an example, an IM having Oracle Instance files on C and E are copied on-line to backup image files with C being made first. In this scenario, the E volume is still being written to while the snapshot of the C volume is being used to create an image. After the C copy is done, the E backup will be created but with files containing higher SCN numbers than those stored in the C backup. If these image files are ever restored, the high SCN numbers on E based files can not be recovered by the redo files on C and the Oracle Instance will not start, failing to open with the ORA-1113 error.
Because it is vital that Oracle data files not be updated while disk images are being made, it is strongly recommend to not use disk imaging software while the PC is runnig from the drives being copied or imaged. A boot disk with the imaging software would be best for this purpose. The PC would be running from the boot disk and the oracle files could not possibley be updated. Again, it is critical to image all volumes that have Oracle data files on them. Failure to do so will lead to a failed IM after the backup is restored. As an added precaution, an IM with important customer data should also be backed up using the IM Backup/Restore tool. Backups from this tool can be used in the event that something unforseen happens with the disk imaging software.
If you have any doubts on the correct procedure for backup of your IM during a work procedure or to provide adequate backup in the event of a hardware failure, please contact your local or regional support group and ask for a review of your backup plan.