如何查看Oracle11g控制文件里面的内容

        控制文件（Control File）是Oracle的物理文件之一，它记录了数据库的名字、数据文件的位置等信息。控制文件的重要性在于，一旦控制文件损坏，数据库将会宕机。控制文件是一个很小的二进制文件，用户不能编辑控制文件，控制文件的修改由Oracle自动完成。那么，我们能够查看控制文件里面的具体信息吗？答案是可以的，我们可以通过转储文件来获得控制文件的详细信息。
1.生成控制文件的转储文件

点击(此处)折叠或打开

1. SQL> select * from v$version;
   
2. 
   
3. BANNER
   
4. --------------------------------------------------------------------------------
   
5. Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
   
6. PL/SQL Release 11.2.0.3.0 - Production
   
7. CORE 11.2.0.3.0 Production
   
8. TNS for Linux: Version 11.2.0.3.0 - Production
   
9. NLSRTL Version 11.2.0.3.0 - Production
   
10. 
    
11. SQL> alter database backup controlfile to trace ;
    
12. 
    
13. Database altered.
    
14. 
    
15. SQL>

2.查找生成的转储文件
我们知道，用户生成的TRACE文件存储在udump目录下。在Oracle10g中，udump路径是$ORACLE_HOME/admin/SID/udump，而Oracle11g则大不一样。我们可以通过查看user_dump_dest参数来定位udump目录的具体位置。

点击(此处)折叠或打开

1. SQL> show parameter user_dump_dest
   
2. 
   
3. NAME TYPE VALUE
   
4. ------------------------------------ ----------- ------------------------------
   
5. user_dump_dest string /u01/app/oracle/diag/rdbms/hoegh/HOEGH/trace
6. SQL>

然后，我们使用ls命令找到最近生成的TRACE文件，就是图示的HOEGH_ora_304.trc文件。

点击(此处)折叠或打开

1. [oracle@hoegh trace]$ ls -ltr
   
2. total 1332
   
3. 此处省略三百字
   
4. -rw-r----- 1 oracle oinstall 932 May 9 21:26 HOEGH_mmon_4805.trm
   
5. -rw-r----- 1 oracle oinstall 9750 May 9 21:26 HOEGH_mmon_4805.trc
   
6. -rw-r----- 1 oracle oinstall 4562 May 9 21:28 HOEGH_dbrm_4789.trm
   
7. -rw-r----- 1 oracle oinstall 80534 May 9 21:28 HOEGH_dbrm_4789.trc
   
8. -rw-r----- 1 oracle oinstall 97 May 9 21:29 HOEGH_ora_304.trm
   
9. -rw-r----- 1 oracle oinstall 12786 May 9 21:29 HOEGH_ora_304.trc

3.查看控制文件具体信息
现在，我们就可以通过more命令来查看控制文件的具体信息了。

点击(此处)折叠或打开

1. [oracle@hoegh trace]$ more HOEGH_ora_304.trc
   
2. Trace file /u01/app/oracle/diag/rdbms/hoegh/HOEGH/trace/HOEGH_ora_304.trc
   
3. Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
   
4. With the Partitioning, OLAP, Data Mining and Real Application Testing options
   
5. ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
   
6. System name: Linux
   
7. Node name: hoegh.example.com
   
8. Release: 2.6.18-164.el5PAE
   
9. Version: #1 SMP Thu Sep 3 02:28:20 EDT 2009
   
10. Machine: i686
    
11. VM name: VMWare Version: 6
    
12. Instance name: HOEGH
    
13. Redo thread mounted by this instance: 1
    
14. Oracle process number: 26
    
15. Unix process pid: 304, image: oracle@hoegh.example.com (TNS V1-V3)
    
16. 
    
17. *** 2016-05-09 21:29:07.246
    
18. -- The following are current System-scope REDO Log Archival related
    
19. -- parameters and can be included in the database initialization file.
    
20. --
    
21. -- LOG_ARCHIVE_DEST=''
    
22. -- LOG_ARCHIVE_DUPLEX_DEST=''
    
23. --
    
24. -- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf
    
25. --
    
26. -- DB_UNIQUE_NAME="HOEGH"
    
27. --
    
28. -- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
    
29. -- LOG_ARCHIVE_MAX_PROCESSES=4
    
30. -- STANDBY_FILE_MANAGEMENT=MANUAL
    
31. -- STANDBY_ARCHIVE_DEST=?/dbs/arch
    
32. -- FAL_CLIENT=''
    
33. -- FAL_SERVER=''
    
34. --
    
35. -- LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch
    
36. '
    
37. -- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
    
38. -- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
    
39. -- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
    
40. -- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
    
41. -- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
    
42. -- LOG_ARCHIVE_DEST_STATE_1=ENABLE
    
43. --
    
44. -- Below are two sets of SQL statements, each of which creates a new
    
45. -- control file and uses it to open the database. The first set opens
    
46. -- the database with the NORESETLOGS option and should be used only if
    
47. -- the current versions of all online logs are available. The second
    
48. -- set opens the database with the RESETLOGS option and should be used
    
49. -- if online logs are unavailable.
    
50. -- The appropriate set of statements can be copied from the trace into
    
51. -- a script file, edited as necessary, and executed when there is a
    
52. -- need to re-create the control file.
    
53. --
    
54. -- Set #1. NORESETLOGS case
    
55. --
    
56. -- The following commands will create a new control file and use it
    
57. -- to open the database.
    
58. -- Data used by Recovery Manager will be lost.
    
59. -- Additional logs may be required for media recovery of offline
    
60. -- Use this only if the current versions of all online logs are
    
61. -- available.
    
62. -- After mounting the created controlfile, the following SQL
    
63. -- statement will place the database in the appropriate
    
64. -- protection mode:
    
65. -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
    
66. STARTUP NOMOUNT
    
67. CREATE CONTROLFILE REUSE DATABASE "HOEGH" NORESETLOGS NOARCHIVELOG
    
68.     MAXLOGFILES 16
    
69.     MAXLOGMEMBERS 3
    
70.     MAXDATAFILES 100
    
71.     MAXINSTANCES 8
    
72.     MAXLOGHISTORY 292
    
73. LOGFILE
    
74.   GROUP 1 '/u01/app/oracle/oradata/HOEGH/redo01.log' SIZE 50M BLOCKSIZE 512,
    
75.   GROUP 2 '/u01/app/oracle/oradata/HOEGH/redo02.log' SIZE 50M BLOCKSIZE 512,
    
76.   GROUP 3 '/u01/app/oracle/oradata/HOEGH/redo03.log' SIZE 50M BLOCKSIZE 512
    
77. -- STANDBY LOGFILE
    
78. DATAFILE
    
79.   '/u01/app/oracle/oradata/HOEGH/system01.dbf',
    
80.   '/u01/app/oracle/oradata/HOEGH/sysaux01.dbf',
    
81.   '/u01/app/oracle/oradata/HOEGH/undotbs01.dbf',
    
82.   '/u01/app/oracle/oradata/HOEGH/users01.dbf',
    
83.   '/u01/app/oracle/oradata/HOEGH/example01.dbf',
    
84.   '/u01/app/oracle/oradata/HOEGH/test01.dbf'
    
85. CHARACTER SET AL32UTF8
    
86. ;
    
87. -- Commands to re-create incarnation table
    
88. -- Below log names MUST be changed to existing filenames on
    
89. -- disk. Any one log file from each branch can be used to
    
90. -- re-create incarnation records.
    
91. -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/
    
92. arch1_1_762197622.dbf';
    
93. -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/
    
94. arch1_1_860888149.dbf';
    
95. -- Recovery is required if any of the datafiles are restored backups,
    
96. -- or if the last shutdown was not normal or immediate.
    
97. RECOVER DATABASE
    
98. -- Database can now be opened normally.
    
99. ALTER DATABASE OPEN;
    
100. -- Commands to add tempfiles to temporary tablespaces.
     
101. -- Online tempfiles have complete space information.
     
102. -- Other tempfiles may require adjustment.
     
103. ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/HOEGH/temp01.dbf'
     
104.      SIZE 30408704 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
     
105. -- End of tempfile additions.
     
106. --
     
107. -- Set #2. RESETLOGS case
     
108. --
     
109. -- The following commands will create a new control file and use it
     
110. -- to open the database.
     
111. -- Data used by Recovery Manager will be lost.
     
112. -- The contents of online logs will be lost and all backups will
     
113. -- be invalidated. Use this only if online logs are damaged.
     
114. -- After mounting the created controlfile, the following SQL
     
115. -- statement will place the database in the appropriate
     
116. -- protection mode:
     
117. -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE
     
118. STARTUP NOMOUNT
     
119. CREATE CONTROLFILE REUSE DATABASE "HOEGH" RESETLOGS NOARCHIVELOG
     
120.     MAXLOGFILES 16
     
121.     MAXLOGMEMBERS 3
     
122.     MAXDATAFILES 100
     
123.     MAXINSTANCES 8
     
124.     MAXLOGHISTORY 292
     
125. LOGFILE
     
126.   GROUP 1 '/u01/app/oracle/oradata/HOEGH/redo01.log' SIZE 50M BLOCKSIZE 512,
     
127.   GROUP 2 '/u01/app/oracle/oradata/HOEGH/redo02.log' SIZE 50M BLOCKSIZE 512,
     
128.   GROUP 3 '/u01/app/oracle/oradata/HOEGH/redo03.log' SIZE 50M BLOCKSIZE 512
     
129. -- STANDBY LOGFILE
     
130. DATAFILE
     
131.   '/u01/app/oracle/oradata/HOEGH/system01.dbf',
     
132.   '/u01/app/oracle/oradata/HOEGH/sysaux01.dbf',
     
133.   '/u01/app/oracle/oradata/HOEGH/undotbs01.dbf',
     
134.   '/u01/app/oracle/oradata/HOEGH/users01.dbf',
     
135.   '/u01/app/oracle/oradata/HOEGH/example01.dbf',
     
136.   '/u01/app/oracle/oradata/HOEGH/test01.dbf'
     
137. CHARACTER SET AL32UTF8
     
138. ;
     
139. -- Commands to re-create incarnation table
     
140. -- Below log names MUST be changed to existing filenames on
     
141. -- disk. Any one log file from each branch can be used to
     
142. -- re-create incarnation records.
     
143. -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/
     
144. arch1_1_762197622.dbf';
     
145. -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/
     
146. arch1_1_860888149.dbf';
     
147. -- Recovery is required if any of the datafiles are restored backups,
     
148. -- or if the last shutdown was not normal or immediate.
     
149. RECOVER DATABASE USING BACKUP CONTROLFILE
     
150. -- Database can now be opened zeroing the online logs.
     
151. ALTER DATABASE OPEN RESETLOGS;
     
152. -- Commands to add tempfiles to temporary tablespaces.
     
153. -- Online tempfiles have complete space information.
     
154. -- Other tempfiles may require adjustment.
     
155. ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/HOEGH/temp01.dbf

我们可以看到转储文件里包含了数据库的名字、数据文件的位置等信息，并且按照是否需要resetlogs分别给出了创建控制文件的sql语句。控制文件非常重要，我们可以把它备份下来以防万一。

~~~~~~~ the end~~~~~~~~~
hoegh
2016.05.09

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/30162081/viewspace-2096756/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/30162081/viewspace-2096756/