If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Its possible to create types in Oracle, and it is possible to write PL/SQL code behind the type. If you wrote a type named kzabndinf and that type is causing unhandled errors, then maybe you would get the behavior that you describe. So look in the database and find an object with the name kzabndinf and see what type of object it is and whether or not it is in an invalid state.

I don't think that this is something native to Oracle, but with the sparse information that you give, it could be.

I have received a reply from Oracle and here it is, just wanted to share with u all

Hi,

this is because of auditing with binds in either Standard Auditing
(audit_trail = DB_EXTERNAL) or Fine Grained Auditing with
audit_trail => DBMS_FGA.DB_EXTENDED, the 'kzabndinf' is an internal
module that is supposed to translate the bind values to a readable
string, the problem is it does not support all datatypes,
datatype 121 is 'DTYADT' which is some sort of object type.
In that case it writes this message to a trace file.

This is expected behavior, it's not a bug. It's likely that in future
releases we'll enhance the auditing system to be able to capture
binds of any type.