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

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.2.0.1.0 - Release: 11.1 to 11.2
Information in this document applies to any platform.

Symptoms

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>"

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms