JDBC Debugging Scopes UCP JDK Logging Enable Debugging Using the Command Line

Using GridLink Data Sources 4-13

4.10 Monitoring GridLink JDBC Resources

The following sections include details about monitoring GridLink JDBC objects: ■ Section 4.10.1, Viewing Run-Time Statistics ■ Section 4.10.2, Debug GridLink Data Sources. For more information on JDBC monitoring, see Section 13, Monitoring WebLogic JDBC Resources.

4.10.1 Viewing Run-Time Statistics

You can view run-time statistics for a GridLink data source via the Administration Console or through the associated runtime MBeans.

4.10.1.1 JDBCOracleDataSourceInstanceRuntimeMBean

The JDBCOracleDataSourceInstanceRuntimeMBean provides methods for getting the current state of the data source instance. For more information, see JDBCOracleDataSourceInstanceRuntimeMBean in the Oracle WebLogic Server MBean Reference.

4.10.1.2 JDBCDataSourceRuntimeMBean

The JDBCDataSourceRuntimeMBean provides methods for getting the current state of the data source instance. The JDBCDataSourceRuntimeMBean provides methods for getting the current state of the data source and for getting statistics about the data source, such as the average number of active connections, the current number of active connections, and the highest number of active connections. For more information, see JDBCDataSourceRuntimeMBean in the Oracle WebLogic Server MBean Reference.

4.10.1.3 ONSDaemonRuntimeMBean

The ONSDaemonRuntimeMBean provides methods for monitoring the ONS client configuration that is associated with a GridLink data source For more information, see ONSDaemonRuntimeMBean in the Oracle WebLogic Server MBean Reference.

4.10.2 Debug GridLink Data Sources

You can activate WebLogic Servers debugging features to track down the specific problem within the application

4.10.2.1 JDBC Debugging Scopes

The following are registered debugging scopes for JDBC: ■ DebugJDBCRAC scope weblogic.jdbc.racl - prints information about GridLink data source lifecycle, UCP callback, and connection information. ■ DebugJDBCONS scope weblogic.jdbc.connection - traces ONS client information, including the LBA event body. Note: Set Client ID On Connection and Enable Identity Based Connection Pooling are mutually exclusive. If you think you need both mechanisms to pass security credentials in your application environment, create separate data sources—one for with Set Client ID On Connection and one with Enable Identity Based Connection Pooling. 4-14 Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server

4.10.2.2 UCP JDK Logging

You can enable UPC JDK logging by following the instructions at http:download.oracle.comdocscdB28359_ 01java.111e10788get_started.htmsthref67 .

4.10.2.3 Enable Debugging Using the Command Line

Set the appropriate GridLink data source debugging properties on the command line. For example, -Dweblogic.debug.DebugJDBCRAC=true -Dweblogic.debug.DebugJDBCONS=true -Dweblogic.debug.DebugJDBCUCP=true This method is static and can only be used at server startup. 5 Configuring JDBC Multi Data Sources 5-1 5 Configuring JDBC Multi Data Sources A multi data source is an abstraction around a group of data sources that provides load balancing or failover processing at the time of connection requests, between the data sources associated with the multi data source. Multi data sources are bound to the JNDI tree or local application context just like data sources are bound to the JNDI tree. Applications lookup a multi data source on the JNDI tree or in the local application context java:compenv just as they do for data sources, and then request a database connection. The multi data source determines which data source to use to satisfy the request depending on the algorithm selected in the multi data source configuration: load balancing or failover. This section includes the following information: ■ Section 5.1, Multi Data Source Features ■ Section 5.2, Creating and Configuring Multi Data Sources ■ Section 5.3, Choosing the Multi Data Source Algorithm ■ Section 5.4, Multi Data Source Fail-Over Limitations and Requirements ■ Section 5.5, Multi Data Source Failover Enhancements ■ Section 5.6, Deploying JDBC Multi Data Sources on Servers and Clusters

5.1 Multi Data Source Features

A multi data source can be thought of as a pool of data sources. Multi data sources are best used for failover or load balancing between nodes of a highly available database system, such as redundant databases or Oracle Real Application Clusters Oracle RAC. The data source member list for a Multi data source supports dynamic updates. This allows environments, such as those using Oracle RAC, to add and remove database nodes and corresponding data sources without redeployment and provide the ability to: ■ Grow and shrink Oracle RAC clusters in response to throughput. See Section 5.1.2, Adding a Database Node. ■ Shutdown Oracle RAC nodes for maintenance. See Section 5.1.1, Removing a Database Node. See Section B, Using Multi Data Sources with Oracle RAC.