ORA-600 [kzaSqlBindLob1], [3237] On Insert After Setting Audit_trail=Db_extended (Doc ID 427798.1)

Last updated on SEPTEMBER 06, 2010

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.2 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.

Symptoms

After setting audit_trail='DB_EXTENDED' and enabling auditing on database objects, the following errors are found in the alert_<sid>.log:

ORA-00600: internal error code, arguments: [kzaSqlBindLob1], [3237], [], [], [], [], [], []
ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (<temp>)
ORA-00001: unique constraint (<constraint_name>) violated

After setting _OPTIM_PEEK_USER_BINDS = false, the error changes to

ORA-00600: internal error code, arguments: [kzaSqlTxtLob1], [3237], [], [], [], [], [], []
ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (<temp>)
ORA-01843: not a valid month

or

ORA-00600: internal error code, arguments: [kzaSqlTxtLob1], [3237], [], [], [], [], [], []
ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (<temp>)
ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc.

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