ORA-600 [13080] WHEN ENABLING A CONSTRAINT WITH SUPPLEMENTAL LOGGING

(Doc ID 1060694.1)

Last updated on SEPTEMBER 04, 2015

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.8 to 11.1.0.7 [Release 9.2 to 11.1]
Information in this document applies to any platform.

Symptoms

When adding supplemental logging to any table, number of internal constraints are being created (system generated).

SQL> alter table scott.emp add supplemental log data (all) columns;
 .
 Table altered.
 .
 SQL> select CONSTRAINT_NAME, status from dba_constraints where
 table_name='EMP';
 .
 CONSTRAINT_NAME STATUS
 ------------------------------ --------
 SYS_C003945 ENABLED
 *SYS_C004535 DISABLED*
 SYS_C004534 DISABLED
 .
 SQL> select log_group_name, log_group_type, generated from all_log_groups
 where table_name='EMP';
 .
 LOG_GROUP_NAME LOG_GROUP_TYPE GENERATED
 ------------------------------ ------------------- --------------
 *SYS_C004535 ALL COLUMN LOGGING GENERATED NAME*
 SYS_C004534 PRIMARY KEY LOGGING GENERATED NAME
 EMPGRP2 USER LOG GROUP USER NAME


Those constraints are by defaults visible in dba_constraints view, thus any user with enough privilege is able to disable, enable, and even drop them. These actions are not supported on this type of constraints, but the action is still possible, the following error occur when trying to enable them:

ORA-600: internal error code, arguments: [13080], [], [], [], [], [], [], []

 

Changes

Any manual altering of the logminer constraints mentioned above.

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