Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Monitoring: Alert Codes for Database Adapters
 

Classic Java CAPS

Using Enterprise Manager Management Applications in Java CAPS

Monitoring Java CAPS Business Processes

Alert Codes for Java CAPS Adapters

Alert Codes Overview

Alert Codes Task Overview

Viewing Alert Codes

To View the Sun Adapter Alert Codes

Alert Codes for Application Adapters

Alert Codes for Communication Adapters

Alert Codes for Database Adapters

Alert Codes for Web Adapters

Alert Codes and Error Messages for Sun Master Index (Repository)

Java EE Based Components

Monitoring Java EE Components

Alert Codes for Database Adapters

You can view alerts by using the Enterprise Manager. For details, refer To View the Sun Adapter Alert Codes.

Database Adapter Alert Codes

Sun Adapter Name
Alert Code
Description
User Action
Database Adapters
  • DB2 Connect

  • DB2 Universal

  • Informix

  • JDBC/ODBC

  • Oracle

  • SQL Server

  • Sybase

  • VSAM

DBCOMMON-CONNECTFAILED000001= Failed to connect to database {0} on host {1}. Reason: The Pooled connection could not be allocated: [{2}]
Occurs during the initial database connection.
  • Database is down; start the database.
  • External configuration information is invalid. You may need to verify the following:

    • Server name

    • Database name

    • User

    • Password

    • Port

DBCOMMON-CONNECTFAILED000002= Operation failed because of a database connection error. Reason: [{0}]
Occurs while retrieving a connection from the database or the pool.
Verify that the database has not terminated with unexpected errors.
DBCOMMON-CONNECTFAILED000002= Operation failed because of a database connection error. Reason: [{0}]
Occurs while retrieving a connection from the database or the pool.
Verify that the database has not terminated with unexpected errors.
DBCOMMON-CONNECTFAILED000003= Connection handle not usable. Reason:[{0}]
The connection in the pool is stale and is not usable.
Probably a database restart occurred causing the connection to be stale, retry the operation after the database is up.
DBCOMMON-XARESOURCEFAILED000001= Unable to get XAResource for the database. Reason: [{0}]
Could not obtain XAResource for the connection.
Check if the database supports XA and has been configured for Distributed Transactions.
DBCOMMON-XACONNECTFAILED000001= Failed to connect to database {0} on host {1}. The XA connection could not be allocated: Reason [{2}]
Occurs during the initial database connection.
  • DCheck if the database is configured for XA and if the database is running.
  • External configuration information is invalid. You may need to verify the following:

    • Server name

    • Database name

    • User

    • Password

    • Port

DBCOMMON-XASTARTFAILED000001= Unable to perform XAStart for the connection. Reason: [{0}]
A connection error has occurred which caused XASTART to fail.
Check if the database is running, and that there are no network issues.
DBCOMMON-XAENDFAILED000001= XAEnd failed. Reason: [{0}]
Error has occurred during a commit on XA connection.
Look for the detailed error mentioned in the alert for the appropriate action.
DBCOMMON-CANNOT-GETISOLATION- LEVEL=Unable to get isolationLevel for the transaction. Reason: [{0}]
Could not read transaction isolation information of the connection.
Transaction isolation is one of the following constants:
  • Connection.TRANSACTION_RE AD_UNCOMMITTED

  • Connection.TRANSACTION_RE AD_COMMITTED

  • Connection.TRANSACTION_RE PEATABLE_READ

  • Connection.TRANSACTION_SE RIALIZABLE

  • Connection.TRANSACTION_N ONE

Note - Confirm with the vendor that the getIsolation() method of the connection is implemented correctly.