Opening the Database
Use
You use this procedure when using BRRECOVER to perform:
· Database point-in-time (PIT) recovery
· Tablespace point-in-time (PIT) recovery
· Restore and application of offline redo log files
This procedure opens the database.
For tablespace PIT recovery, it also plugs in the exported tablespaces.
Prerequisites
· BRRECOVER:
¡ Checks tablespaces and, if offline, recommends you to switch them online
¡ Checks data files and warns you if they are not online
· BRRECOVER deletes files that were added after the selected backup (for whole database reset) or the PIT (for database or tablespace PIT). It identified these during the database status check or selection of database backups. This does not apply to complete database recovery.
· The resetlogs parameter to open the database is relevant for the following types of recovery:
¡ Database PIT
¡ Tablespace PIT
¡ Whole database reset if the selected backup was online
¡ Restore and application of offline redo log files
Resetlogs reformats the online redo log files and resets their sequence number to 1. In addition, it updates the control files to reflect a new incarnation of the database.
· For tablespace PIT recovery, BRRECOVER reinstates the tablespaces that were exported because they were not required for the recovery. To do this, BRRECOVER does the following after it has reopened the database:
¡ It temporarily drops the affected tablespaces.
¡ It calls the Oracle IMP tool to import the affected tablespaces (to be precise, it imports the metadata of these tablespaces).
¡ It sets the affected tablespaces to READ-WRITE status.
Procedure
...
1. Select the required option for Reset logs option (reset_logs).
Unless you are an expert, we recommend you to accept the setting that BRRECOVER proposes.
If the resetlogs option is set, BRRECOVER warns you that no more logs can be applied after the database has been opened. Normally you can ignore this warning.
2. Choose Yes to continue opening the database.
BRRECOVER opens the database.
For a PIT recovery or a whole database reset from an online consistent backup, BRRECOVER recreates the missing temporary database files.
BRRECOVER then checks the tablespaces and data files, the redo log files, and the control files.
For a PIT recovery and whole database reset, BRRECOVER deletes files that are no longer used by the database.
For a tablespace PIT recovery, BRRECOVER reinstates the tables that were exported as described at the end of “Prerequisites” above.
If successful, BRRECOVER displays a message like the following, depending on the type of recovery:
Database point-in-time recovery completed.
3. 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, using a database PIT recovery.
BR0614I Database instance GC2 is mounted
BR0064I Database instance GC2 will be shut down now
BR0280I Time stamp 2003-01-29 19.44.28
BR0307I Shutting down database instance GC2 ...
BR0280I Time stamp 2003-01-29 19.44.35
BR0308I Shutdown of database instance GC2 successful
BR0280I Time stamp 2003-01-29 19.44.35
BR0657I Input menu 135 # please check/enter input values
-------------------------------------------------------------------
Options for opening database instance GC2
1 ~ Reset logs option (reset_logs) . [resetlogs]
2 * Open database command (command). [alter database open resetlogs]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------
BR0280I Time stamp 2003-01-29 19.44.35
BR0134I Unattended mode with 'force' active - continuing processing with default reply 'cont'
BR0786I Database instance GC2 will be opened now with option 'resetlogs'
BR0787I No more archivelog files can be applied after database has been opened
BR0675I Do you want to perform this action?
BR0126I Unattended mode active - continuing processing with default reply 'yes'
BR0280I Time stamp 2003-01-29 19.44.35
BR0304I Starting and opening database instance GC2 ...
BR0280I Time stamp 2003-01-29 19.44.55
BR0305I Start and open of database instance GC2 successful
BR0280I Time stamp 2003-01-29 19.44.57
BR0789I Temporary database file /oracle/GC2/sapdata3/temp_1/temp.data1 was recreated
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 0000-00-00 00.00.00 0 35651591 FILE NOLINK
/oracle/GC2/mirrlog/redo01m2.dbf INUSE 1 2097664 0000-00-00 00.00.00 0 35651591 FILE NOLINK
.....
BR0120I Control files
File Size Reset time Reset scn Device Type Link
/oracle/GC2/sapdata1/cntrl/control01.ctl 4579328 2003-01-29 19.44.45 5101776 35651591 FILE NOLINK
/oracle/GC2/sapdata2/cntrl/control02.ctl 4579328 2003-01-29 19.44.45 5101776 35651591 FILE NOLINK
/oracle/GC2/sapdata3/cntrl/control03.ctl 4579328 2003-01-29 19.44.45 5101776 35651591 FILE NOLINK
BR0716I Database point-in-time recovery completed