The transfer control file must be performed in a database opening (OPEN) or a mount.
Connect database
E: /> SQLPLUS "/ as sysdba"
SQL * Plus: Release
9.2.0
.1.0 - Production on Friday May 14 08:52:03 2004
CopyRight (C) 1982, 2002, Oracle Corporation. All Rights Reserved.
Connected to:
Oracle9i
Enterprise
Edition Release
9.2.0
.1.0 - Production
With the partitioning, OLAP AND ORACLE DATA MINING OPTIONS
JServer Release
9.2.0
.1.0 - Production
2. Determine the directory of the tracking file:
Sys @ Test_lunar> Show Parameter Dump
Name Type Value
----------------------------------- --- ---------------------------
Background_core_dump string partial
Background_dump_dest string E: / Oracle / Admin / Test / BDUMP
Core_dump_dest string E: / Oracle / Admin / Test / CDUMP
MAX_DUMP_FILE_SIZE STRING UNLIMITED
Shadow_core_dump string partial
User_dump_dest string E: / Oracle / Admin / Test / UDUMP
Sys @ Test_lunar>
Sys @ Test_lunar> Host Dir E: / Oracle / Admin / Test / UDUMP
The volume in the driver E is Oracle
The serial number of the volume is
707A
-C
50C
E: / Oracle / Admin / Test / UDUMP directory
2002-01-13
21:59
2002-01-13
21:59
0 file 0 bytes
2 catalogs 2, 444, 267, 520 available bytes
3. Dump control file header
Sys @ Test_lunar> ALTER Session Set Events 'Immediate Trace Name Controlf Level 1';
The session has changed.
Sys @ Test_lunar> Host Dir E: / Oracle / Admin / Test / UDUMP
The volume in the driver E is Oracle
The serial number of the volume is
707A
-C
50C
E: / Oracle / Admin / Test / UDUMP directory
2002-01-13
21:59
2002-01-13
21:59
2004-05-14
09:06
949 Test_ora_1364.TRC
1 file 949 bytes 2 directory 2,444,263,424 available bytes
Sys @ Test_lunar>
4. Interpret the control file header (Level 1) information from DUMP
The following is the content of TEST_ORA_1364.TRC (23 lines):
(1) Dump file e: /oracle/admin/test/udump/test_ora_1364.trc
(2) Fri May 14
09:06:10
2004
Create a timestamp of a tracking file
(3) Oracle V
9.2.0
.1.0 - Production vsnsta = 0
The current version of the database is V
9.2.0
.1.0
Note: Difference to (18)
(4) vSnsql = 12 vSnXtr = 3???
(5) Windows 2000 Version 5.0 Service Pack 4, CPU Type 586
Current OS information
(6) Oracle9i
Enterprise
Edition Release
9.2.0
.1.0 - Production
(7) with the partitioning, OLAP AND ORACLE DATA MINING OPTIONS
(8) JServer Release
9.2.0
.1.0 - Production
(9) Windows 2000 Version 5.0 Service Pack 4, CPU Type 586
(10) Instance Name: TEST
Instance name is TEST
(11) Redo thread mounted by this instance: 1
This shows that this is a single instance database, the current thread is loaded by instance 1
(12) Oracle Process Number: 13
At present, Oracle's process is 13, this information is the same as the result of select count (*) from V $ Process:
Sys @ Test_lunar> SELECT Count (*) from V $ Process;
Count (*)
------------
13
Sys @ Test_lunar>
(13) Windows Thread Id: 1364, Image: Oracle.exe
This information reflects information on the executable part of the front desk process. Note that Oracle is run as an Oracle.exe process on a Windows platform. So, the executable portion in the front desk is: Oracle.exe; the thread number of the creation of the trace file is 1364 (decimal).
If in UNIX, this part of this information is similar to the following information:
Image: $ 1 $ dua41: [v8root.rdbms] sqlplus.exe; 8
That is, the tracking file is created by the front desk process SQLPLUS.EXE, and its operating system process number (PID) is 8
(14) *** 2004-05-14 09: 06: 10.000
Create a timestamp of a tracking file
(15) *** session ID: (10.9) 2004-05-14 09: 06: 10.000 Create a SID and Serial # of the session of the control file, in this case, SID is 10, serial # is 9, this part of the information can As seen in the V $ Session view.
Sys @ Test_lunar> SELECT SID, Serial #, UserName from V $ Session;
Sid Serial # UserName
---------- ----------------------------------------------------------------------------------------------------------------
1 1
twenty one
3 1
4 1
5 1
6 1
7 1
8 1
9 1
10 9 SYS
10 lines have been selected.
Sys @ Test_lunar>
(16) Dump of control files, SEQ # 2929 = 0xB71
Note This is a dump of a control file. SEQ # is the serial number of the control file, which means that the number of updates to the control file can also be regarded as the version of the control file. 2929 is a 10-based, 0xB71 is a hexadecimal representation. (This line information is the same as the information given by 21 lines)
********* The following content is a general file header information ************
Universal File Header Information should be the same for all data files, control files, and log files in the database.
(17) File header:
(18) Software vsn = 153092096 = 0x9200000, Compatibility VSN = 134217728 = 0x8000000
Point out the version of Oracle when creating a control file, here is 0x9200000, ie,
9.2.0
.
Compatibility VSN pointed out that the compatible version is 0x8000000, ie, 8.0.
Note: Differences with (3) entry
(19) DB ID = 1750352942 = 0x6854442e, db name = 'test1'
DB ID is the database identification number, Oracle is derived from the creation time and database name of the database; DB name is the database name, this example is TEST1.
(20) ACTIVATION ID = 0 = 0x0
(21) Control SEQ = 2929 = 0xB71, File size = 228 = 0xE4
Control SEQ The meaning of 16 line information;
FILE SIZE points out the physical size of the control file, the unit is block,
That is, the actual size of the control file = File size * The size of the data block (DB_BLOCK_SIZE)
(22) File Number = 0, BLKSIZ = 8192, File Type = 1 CONTROL
The file number of the control file is 0, the type is 1;
BLKSIZ corresponds to the size of the operating system data block, 8192K on the Windows platform (if it is a UNIX operating system, the value of BLKSIZ is 512)? ? ?
******************************************************************************************************************************************************* *********
(23) *** End of dump ***
