Database Connection Monitoring

By default, your application uses a common database userid for accessing the information from the connection pools used by the product (through the Universal Connection Pool (UCP)). While this sufficient for execution of the product, it can complicate monitoring individual connections and troubleshooting database issues with individual users or transactions.

It is possible to show additional details that are inherited from the from the online and Web Services components. The following information is available from the connection and accessible from v$session.

Parameter	Online	Web Service	Batch
CLIENT_IDENTIFIER	Userid	Userid	Userid
MODULE	Service Name	Web Service Name	Batch Control
ACTION	Transaction Type	Transaction Type	Thread Number
CLIENT_INFO	Contents of Database Tag characteristic on User	"Web Service"	Threadpool Name

Note:

Due to the length limitation on CLIENT_IDENTIFIER, the value will be the authorization identifier not the authentication identifier.

For example, the following database query will return the session ids and the users using then at any time:

SELECT sid, client_identifier, module, client_info, action FROM V$SESSION;

The new information can be used to track sessions using the v$session view, use more advanced features of the database and use other database options.