Only some application database inserts/updates are updating in the tables
(Doc ID 1275538.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Business Process Management Suite - Version: 5.7 to 10.3
Information in this document applies to any platform.
After enabling JDBC tracing on the Oracle driver (see below how this was done), in the Oracle Trace logs we see the following:
26791187|12/14/2010 10:01:15 AM|0|0|UNKNOWN|commit;
26791188|12/14/2010 10:01:15 AM|0|0|UNKNOWN|
26791188|12/14/2010 10:01:15 AM|0|0|UNKNOWN|delete from "CITRECOVERY"."CIT_TRACKING" where ROWID = 'AAASsOAANAAAACFAAC';
26791189|12/14/2010 10:01:15 AM|0|0|UNKNOWN|rollback;
26791190|12/14/2010 10:01:15 AM|0|0|UNKNOWN|set transaction read write;
As you can see the application performed an insert, but it did not specifically perform a delete by rowid. So it seems the driver is deleting the row right after it has been inserted.
Here is the documentation on how to do it:
I've tested this before by using the tracing jars, the ones with the _g in the filename, downloadable from the oracle website:
you would have to replace the current jar with a trace jar.
Then create a file called OracleLog.properties:
java.util.logging.FileHandler.pattern = jdbc.log
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
add the following properties to the JVM:
and then restart the jvm and search for the file jdbc.log that it should create which should log all of the insertsl.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|