See "Configure the statement cache for a JDBC data source" in the Oracle WebLogic Server Administration Console Help.Ĭonnection Testing Options for a Data Source You can use the Administration Console to set statement cache options for a data source. Statement Cache Size-The number of statements to store in the cache for each connection. Statement Cache Type-The algorithm that determines which statements to store in the statement cache. Statement cache configuration options include: That is, the statement cache for each connection in a data source uses the statement cache options specified for the data source, but each connection caches it's own statements. However, you configure statement cache options per data source. Reusing prepared and callable statements reduces CPU usage on the database server, improving performance for the current statement and leaving CPU cycles for other tasks.Įach connection in a data source has its own individual cache of prepared and callable statements used on the connection. When an application or EJB calls any of the statements stored in the cache, WebLogic Server reuses the statement stored in the cache. To minimize the processing costs, WebLogic Server can cache prepared and callable statements used in your applications. When you use a prepared statement or callable statement in an application or EJB, there is considerable processing overhead for the communication between the application server and the database server and on the database server itself. Increasing Performance with the Statement Cache