Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to restore Oracle RAC for aix storage double control lock disk leads to ASM control file damage". In daily operation, it is believed that many people have doubts about how to restore ASM control file damage caused by Oracle RAC for aix storage double control lock disk. The editor consulted all kinds of materials and sorted out simple and useful operation methods. I hope it will be helpful for you to answer the question of "how to restore the Oracle RAC for aix storage double control lock disk resulting in the corruption of the ASM control file"! Next, please follow the editor to study!

Failure scenario: AIX IBM storage replaces the storage controller power module, which causes the storage dual control to lose power at the same time, and the locking disk occurs after the storage dual control resumes power supply, and after the IBM is released.

RAC database cannot be started normally. Startup error: ORA-00600: internal error code, arguments: [2131], [33], [32], []

The recovery plan determines that due to the huge amount of damaged database data, as much as 30T, and it is required to open the database as soon as possible, it is acceptable to lose some of the data.

There is a backup of the database. After consultation, the backup control file is used to restore the database and restore the inconsistency of the database.

Recovery process:

1. Pull the backup set of control files from the tape library and restore it to the ASM storage of Oracle RAC database

-- when you try to start the database, you will encounter an error message:

ORA-00600: internal error code, arguments: [3020], [718], [2828551], [3014338823], [], []

ORA-10567: Redo is inconsistent with data block (file# 718, block# 2828551, file offset is unknown bytes)

2. Generate the pfile of Oracle and add the following three parameters

_ allow_resetlogs_corruption=true # skips redo crash and allows resetlogs to open the library

Undo_management=manual # changes undo management to manual management

Event= "10513 trace name context forever,level 2" # Open 10513 event skips consistency verification

* .cluster_database=false

-- at this point, you will encounter an error message when you try to start the database:

ORA-00600: internal error code, arguments: [2662], [3735], [1979553782], [3735], [1979584838], [20971664], [], []

3. After the Oracle database uses backup control files to restore the database, it is necessary to promote the SCN of control files.

The current SCN= of the database 3735.1979584838 = (37354294967296) + 197958483816043682435398

Giga=16043682435398/1024/1024/1024=14941.843=14941

New SCN=14942*1024*1024*1024=16043850334208 that needs to be promoted

Oracle database 10g control file promotion can be added to pfile parameter: _ minimum_giga_scn

ORACLE 11.2.0.4 SCN Propulsion method oradebug

This database control file SCN advance step

SQL > oradebug setmypid

Statement processed.

SQL > oradebug dumpvar sga kcsgscn_

Kcslf kcsgscn_ [700000000019B70, 700000000019BA0) = 00000000 00000000 00000000000000000000000000000000000000000000700000000019850

SQL > oradebug poke 0x700000000019B70 8 16043850334208

BEFORE: [700000000019B70, 700000000019B78) = 00000000 00000000

AFTER: [700000000019B70, 700000000019B78) = 00000E97 80000000

SQL > oradebug dumpvar sga kcsgscn_

Kcslf kcsgscn_ [700000000019B70, 700000000019BA0) = 00000E97 8000000000000000000000000000000000000000000000000000000000000019850

SQL >

-- when you try to start the database, you will encounter an error message:

ORA-00600: internal error code, arguments: [4193], []

The next processing of ORA600 [4193] is the reconstruction of ORACLE rac's undo table space, which needs to be matched with parameters: undo_management and _ CORRUPTED_ROLLBACK_SEGMENTS.

4. After processing ORA600 [4193], the database can be started and opened to open state. At this time, it is best to make a full database backup, if conditions permit.

On rebuilding the database, the failure database is exported logically to guide the new environment. Otherwise, the following error messages will be encountered from time to time in subsequent use:

ORA600 [6122] and ORA600 [KDSGRP1], the actual file is caused by a bad block of index logic, and the related indexes can be rebuilt with drop and create.

At this point, the study on "how to restore the Oracle RAC for aix storage double control lock disk leads to ASM control file corruption" is over. I hope to be able to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.