Get the App
SLTechnology News&Howtos  ›  Database  › 

Oracle backup controlfile and find the backup file directory

Shulou Source: shulou.com Published: 2022-06-01 13:27:37 10月03日 Update

Last login: Fri Jul 11 15:25:49 2014 from chenjh

[oracle@dbachenjh ~] $sqlplus / nolog

SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 11 16:45:46 2014

Copyright (c) 1982, 2011, Oracle. All rights reserved.

SQL > conn / as sysdba

Connected.

SQL > alter database backup controlfile to trace;- backup control files to trace

Database altered.

SQL > show parameter dump;- finds the directory of the trace file

NAME TYPE VALUE

-

Background_core_dump string partial

Background_dump_dest string / s01/oracle/diag/rdbms/chenjh/chenjh

/ trace

Core_dump_dest string / s01/oracle/diag/rdbms/chenjh/chenjh

/ cdump

Max_dump_file_size string unlimited

Shadow_core_dump string partial

User_dump_dest string / s01/oracle/diag/rdbms/chenjh/chenjh

/ trace

SQL > ho

[oracle@dbachenjh ~] $cd / s01/oracle/diag/rdbms/chenjh/chenjh/

/ [oracle@dbachenjh chenjh] $cd trace/

[oracle@dbachenjh trace] $ls alert_chenjh.log

Alert_chenjh.log

[oracle@dbachenjh trace] $tail-30f alert_chenjh.log-view the last 30 messages in the log

Private strand flush not complete

Current log# 3 seq# 348 mem# 0: / s01/oracle/oradata/chenjh/redo03.log

Thread 1 advanced to log sequence 349 (LGWR switch)

Current log# 2 seq# 349 mem# 0: / s01/oracle/oradata/chenjh/redo02.log

Fri Jul 11 02:01:02 2014

Archived Log entry 342 added for thread 1 sequence 348 ID 0xba3d3cac dest 1:

Fri Jul 11 07:00:47 2014

Thread 1 cannot allocate new log, sequence 350

Private strand flush not complete

Current log# 2 seq# 349 mem# 0: / s01/oracle/oradata/chenjh/redo02.log

Thread 1 advanced to log sequence 350 (LGWR switch)

Current log# 1 seq# 350 mem# 0: / s01/oracle/oradata/chenjh/redo01.log

Fri Jul 11 07:00:51 2014

Archived Log entry 343 added for thread 1 sequence 349 ID 0xba3d3cac dest 1:

Fri Jul 11 12:00:18 2014

Thread 1 cannot allocate new log, sequence 351

Private strand flush not complete

Current log# 1 seq# 350 mem# 0: / s01/oracle/oradata/chenjh/redo01.log

Thread 1 advanced to log sequence 351 (LGWR switch)

Current log# 3 seq# 351 mem# 0: / s01/oracle/oradata/chenjh/redo03.log

Fri Jul 11 12:00:21 2014

Archived Log entry 344 added for thread 1 sequence 350 ID 0xba3d3cac dest 1:

Fri Jul 11 16:46:10 2014

Alter database backup controlfile to trace

Backup controlfile written to trace file / s01/oracle/diag/rdbms/chenjh/chenjh/trace/chenjh_ora_23408.trc

Completed: alter database backup controlfile to trace- sees the directory and name of the backup file from the log

[oracle@dbachenjh trace] the content below $more chenjh_ora_23408.trc--- is the content of the control file.

Trace file / s01/oracle/diag/rdbms/chenjh/chenjh/trace/chenjh_ora_23408.trc

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0-64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

ORACLE_HOME = / s01/oracle/proudct/11.2.0.1/db_home1

System name: Linux

Node name: dbachenjh

Release: 2.6.32-300.10.1.el5uek

Version: # 1 SMP Wed Feb 22 17:37:40 EST 2012

Machine: x86_64

VM name: VMWare Version: 6

Instance name: chenjh

Redo thread mounted by this instance: 1

Oracle process number: 44

Unix process pid: 23408, p_w_picpath: oracle@dbachenjh (TNS V1-V3)

* 2014-07-11 16 46 purl 10.328

* SESSION ID: (11.64861) 2014-07-11 16 purl 46 purl 10.328

* CLIENT ID: () 2014-07-11 16 purl 46 10. 328

* SERVICE NAME: (SYS$USERS) 2014-07-11 16 purl 46 purl 10.328

* MODULE NAME: (sqlplus@dbachenjh (TNS V1-V3)) 2014-07-11 16 purl 46 purl 10.328

* ACTION NAME: () 2014-07-11 16 purl 46 10. 328

-- 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= "chenjh"

--

-- 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=/arch_log'

-- 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 "chenjh" NORESETLOGS ARCHIVELOG

MAXLOGFILES 16

MAXLOGMEMBERS 3

MAXDATAFILES 100

MAXINSTANCES 8

MAXLOGHISTORY 292

LOGFILE

GROUP 1'/ s01 SIZE BLOCKSIZE 50m oradata BLOCKSIZE 512

GROUP 2'/ s01 SIZE SIZE 50m oradat 512

GROUP 3'/ s01 SIZE BLOCKSIZE 50m oradata BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

'/ s01Universe oracleplexoradataUniplicatechenjhscarplessystem01.dbf'

'/ s01scarp oraclescarp oradataUniplicatechenjhUniplicatesysaux01.dbf'

'/ s01Universe oraclescarp chenjhscarp undotbs01.dbf'

'/ s01Universe oracleplicoradataPlacement chenjhscarp users01.dbf'

'/ s01Universe oracleplicoradataPlacement chenjhUnique example01.dbf'

'/ s01Universe oraclescarp chenjhscarp chenjh01.dbf'

'/ s01Universe oraclescarp chenjhscarp chenjh02.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'/ arch_log/1_1_762083164.dbf'

-- ALTER DATABASE REGISTER LOGFILE'/ arch_log/1_1_848329454.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 TEMP ADD TEMPFILE'/ s01Accord oradataAccord temp01.dbf'

SIZE 30408704 REUSE AUTOEXTEND ON NEXT 5242880 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 "chenjh" RESETLOGS ARCHIVELOG

MAXLOGFILES 16

MAXLOGMEMBERS 3

MAXDATAFILES 100

MAXINSTANCES 8

MAXLOGHISTORY 292

LOGFILE

GROUP 1'/ s01 SIZE BLOCKSIZE 50m oradata BLOCKSIZE 512

GROUP 2'/ s01 SIZE SIZE 50m oradat 512

GROUP 3'/ s01 SIZE BLOCKSIZE 50m oradata BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

'/ s01Universe oracleplexoradataUniplicatechenjhscarplessystem01.dbf'

'/ s01scarp oraclescarp oradataUniplicatechenjhUniplicatesysaux01.dbf'

'/ s01Universe oraclescarp chenjhscarp undotbs01.dbf'

'/ s01Universe oracleplicoradataPlacement chenjhscarp users01.dbf'

'/ s01Universe oracleplicoradataPlacement chenjhUnique example01.dbf'

'/ s01Universe oraclescarp chenjhscarp chenjh01.dbf'

'/ s01Universe oraclescarp chenjhscarp chenjh02.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'/ arch_log/1_1_762083164.dbf'

-- ALTER DATABASE REGISTER LOGFILE'/ arch_log/1_1_848329454.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 TEMP ADD TEMPFILE'/ s01Accord oradataAccord temp01.dbf'

SIZE 30408704 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 32767M

-- End of tempfile additions.

--

Tags: File backup directory content log control information name face Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Huawei MySQL Xiaomi Linux Apple