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

[Former Member]

Dear SAP Support

When I am starting the SAP server with command 'startsap' I am getting

following error

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

[0x0A648D6D8],[2], [], [], [], [], []

Please help to resolve the issue

Regards

Dharmendra

[Former Member · Accepted solution]

Dharmendra,

There are a number of bugs in Oracle that causes ORA-00600 error. It all depends on your Oracle version. What version are you using?

Check SAP Note 376755 - ORA-00600 - what to do?

http://www.mydatabasesupport.com/ora-00600-internal-error-code.html

https://metalink.oracle.com/CSP/ui/flash.html#tab=Dashboard(page=Dashboard&id=fv7nl98j()),(page=KBNa...

You can find a corresponding trace file in your bdump directory that will have more information. Then, you can take that ORA-600, login to Metalink (www.metalink.oracle.com), and they have an ORA-600 information tool. That can assist you.

Search Metalink for ORA-00600 error.

Also check syslog and the Oracle alert<SID>.log.

Thanks,

Sushil

Edited by: Sushil Suryawanshi on May 27, 2009 12:37 PM

[Former Member · Accepted solution]

Please try to independently start your database with startup and see if it come up ..

Also please post ur Oracle alert<SID>.log.

[Former Member · Accepted solution]

Thanks guys

I recovered the system from last offline backup. Its up and working fine now.

Regards

Dharmendra

[Former Member]

***

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

***

- Using RMAN, try:

***

RMAN> startup mount;

RMAN> recover database;

***

- Check the alert.log and see on which redo logfile group the recover stops

***

Recovery of Online Redo Log: Thread 1 Group 7 Seq 2033

Mem# 0: <logfile member 0>

Mem# 1: <logfile member 1>

***

- Compare the redo logfiles members (Just to confirm they differ)

diff <logfile member 0> <logfile member 1>

- Put second logfile member unavailable

mv <logfile member 1> <logfile member 1>.ori

- Recover again:

***

RMAN> recover database;

***

- You can see in the alert.log that Oracle is using the remaining redo logfile member

- Try a clean startup now

RMAN> shutdown immediate;

RMAN> startup;

- Remember to recreate the logfile group (or remove/add the logifle member you put unavailable)

SQL> alter database drop logfile group 7;

SQL> alter database add logfile group 7 SIZE <same size as group just removed>K;

Regards,

William Quintero

http://www.linkedin.com/in/williamquintero

[Former Member]

please post the dev_w0 logs for correct error detection

Rohit