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

In the previous blog post, we explained in detail how to simulate ORA-600 [2662] error: ORA-600 [2662] error simulation

Next, let's briefly introduce how to solve the problem of 2662.

Thu Aug 01 10:50:36 CST 2013

Errors in file / oracle/app/admin/test/bdump/test_smon_14956.trc:

ORA-00600: internal error code, arguments: [2662], [0], [469288], [0], [20502828], [4194344], [], []

Thu Aug 01 10:50:36 CST 2013

Errors in file / oracle/app/admin/test/udump/test_ora_15243.trc:

ORA-00600: internal error code, arguments: [2662], [0], [469295], [0], [20502828], [4194344], [], []

Thu Aug 01 10:50:39 CST 2013

Errors in file / oracle/app/admin/test/udump/test_ora_15243.trc:

ORA-00600: internal error code, arguments: [2662], [0], [469295], [0], [20502828], [4194344], [], []

Error 600 happened during db open, shutting down database

USER: terminating instance due to error 600

Instance terminated by USER, pid = 15243

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

Thu Aug 01 10:50:40 CST 2013

Errors in file / oracle/app/admin/test/udump/test_ora_15243.trc:

ORA-00600: internal error code, arguments: [opiodr: call 2], []

ORA-27300: OS system dependent operation:semctl failed with status: 22

ORA-27301: OS failure message: Invalid argument

ORA-27302: failure occurred at: sskgpwpost1

ORA-27303: additional information: semid = 1572871

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00600: internal error code, arguments: [2662], [0], [469295], [0], [20502828], [4194344], [], []

Because the parameters of 2662 are as follows: ORA-600 [2662] [A] [B] [C] [D] [E]

ARGUMENTS:

Arg [a] Current SCN WRAP

Arg [b] Current SCN BASE-(that is, select checkpoint_change# from v$database) can also be understood as current SCN

Arg [c] dependent SCN WRAP

Arg [d] dependent SCN BASE, that is, the SCN b and d of the data block in which the current error occurs, is the scn difference generated by 2662.

Arg [e] Where present this is the DBA where the dependent SCN came from. -that is, the DBA corresponding to the exception problem

The parameter format of ORA-600 is as follows:

Arg [a] Current SCN WRAP

Arg [b] Current SCN BASE

Arg [c] dependent SCNWRAP

Arg [d] dependent SCN BASE

Arg [e] Where present this is the DBA wherethe dependent SCN came from.

ORA-00600: internal error code, arguments: [2662], [0], [1073748930], [0], [1073945531], [4194364], [], []

1) calculate level

1. 1) Arg {c} * 4 gives a value, assuming V_Wrap

1.2) if Arg [d] = 0, then the VWrapvalue is the required level

Arg [d]

< 1073741824，V_Wrap+1为需要的level Arg [d] < 2147483648，V_Wrap+2为需要的level Arg [d] < 3221225472，V_Wrap+3为需要的level 本次我通过添加事件和隐含参数来解决2662 问题： [oracle@s1-10g lib]$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.5.0 - Production on Thu Aug 1 11:46:08 2013 Copyright (c) 1982, 2010, Oracle. All Rights Reserved. Connected to an idle instance. SQL>

Startup mount

ORACLE instance started.

Total System Global Area 1610612736 bytes

Fixed Size 2096632 bytes

Variable Size 385876488 bytes

Database Buffers 1207959552 bytes

Redo Buffers 14680064 bytes

Database mounted.

SQL > alter system set "_ allow_error_simulation" = true scope=spfile

Under Oracle 9i, you can add SCN by directly using the alter session command. But below Oracle 10g, you also need to modify the implicit parameter: _ allow_error_simulation, and set it to true in order to really improve scn.

SQL > startup mount force

ORACLE instance started.

Total System Global Area 1610612736 bytes

Fixed Size 2096632 bytes

Variable Size 385876488 bytes

Database Buffers 1207959552 bytes

Redo Buffers 14680064 bytes

Database mounted.

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

Session altered.

SQL > alter database open

Database altered.

Observe the background log:

Thu Aug 01 11:47:14 CST 2013

Thread 1 advanced to log sequence 17 (thread open)

Thread 1 opened at log sequence 17

Current log# 2 seq# 17 mem# 0: / home/oradata/test/redo02.log

Successful open of redo thread 1

Thu Aug 01 11:47:14 CST 2013

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Debugging event used to advance scn to 1073741824

Thu Aug 01 11:47:14 CST 2013

SMON: enabling cache recovery

Thu Aug 01 11:47:14 CST 2013

Successfully onlined Undo Tablespace 1.

Thu Aug 01 11:47:14 CST 2013

SMON: enabling tx recovery

Thu Aug 01 11:47:15 CST 2013

Database Characterset is ZHS16GBK

Original blog address: http://blog.itpub.net/23732248/

Original author: Ying Feng (frank-ying)

-

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.