System Administrator’s Guide U42252-J-Z915-1-76
Recovery Troubleshooting
started. You are recommended to use the archive directory of the
”recovery instance“ for this purpose. You can determine which
directory this is by issuing the following command:
show parameter log_archive_dest
In this case you can use the autorecovery option; after you call
recover database ... ORACLE will then automatically process the
redolog files. If you use one or more other directories you will have
to specify the pathname for each redolog file interactively with
ORACLE.
Backups are much simpler if the archive directory has the same path
on all the instances. In this case NetWorker will copy the redolog files
to the correct location straightaway.
●If the database was backed up offline, then proceed as described in the
section “Manual Recovery”.
●A recovery until time (using ora_recut) can be carried out both for offline and
online backups and can only be run on the OPS node, which also starts
the database backup.
If you note when recovering the tablespaces that you also have to
recreate directories that are in the pathnames of the tablespaces, please
check the owner and group of these directories. NetWorker normally
creates new directories with the owner root, which will cause access
problems in the case of a database directory.
Please note that when the recovery has finished, the archiving monitor
(amon) will have to be restarted on each individual (!) node of the OPS
system.
5.3 Troubleshooting
No space left on device xxx
You may possibly receive this error message during a recovery. Apart from the
fact that there might really be insufficient space on the disk, there is also the
possibility that an sqldba-, svrmgrl-, sqlplus- or some other database process is
blocking the required disk space. In this case you only need to terminate the
database processes.
i
i