Oracle hint: Adding the wrong raw device causes redo exception resolution

Recently a friend database abnormal, consulting me, through the analysis log found that the other people do not understand the bare devices in Aix and Oracle database and then directly use the OEM to create a new table space, resulting in database crash and not start properly

The code is as follows

Copy Code

Thread 1 advanced to log sequence 4395 Current log# 1 seq# 4395 mem# 0:/dev/rorcl_redo01 Thu June 12 19:28:38 2014 /* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/orcl_redo04 ' SIZE 2000M EXTENT MANAGEMENT Local SEGMENT spaces MANAGEMENT AUTO ORA-1119 signalled during:/* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/orcl_redo04 ' SIZE 2000M EXTENT MANAGEMENT SEGMENT space MANAGEMENT AUTO ... Thu June 12 19:36:23 2014 /* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/orcl_redo03 ' SIZE 2000M EXTENT MANAGEMENT Local SEGMENT spaces MANAGEMENT AUTO Thu June 12 19:43:56 2014 ORA-604 signalled during:/* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/orcl_redo03 ' SIZE 2000M EXTENT MANAGEMENT SEGMENT space MANAGEMENT AUTO ... Thu June 12 19:48:11 2014 /* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/rorcl_redo03 ' SIZE 2000M EXTENT MANAGEMENT Local SEGMENT space MANAGEMENT AUTO Thu June 12 19:48:11 2014 ORA-1537 signalled during:/* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/rorcl_redo03 ' SIZE 2000M EXTENT MANAGEMENT SEGMENT space MANAGEMENT AUTO ... Thu June 12 19:48:20 2014 /* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/rorcl_redo04 ' SIZE 2000M EXTENT MANAGEMENT Local SEGMENT space MANAGEMENT AUTO ORA-1537 signalled during:/* Oracleoem/CREATE smallfile tablespace "Xifenfei" LOGGING datafile '/dev/rorcl_redo04 ' SIZE 2000M EXTENT MANAGEMENT SEGMENT space MANAGEMENT AUTO ... Fri June 13 00:50:37 2014 Trace dumping is performing id=[cdmp_20140613005032] Fri June 13 00:50:40 2014 Reconfiguration started (Old Inc 4, New Inc 6) List of nodes: 0 Global Resource Directory Frozen * Dead instance detected-domain 0 Invalid = TRUE ............ Fri June 13 00:50:40 2014 Beginning instance recovery of 1 threads Reconfiguration complete Fri June 13 00:50:41 2014 Parallel recovery started with 7 processes Fri June 13 00:50:43 2014 Started Redo scan Fri June 13 00:50:43 2014 Errors in FILE/ORACLE/ADMIN/ORCL/BDUMP/ORCL1_SMON_213438.TRC: Ora-00316:log 3 of Thread 2, type 0 in header isn't log file Ora-00312:online Log 3 thread 2: '/dev/rorcl_redo03 ' Fri June 13 00:50:43 2014 Errors in FILE/ORACLE/ADMIN/ORCL/BDUMP/ORCL1_SMON_213438.TRC: Ora-00316:log 3 of Thread 2, type 0 in header isn't log file Ora-00312:online Log 3 thread 2: '/dev/rorcl_redo03 ' Smon:terminating instance due to error 316 Fri June 13 00:50:43 2014 Errors in FILE/ORACLE/ADMIN/ORCL/BDUMP/ORCL1_LGWR_335980.TRC: Ora-00316:log of thread, type in header isn't log file Instance terminated by Smon, PID = 213438

As you can see from here, two errors were made during the use of the OEM to create tablespace
1. The name of the block device and character device that does not distinguish Chu Aix
2. Create a new tablespace for the current redo that 2 nodes are using as a device that does not use the device
The current redo (/dev/rorcl_redo03) of the 2-node is corrupted due to the use of the wrong file and wrong device to create the tablespace (because the redo header is read first, so the priority feedback in the database is Ora-00316:log of thread, Type in header isn't log file. Thus causing the database 2 node to crash first and then node 1 for instance recovery, but since the 2 node's current redo has been corrupted, the instance recovery cannot be completed. Thus two nodes are crash. The database is not functioning because the current redo of one node of the RAC is corrupted.
If there is a backup the database can be recovered using a backup restore, and if no backup can only use the forced Raghu method to salvage the data. Hope not to happen a big data loss tragedy
The introduction of this case would like to give you a warning: the database of raw equipment operation please be cautious, do not know not to disorderly operation, or serious consequences

Contact: Mobile Phone (13429648788) QQ (107644445)

Link: http://www.xifenfei.com/5370.html

Title: Oracle Security Alert: Adding the wrong raw device causes redo anomalies