How to turn on CR4E plugin logging?

Question

<p><font face="arial,helvetica,sans-serif" size="2">Hi,</font></p><p><font face="arial,helvetica,sans-serif" size="2">I am getting the following error when I am designing a report using CLOB field.</font></p><p><font face="arial,helvetica,sans-serif"><font size="2">J</font><font size="2">DBC Error: This operation is not supported.  Caused by: JDBC Error: This operation is not supported.</font><br /></font></p><font face="arial,helvetica,sans-serif" size="2">  Caused by: JDBC Error: This operation is not supported.<br />  Caused by: JDBC Error: This operation is not supported.<br />  Caused by: JDBC Error: This operation is not supported.<br />  Caused by: JDBC Error: This operation is not supported.<br />  Caused by: This operation is not supported.<br />  Plug-in Vendor: Business Objects<br />  Plug-in Name: Crystal Reports Designer Editor Package<br />  Plug-in ID: com.businessobjects.crystalreports.designer.editor<br />  Plug-in Version: 1.0.0.v671<br /></font><p style="text-indent: 6pt" class="MsoNormal"><font face="arial,helvetica,sans-serif" size="2"></font></p><p><font face="arial,helvetica,sans-serif" size="2">First of all, does CR4E support CLOB and BLOB fields?</font></p><p><font face="arial,helvetica,sans-serif" size="2">Second, can I enable CR4E designer plugin logging so I can see more information on what operation the designer is trying to call?</font></p><p><font face="arial,helvetica,sans-serif" size="2">The backend is OpenText DB with Generic JDBC driver.</font></p><p><font face="arial,helvetica,sans-serif" size="2">Thanks,</font></p><p><font face="arial,helvetica,sans-serif" size="2">Tim</font><br /> </p><p> </p><p> </p>

Answer 1

Russ Burkert wrote:
That did not work. There is nothing on the console or any of the logs that is new concerning sql logging. What didn't work?
Added the specified properties to the driver using the console and modified the
commEnv script so wlspy.jar is included in the WEBLOGIC_CLASSPATH. WebLogic was restarted.
However, spy.log is created and at least I can now see some database errors
(ORA-xxxx) coming back from Oracle (which is very helpful). But, no actual SQL in that log, either.
Upon further scrutiny of spy.log, I can see this kind of stuff:
PreparedStatement[35].setString(int parameterIndex, String x)
parameterIndex = 39
x = RN22
OK
All of our database transactions right now are inserts. I see how this maps to the JPA
objects, but it is quite grueling to have to figure out the index/offset of each piece
of data in the object and then cross-reference that to its DB table/column equivalent.
Is there any way to just see a simple INSERT statement somewhere?There has to be INSERT statements in the spy log. They may well be done by PreparedStatements,
which show their SQL once at the prepare, early in the log, and then re-executed indefinitely.
Find the SQL for a given prepared statement so you can know what failed when the XXXth execute()
returns a SQLException.
Joe