Many Trace Files with Message "Unhandled Datatype (nnn) Found In Kzabndinf" (or Kxsbndinf) Created
Last updated on NOVEMBER 23, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 184.108.40.206 [Release 10.2 to 12.1]
Information in this document applies to any platform.
Checked for relevance on 18-Apr-2013.
This problem can occur on any platform.
When setting up the AUDIT_TRAIL parameter to DB_EXTENDED, there are many trace files with a message like the ones below created in the trace file destination:
Unhandled datatype (nnn) found in kzabndinf
Unhandled datatype (nnn) found in kxsbndinf
where nnn can be any of the following types:
102 - Ref cursor type
112 - CLOB
112 - NCLOB
113 - BLOB
122 - Named collection type (VARRAY or nested table)
or the type associated with a specific user defined data type (to be found in col$ in the type# column).
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