Oracle often uses file templates for recovery

Colleague: Something has happened. I have connected to the wrong server and uninstalled the database in the production environment. Can you restore it? Me: Do you still have the data files? Colleague: I don’t know, I unload according to the online documents, the registry is deleted, found the environment is wrong, hurriedly terminated. Me: Send it remotely.

The oracle installation directory has been deleted, and the service has been disabled. Fortunately, all the data files are still in the directory (data files, control files, redo files).

No available pfile file template was found during recovery, so I copied it from another environment and corrected it. In view of the similar situation often encountered during recovery, I now record the commonly used file template.

Pfile. ora file template

db_name='ORCL'
memory_target=1G
processes = 150
audit_file_dest='/app/oracle/admin/orcl/adump'
audit_trail ='db'
db_block_size=8192
db_domain=''
db_recovery_file_dest='/app/oracle/flash_recovery_area'
db_recovery_file_dest_size=2G
diagnostic_dest='/app/oracle'
dispatchers='(PROTOCOL=TCP) (SERVICE=ORCLXDB)'
open_cursors=300
remote_login_passwordfile='EXCLUSIVE'
undo_tablespace='UNDOTBS1'
control_files ='/data/oradata/orcl/control01.ctl','/app/oracle/fast_recovery_area/orcl/control02.ctl'
Copy the code

Rebuild the control file template

-- 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
-- STANDBY_ARCHIVE_DEST=?/dbs/arch
-- FAL_CLIENT=''
-- FAL_SERVER=''
--
-- LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
-- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
-- LOG_ARCHIVE_DEST_1='NOREGISTER 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 "ORCL" NORESETLOGS FORCE LOGGING NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 2920
LOGFILE
  GROUP 1 '/data/oradata/orcl/redo01.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 2 '/data/oradata/orcl/redo02.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 3 '/data/oradata/orcl/redo03.log'  SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '/data/oradata/orcl/system01.dbf',
  '/data/oradata/orcl/sysaux01.dbf',
  '/data/oradata/orcl/undotbs01.dbf',
  '/data/oradata/orcl/users01.dbf',
  '/data/oradata/orcl/syd01.dbf',
  '/data/oradata/orcl/o2o01.dbf ',
  '/data/oradata/orcl/syd01.dbf ',
  '/data/oradata/orcl/o2o01.dbf',
  '/data/oradata/orcl/o2o02.dbf',
  '/data/oradata/orcl/o2o03.dbf',
  '/data/oradata/orcl/o2o04.dbf',
  '/data/oradata/orcl/oa01.dbf'
CHARACTER SET AL32UTF8
;

-- Take files offline to match current control file.
ALTER DATABASE DATAFILE '/data/oradata/orcl/syd01.dbf ' OFFLINE DROP;
ALTER DATABASE DATAFILE '/data/oradata/orcl/o2o01.dbf' OFFLINE DROP;
ALTER DATABASE DATAFILE '/data/oradata/orcl/o2o02.dbf' OFFLINE DROP;

-- 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 '/app/oracle/fast_recovery_area/ORCL/archivelog/2021_08_20/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/app/oracle/fast_recovery_area/ORCL/archivelog/2021_08_20/o1_mf_1_1_%u_.arc';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE

-- 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 TEMP ADD TEMPFILE '/data/oradata/orcl/temp01.dbf'
     SIZE 1528M REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
ALTER TABLESPACE TEST_TEMP ADD TEMPFILE '/data/oradata/orcl/test_temp01.dbf'
     SIZE 104857600  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 32767M;
ALTER TABLESPACE OA_TEMP ADD TEMPFILE '/data/oradata/orcl/oa_temp01.dbf'
     SIZE 104857600  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 32767M;
-- 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 "ORCL" RESETLOGS FORCE LOGGING NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 2920
LOGFILE
  GROUP 1 '/data/oradata/orcl/redo01.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 2 '/data/oradata/orcl/redo02.log'  SIZE 50M BLOCKSIZE 512,
  GROUP 3 '/data/oradata/orcl/redo03.log'  SIZE 50M BLOCKSIZE 512
-- STANDBY LOGFILE
DATAFILE
  '/data/oradata/orcl/system01.dbf',
  '/data/oradata/orcl/sysaux01.dbf',
  '/data/oradata/orcl/undotbs01.dbf',
  '/data/oradata/orcl/users01.dbf',
  '/data/oradata/orcl/syd01.dbf',
  '/data/oradata/orcl/o2o01.dbf ',
  '/data/oradata/orcl/syd01.dbf ',
  '/data/oradata/orcl/o2o01.dbf',
  '/data/oradata/orcl/o2o02.dbf',
  '/data/oradata/orcl/o2o03.dbf',
  '/data/oradata/orcl/o2o04.dbf',
  '/data/oradata/orcl/oa01.dbf'
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 '/app/oracle/fast_recovery_area/ORCL/archivelog/2021_08_20/o1_mf_1_1_%u_.arc';
-- ALTER DATABASE REGISTER LOGFILE '/app/oracle/fast_recovery_area/ORCL/archivelog/2021_08_20/o1_mf_1_1_%u_.arc';
-- 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 TEMP ADD TEMPFILE '/data/oradata/orcl/temp01.dbf'
     SIZE 1528M REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
ALTER TABLESPACE TEST_TEMP ADD TEMPFILE '/data/oradata/orcl/test_temp01.dbf'
     SIZE 104857600  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 32767M;
ALTER TABLESPACE OA_TEMP ADD TEMPFILE '/data/oradata/orcl/oa_temp01.dbf'
     SIZE 104857600  REUSE AUTOEXTEND ON NEXT 8192  MAXSIZE 32767M;
-- End of tempfile additions.
--
Copy the code

Tnsnames. ora file template

# tnsnames.ora Network Configuration File: F:\app\oracle\home\network\admin\tnsnames.ora # Generated by Oracle Configuration Tools.10.67.78.33_orcl = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.67.78.33)(PORT = 9521)) (CONNECT_DATA = (SERVICE_NAME = Orcl)(UR=A)) 192.168.100.77_syd = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.100.77)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = Syd)(UR=A))) 10.67.78.63_ORCL = (DESCRIPTION = (ADDRESS = (HOST = 10.67.78.63)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orCL) ))Copy the code

listener.ora

Rebuild the listener.

Oracle often uses file templates for recovery

Pfile. ora file template

Rebuild the control file template

Tnsnames. ora file template

listener.ora

Related Posts

Using MySQL as an example, let’s talk about index creation principles and execution plan analysis.

Number theory – congruence and inverse elements

Springboot series (12): How to code to send email alerts, you must be able to! (last)