-- 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="EPP" -- -- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG' -- LOG_ARCHIVE_MAX_PROCESSES=4 -- STANDBY_FILE_MANAGEMENT=MANUAL -- STANDBY_ARCHIVE_DEST=?/dbs/arch -- FAL_CLIENT='' -- FAL_SERVER='' -- -- LOG_ARCHIVE_DEST_1='LOCATION=/oracle/EPP/oraarch/EPParch' -- LOG_ARCHIVE_DEST_1='OPTIONAL REOPEN=300 NODELAY' -- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC' -- LOG_ARCHIVE_DEST_1='REGISTER NOALTERNATE 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 "EPP" NORESETLOGS ARCHIVELOG MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXDATAFILES 1000 MAXINSTANCES 50 MAXLOGHISTORY 1168 LOGFILE GROUP 1 ( '/oracle/EPP/origlogA/log_g11m1.dbf', '/oracle/EPP/mirrlogA/log_g11m2.dbf' ) SIZE 200M BLOCKSIZE 512, GROUP 2 ( '/oracle/EPP/origlogB/log_g12m1.dbf', '/oracle/EPP/mirrlogB/log_g12m2.dbf' ) SIZE 200M BLOCKSIZE 512, GROUP 3 ( '/oracle/EPP/origlogA/log_g13m1.dbf', '/oracle/EPP/mirrlogA/log_g13m2.dbf' ) SIZE 200M BLOCKSIZE 512, GROUP 4 ( '/oracle/EPP/origlogB/log_g14m1.dbf', '/oracle/EPP/mirrlogB/log_g14m2.dbf' ) SIZE 200M BLOCKSIZE 512 -- STANDBY LOGFILE DATAFILE '/oracle/EPP/sapdata1/system_1/system.data1', '/oracle/EPP/sapdata1/sysaux_1/sysaux.data1', '/oracle/EPP/sapdata2/undo_1/undo.data1', '/oracle/EPP/sapdata4/sr3db_1/sr3db.data1', '/oracle/EPP/sapdata4/sr3db_2/sr3db.data2', '/oracle/EPP/sapdata1/sysaux_2/sysaux.data2' CHARACTER SET UTF8 ; -- 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 '/oracle/EPP/oraarch/EPParch1_1_807889104.dbf'; -- 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; -- Commands to add tempfiles to temporary tablespaces. -- Online tempfiles have complete space information. -- Other tempfiles may require adjustment. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/EPP/sapdata2/temp_1/temp.data1' SIZE 1460M REUSE AUTOEXTEND ON NEXT 20971520 MAXSIZE 10000M; -- End of tempfile additions. -- -- 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 "EPP" RESETLOGS ARCHIVELOG MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXDATAFILES 1000 MAXINSTANCES 50 MAXLOGHISTORY 1168 LOGFILE GROUP 1 ( '/oracle/EPP/origlogA/log_g11m1.dbf', '/oracle/EPP/mirrlogA/log_g11m2.dbf' ) SIZE 200M BLOCKSIZE 512, GROUP 2 ( '/oracle/EPP/origlogB/log_g12m1.dbf', '/oracle/EPP/mirrlogB/log_g12m2.dbf' ) SIZE 200M BLOCKSIZE 512, GROUP 3 ( '/oracle/EPP/origlogA/log_g13m1.dbf', '/oracle/EPP/mirrlogA/log_g13m2.dbf' ) SIZE 200M BLOCKSIZE 512, GROUP 4 ( '/oracle/EPP/origlogB/log_g14m1.dbf', '/oracle/EPP/mirrlogB/log_g14m2.dbf' ) SIZE 200M BLOCKSIZE 512 -- STANDBY LOGFILE DATAFILE '/oracle/EPP/sapdata1/system_1/system.data1', '/oracle/EPP/sapdata1/sysaux_1/sysaux.data1', '/oracle/EPP/sapdata2/undo_1/undo.data1', '/oracle/EPP/sapdata4/sr3db_1/sr3db.data1', '/oracle/EPP/sapdata4/sr3db_2/sr3db.data2', '/oracle/EPP/sapdata1/sysaux_2/sysaux.data2' CHARACTER SET UTF8 ; -- 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 '/oracle/EPP/oraarch/EPParch1_1_807889104.dbf'; -- 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 -- Database can now be opened zeroing the online logs. ALTER DATABASE OPEN RESETLOGS; -- Commands to add tempfiles to temporary tablespaces. -- Online tempfiles have complete space information. -- Other tempfiles may require adjustment. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/EPP/sapdata2/temp_1/temp.data1' SIZE 1460M REUSE AUTOEXTEND ON NEXT 20971520 MAXSIZE 10000M; -- End of tempfile additions. --