0% found this document useful (0 votes)
340 views4 pages

Database Startup Fails With ORA-00600: Internal Error Code, Arguments: (kdsgrp1) (Doc ID 2237293.1)

Uploaded by

Nikhil Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
340 views4 pages

Database Startup Fails With ORA-00600: Internal Error Code, Arguments: (kdsgrp1) (Doc ID 2237293.1)

Uploaded by

Nikhil Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Document 2237293.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=54...

Last Login:
PowerView February 10, 2022 8:21 AM EST Switch to Cloud Support
is Off Gourav (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates Community

Give Feedback...
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

Database Startup Fails with ORA-00600: internal error code, arguments: [kdsgrp1] (Doc ID 2237293.1) To Bottom

In this Document Was this document helpful?

Symptoms Yes
No
Changes
Cause
Document Details
Solution
References
Type:
PROBLEM
Status:
PUBLISHED
Last Major
Aug 4, 2018
Update:
Jan 4, 2021
Last Update:
APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later Related Products
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database - Enterprise
Oracle Database Exadata Cloud Machine - Version N/A and later Edition
Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Database Cloud Schema
Oracle Cloud Infrastructure - Database Service - Version N/A and later Service
Information in this document applies to any platform. Gen 1 Exadata Cloud at
Customer (Oracle Exadata
Database Cloud Machine)
SYMPTOMS Oracle Database Exadata
Express Cloud Service
Oracle Cloud Infrastructure -
Database Service
Show More
Database startup Fails with ORA-00600: internal error code, arguments: [kdsgrp1] and ORA-1092

Information Centers

Total System Global Area 1068937216 bytes 19c Database Self-Guided


Upgrade with Best Practices
Fixed Size 2235208 bytes [1919.2]
Variable Size 784336056 bytes
Database Buffers 276824064 bytes Information Center:
Transportable Tablespaces
Redo Buffers 5541888 bytes
(TTS) for Oracle Database
Database mounted. [1461278.2]
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], Index of Oracle Database
Information Centers
[], [], [], [], []
[1568043.2]
Process ID: 1747472
Session ID: 265 Serial number: 3 インフォメーション・セン
ター: データベースおよび
Enterprise Manager 日本語ド
キュメント [1946305.2]

Information Center: Data


Warehousing [1487754.2]
Alert log shows the below information Show More

Document References
Collecting Diagnostics for
Oracle Support [411.1]

Recently Viewed

Incorrect validation rule


appears to the copied E2B
R3 (V3.0) message profile
[2360835.1]
Use of EDQM Terminologies
for Dose Forms (DF) and
Routes of Administration
(ROA) [2830452.1]
Workaround for ICSR Check
Validation Errors on LAB
TEST Units for OOB MFDS
profile [2794956.1]
Optional Validaition Not
Allowing R3 E2B Reports To
Generate. [2669868.1]

1 of 4 04-03-2022, 06:16 pm
Document 2237293.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=54...

Update the EMA R3 Profile


Errors in file /app/ora/local/admin/test/diag/rdbms/test/trace/test_ora_3326715.trc (incident=29018): Conformance Rule to Apply
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], [] Reporter Country EU
Incident details in: /app/ora/local/admin/test/diag/rdbms/test/incident/incdir_29018/test_ora_3326715_i29018.trc [2561695.1]
Sat Feb 18 19:50:56 2017 Show More
Dumping diagnostic data in directory=[cdmp_20170218195056], requested by (instance=1, osid=3326715), summary=
[incident=29017].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Undo initialization errored: err:600 serial:0 start:629908304 end:629912594 diff:4290 (42 seconds)
Errors in file /app/ora/local/admin/test/diag/rdbms/test/trace/test_ora_3326715.trc:
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Errors in file /app/ora/local/admin/test/diag/rdbms/test/trace/test_ora_3326715.trc:
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER (ospid: 3326715): terminating the instance due to error 600
Instance terminated by USER, pid = 3326715
ORA-1092 signalled during: ALTER DATABASE OPEN...
opiodr aborting process unknown ospid (3326715) as a result of ORA-1092
Sat Feb 18 19:50:57 2017
ORA-1092 : opitsk aborting process

Call stack :-ktgRunStmt1 ktsmg_summary_tur ktsmg_summary_undoinfo ktusmout_online_ut ktusmiut_init_ut

CHANGES

CAUSE

Error is reporting while query Undo stat information during the startup.

ORA-00600: internal error code, arguments: [kdsgrp1] is reported when an inconsistency is found between the table and its
related indexes

SOLUTION

Step 1 : Identify the affected Object

Trace file would have information like Below

*** 2017-02-18 20:31:44.677


* kdsgrp1-1: *************************************************
row 0x0080402f.18 continuation at
0x0080402f.18 file# 2 block# 16431 slot 24 not found ---> relative file no and block number reported
KDSTABN_GET: 0 ..... ntab: 1
curSlot: 24 ..... nrows: 66
kdsgrp - dump CR block dba=0x0080402f
Block header dump: 0x0080402f
Object id on Block? Y
seg/obj: 0x194e csc: 0xa3f.d9aa0b09 itc: 2 flg: E typ: 1 - DATA
brn: 1 bdba: 0x801680 ver: 0x01 opc: 0

So in this case the ORA-600 is raised in rfile # --> 2 and block # 16431.

The relative file no(rfile#) for this file is 2 ,but the absolute file no (file#) may be different.

Run the below to confirm both are same

Select file#,name from v$datafile where rfile#=2 ;

We will be using the value of file# and block no in Step 5 to identify the object involved

Step 2 :- No mount the database and create a pfile

SQL>Startup nomount ; -----------------> Here we are using spfile. If you are using pfile go to step 3

SQL>Create pfile='/tmp/corrupt.ora' from spfile ;

SQL>Shutdown immediate ;

2 of 4 04-03-2022, 06:16 pm
Document 2237293.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=54...

Step 3 :- In pfile created add the below parameters

Add these parameters at the end of the pfile

_smu_debug_mode=1024;
_rollback_segment_count=1
undo_management=manual;

Step 4 :- Startup restrict mount and open with this pfile

SQL>Startup restrict mount pfile=/tmp/corrupt.ora

SQL>Show parameter undo

SQL>Alter database open ;

Step 5 :- Now identify the object involved

Query would be

SELECT segment_type, owner, segment_name


FROM dba_extents
WHERE file_id = <file number>
AND <block number> BETWEEN block_id and block_id+blocks-1;

File number(file#) and block number you get from Step 1

So in our example its

SQL>Select segment_name,segment_type,owner from dba_extents where file_id=2 and 16431 between block_id and block_id +
blocks -1 ;

Check if this returns object as WRH$_UNDO Go to Step 6. If it returns a different object and its a sys object open a Service
request with Oracle support else go to next step(step 6) for non sys objects

Step 6 :-Analyze the output involved to check for any corruption in Index

SQL>Analyze table <owner>.WRH$_UNDO validate structure online ;

If this comes out clean

SQL>Analyze table <owner>.WRH$_UNDO validate structure cascade online ;

This will fail with ora-1499

Rebuild the Index online

Alter index WRH$_UNDOSTAT_PK rebuild online ;

Re-run

SQL>Analyze table <owner>.WRH$_UNDO validate structure cascade online ;

If this comes out clean go to step 7 . If this still fails with Ora-1499 then go to below step

a> Alter table wrh$_undostat disable constraint WRH$_UNDOSTAT_PK;

Alter table wrh$_undostat enable constraint WRH$_UNDOSTAT_PK;

3 of 4 04-03-2022, 06:16 pm
Document 2237293.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=54...

SQL>Analyze table <owner>.WRH$_UNDO validate structure cascade online ;

If this comes out clean

Step 7 :-

SQL>Shutdown immediate ;

SQL>Startup --------------> Using your spfile

Check the alert log for any errors

REFERENCES

NOTE:411.1 - Collecting Diagnostics For Oracle Support


Didn't find what you are looking for? Ask in Community...

Related
Products
Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition > Corruption > Undo Corruption
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Schema Service
Oracle Cloud > Oracle Infrastructure Cloud > Oracle Cloud at Customer > Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine)
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Exadata Express Cloud Service
Oracle Cloud > Oracle Platform Cloud > Oracle Cloud Infrastructure - Database Service > Oracle Cloud Infrastructure - Database Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Backup Service > Oracle Database Backup Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Exadata Service > Oracle Database Cloud Exadata Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Service

Back to Top
Copyright (c) 2022, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

4 of 4 04-03-2022, 06:16 pm

You might also like