OAM RDBMS Auditing Fails With ORA-01036: Illegal Variable Name/Number (Doc ID 727076.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Identity - Version: 10.1.4 and later   [Release: 10g and later ]
Information in this document applies to any platform.
***Checked for relevance on 21-AUG-2010***

Symptoms

OAM auditing to RDBMS database is not working, the entry is not created in the oblix_audit_events table.

The Identity Server oblog.log shows error ORA-01036: illegal variable name/number ; Error Code from OCIErrorGet 1036.


2008/06/26@02:15:01.127612 12339 475165 AUDIT ERROR 0x00001D04 ../dbauditwriter.cpp:611 "The database audit writer was unable to perform the write" sqlError ^Error Record number = 1 Error Message;ORA-01036: illegal variable name/number%0a;Error Code from OCIErrorGet1036

2008/06/26@02:15:01.127860 12339 475165 AUDIT WARNING 0x0000086C obpaudit_handler.cpp:1418 "Unable to write the audit record"

2008/06/26@02:16:15.687521 12333 376855 SQL_ADAPTER ERROR 0x00000070 ../ocierrormap.cpp:53 "OCI SQL statement bind failed" method^OCIAdapter::bindPlaceHolders ociRetCode^OCI_ERROR Diagnostic Record number^1 Error Message^ORA-01036: illegal variable name/number%0a Error Code from OCIErrorGet^1036

2008/06/26@02:16:15.772415 12333 376855 SQL_ADAPTER ERROR 0x00001E10 ../sqlproxy.h:277 "SQL Operation failed. But connection is UP only" function^SQLProxy::handleSQLoperationStatus dbAccessed^true



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