3com database adapter module for networker nsr-ora v3.2 User Manual

System Administrator’s Guide

U42252-J-Z915-1-76

Recovery

Please look for a solution or give up!!
Sqldba>

or

ERROR: couldn’t get log_file <....dbf>
Please try to find it yourself
$

You can enter optional commands after the prompts Sqldba> and $ in order 
to recover errors (e.g. to stop a database, rename a file, etc.). When you 
have finished, just enter %? to return to ora_recut. You can then decide 
whether you want to continue the recovery using ora_recut or whether you 
want to abort it.

   If the recovery is meanwhile aborted, it is not possible to restart it from 

that point any more. The database has to be restored first before a 
new recovery attempt with ora_recut can be made.

After the recovery is completed ora_recut opens the database using the 
following command:

database reset logfiles

  The database should be backed up as soon as possible after a 

successful recovery.

In the event of a physical fault in your database you can carry out a fully-auto-
matic recovery. You can carry out a fully-automatic recovery with the assistance 
of the nsrora_rec command.

nsrora_rec [<ORA-SID>]

Under normal circumstances, this file does not require any options. If only one 
Oracle database is configured, the recovery is also performed immediately. If 
several databases are configured on this machine, the user is asked to choose 
a database using the ORACLE_SID. This can also be specified in the call.

# nsrora_rec 

INFO: *** Invoking Crash Analyzer ***
INFO: Trying to shutdown database within 30 seconds ... done 
(0).
INFO: Getting required database files ... done.
INFO: Generating miscellenous informations ... done.