Connection Multithreaded Usage PROFILE_TYPE_CONN_MT_USAGE_ STR Statement Cache Entry PROFILE_TYPE_STMT_CACHE_ENTRY_STR Statements Usage PROFILE_TYPE_STMT_USAGE_STR
13.2.1.6 Connection Multithreaded Usage PROFILE_TYPE_CONN_MT_USAGE_ STR
Enable connection multithreaded usage profiling to collect information about threads that erroneously use a connection that was previously obtained by a different thread. This information is useful when an application reports a problem that you suspect may have been caused by the simultaneous use of a connection by more than one thread. The record contains the following information: ■ PoolName - name of the data source to which this connection belongs ■ ID - stack trace of the other thread that was found using the connection ■ User - stack trace of the thread that reserved the connection ■ Timestamp - time stamp showing when usage of the connection by multiple threads was detected13.2.1.7 Statement Cache Entry PROFILE_TYPE_STMT_CACHE_ENTRY_STR
Enable statement cache entry profiling to collect information for prepared and callable statements added to the statement cache, and for the threads that originated the cached statements. This information can help you determine how the cache is being used. The record contains the following information: ■ PoolName - name of the data source to which this connection belongs ■ ID - string representation of the statement ■ User - stack trace of the thread using the statement ■ Timestamp - time stamp showing when the statement was added to the cache13.2.1.8 Statements Usage PROFILE_TYPE_STMT_USAGE_STR
Enable statements usage profiling to collect information about threads currently executing SQL statements from the statement cache. This information can help you determine how statements are being used. The record contains the following information: ■ PoolName - name of the data source to which this connection belongs ■ ID - SQL statement being executed via the statement ■ User - stack trace of the thread using the statement ■ Timestamp - duration of statement execution13.2.2 Accessing Diagnostic Data
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to this Document
» Enhanced Oracle RAC Support Reorganization of JDBC Resources
» JDBC System Modules Data Source Configuration Files
» JDBC Application Modules Data Source Configuration Files
» JDBC Module File Naming Requirements JDBC Modules in Versioned Applications JDBC Schema
» Using WLST to Create JDBC System Resources
» Data Source Names JNDI Names Selecting a Database Type Selecting a JDBC Driver
» Configure Transaction Options Creating a JDBC Data Source
» Types of Data Source Pools Using a User NamePassword Set Client ID On Connection
» Fast Connection Failover Runtime Connection Load Balancing
» Configure Transaction Options Creating a GridLink Data Source
» Test Connections Test ONS Client Configuration Target the Data Source
» Using a User NamePassword Set Client ID On Connection
» JDBC Debugging Scopes UCP JDK Logging Enable Debugging Using the Command Line
» Test Connections on Reserve to Enable Fail-Over No Fail-Over for In-Use Connections
» Callback Handler Requirements Callback Handler Configuration
» Administrative Considerations and Limitations for LLR Data Sources
» Database Connection Testing Configuration Recommendations Default Test Table Name
» Connection Reserve Timeout Limiting the Number of Waiting Connection Requests
» Enabling Connection Creation Retries Automatically Recovering Leaked Connections
» Software Requirements JDBC Driver Requirements JDBC Drivers Installed with WebLogic Server
» Enable Debugging Using the Command Line Enable Debugging Using the WebLogic Scripting Tool
» Changes to the config.xml File
» JDBC Debugging Scopes Request Dyeing
» Testing Data Sources and Database Connections Shrinking a Connection Pool
Show more