Primary Note on Oracle WebLogic Server JDBC/Database/Drivers Support Patterns
(Doc ID 761097.1)
Last updated on MAY 25, 2021
Oracle WebLogic Server - Version 6.1 and later Information in this document applies to any platform.
This document is a Primary Note referring to support patterns on JDBC and other database resources related issues.
Investigating JDBC Problems
Problems with the configuration of a JDBC datasource or using non-recommended programming techniques can lead to many different issues around the JDBC pool connections, the related databases, or the WebLogic Server instance. Also, the underlying database and network configuration and architecture can lead to issues with JDBC connections. This pattern provides troubleshooting tips for several of these topics and also information on how to investigate JDBC problems further. <Note 1280894.1>
CLOB/BLOB Data Type Handling Issues
WebLogic Server versions that support the JDBC 3.0/4.0 specifications support the use of BLOB (Binary Large Object) and CLOB (Character Large Object) data types. Users face many problems when they use incorrect programming techniques with the above data types. Also, changes in the database driver APIs when migrating from one WebLogic Server version to another leads to incompatible code. This pattern provides some common methodologies that can be followed to troubleshoot CLOB/BLOB problems using the Oracle database. <Note 1332275.1>
Oracle and RAC (Real Application Clusters) Configuration and Testing
Real Application Clusters (RAC) is a quasi High Availability configuration that provides load balancing between nodes in a RAC instance, failover, and scalability of a data base. It provides a way of adding nodes to a database, increasing capacity, and increasing performance. <Note 1148726.1>
Investigating "ORA-01000: maximum open cursors exeeded"
Oracle uses the OPEN_CURSORS parameter to specify the maximum number of open cursors a session can have at once. When this number is exceeded, Oracle reports an ORA-01000 error. When this error is propagated to WebLogic Server, a SQLException is thrown. <Note 1141024.1>
JDBC Causes WebLogic Server Hang
There can be different possible reasons for JDBC calls to lead to a hanging WLS instance, such as the use of DriverManager.getConnection() in JDBC code, long-running SQL queries, hanging database, slow network, application-level deadlock, problems with RefreshMinutes or TestFrequencySeconds settings, and pool shrinking. This pattern addresses troubleshooting for these common problems. <Note 1135278.1>
Investigating JDBC MultiPool Issues in WebLogic Server
WebLogic Server MultiPools are of two distinct types: high availability or load balancing Multipool algorithms. These are mutually exclusive and intended to achieve different goals. This pattern provides information on both algorithms, their limitations, enhancements implemented in different WLS versions, common issues, and answers to frequently asked questions to help you avoid problems. <Note 1148756.1>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!