Significant Throughput Degradation When getParameterMetadata is Called on Every PreparedStatement
(Doc ID 2169848.1)
Last updated on MARCH 18, 2019
Applies to:JDBC - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In a JDBC application, getParameterMetadata is called on every PreparedStatement.
The JDBC application experiences significant throughput degradation during performance test.
Symptoms may include:
- The JDBC application encounters no errors on the client side. If errorstack is set for error such as ORA-904 or ORA-918, it is seen that SQL statements fail with those parse errors on the server side:
----- Error Stack Dump -----
ORA-00904: "<COLUMN_NAME>": invalid identifier
----- Current SQL Statement for this session (sql_id=29s22pyghmf9b) -----
SELECT <COLUMN_NAME> FROM <TABLE_NAME>
- High "library cache lock" and "library cache: mutex X" waits under the "Top 10 Foreground Events by Total Wait Time" section of AWR:
The problem appears after upgrading JDBC driver to 12.1.0.x and applying merge patch containing fix for Bug 18644587.
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