Feedback
Did this article resolve your question/issue?

   

Article

Performance/latency issue observed when calling a stored procedure.

Information

 
TitlePerformance/latency issue observed when calling a stored procedure.
URL NamePeformance-issue-noticed-when-calling-a-stored-procedure
Article Number000185470
EnvironmentProduct: Connect for JDBC Oracle driver
Version: 5.1
OS: Java
Database: Oracle
Application: All supported applications
Question/Problem Description
Performance/latency issue observed when calling a stored procedure using the Connect for JDBC Oracle driver.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Set MaxPooledStatements to a positive integer that represents a number of prepared statements to be cached.

MaxPooledStatements

Purpose
Specifies the maximum number of prepared statements to be pooled for each connection and enables the driver’s internal prepared statement pooling when set to an integer greater than zero (0). The driver’s internal prepared statement pooling provides performance benefits when the driver is not running from within an application server or another application that provides its own statement pooling.

Valid Values
0 | x

where:
x
is a positive integer that represents a number of prepared statements to be cached.

Behavior

If set to 0, the driver’s internal prepared statement pooling is not enabled.

If set to x, the driver’s internal prepared statement pooling is enabled and the driver uses the specified value to cache up to that many prepared statements created by an application. 

If the value set for this property is greater than the number of prepared statements that are used by the application, all prepared statements that are created by the application are cached. Because CallableStatement is a sub-class of PreparedStatement, CallableStatements also are cached.

Notes
When you enable statement pooling, your applications can access the Statement Pool Monitor directly with DataDirect-specific methods. However, you can also enable the Statement Pool Monitor as a JMX MBean. To enable the Statement Pool Monitor as an MBean, statement pooling must be enabled with MaxPooledStatements and the Statement Pool Monitor MBean must be registered using the RegisterStatementPoolMonitorMBean connection property.

Example
If the value of this property is set to 20, the driver caches the last 20 prepared statements that are created by the application.

Default
0


See our online documentation https://www.progress.com/documentation/datadirect-connectors at :

Oracle database : JDBC driver : User's guide : DataDirect Connect Drivers : Oracle Driver : Connection Properties : MaxPooledStatements
Workaround
Notes
Last Modified Date6/23/2016 1:32 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.