ORA-600 ktagetg can’t be used for a DDL

Not much to say.

So far been unable to prove my fledgling theory via an isolated test case, but if someone else gets this error, then this post might at least provide a possible resolution.

Background is that release scripts failed to create a materialized view at time T1 due to dependent object not existing, @ T2 revised release scripts failed repeatedly with:

ORA-00600: internal error code, arguments: [ktagetg can't be used for a DDL.], [], [], [], [], [], [], []


No published matches via metalink ORA-600 lookup.

Resolution, in my particular circumstances, was to create a dummy materialized view with the same name but with a much simpler definition, drop it and then recreate via the original script. The creating and dropping cleaned up/out something that wasn’t otherwise being cleaned out.

Also on metalink, a useful article here (175982.1), including information on error lookups by mnemonic – ktagetg as in “ORA-00600: internal error code, arguments: [ktagetg can’t be used for a DDL.]” stands for “Kernel Transaction Access Get Generic DML lock” and the kta module provides “support for DML locks and temporary tables associated with table access”.

About these ads

One Response to ORA-600 ktagetg can’t be used for a DDL

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 72 other followers

%d bloggers like this: