Shulou(Shulou.com)06/01 Report--

Operating system: RHEL5.8 x64

Database: Oracle 10.2.0.5.0

Failure condition:

A stand-alone dawning PC server 4 300G SAS disks, RAID5 bad two disks (server panel no fault prompt, no one found), causing RAID5 disk array to hang up, the operating system crashed, the system can not boot. After the data recovery company recovers the disk data, the data file is restored and the following error prompt is found when starting the database:

1. Database warning log

Tail-f alert_orcl.log

Database mounted in Exclusive Mode

Completed: ALTER DATABASE MOUNT

Sat Sep 16 02:32:44 CST 2017

ALTER DATABASE OPEN

Sat Sep 16 02:32:44 CST 2017

Beginning crash recovery of 1 threads

Parallel recovery started with 2 processes

Sat Sep 16 02:32:44 CST 2017

Started redo scan

Sat Sep 16 02:32:44 CST 2017

Errors in file / u01/app/oracle/admin/orcl/udump/orcl_ora_27990.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1:'/ u01 thread

ORA-27046: file size is not a multiple of logical block size

Additional information: 1

Sat Sep 16 02:32:44 CST 2017

Aborting crash recovery due to error 313

Sat Sep 16 02:32:44 CST 2017

Errors in file / u01/app/oracle/admin/orcl/udump/orcl_ora_27990.trc:

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1:'/ u01 thread

ORA-27046: file size is not a multiple of logical block size

Additional information: 1

ORA-313 signalled during: ALTER DATABASE OPEN...

two。 Prompt at startup

[oracle@tcdb ~] $sqlplus / as sysdba

SQL*Plus: Release 10.2.0.5.0-Production on 6 02:28:33 2017

Copyright (c) 1982, 2010, Oracle. All Rights Reserved.

Connected to an idle instance.

SQL > startup

ORACLE instance started.

Total System Global Area 1610612736 bytes

Fixed Size 2096632 bytes

Variable Size 553648648 bytes

Database Buffers 1040187392 bytes

Redo Buffers 14680064 bytes

Database mounted.

ORA-00313: open failed for members of log group 3 of thread 1

ORA-00312: online log 3 thread 1:'/ u01 thread

ORA-27046: file size is not a multiple of logical block size

Additional information: 1

SQL >

According to the situation, the database is irregular, the redo file is damaged, and the failure occurs at 7: 00 a. M.

SQL > select open_mode from v$database

OPEN_MODE

-

MOUNTED

SQL > set pagesize 999

SQL > set linesize 200

SQL > alter session set nls_date_format='yyyy-mm-dd hh34:mi:ss'

Session altered.

SQL > select * from v$log

GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIME

-

1 1 3406 52428800 1 NO INACTIVE 187001363 2017-08-20 07:02:30

3 1 3408 52428800 1 NO CURRENT 187084379 2017-08-21 07:03:24

2 1 3407 52428800 1 NO INACTIVE 187044837 2017-08-20 19:40:06

The current log is corrupt

SQL >

SQL > create pfile from spfile

File created.

Add implicit parameters to the pfile:

*. _ allow_resetlogs_corruption=true

*. _ allow_error_simulation=true

SQL > startup mount pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initorcl.ora'

ORACLE instance started.

Total System Global Area 1610612736 bytes

Fixed Size 2096632 bytes

Variable Size 553648648 bytes

Database Buffers 1040187392 bytes

Redo Buffers 14680064 bytes

Database mounted.

Try resetlogs to open the database again

SQL > alter database open resetlogs

Alter database open resetlogs

*

ERROR at line 1:

ORA-01139: RESETLOGS option only valid after an incomplete database recovery

SQL > recover database until cancel

ORA-00279: change 187084379 generated at 08/21/2017 07:03:24 needed for thread 1

ORA-00289: suggestion: / u01/app/oracle/flash_recovery_area/ORCL/archivelog/2017_10_18/o1_mf_1_3408_%u_.arc

ORA-00280: change 187084379 for thread 1 is in sequence # 3408

Specify log: {= suggested | filename | AUTO | CANCEL}

Auto

ORA-00308: cannot open archived log'/ u01 ActionAccord flashbacks recoveryworlareaUniplicorCLarchivelogAccording to 2017, October 10, 18,2017, 1mm, 3408, 3408% upright. Arc'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-00308: cannot open archived log'/ u01 ActionAccord flashbacks recoveryworlareaUniplicorCLarchivelogAccording to 2017, October 10, 18,2017, 1mm, 3408, 3408% upright. Arc'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below

ORA-01194: file 1 needs more recovery to be consistent

ORA-01110: data file 1:'/ u01 *

SQL > alter database open resetlogs

Alter database open resetlogs

*

ERROR at line 1:

ORA-00603: ORACLE server session terminated by fatal error

The alter log reports the following error:

Wed Oct 18 03:06:38 CST 2017

Errors in file / u01/app/oracle/admin/orcl/udump/orcl_ora_18057.trc:

ORA-00600: internal error code, arguments: [2662], [0], [187086068], [0], [187092671], [8388617], [], []

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00600: internal error code, arguments: [2662], [0], [187086066], [0], [187092671], [8388617], [], []

Wed Oct 18 03:06:39 CST 2017

Errors in file / u01/app/oracle/admin/orcl/udump/orcl_ora_18057.trc:

ORA-00600: internal error code, arguments: [2662], [0], [187086069], [0], [187092671], [8388617], [], []

ORA-00600: internal error code, arguments: [2662], [0], [187086068], [0], [187092671], [8388617], [], []

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00600: internal error code, arguments: [2662], [0], [187086066], [0], [187092671], [8388617], [], []

Wed Oct 18 03:06:40 CST 2017

Errors in file / u01/app/oracle/admin/orcl/udump/orcl_ora_18057.trc:

ORA-00600: internal error code, arguments: [2662], [0], [187086069], [0], [187092671], [8388617], [], []

ORA-00600: internal error code, arguments: [2662], [0], [187086068], [0], [187092671], [8388617], [], []

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00600: internal error code, arguments: [2662], [0], [187086066], [0], [187092671], [8388617], [], []

[2662] SCN needs to be pushed to bring SCN to a consistent state.

SQL > conn / as sysdba

Connected to an idle instance.

SQL > startup mount pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initorcl.ora'

ORACLE instance started.

Total System Global Area 167772160 bytes

Fixed Size 1272600 bytes

Variable Size 96470248 bytes

Database Buffers 67108864 bytes

Redo Buffers 2920448 bytes

Database mounted.

SQL > alter session set events' 10015 trace name adjust_scn level 1'

Session altered.

SQL > alter database open

Database altered.

Note: two parameters, create spfile from pfile, should be removed after that.

When the database starts normally, the current redo log is damaged, which will theoretically cause data loss. Considering that no business data is generated by the application at 7: 00 in the morning, and the observation application and test function are normal, the database is not logically rebuilt.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.