ORA-00600: [kfgFinalize_2],

ORA-00600: [kfgFinalize_2],

Environment:

OS: OEL5.6

RAC: 10.2.0.1.0

[Root @ rac2 ~] # Crs_stat-t

Name Type Target State Host

------------------------------------------------------------

Ora... B1.inst application ONLINE rac1

Ora... B2.inst application ONLINE OFFLINE

Ora. RACDB. db application ONLINE rac2

Ora... SM1.asm application ONLINE rac1

Ora... C1.lsnr application ONLINE rac1

Ora. rac1.gsd application ONLINE rac1

Ora. rac1.ons application ONLINE rac1

Ora. rac1.vip application ONLINE rac1

Ora... SM2.asm application ONLINE rac2

Ora... C2.lsnr application ONLINE rac2

Ora. rac2.gsd application ONLINE rac2

Ora. rac2.ons application ONLINE rac2

Ora. rac2.vip application ONLINE rac2

The second node instance of rac cannot be started.

Try to start manually

[Oracle @ rac2 ~] $ Export ORACLE_SID = RACDB2

[Oracle @ rac2 ~] $ Sqlplus/as sysdba

 

SQL * Plus: Release 10.2.0.1.0-Production on Thu Aug 21 14:34:44 2014

 

Copyright (c) 1982,200 5, Oracle. All rights reserved.

 

Connected to an idle instance.

 

SQL> startup

ORA-01078: failure in processing system parameters

ORA-01565: error in identifying file '+ DATA/RACDB/spfileRACDB. ora'

ORA-17503: ksfdopn: 2 Failed to open file + DATA/RACDB/spfileRACDB. ora

ORA-15056: additional error message

ORA-17503: ksfdopn: DGOpenFile05 Failed to open file + DATA/racdb/spfileracdb. ora

ORA-17503: ksfdopn: 2 Failed to open file + DATA/racdb/spfileracdb. ora

ORA-15001: diskgroup "DATA" does not exist or is not mounted

ORA-06512: at line 4

No mount is displayed for diskgroup.

Check the diskgroup status under ASM and try to mount

[Oracle @ rac2 ~] $ Export ORACLE_SID = + ASM2

[Oracle @ rac2 ~] $ Sqlplus/as sysdba

 

SQL * Plus: Release 10.2.0.1.0-Production on Thu Aug 21 14:41:59 2014

 

Copyright (c) 1982,200 5, Oracle. All rights reserved.

 

 

Connected:

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-Production

With the Partitioning, Real Application Clusters, OLAP and Data Mining options

 

 

SQL> desc v $ asm_diskgroup;

Name Null? Type

-----------------------------------------------------------------------------

GROUP_NUMBER NUMBER

NAME VARCHAR2 (30)

SECTOR_SIZE NUMBER

BLOCK_SIZE NUMBER

ALLOCATION_UNIT_SIZE NUMBER

STATE VARCHAR2 (11)

TYPE VARCHAR2 (6)

TOTAL_MB NUMBER

FREE_MB NUMBER

Required_pai_free_mb NUMBER

USABLE_FILE_MB NUMBER

OFFLINE_DISKS NUMBER

UNBALANCED VARCHAR2 (1)

COMPATIBILITY VARCHAR2 (60)

DATABASE_COMPATIBILITY VARCHAR2 (60)

 

SQL> select NAME, STATE from v $ asm_diskgroup;

 

NAME STATE

-----------------------------------------

FRA DISMOUNTED

DATA DISMOUNTED

 

SQL> alter diskgroup DATA mount;

Alter diskgroup DATA mount

*

ERROR at line 1:

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

[], []

Reported ORA-600: [kfgFinalize_2]

After online verification:

After the ASM exception crashes, it may cause the first time the ASM instance restarts an exception, reported ORA-600: [kfgFinalize_2]

The final solution is to stop the ASM on all nodes and restart it.

ORA-00600 solution; it's time for ORACLE experts

[Kccpb_sanity_check_2] indicates that seq # of the last read block is
Higher than the seq # of the control file header block. This is indication
The lost write of the header block during commit of the previous cf
Transaction.

Because the database is damaged, the sequence # in the block is incorrect. We recommend that you restore data in the case of backup. Otherwise, you need experts to fix the data. If it is not a production database, we recommend that you recreate it.

Error code parsing for Oracle ORA-00600

The ORA-600 [4137] transaction id does not match, the problem may exist in the rollback segment or the object itself has a rollback error While backing out an undo record (I. e. at the time of rollback) we found a transaction id mis-match indicating either a resume uption in the rollback segment or resume uption in an object which the rollback segment is trying to apply undo records on.
This wocould indicate a random upted rollback segment. Undo/Redo

DESCRIPTION:

While backing out an undo record (I. e. at the time of rollback) we found
Transaction id mis-match indicating either a transaction uption in the rollback
Segment or partition uption in an object which the rollback segment is trying
Apply undo records on.

Patch undo is required to fix this problem.

If you are not sure, contact the professional ORACLE Database repair team of shita software to help you recover it!

Shita software professional database repair team