Checking the Status of Database Files – II

Use

You check the database status when using BRRECOVER to perform one of the following:

·        Database Point-In-Time Recovery with BR*Tools

·        Whole Database Reset with BR*Tools

This procedure checks the availability and status of database files to determine how to handle them during restore and recovery.

Prerequisites

·        BRRECOVER checks whether the control files are available.

If the control files are available, BRRECOVER remounts – that is, closes and again mounts – the database to refresh the views V$DATAFILE and V$RECOVER_FILE.

·        BRRECOVER checks the following files to identify which ones need to be overwritten:

Ў        Control files

Ў        Redo log files

Ў        Data files

·        BRRECOVER identifies files that need to be later deleted. It identifies files that were added after the:

Ў        Selected backup – for whole database reset

Ў        PIT – for database or tablespace PIT

For example, a tablespace might have been extended after the selected backup or PIT. Such files need to be later deleted.

BRRECOVER writes the results of the status check to the BRRECOVER detail log file. See “Example” below for the contents of the log file.

Procedure

...

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

       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 this procedure.

BR0614I Database instance GC2 is mounted

BR0750I Database instance GC2 will be remounted now

 

BR0280I Time stamp 2003-01-29 19.35.51

BR0307I Shutting down database instance GC2 ...

 

BR0280I Time stamp 2003-01-29 19.35.57

BR0308I Shutdown of database instance GC2 successful

 

BR0370I Directory /oracle/GC2/sapbackup/vdjwhnnh created

 

BR0202I Saving /oracle/GC2/sapdata1/cntrl/control01.ctl

BR0203I to /oracle/GC2/sapbackup/vdjwhnnh/control01.ctl ...

 

BR0280I Time stamp 2003-01-29 19.35.58

BR0330I Starting and mounting database instance GC2 ...

 

BR0280I Time stamp 2003-01-29 19.36.08

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           RECOVER     3     10493952  2002-07-31 16.55.55             5954     35651591  FILE  NOLINK

EXAMPLE        UNKNOWN    /oracle/GC2/sapdata2/example_1/example.data1       RECOVER     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...

 

BR0428W File /oracle/GC2/sapdata1/drsys_1/drsys.data1 will be overwritten

BR0428W File /oracle/GC2/sapdata2/example_1/example.data1 will be overwritten

BR0428W File /oracle/GC2/sapdata4/indx_1/indx.data1 will be overwritten

.....

 

BR0280I Time stamp 2003-01-29 19.36.09

BR0668I Warnings or errors occurred - you can continue to ignore them or go back to repeat the last action