Show TOC

Procedure documentationChecking the Status of Database Files - I Locate this document in the navigation structure

 

You check the database status when using BRRECOVER to perform Complete database recovery.

This procedure checks the database for critical errors that might prevent production operation.

Prerequisites

BRRECOVER remounts – that is, closes and again mounts – the database to refresh the views V$DATAFILE and V$RECOVER_FILE. It then checks the availability of the following files:

  • Control files

  • Redo log files

  • Data files

BRRECOVER checks whether there are any data files not online. If so, it recommends to set them online.

See Example below for the contents of the log file.

Procedure

  1. Check the display and continue with the database recovery.

    Note Note

    If there are no files that need to be recovered, BRRECOVER stops the recovery automatically.

    End of the note.

  2. Check the results in the BRRECOVER detail log, v<encoded timestamp>.<ext>.

    For more information on how to view the logs, see Showing Logs with BR*Tools.

Example

This example shows the contents of the BRRECOVER detail log file for the recovery phase “Check Status of Database Files”.

BR0614I Database instance GC2 is mounted

BR0750I Database instance GC2 will be remounted now

BR0280I Time stamp 2003-01-29 19.12.25

BR0307I Shutting down database instance GC2 ...

BR0280I Time stamp 2003-01-29 19.12.31

BR0308I Shutdown of database instance GC2 successful

BR0280I Time stamp 2003-01-29 19.12.31

BR0330I Starting and mounting database instance GC2 ...

BR0280I Time stamp 2003-01-29 19.12.41

BR0331I Start and mount of database instance GC2 successful

BR0118I Tablespaces and data files

Tablespace Status File Status Id. Size Creation time Creation scn Device Type Link

DRSYS UNKNOWN /oracle/GC2/sapdata1/drsys_1/drsys.data1 ONLINE 3 10493952 2002-07-31 16.55.55 5954 35651591 FILE NOLINK

EXAMPLE UNKNOWN /oracle/GC2/sapdata2/example_1/example.data1 ONLINE 4 126492672 2002-07-31 16.55.57 5973 35651591 FILE NOLINK

.....

BR0119I Redo log files

File Status Group Size First time First scn Device Type Link

/oracle/GC2/origlog/redo01m1.dbf INUSE 1 2097664 2003-01-29 19.04.28 5101811 35651591 FILE NOLINK

/oracle/GC2/mirrlog/redo01m2.dbf INUSE 1 2097664 2003-01-29 19.04.28 5101811 35651591 FILE NOLINK

.....

BR0120I Control files

File Size Reset time Reset scn Device Type Link

/oracle/GC2/sapdata1/cntrl/control01.ctl 4579328 2003-01-28 21.11.19 5040603 35651591 FILE NOLINK

/oracle/GC2/sapdata2/cntrl/control02.ctl 4579328 2003-01-28 21.11.19 5040603 35651591 FILE NOLINK

/oracle/GC2/sapdata3/cntrl/control03.ctl 4579328 2003-01-28 21.11.19 5040603 35651591 FILE NOLINK

BR0755I Checking the status of database files for instance GC2...

BR0758I Data file /oracle/GC2/sapdata5/stabd_1/stabd.data1 not found - it will be restored/recreated and recovered

BR0758I Data file /oracle/GC2/sapdata6/stabi_1/stabi.data1 not found - it will be restored/recreated and recovered

BR0760I Data file /oracle/GC2/sapdata6/testd_1/testd.data1 not current - it will be recovered

BR0760I Data file /oracle/GC2/sapdata6/testd_2/testd.data2 not current - it will be recovered

BR0760I Data file /oracle/GC2/sapdata5/testi_1/testi.data1 not current - it will be recovered