oracle控制檔案轉儲說明
#環境
os:centos 6.6 x64
db version:11.2.0.4.0
#轉儲控制檔案
[oracle@ct6605 trace]$ sqlplus / as sysdba
#可以使用alter session set events 'immediate trace name controlf level 2';或oradebug dump controlf 2
SQL> oradebug setmypid
SQL> oradebug dump controlf 2;
#顯示控制檔案的轉儲內容
[oracle@ct6605 ~]$ cd /u01/app/oracle/diag/rdbms/ct66/ct66/trace
#可以透過上面sqlplus中的spid或ll -rth排序來確定是那個檔案
[oracle@ct6605 trace]$ vi ct66_ora_12060.trc
#以下只顯示控制檔案的dump內容
*** 2016-02-19 17:55:46.970
Processing Oradebug command 'dump controlf 2'
DUMP OF CONTROL FILES, Seq # 13242 = 0x33ba
#通用檔案頭
#第一個資料庫檔案(control,redo,archive,data,temp file)都有相同的檔案頭.也可能透過x$kcvfh或x$kcvfhall檢視.
V10 STYLE FILE HEADER:
Compatibility Vsn = 186647552=0xb200400
#db id,db name
Db ID=665652355=0x27ad0c83, Db Name='CT66'
Activation ID=0=0x0
#Control Seq是記錄控制檔案最後一次更新的順序號,用以和控制檔案中這個順序號做對比來確定控制檔案的新舊.
#File size是記錄在快取層的當前檔案的大小,單位是塊,單位塊大小是16384
Control Seq=13242=0x33ba, File size=604=0x25c
#File Number此日誌檔案的絕對檔案號.
#Blksiz此日誌檔案的塊大小.
#File Type檔案型別:
KCCTYPCF 1 control file
KCCTYPRL 2 redo log file
KCCTYPDF 3 vanilla db file; that is,normal data, index, and undo blocks
KCCTYPBC 4 backup control file
KCCTYPBP 5 backup piece
KCCTYPTF 6 temporary db file
File Number=0, Blksiz=16384, File Type=1 CONTROL
***************************************************************************
DATABASE ENTRY 資料庫標識
***************************************************************************
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
12/31/2015 17:40:19
#DB Name資料庫名稱
DB Name "CT66"
#Database flags
KCCDIMRE 0x00000001 whether media recovery enabled(that is: ARCHIVELOG mode)
KCCDICKD 0x00000002 if dictionary must be checked with control file
KCCDIRLR 0x00000004 DB OPEN RESETLOGS required
KCCDIJNK 0x00000008 (junk value from beta)
KCCDIMRC 0x00000010 was/is last mounted READ_COMPATIBLE
KCCDICNV 0x00000020 controlfile was just created by convert from v6
KCCDIIRA 0x00000040 Incomplete Recovery Allowed when resetting logs
KCCDICCF 0x00000100 Controlfile was created with CREATE CONTROLFILE
KCCDIINV 0x00000200 Invalid control file or database; still creating
KCCDISBD 0x00000400 StandBy Database; control file for hot standby
KCCDIORL 0x00000800 Opened ResetLogs; set until dictionary check
KCCDICFC 0x00001000 valid ControlFile Checkpoint in backup cf
KCCDISSN 0x00002000 SnapShot controlfile fileName pointer valid
KCCDIUCD 0x00004000 lazy file header Update Checkpoint cycle Done
KCCDICLO 0x00008000 clone database
KCCDINDL 0x00010000 standby database No Data Loss
KCCDISPK 0x00020000 Supplemental log primary keys
KCCDISUI 0x00040000 Supplemental log unique indexes
KCCDISFK 0x00080000 Supplemental log foreign keys
KCCDIGDA 0x00100000 Database guard all
KCCDIGDS 0x00200000 Database guard standby data
KCCDIIMR 0x00400000 Group Membership Recovery is supported
KCCDIEAR 0x00800000 End-of-redo Archival Received
KCCDISTR 0x01000000 Standby Terminal Recovery
KCCDILSB 0x02000000 Logical StandBy database
Database flags = 0x00404001 0x00001200
#Controlfile Creation Timestamp控制檔案建立時間
Controlfile Creation Timestamp 12/31/2015 17:40:19
#Incmplt recovery scn在不完全恢復時最後應用的scn,資料庫開啟後會清空
Incmplt recovery scn: 0x0000.00000000
#Resetlogs scn是resetlogs的唯一標識,用以在資料庫開啟時同資料檔案和日誌檔案比對
Resetlogs scn: 0x0000.000e2006 Resetlogs Timestamp 12/31/2015 17:40:19
#Prior resetlogs scn是上一次resetlogs的唯一標識
Prior resetlogs scn: 0x0000.00000001 Prior resetlogs Timestamp 08/24/2013 11:37:30
Redo Version: compatible=0xb200400
#Data files = 7, #Online files = 7
#Database checkpoint scn是資料庫scn,表示最近一次全量checkpoint操作時的scn,對應v$database.checkpoint_change#
Database checkpoint: Thread=1 scn: 0x0000.001d1426
#Enabled: the number of enabled threads
#Open: the number of open threads
#Head: head of thread link list
#Tail: tail of thread link list
Threads: #Enabled=1, #Open=1, Head=1, Tail=1
enabled threads: 01000000 00000000 00000000 00000000 00000000 00000000
...
Max log members = 3, Max data members = 1
Arch list: Head=3, Tail=3, Force scn: 0x0000.001c3a88scn: 0x0000.00000000
Activation ID: 665633411
SCN compatibility 1
Auto-rollover enabled
#Controlfile Checkpoint at SCN: It is updated after every checkpoint (may it betablespace, thread, or database) and is always greater than or equal to the database checkpoint when the database is open.
Controlfile Checkpointed at scn: 0x0000.001d985e 02/19/2016 17:53:57
thread:0 rba:(0x0.0.0)
enabled threads: 00000000 00000000 00000000 00000000 00000000 00000000
...
***************************************************************************
CHECKPOINT PROGRESS RECORDS
***************************************************************************
(size = 8180, compat size = 8180, section max = 11, section in-use = 0,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 2, numrecs = 11)
#Thread是程式所屬的執行緒號
#Status:
KCCCP_UNKNOWN (0): does not contain valid information
KCCCP_CLOSED (1): thread closed; no thread recovery needed
KCCCP_OPEN (2): thread open; data can be used for recovery
#Dirty是dirty count在檢查點佇列中的長度
THREAD #1 - status:0x2 flags:0x0 dirty:10
#Low cache RBA: The low RBA of the checkpoint queues indicate where recovery can begin.
#On Disk RBA是當前系統最新rba
low cache rba:(0x75.f505.0) on disk rba:(0x75.f51b.0)
#On Disk SCN是當前系統最新rba所對應的scn,由ckpt程式3秒更新一次.crash recover至少要應用到此.對應x$kcccp.cpods
on disk scn: 0x0000.001d9872 02/19/2016 17:54:50
#Resetlogs SCN是最後一次resetlogs的scn
resetlogs scn: 0x0000.000e2006 12/31/2015 17:40:19
#Heartbeat: The heartbeat is incremented in CKPT's timeout action, provided that the thread is mounted.
heartbeat: 902915463 mount id: 668479460
...
***************************************************************************
EXTENDED DATABASE ENTRY
***************************************************************************
(size = 900, compat size = 900, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 140, numrecs = 1)
Control AutoBackup date(dd/mm/yyyy)=31/12/2015
Next AutoBackup sequence= 0
Database recovery target inc#:2, Last open inc#:2
flg:0x0, flag:0x0
Change tracking state=0, file index=0, checkpoint count=0scn: 0x0000.00000000
Flashback log count=0, block count=0
Desired flashback log size=0 blocks
Oldest guarantee restore point=0
Highest thread enable/disable scn: 0x0000.00000000
Number of Open thread with finite next SCN in last log: 0
Number of half-enabled redo threads: 0
Sum of absolute file numbers for files currently being moved online: 0
#oradebug dump controlf 3還包括以下資訊
REDO THREAD RECORDS
LOG FILE RECORDS
DATA FILE RECORDS
TEMP FILE RECORDS
TABLESPACE RECORDS
RMAN CONFIGURATION RECORDS
FLASHBACK LOGFILE RECORDS
MTTR RECORDS
STANDBY DATABASE MAP RECORDS
RESTORE POINT RECORDS
ACM SERVICE RECORDS
LOG FILE HISTORY RECORDS 日誌檔案歷史資訊
OFFLINE RANGE RECORDS
ARCHIVED LOG RECORDS 歸檔日誌資訊
FOREIGN ARCHIVED LOG RECORDS
BACKUP SET RECORDS
BACKUP PIECE RECORDS
BACKUP DATAFILE RECORDS
BACKUP LOG RECORDS
DATAFILE COPY RECORDS
BACKUP DATAFILE CORRUPTION RECORDS
DATAFILE COPY CORRUPTION RECORDS
DELETION RECORDS
PROXY COPY RECORDS
INCARNATION RECORDS
RMAN STATUS RECORDS
DATAFILE HISTORY RECORDS
NORMAL RESTORE POINT RECORDS
DATABASE BLOCK CORRUPTION RECORDS
os:centos 6.6 x64
db version:11.2.0.4.0
#轉儲控制檔案
[oracle@ct6605 trace]$ sqlplus / as sysdba
#可以使用alter session set events 'immediate trace name controlf level 2';或oradebug dump controlf 2
SQL> oradebug setmypid
SQL> oradebug dump controlf 2;
#顯示控制檔案的轉儲內容
[oracle@ct6605 ~]$ cd /u01/app/oracle/diag/rdbms/ct66/ct66/trace
#可以透過上面sqlplus中的spid或ll -rth排序來確定是那個檔案
[oracle@ct6605 trace]$ vi ct66_ora_12060.trc
#以下只顯示控制檔案的dump內容
*** 2016-02-19 17:55:46.970
Processing Oradebug command 'dump controlf 2'
DUMP OF CONTROL FILES, Seq # 13242 = 0x33ba
#通用檔案頭
#第一個資料庫檔案(control,redo,archive,data,temp file)都有相同的檔案頭.也可能透過x$kcvfh或x$kcvfhall檢視.
V10 STYLE FILE HEADER:
Compatibility Vsn = 186647552=0xb200400
#db id,db name
Db ID=665652355=0x27ad0c83, Db Name='CT66'
Activation ID=0=0x0
#Control Seq是記錄控制檔案最後一次更新的順序號,用以和控制檔案中這個順序號做對比來確定控制檔案的新舊.
#File size是記錄在快取層的當前檔案的大小,單位是塊,單位塊大小是16384
Control Seq=13242=0x33ba, File size=604=0x25c
#File Number此日誌檔案的絕對檔案號.
#Blksiz此日誌檔案的塊大小.
#File Type檔案型別:
KCCTYPCF 1 control file
KCCTYPRL 2 redo log file
KCCTYPDF 3 vanilla db file; that is,normal data, index, and undo blocks
KCCTYPBC 4 backup control file
KCCTYPBP 5 backup piece
KCCTYPTF 6 temporary db file
File Number=0, Blksiz=16384, File Type=1 CONTROL
***************************************************************************
DATABASE ENTRY 資料庫標識
***************************************************************************
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
12/31/2015 17:40:19
#DB Name資料庫名稱
DB Name "CT66"
#Database flags
KCCDIMRE 0x00000001 whether media recovery enabled(that is: ARCHIVELOG mode)
KCCDICKD 0x00000002 if dictionary must be checked with control file
KCCDIRLR 0x00000004 DB OPEN RESETLOGS required
KCCDIJNK 0x00000008 (junk value from beta)
KCCDIMRC 0x00000010 was/is last mounted READ_COMPATIBLE
KCCDICNV 0x00000020 controlfile was just created by convert from v6
KCCDIIRA 0x00000040 Incomplete Recovery Allowed when resetting logs
KCCDICCF 0x00000100 Controlfile was created with CREATE CONTROLFILE
KCCDIINV 0x00000200 Invalid control file or database; still creating
KCCDISBD 0x00000400 StandBy Database; control file for hot standby
KCCDIORL 0x00000800 Opened ResetLogs; set until dictionary check
KCCDICFC 0x00001000 valid ControlFile Checkpoint in backup cf
KCCDISSN 0x00002000 SnapShot controlfile fileName pointer valid
KCCDIUCD 0x00004000 lazy file header Update Checkpoint cycle Done
KCCDICLO 0x00008000 clone database
KCCDINDL 0x00010000 standby database No Data Loss
KCCDISPK 0x00020000 Supplemental log primary keys
KCCDISUI 0x00040000 Supplemental log unique indexes
KCCDISFK 0x00080000 Supplemental log foreign keys
KCCDIGDA 0x00100000 Database guard all
KCCDIGDS 0x00200000 Database guard standby data
KCCDIIMR 0x00400000 Group Membership Recovery is supported
KCCDIEAR 0x00800000 End-of-redo Archival Received
KCCDISTR 0x01000000 Standby Terminal Recovery
KCCDILSB 0x02000000 Logical StandBy database
Database flags = 0x00404001 0x00001200
#Controlfile Creation Timestamp控制檔案建立時間
Controlfile Creation Timestamp 12/31/2015 17:40:19
#Incmplt recovery scn在不完全恢復時最後應用的scn,資料庫開啟後會清空
Incmplt recovery scn: 0x0000.00000000
#Resetlogs scn是resetlogs的唯一標識,用以在資料庫開啟時同資料檔案和日誌檔案比對
Resetlogs scn: 0x0000.000e2006 Resetlogs Timestamp 12/31/2015 17:40:19
#Prior resetlogs scn是上一次resetlogs的唯一標識
Prior resetlogs scn: 0x0000.00000001 Prior resetlogs Timestamp 08/24/2013 11:37:30
Redo Version: compatible=0xb200400
#Data files = 7, #Online files = 7
#Database checkpoint scn是資料庫scn,表示最近一次全量checkpoint操作時的scn,對應v$database.checkpoint_change#
Database checkpoint: Thread=1 scn: 0x0000.001d1426
#Enabled: the number of enabled threads
#Open: the number of open threads
#Head: head of thread link list
#Tail: tail of thread link list
Threads: #Enabled=1, #Open=1, Head=1, Tail=1
enabled threads: 01000000 00000000 00000000 00000000 00000000 00000000
...
Max log members = 3, Max data members = 1
Arch list: Head=3, Tail=3, Force scn: 0x0000.001c3a88scn: 0x0000.00000000
Activation ID: 665633411
SCN compatibility 1
Auto-rollover enabled
#Controlfile Checkpoint at SCN: It is updated after every checkpoint (may it betablespace, thread, or database) and is always greater than or equal to the database checkpoint when the database is open.
Controlfile Checkpointed at scn: 0x0000.001d985e 02/19/2016 17:53:57
thread:0 rba:(0x0.0.0)
enabled threads: 00000000 00000000 00000000 00000000 00000000 00000000
...
***************************************************************************
CHECKPOINT PROGRESS RECORDS
***************************************************************************
(size = 8180, compat size = 8180, section max = 11, section in-use = 0,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 2, numrecs = 11)
#Thread是程式所屬的執行緒號
#Status:
KCCCP_UNKNOWN (0): does not contain valid information
KCCCP_CLOSED (1): thread closed; no thread recovery needed
KCCCP_OPEN (2): thread open; data can be used for recovery
#Dirty是dirty count在檢查點佇列中的長度
THREAD #1 - status:0x2 flags:0x0 dirty:10
#Low cache RBA: The low RBA of the checkpoint queues indicate where recovery can begin.
#On Disk RBA是當前系統最新rba
low cache rba:(0x75.f505.0) on disk rba:(0x75.f51b.0)
#On Disk SCN是當前系統最新rba所對應的scn,由ckpt程式3秒更新一次.crash recover至少要應用到此.對應x$kcccp.cpods
on disk scn: 0x0000.001d9872 02/19/2016 17:54:50
#Resetlogs SCN是最後一次resetlogs的scn
resetlogs scn: 0x0000.000e2006 12/31/2015 17:40:19
#Heartbeat: The heartbeat is incremented in CKPT's timeout action, provided that the thread is mounted.
heartbeat: 902915463 mount id: 668479460
...
***************************************************************************
EXTENDED DATABASE ENTRY
***************************************************************************
(size = 900, compat size = 900, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 140, numrecs = 1)
Control AutoBackup date(dd/mm/yyyy)=31/12/2015
Next AutoBackup sequence= 0
Database recovery target inc#:2, Last open inc#:2
flg:0x0, flag:0x0
Change tracking state=0, file index=0, checkpoint count=0scn: 0x0000.00000000
Flashback log count=0, block count=0
Desired flashback log size=0 blocks
Oldest guarantee restore point=0
Highest thread enable/disable scn: 0x0000.00000000
Number of Open thread with finite next SCN in last log: 0
Number of half-enabled redo threads: 0
Sum of absolute file numbers for files currently being moved online: 0
#oradebug dump controlf 3還包括以下資訊
REDO THREAD RECORDS
LOG FILE RECORDS
DATA FILE RECORDS
TEMP FILE RECORDS
TABLESPACE RECORDS
RMAN CONFIGURATION RECORDS
FLASHBACK LOGFILE RECORDS
MTTR RECORDS
STANDBY DATABASE MAP RECORDS
RESTORE POINT RECORDS
ACM SERVICE RECORDS
LOG FILE HISTORY RECORDS 日誌檔案歷史資訊
OFFLINE RANGE RECORDS
ARCHIVED LOG RECORDS 歸檔日誌資訊
FOREIGN ARCHIVED LOG RECORDS
BACKUP SET RECORDS
BACKUP PIECE RECORDS
BACKUP DATAFILE RECORDS
BACKUP LOG RECORDS
DATAFILE COPY RECORDS
BACKUP DATAFILE CORRUPTION RECORDS
DATAFILE COPY CORRUPTION RECORDS
DELETION RECORDS
PROXY COPY RECORDS
INCARNATION RECORDS
RMAN STATUS RECORDS
DATAFILE HISTORY RECORDS
NORMAL RESTORE POINT RECORDS
DATABASE BLOCK CORRUPTION RECORDS
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28539951/viewspace-1994654/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle安裝光碟內容的檔案說明Oracle
- Oracle 控制檔案Oracle
- fepk檔案格式說明
- Linux下玩轉nginx系列(二)——nginx配置檔案說明LinuxNginx
- Nginx的配置檔案說明Nginx
- Oracle Latch 說明Oracle
- ORACLE 控制檔案(Control Files)概述Oracle
- nginx日誌配置檔案說明Nginx
- Linux下玩轉nginx系列(三)---nginx日誌配置檔案說明LinuxNginx
- oracle orapwd使用說明Oracle
- 【ROWID】Oracle rowid說明Oracle
- django的初始化檔案說明Django
- 轉換說明
- Hadoop之HDFS檔案讀寫流程說明Hadoop
- C++檔案說明及使用方法C++
- CentOS8中systemd配置檔案說明CentOS
- Oracle 控制檔案損壞解決方案Oracle
- Linux中log檔案是什麼意思?Linux日誌檔案說明Linux
- 易優CMS模板目錄各檔案說明
- Oracle 11g 重新建立控制檔案Oracle
- oracle11g修改控制檔案路徑Oracle
- oracle 控制檔案及引數檔案何時自動備份Oracle
- Oracle Table建立引數說明Oracle
- Oracle 官方文件 結構說明Oracle
- 【RMAN】Oracle中如何備份控制檔案?備份控制檔案的方式有哪幾種?Oracle
- 【ORACLE】Oracle常用SQL及重點功能說明OracleSQL
- 轉:使用 Tkprof 分析 ORACLE 跟蹤檔案Oracle
- 自研 PHP 框架 1.1_index.php 檔案說明PHP框架Index
- 自研 PHP 框架 1.0_index.php 檔案說明PHP框架Index
- Centos系統中 Systemd 的Unit檔案配置說明CentOS
- Centos7 中 Systemd 的Unit檔案配置說明CentOS
- win10桌面檔案在c盤哪 win10桌面檔案c盤儲存路徑說明Win10
- RU 和 RUR oracle補丁說明Oracle
- 【NETWORK】Oracle RAC 心跳地址配置說明Oracle
- JVM(筆記)—— Class 類檔案結構的說明(二)JVM筆記
- 轉載:__builtin_expect 說明UI
- oracle快速拿到重建控制檔案語句的方法二Oracle
- 清除Oracle控制檔案中的歸檔資訊v$archived_logOracleHive
- Redis 6.0 訪問控制列表ACL說明Redis