Mar 31st, 2011, 01:22 PM
redundant metadata sql in SimpleJdbcCall
UPDATE: looks like this is an issue with ojdbc6 and ojdbc5. with ojdbc5 it looks gud, but with ojdbc6 the way we retrieve metadata of a cursor is causing lot of sql executions and response time increase.
the spring framework jdbcTemplate also uses the same code in queryForList() call impl.
Is there a way to disable multiple metadata sql runs from spring whenever we use SimpleJdbcCall for invocation.
The metadata is required but can be cached once for deployement as it doesnt change in our system frequently.
These sql's are causing db load.
Last edited by snukala; Apr 5th, 2011 at 02:15 PM.
Reason: update about ojdbc6 and ojdbc5
Aug 31st, 2011, 11:30 AM
Please inform me if you have come to a solution
I have the same issues.
In addition, doExecute which invokes checkCompiled changes the "isCompiled" field of AbstractJdbcCall - hence, SimpleJdbcCall is not thread safe!!
Please inform on how you managed to cache these redundant SQLs