Using Oracle 19c JDBC driver and 10.7 HF85 which supports this to address issues with Unknown SQL
Previously Unknown sql was related to the following class: oracle.jdbc.driver.T4CPreparedStatement .
Now, there are unknown sql with stored procedures related to the following class: oracle.jdbc.driver.T4CCallableStatement.
This is for an application running in Weblogic for an application deployed in Oracle Webcenter sites.
It is apparent that statement->sql-string mapping tracer did not see callable statement and thus it could not return normalized sql statement for metric naming purpose.
This could happen if an oracle specific, non-standard method of db connection was called to create CallableStatement instance.
Release : 10.7.0
Component : Introscope
These are suggestions that can be applied to any agent that already supports Oracle 19c, this includes 10.7 HF85 and 21.3 and higher
1. Append following directives to wily/releases/<release>/core/
TraceOneMethodWithParametersIf
#
#
2. Test with the initial configuration, if there are still Unknown SQL metrics returned, please uncomment the two commented lines as well
TraceOneMethodWithParametersIf
TraceOneMethodWithParametersIf
TraceOneMethodWithParametersIf