My Oracle Support Banner

Ora-600 [Kqdobu:Upd-Nex_status] (Doc ID 1138153.1)

Last updated on OCTOBER 11, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


Get ora-600 [kqdobu:ins-nex_status] error when creating an object for which a synonym used to exist.

This error can be seen for example on import:

ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-00600: internal error code, arguments: [kqdobu:upd-nex_status], [0x4BE6A64A0], [298], [76743], [99], [ERR$DP014801B20001], [10], [5], [0], [2614561999], [], []
ORA-06512: at "SYS.KUPW$WORKER", line 1714
ORA-06512: at line 2

The trace file for ORA-600 [kqdobu:upd-nex_status] shows something like:

========= Dump for incident 19515 (ORA 600 [kqdobu:upd-nex_status]) ========

dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=c8ghj5r8d76jq) -----
CREATE TABLE "<owner>"."<table name>"


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.