How to turn of debug output from the jdriver for Oracle

Question

We are running our builds with Ant and doing unit-tests with junit/cactus.
The Weblogic jDriver produces what appears to be debug info on standard out which
in turn is captured by junit in xml files reporting errors etc. The problem is that
the WebLogic driver ( WL6.1 SP2) sometimes produces binary 0's ( see below) ending
up in the result xml files, and that Ant's result xml parser cannot handle - (nor
should it ).
This is probably a bug in the c-code for the jdriver , the oci dll ?
Would much appreciate how to turn off the debug(?) logging that the jDriver does:
looks like this (look for the string "[6 binary 0's]"):
Parsing: select length(SYSDATE) from dual
Executing: select length(SYSDATE) from dual
Parsing: select VALUE from V$NLS_PARAMETERS where PARAMETER='NLS_NUMERIC_CHARACTERS'
Executing: select VALUE from V$NLS_PARAMETERS where PARAMETER='NLS_NUMERIC_CHARACTERS'
Done logging in at: 60
Connection: using OCI API: OCI8[6 binary 0's]
Connection successfully established via plain JDBC
DriverManager.getDriver("jdbc:weblogic:oracle:LSS_DBSVC_DEV_autobuild")
trying driver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]
getDriver returning driver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]

Answer 1

Hi Gunnar,
I'd check your code for appearances of "DriverManager.setLogWriter" that set
log writer to System.out. This is the way to get driver's debug output
to standard out.
Regards,
Slava Imeshev
"Gunnar Skogen" <[email protected]> wrote in message
news:3d2972bb$[email protected]..
>
We are running our builds with Ant and doing unit-tests with junit/cactus.
The Weblogic jDriver produces what appears to be debug info on standardout which
in turn is captured by junit in xml files reporting errors etc. Theproblem is that
the WebLogic driver ( WL6.1 SP2) sometimes produces binary 0's ( seebelow) ending
up in the result xml files, and that Ant's result xml parser cannothandle - (nor
should it ).
This is probably a bug in the c-code for the jdriver , the oci dll ?
Would much appreciate how to turn off the debug(?) logging that thejDriver does:
looks like this (look for the string "[6 binary 0's]"):
Parsing: select length(SYSDATE) from dual
Executing: select length(SYSDATE) from dual
Parsing: select VALUE from V$NLS_PARAMETERS wherePARAMETER='NLS_NUMERIC_CHARACTERS'
Executing: select VALUE from V$NLS_PARAMETERS wherePARAMETER='NLS_NUMERIC_CHARACTERS'
Done logging in at: 60
Connection: using OCI API: OCI8[6 binary 0's]
Connection successfully established via plain JDBC
DriverManager.getDriver("jdbc:weblogic:oracle:LSS_DBSVC_DEV_autobuild")
tryingdriver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]
getDriver returningdriver[className=weblogic.jdbc.oci.Driver,weblogic.jdbc.oci.Driver@3383e9]
>
>