Problem with logging NClob type value

5 views
Skip to first unread message

Adam Gąsior

unread,
Jun 3, 2022, 12:53:10 PM6/3/22
to p6spy-de...@googlegroups.com

Dear P6Spy Developers,

 

I encountered a problem with logging LOB value defined as procedure/function argument. The following stored procedure is defined in Oracle:

 

procedure execute_sql(p_input in nclob, p_output out nclob, p_status out nclob)

 

With  p_input having the value ‘table_name‘ results in logging (instead of expected ‘table_name‘)

 

    {call execute_sql('java.io.StringReader@15a472f0',NULL,?)}

 

        Connection ID: 928

        Execution Time: 31 ms

        Time: 2022/06/03 15:09:52

 

        Call Stack (number 1 is entry point):

 

Technological stack: Java 11, Spring boot 2, Oracle 19c

 

Spy.properties file:

driverlist=oracle.jdbc.OracleDriver

dateformat=yyyy-MM-dd hh:mm:ss a

appender=com.p6spy.engine.spy.appender.FileLogger

 

Is there any way/workaround to log the NCLOB value properly

 

The question is also posted on Stack Overflow: java - P6spy, log NClob type value - Stack Overflow

Regards,

Adam Gąsior

Director of IT department

mobile. +48 884-304-770 
e-mail : 
aga...@prolan.com.pl
Prolan sp. z o.o. 
44-100 Gliwice ul. Sowińskiego 3 

 

 

 

Reply all
Reply to author
Forward
0 new messages