Logging The Call Statement When The Oracle Adapter Invokes An Oracle Stored Procedure. (Doc ID 1425566.1)

Last updated on NOVEMBER 02, 2016

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.2 and later
Information in this document applies to any platform.
****Checked fore relevance on 14-Oct-2013****

Symptoms

In Java CAPS 5.1.3 it was possible to trace the call statement when the Oracle Adapter invoked an Oracle Stored Procedure.

For example, given the table and procedure:

create table tracetab (col1 varchar(10));
create procedure traceproc as
begin
insert into tracetab values ('AAA');
end;


and the JCD code to execute the procedure:

otdTraceProc_1.getTRACEPROC().execute();
otdTraceProc_1.commit();


the application server log file includes the following output showing the call statement when the JCD is executed:

[#|2011-11-11T15:40:22.843+0000|FINE|IS5.1.3|STC.eWay.DB.Oracle.com.stc.connector.oracleadapter.base.PreparedStatementAgentImpl|_ThreadID=48; ThreadName=Worker: 10; Context=project=prjExecOrclProc,deployment=dpOrclProc,collab=CMap1_jcdTraceProc1,external=File1;|{ call TRACEPROC()}|#]

However, if this JCD is executed on Java CAPS 6.2 the above trace message is not logged.

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