Checking the Status of Tablespaces
Use
You check the status of tablespaces when using BRRECOVER to perform Tablespace Point-In-Time Recovery. After you have selected the tablespaces to recover, this procedure identifies the corresponding database files.
Prerequisites
· BRRECOVER checks that all files are online. This is normally true if the database is open.
· BRRECOVER identifies which data files need to be recovered, based on the tablespaces that you selected earlier.
· BRRECOVER checks if the tablespaces that you selected and the other data tablespaces are separate self-contained groups. This means that it checks whether there are references such as indexes or constraints that point from members of a group to members outside this group. If so, you cannot continue with the recovery.
Procedure
...
1. Check the display and continue with the tablespace 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
BR0655I Control menu 106 - please decide how to proceed
------------------------------------------------------------------
Tablespace point-in-time recovery main menu
1 + Set point-in-time and tablespaces for recovery
2 + Select database backup
3 = Check the status of tablespaces
4 * Export tablespaces not being recovered
5 * Restore required data files
6 # Restore and apply incremental backup
7 * Restore and apply archivelog files
8 * Open database and plug in exported tablespaces
9 - Exit program
10 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
------------------------------------------------------------------
BR0662I Enter your choice:
BR0280I Time stamp 2003-01-31 18.36.35
BR0663I Your choice: 'c'
BR0259I Program execution will be continued...
BR0342I Database instance GC2 is open in RESTRICT mode
BR0118I Tablespaces and data files
Tablespace Status File Status Id. Size Creation time Creation scn Device Type Link
DRSYS ONLINE /oracle/GC2/sapdata1/drsys_1/drsys.data1 ONLINE 3 10493952 2002-07-31 16.55.55 5954 35651591 FILE NOLINK
EXAMPLE ONLINE /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-31 11.55.28 5217256 35651591 FILE NOLINK
/oracle/GC2/mirrlog/redo01m2.dbf INUSE 1 2097664 2003-01-31 11.55.28 5217256 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
.....
BR0668I Warnings or errors occured - you can continue to ignore them or go back to repeat the last action
BR0280I Time stamp 2003-01-31 18.36.35
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
BR0280I Time stamp 2003-01-31 18.36.36
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I Time stamp 2003-01-31 18.36.37
BR0739I Checking if following tablespaces are self-contained:
DRSYS,EXAMPLE,INDX,PSAPRAWD,PSAPRAWI,
PSAPTESTI,TOOLS,USERS,XDB
BR0285I This function can take several seconds/minutes - be patient
BR0280I Time stamp 2003-01-31 18.36.52
BR0739I Checking if following tablespaces are self-contained:
PSAPSTABD,PSAPSTABI,PSAPTESTD,PSAPTTTTD
BR0285I This function can take several seconds/minutes - be patient