-- The following are current System-scope REDO Log Archival related -- parameters and can be included in the database initialization file. -- -- LOG_ARCHIVE_DEST='' -- LOG_ARCHIVE_DUPLEX_DEST='' -- -- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf -- -- DB_UNIQUE_NAME="orcl" -- -- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG' -- LOG_ARCHIVE_MAX_PROCESSES=4 -- STANDBY_FILE_MANAGEMENT=MANUAL -- FAL_CLIENT='' -- FAL_SERVER='' -- -- LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST' -- LOG_ARCHIVE_DEST_1='MANDATORY REOPEN=300 NODELAY' -- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM NOVERIFY SYNC' -- LOG_ARCHIVE_DEST_1='NOREGISTER' -- LOG_ARCHIVE_DEST_1='NOALTERNATE' -- LOG_ARCHIVE_DEST_1='NODEPENDENCY' -- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME' -- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)' -- LOG_ARCHIVE_DEST_STATE_1=ENABLE -- -- Below are two sets of SQL statements, each of which creates a new -- control file and uses it to open the database. The first set opens -- the database with the NORESETLOGS option and should be used only if -- the current versions of all online logs are available. The second -- set opens the database with the RESETLOGS option and should be used -- if online logs are unavailable. -- The appropriate set of statements can be copied from the trace into -- a script file, edited as necessary, and executed when there is a -- need to re-create the control file. -- -- Set #1. NORESETLOGS case -- -- The following commands will create a new control file and use it -- to open the database. -- Data used by Recovery Manager will be lost. -- Additional logs may be required for media recovery of offline -- Use this only if the current versions of all online logs are -- available. -- After mounting the created controlfile, the following SQL -- statement will place the database in the appropriate -- protection mode: -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS ARCHIVELOG MAXLOGFILES 192 MAXLOGMEMBERS 3 MAXDATAFILES 1024 MAXINSTANCES 32 MAXLOGHISTORY 292 LOGFILE GROUP 1 ( '+DATA/ORCL/ONLINELOG/group_1.278.1053451027', '+DATA/ORCL/ONLINELOG/group_1.276.1053451027' ) SIZE 200M BLOCKSIZE 512, GROUP 2 ( '+DATA/ORCL/ONLINELOG/group_2.277.1053451027', '+DATA/ORCL/ONLINELOG/group_2.275.1053451027' ) SIZE 200M BLOCKSIZE 512, GROUP 3 ( '+DATA/ORCL/ONLINELOG/group_3.268.1053451541', '+DATA/ORCL/ONLINELOG/group_3.266.1053451541' ) SIZE 200M BLOCKSIZE 512, GROUP 4 ( '+DATA/ORCL/ONLINELOG/group_4.287.1053451543', '+DATA/ORCL/ONLINELOG/group_4.286.1053451543' ) SIZE 200M BLOCKSIZE 512 -- STANDBY LOGFILE DATAFILE '+DATA/ORCL/DATAFILE/system.279.1053450871', '+DATA/ORCL/DATAFILE/sysaux.263.1053450915', '+DATA/ORCL/DATAFILE/undotbs1.264.1053450941', '+DATA/ORCL/DATAFILE/undotbs2.265.1053451371', '+DATA/ORCL/DATAFILE/users.285.1053450941' CHARACTER SET AL32UTF8 ; -- Commands to re-create incarnation table -- Below log names MUST be changed to existing filenames on -- disk. Any one log file from each branch can be used to -- re-create incarnation records. -- ALTER DATABASE REGISTER LOGFILE '+DATA'; -- Recovery is required if any of the datafiles are restored backups, -- or if the last shutdown was not normal or immediate. RECOVER DATABASE -- All logs need archiving and a log switch is needed. ALTER SYSTEM ARCHIVE LOG ALL; -- Database can now be opened normally. ALTER DATABASE OPEN; -- Files in read-only tablespaces are now named. ALTER DATABASE RENAME FILE 'MISSING00002' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. ALTER DATABASE RENAME FILE 'MISSING00008' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. ALTER DATABASE RENAME FILE 'MISSING00009' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. ALTER DATABASE RENAME FILE 'MISSING00010' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. -- Online the files in read-only tablespaces. -- No tempfile entries found to add. -- -- Set #2. RESETLOGS case -- -- The following commands will create a new control file and use it -- to open the database. -- Data used by Recovery Manager will be lost. -- The contents of online logs will be lost and all backups will -- be invalidated. Use this only if online logs are damaged. -- After mounting the created controlfile, the following SQL -- statement will place the database in the appropriate -- protection mode: -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG MAXLOGFILES 192 MAXLOGMEMBERS 3 MAXDATAFILES 1024 MAXINSTANCES 32 MAXLOGHISTORY 292 LOGFILE GROUP 1 ( '+DATA/ORCL/ONLINELOG/group_1.278.1053451027', '+DATA/ORCL/ONLINELOG/group_1.276.1053451027' ) SIZE 200M BLOCKSIZE 512, GROUP 2 ( '+DATA/ORCL/ONLINELOG/group_2.277.1053451027', '+DATA/ORCL/ONLINELOG/group_2.275.1053451027' ) SIZE 200M BLOCKSIZE 512 -- STANDBY LOGFILE DATAFILE '+DATA/ORCL/DATAFILE/system.279.1053450871', '+DATA/ORCL/DATAFILE/sysaux.263.1053450915', '+DATA/ORCL/DATAFILE/undotbs1.264.1053450941', '+DATA/ORCL/DATAFILE/undotbs2.265.1053451371', '+DATA/ORCL/DATAFILE/users.285.1053450941' CHARACTER SET AL32UTF8 ; -- Commands to re-create incarnation table -- Below log names MUST be changed to existing filenames on -- disk. Any one log file from each branch can be used to -- re-create incarnation records. -- ALTER DATABASE REGISTER LOGFILE '+DATA'; -- Recovery is required if any of the datafiles are restored backups, -- or if the last shutdown was not normal or immediate. RECOVER DATABASE USING BACKUP CONTROLFILE -- Create log files for threads other than thread one. ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 3 ( '+DATA/ORCL/ONLINELOG/group_3.268.1053451541', '+DATA/ORCL/ONLINELOG/group_3.266.1053451541' ) SIZE 200M BLOCKSIZE 512 REUSE, GROUP 4 ( '+DATA/ORCL/ONLINELOG/group_4.287.1053451543', '+DATA/ORCL/ONLINELOG/group_4.286.1053451543' ) SIZE 200M BLOCKSIZE 512 REUSE; -- Database can now be opened zeroing the online logs. ALTER DATABASE OPEN RESETLOGS; -- Files in read-only tablespaces are now named. ALTER DATABASE RENAME FILE 'MISSING00002' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. ALTER DATABASE RENAME FILE 'MISSING00008' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. ALTER DATABASE RENAME FILE 'MISSING00009' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. ALTER DATABASE RENAME FILE 'MISSING00010' -- WARNING! This command can not be completed because the file -- needs to be renamed to a real file name. -- Online the files in read-only tablespaces. -- No tempfile entries found to add. --