HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

Option:2 Using ascii control file
Modify the backed up ascii control file, and the format is as follows:
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "EXT2TEST" NORESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/EXT2TEST/redo/EXT2TEST/redo01.log' SIZE 50M BLOCKSIZE
512,
GROUP 2 '/EXT2TEST/redo/EXT2TEST/redo02.log' SIZE 50M BLOCKSIZE
512,
GROUP 3 '/EXT2TEST/redo/EXT2TEST/redo03.log' SIZE 50M BLOCKSIZE 512
DATAFILE
'/EXT2TEST/data/EXT2TEST/system01.dbf',
'/EXT2TEST/data/EXT2TEST/sysaux01.dbf',
'/EXT2TEST/data/EXT2TEST/undotbs01.dbf',
'/EXT2TEST/data/EXT2TEST/users01.dbf'
CHARACTER SET WE8MSWIN1252
;
Run the commands similar to the above to start a database in no mount stage, and create the
database control files.
After the control files are in place, you need to recover the database, using command similar to
the following:
• SQL> recover automatic database using backup controlfile until cancel;
Then reset logs for the database:
• SQL> alter database open resetlogs;
The primary database must be open after the above procedure.
NOTE: The above example is a sample recovery procedure. For different failure scenarios and
how to recover the Oracle database, refer to Oracle documentation.
122 Using the Recovery Manager Rollback Utility