Under normal circumstances, the steps of adding a data file in the RAC in the naked device environment are:
1. Divide or plan a new partition on each node and hool it with RAW.
2. Establish a link symbol link at each node, allowing database icons to access file systems, visiting naked devices
3. Ensure that both nodes complete the above operation, then create a data file on one of the nodes.
However, if the above operation is not careful, some annoying accidents may occur. If you perform step 3, you should first complete 1, 2 on each node, but if 1, 2 does not perform success in each node, It is only to be successful on the node of the creation of a data file, and other nodes can not find the newly created data file.
What is the remedy? On the node where the data file is found:
1. Hurry up with RAW to hinge the partition
2. Establish a corresponding LINK for partitioning
3, restart the database?
What should I do if I can't restart the database (such as the 24 * 7 system)? Just implementing the above 1, 2 steps, this new node still can't find the newly created data file, will report the following error:
Sun aug 1 10:44:46 2004
Errors in file / opt / oracle / admin / tbdb2 / bdump / tbdb
2in
2_dbw0_1564.trc:
ORA-01186: File 39 Failed Verification Tests
ORA-01157: Cannot Identify / Lock Data File 39 - See Dbwr TRACE FILE
ORA-01110: Data file 39: '/opt/oracle/product/9.2/dbs/tbdb2/tbs_index2_2.dbf'
Sun aug 1 10:44:46 2004
File 39 Not Verified Due To Error ORA-01157
Sun aug 1 10:44:46 2004
Errors in file / opt / oracle / admin / tbdb2 / bdump / tbdb
2in
2_dbw0_1564.trc:
ORA-01157: Cannot Identify / Lock Data File 39 - See Dbwr TRACE FILE
ORA-01110: Data file 39: '/opt/oracle/product/9.2/dbs/tbdb2/tbs_index2_2.dbf'
ORA-27037: UNABLE TO OBTAIN FILE STATUS
Linux Error: 2: No Such File or Directory
AdditionAl Information: 3
How to do it? In fact, it is not difficult to use the backup and recovery approach, OFFLINE-> Recover datafile-> Online, such as
Rman> Connect Target
Rman> Run {
SQL 'ALTER DATABASE DATAFILE 39 OFFLINE';
Recover DataFile 39;
SQL '' ALTER DATABASE DATAFILE 39 Online ';
}
Then, we can access the data file normally, the above execution steps will generate the following corresponding logs in Alert
Completed: Alter Database DataFile 39 Offline
Sun aug 1 15:43:39 2004
Media Recovery DataFile: 39
Media Recovery Start
Starting DataFile 39 Recovery in Thread 2 SEQUENCE 1201
DataFile 39: '/opt/oracle/product/9.2/dbs/tbdb2/tbs_index2_2.dbf'
Media Recovery Log
Recovery Of Online Redo Log: Thread 2 Group 4 SEQ 1201
Reading
MEM 0
MEM # 0 errs 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t2_11.log
MEM # 1 errs 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t2_12.log
Recovery Of Online Redo Log: Thread 1 Group 2 SEQ 1385
Reading
MEM 0
MEM # 0 errs 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t1_21.log
MEM # 1 errs 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t1_22.log
Recovery Of Online Redo Log: Thread 1 Group 3 SEQ 1386
Reading
MEM 0
MEM # 0 Errs 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t1_31.log
MEM # 1 errs 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t1_32.log
Media Recovery Complete
Completed: Alter Database Recover if Needed
DataFile 39
Sun aug 1 15:46:30 2004
Thread 2 Advanced to Log Sequence 1202
Current log # 5 SEQ # 1202 MEM # 0: /opt/oracle/product/9.2/dbs/tbdb2/redo_t2_21.log
Current log # 5 SEQ # 1202 MEM # 1: /opt/oracle/product/9.2/dbs/tbdb2/redo_t2_22.log
Sun aug 1 15:47:10 2004
Alter Database DataFile 39 Online
Sun aug 1 15:47:10 2004
Starting Control AutoBackup
Control Autobackup Written to Disk Device
Handle '/ NetAppdata1 / RManback / TBDB2 / C-1413006996-20040801-05'
Completed: Alter Database DataFile 39 Online
