oracle controlfile might be corrupted(Instance terminated by CKPT)

[Former Member]

hi everyone,

I have come across an oracle crash.

My oracle version is 10.2.0.4 with windows2003

My ERP system version is EHP4/NW7.01

the error info in the alert.log as follow:

******************************************

The controlfile header block returned by the OS

has a sequence number that is too old.

The controlfile might be corrupted.

PLEASE DO NOT ATTEMPT TO START UP THE INSTANCE

without following the steps below.

RE-STARTING THE INSTANCE CAN CAUSE SERIOUS DAMAGE

TO THE DATABASE, if the controlfile is truly corrupted.

In order to re-start the instance safely,

please do the following:

(1) Save all copies of the controlfile for later

analysis and contact your OS vendor and Oracle support.

(2) Mount the instance and issue:

ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

(3) Unmount the instance.

(4) Use the script in the trace file to

RE-CREATE THE CONTROLFILE and open the database.

***********************************************

Mon Nov 02 15:01:51 2009

Instance terminated by CKPT, pid = 3532

And I do have done everything about recreating controlfiles as uppon,but few hours later,the instance terminated too with the same error info.

Did anyone have come acrose with this issues?

Any advise wiil be much appreciated!

Thanks very much

Best regards!

Peter

[Former Member]

Hi,

Please provide the log file for CKPT process.

Thanks,

Shambo

[Former Member]

hi shambo

Thankyou very much!

************************CKPT log*******************

Dump file e:\oracle\ide\saptrace\background\ide_ckpt_3500.trc

Mon Nov 02 20:17:31 2009

ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0

vsnsql=14 vsnxtr=3

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

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

Windows Server 2003 Version V5.2 Service Pack 2

CPU : 1 - type 8664, 1 Physical Cores

Process Affinity : 0x0000000000000000

Memory (Avail/Total): Ph:679M/3583M, Ph+PgF:2572M/11546M

Instance name: ide

Redo thread mounted by this instance: 1

Oracle process number: 8

Windows thread id: 3500, image: ORACLE.EXE (CKPT)

• SERVICE NAME:(SYS$BACKGROUND) 2009-11-02 20:17:30.828

• SESSION ID:(275.1) 2009-11-02 20:17:30.828

• 2009-11-02 20:17:30.828

ksedmp: internal or fatal error

ORA-00600: internal error code, arguments: [kccchb_3], [24426], [24427], [24427], [], [], [], []

check trace file e:\oracle\spa\102\rdbms\trace\ide_ora_0.trc for preloading .sym file messages

-

---

Call Stack Trace -

---

calling call entry argument values in hex

location type point (? means dubious value)

-

---

-

---

-

---

-

---

ksedmp663 CALL??? ksedst55 003C878B8 000000000 00CE5C548

000000000

ksfdmp19 CALL??? ksedmp663 000000003 01972AA70 000000001

003CACC80

kgerinv158 CALL??? ksfdmp19 00000FFFF 000000000 000014238

01972A430

kgeasnmierr62 CALL??? kgerinv158 5B7433B376A5 0FFFFFFFF

00E3B7E14 01973D798

kccchb3018 CALL??? kgeasnmierr62 00001FFE0 000000077 000000002

u2026u2026u2026u2026

Edited by: wang lu on Nov 3, 2009 12:03 AM

[Former Member]

hDump file e:\oracle\spa\102\rdbms\trace\ide_ora_0.trc

Thu Oct 29 20:34:20 2009

ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0

vsnsql=14 vsnxtr=3

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

Windows Server 2003 Version V5.2 Service Pack 2

CPU : 1 - type 8664, 1 Physical Cores

Process Affinity : 0x0000000000000000

Memory (Avail/Total): Ph:2522M/3583M, Ph+PgF:10763M/11546M

Instance name: ide

Redo thread mounted by this instance: 0 <none>

Oracle process number: 0

Windows thread id: 3040, image: ORACLE.EXE

• 2009-10-29 20:34:20.890

===== begin preloading .sym files

===== end preloading .sym files

Dump file e:\oracle\spa\102\rdbms\trace\ide_ora_0.trc

Mon Nov 02 11:01:56 2009

ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0

vsnsql=14 vsnxtr=3

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

Windows Server 2003 Version V5.2 Service Pack 2

CPU : 1 - type 8664, 1 Physical Cores

Process Affinity : 0x0000000000000000

Memory (Avail/Total): Ph:1761M/1999M, Ph+PgF:9955M/10056M

Instance name: ide

Redo thread mounted by this instance: 0 <none>

Oracle process number: 0

Windows thread id: 1200, image: ORACLE.EXE

• 2009-11-02 11:01:56.812

===== begin preloading .sym files

===== end preloading .sym files

Dump file e:\oracle\spa\102\rdbms\trace\ide_ora_0.trc

Mon Nov 02 11:05:59 2009

ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0

vsnsql=14 vsnxtr=3

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

Windows Server 2003 Version V5.2 Service Pack 2

CPU : 1 - type 8664, 1 Physical Cores

Process Affinity : 0x0000000000000000

Memory (Avail/Total): Ph:1761M/1999M, Ph+PgF:9955M/10056M

Instance name: ide

Redo thread mounted by this instance: 0 <none>

Oracle process number: 0

Windows thread id: 1188, image: ORACLE.EXE

• 2009-11-02 11:06:00.046

===== begin preloading .sym files

===== end preloading .sym files

Dump file e:\oracle\spa\102\rdbms\trace\ide_ora_0.trc

Mon Nov 02 11:43:58 2009

ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0

vsnsql=14 vsnxtr=3

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

Windows Server 2003 Version V5.2 Service Pack 2

CPU : 1 - type 8664, 1 Physical Cores

Process Affinity : 0x0000000000000000

Memory (Avail/Total): Ph:3247M/3583M, Ph+PgF:11441M/11546M

Instance name: ide

Redo thread mounted by this instance: 0 <none>

Oracle process number: 0

Windows thread id: 1180, image: ORACLE.EXE

• 2009-11-02 11:43:58.750

===== begin preloading .sym files

===== end preloading .sym files

Edited by: wang lu on Nov 2, 2009 11:57 PM

Edited by: wang lu on Nov 3, 2009 12:01 AM

[stefan_koehler]

Hello Wang,

why opening two threads for the same issue?

ORA-00600: internal error code, arguments: kccchb_3, 24426, 24427, 24427], [, ], [, []

An ORA-00600 and no information available about the code frag "kccchb_3" on windows in metalink or service market place.

Only solution: Open a SR or a SAP call for that error.

Regards

Stefan