This article explains how to troubleshoot the common issues that occur when adding an IBM DB2 monitor in Applications Manager. Each section names the message it applies to, so match the message on screen and go to that section.
1. Before you begin
Verify the following details before troubleshooting the connection:
- DB2 server hostname or IP address.
- DB2 listener port.
- Database name.
- Whether the connection uses SSL.
- Monitoring username and password.
- Whether the database is a primary or standby database in an HADR setup.
Run connectivity tests from the Applications Manager host, not from a different computer. Network access from another machine does not necessarily mean that Applications Manager can reach the DB2 server.
2. Database name is incorrect or not catalogued
Applications Manager message
The Database name given is wrong. Please configure with correct values.
Driver error
[jcc][t4][2057][11264] The application server rejected establishment of the connection. An attempt was made to access a database, <name>, which was either not found or does not support transactions.
This error usually indicates that the database name supplied to Applications Manager is incorrect, the database is not available at the specified server, or the database is not catalogued as expected by the DB2 client configuration.
Resolution
- Verify the database name with the DB2 administrator. Database names may be case-sensitive depending on how they were created and referenced.
Confirm that the database exists on the target DB2 server. On the DB2 server, the databases served by the instance are listed by:
db2 list db directory
- Check that the value entered is the database name and not the instance name or a database alias. Supplying the instance name, such as
db2inst1, is the most common cause of this error. - If the environment uses DB2 client catalog entries, verify that the database is catalogued correctly and points to the intended server and port.
- Update the database name in Applications Manager and try adding the monitor again.
Note: if the database name is correct but the error continues, verify the DB2 server, port and database configuration with the database administrator.
3. SSL errors
SSL failures have their own article, because the checks differ from the ones above. Go to
Troubleshooting SSL Errors While Adding a DB2 Monitor if the monitor reports any of these:
- Unable to connect to the DB2 server. Please provide proper SSL certificates used to make SSL connection.
- Unable to connect to the DB2 server. The SSL trust store configured for this connection is invalid or inaccessible.
- Unable to connect to the DB2 server. If the SSL option is enabled for this monitor, check that the DB2 server is listening for SSL connections on the port given.
- Unable to connect to the DB2 server. The connection was dropped by the server or the network.
4. Monitoring user permissions
Applications Manager message
The given user <name> does not have execute privilege on the DB2 monitoring view (SNAPSHOT_DATABASE / SNAP_GET_DB / MON_GET_DATABASE / SYSIBMADM.SNAPDB) required to collect database statistics. Please grant the required privilege to this user.
The DB2 monitoring user must have the privileges needed to access the monitoring interfaces queried by Applications Manager. These interfaces are used to collect database, instance, connection and performance statistics. Access to application data is not required for these monitoring operations.
Applications Manager supports multiple monitoring interfaces across DB2 versions. Depending on the DB2 version and the availability of these interfaces, the collector may use different views or table functions to retrieve the required statistics. The monitoring user therefore does not necessarily need privileges on every object listed below; the required permissions depend on the interfaces available in your DB2 environment and the ones the collector uses.
1. Administrative views
The following administrative views are used to retrieve monitoring information. The monitoring user requires SELECT permission on the applicable views.
| Object | Purpose |
SYSIBMADM.SNAPDB | Database-level statistics |
SYSIBMADM.SNAPDBM | Database-manager statistics |
SYSIBMADM.MON_CURRENT_SQL | Currently executing SQL information |
SYSIBMADM.ENV_INST_INFO | Instance and version information |
Example GRANT statements:
GRANT SELECT ON TABLE SYSIBMADM.SNAPDB TO USER <monitoring_user>;
GRANT SELECT ON TABLE SYSIBMADM.SNAPDBM TO USER <monitoring_user>;
GRANT SELECT ON TABLE SYSIBMADM.MON_CURRENT_SQL TO USER <monitoring_user>;
GRANT SELECT ON TABLE SYSIBMADM.ENV_INST_INFO TO USER <monitoring_user>;
2. Monitoring table functions
Applications Manager may also use the following table functions. The monitoring user requires the appropriate EXECUTE privilege on the applicable functions.
| Object | Purpose |
SYSPROC.MON_GET_DATABASE | Database statistics |
SYSPROC.MON_GET_CONNECTION | Connection statistics |
SYSPROC.SNAPSHOT_DATABASE | Database statistics |
SYSPROC.SNAP_GET_DB | Database statistics |
SYSPROC.SNAPSHOT_DBM | Database-manager statistics |
SYSPROC.HEALTH_DBM_INFO | Instance health information |
Example GRANT statements:
GRANT EXECUTE ON FUNCTION SYSPROC.MON_GET_DATABASE TO USER <monitoring_user>;
GRANT EXECUTE ON FUNCTION SYSPROC.MON_GET_CONNECTION TO USER <monitoring_user>;
GRANT EXECUTE ON FUNCTION SYSPROC.SNAPSHOT_DATABASE TO USER <monitoring_user>;
GRANT EXECUTE ON FUNCTION SYSPROC.SNAP_GET_DB TO USER <monitoring_user>;
GRANT EXECUTE ON FUNCTION SYSPROC.SNAPSHOT_DBM TO USER <monitoring_user>;
GRANT EXECUTE ON FUNCTION SYSPROC.HEALTH_DBM_INFO TO USER <monitoring_user>;
Important. The statements above are examples, not a universal privilege script. The exact object names, schemas, function signatures, authorization syntax and required privileges vary by DB2 platform and version, and some functions require EXECUTE on a specific function signature. Have the DB2 administrator verify the applicable objects and privileges before running them.
3. Alternative: SYSMON authority
Instead of granting privileges individually, the DB2 administrator may configure SYSMON authority for the monitoring user. SYSMON is an instance-level monitoring authority that provides access to the supported DB2 monitoring interfaces.
UPDATE DBM CFG USING SYSMON_GROUP <operating_system_group>
The monitoring user must belong to the configured operating-system group. Depending on the DB2 configuration, an instance restart may be required for the change to take effect.
Important. Configuring SYSMON is an instance-level security and configuration change. Consult the DB2 administrator before applying it, and verify that this approach is supported for your DB2 platform and deployment. Do not grant broad administrative authorities such as DBADM or DATAACCESS solely to resolve a monitoring permission issue.
5. Connection reached an HADR standby
Applications Manager message
The connection reached a High Availability Disaster Recovery (HADR) standby database, which does not accept client connections. Check whether a failover has redirected this connection to the standby.
If the connection is directed to an HADR standby database, the database may not be available for the type of connection or monitoring operation being attempted.
Resolution
- Confirm the database role and state with the DB2 administrator.
- Verify whether the configured hostname or address points to the primary or the standby server.
- Confirm that the standby is intended to accept the connection and that the required monitoring operations are supported in its current state.
- If a failover or role transition has occurred, verify that Applications Manager is connecting to the intended database endpoint.
Do not change the HADR role or force a database takeover solely to resolve a monitoring connection issue. Follow your organization's DB2 high-availability procedures.
6. DB2 port is not reachable
Applications Manager messages
Service is not Running. Root Cause: Service port 50000 not accessible from appmanagerhost
Unable to connect to the DB2 server. The host answered but the port did not accept the connection. Check that DB2 is running and listening on the port given, and that no firewall is blocking it.
Applications Manager could not reach the configured DB2 service port from the Applications Manager host. The first message comes from the service check. The second comes from the monitor's own connection attempt, and also appears when DB2 refuses the connection outright — the host is up, but nothing is listening on that port.
Resolution
- Verify the DB2 hostname and listener port configured in Applications Manager.
- Confirm that the DB2 instance and listener are running.
- From the Applications Manager host, test whether the configured port is reachable. On Windows, use
Test-NetConnection <DB2-host> -Port <port>. On Linux, use an available TCP connectivity tool such as nc. - Check whether a firewall, network ACL, routing rule or security policy blocks the connection.
- Ask the DB2 administrator to confirm that the instance is listening on the expected interface and port.
7. Incorrect username or password
Applications Manager messages
The given Username is wrong. Please configure with correct values
The given Password is wrong. Please configure with correct values
The given Username or Password is wrong. Please configure with correct values
Which of the three appears depends on what the DB2 server reported. All three mean the credentials were rejected.
Verify the username and password with the DB2 administrator. Confirm that the account is active, that the password has not expired, and that the account is authorized to connect to the database. DB2 authenticates against the operating system by default, so the account must be valid on the DB2 host, not only inside the database.
Update the credentials in Applications Manager and retry the monitor addition.
8. Unclassified DB2 SQL errors
Applications Manager message
DB2 SQL Error: SQLCODE=-xxxx, SQLSTATE=xxxxx, SQLERRMC=SRV_DBM_TMT, DRIVER=...
DB2 returned an SQL error that is not covered by the specific troubleshooting sections in this article.
Resolution
- Record the complete SQLCODE, SQLSTATE, SQLERRMC and driver details.
- Check the DB2 diagnostic log for additional information about the error.
- Verify whether the error relates to database availability, permissions, configuration or a DB2 server-side condition.
- If the cause is unclear, provide the complete error details to the Applications Manager support team.
9. Host or DB2 server is down
Applications Manager messages
The Machine is down.
The DB2 Server is down.
Driver errors
Unknown server <name>
Error opening socket to server <host> on port <port>. Server may be down.
This is not the same as section 6. There, the host answered and only the port refused the connection. Here Applications Manager could not reach the host at all, or could not open a socket to it — the name did not resolve, the machine did not answer, or nothing is listening and the host gave no response.
Resolution
- Check that the hostname entered in Applications Manager resolves from the Applications Manager host. If it does not, correct the name or use the IP address.
- Confirm the machine is powered on and reachable. From the Applications Manager host, ping it, or use any available network test if ICMP is blocked in your network.
- If the name resolves to an unexpected address, check DNS and the local hosts file on the Applications Manager host.
- Check routing between the two machines, including any VPN, NAT or network segmentation that applies.
- Confirm with the DB2 administrator that the DB2 instance is running on that machine.
- If the host answers but the connection is refused, go to section 6 instead — that is a port problem rather than a host problem.
10. Account is expired, revoked or disabled
Applications Manager message
Unable to connect to the DB2 server. DB2 accepted the connection but would not accept the account. The password may have expired, or the account may be revoked or disabled on the DB2 host. The password stored in Applications Manager is not necessarily wrong.
Driver error
[jcc][t4][2013][11249] Connection authorization failure occurred. Reason: Password expired. ERRORCODE=-4499, SQLSTATE=08001
This is not the same as section 7. There, DB2 rejected the user name or the password as wrong. Here the credentials were recognised and the account itself was refused, so correcting the password in Applications Manager will not help until the account is usable again. The reason text names which case it is: Password expired, Userid revoked or Userid disabled.
DB2 authenticates against the operating system by default, so the expiry or lock is usually an operating-system account state on the DB2 host rather than anything inside the database.
Resolution
- Read the reason from the driver error above. It tells you whether the password expired or the account was revoked or disabled.
- Ask the DB2 or system administrator to check the account state on the DB2 host. On Linux, this is the password-ageing and lock state for the operating-system user; on Windows, the domain or local account state.
- Have the password reset or the account re-enabled, then update the password in Applications Manager if it changed.
- If the password expires on a schedule, consider a monitoring account exempt from password ageing, so collection does not stop every cycle. It needs only the monitoring privileges listed in section 4.
- Save the monitor again, or wait for the next poll, and confirm it recovers.
11. DB2 is not accepting connections
Applications Manager message
Unable to connect to the DB2 server. DB2 answered but is not accepting this connection. The instance may be stopping or quiesced, the database may be held in an exclusive mode, or the instance may have reached its connection limit.
Driver errors
SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request.
SQL1035N The operation failed because the specified database cannot be connected to in the mode requested.
Unlike sections 6 and 9, the host and the port are fine and DB2 itself replied. It declined this particular connection, so nothing in the monitor configuration is wrong. These are usually temporary.
Resolution
Ask the DB2 administrator whether the instance or database is quiesced, stopping or in maintenance. A quiesced database accepts only users holding the quiesce authority.
db2 get snapshot for database manager | findstr /i quiesce
Check whether the instance has reached its connection limit. Compare the connections in use against the configured maximum.
db2 get db cfg for <database> | findstr /i MAXAPPLS
db2 get dbm cfg | findstr /i MAX_CONNECTIONS
- Check whether another session holds the database in an exclusive mode, which is what SQL1035N usually means.
- Wait for the maintenance window to finish, or ask for the quiesce to be lifted, then let the monitor poll again. No change is needed in Applications Manager.
- If it persists outside maintenance, ask the DB2 administrator to check the diagnostic log for the reason the instance is refusing requests.
12. DB2 packages are not bound
Applications Manager message
Unable to connect to the DB2 server. The DB2 packages that the JDBC driver needs are not bound on this database. Ask the DB2 administrator to bind them.
Driver error
SQL0805N Package "NULLID.SYSLH203" was not found. SQLSTATE=51002
The JDBC driver runs its SQL through packages that must exist in the database. They are missing here. This is a database-side setup step, not a monitor setting, and it is most often seen on a newly created database or after the DB2 client or driver has been upgraded. The package name in the message varies.
Resolution
Ask the DB2 administrator to bind the driver packages against this database. The usual step is to bind the list shipped with the DB2 client.
db2 connect to <database>
db2 bind @db2cli.lst blocking all grant public
- Confirm the monitoring user can execute the bound packages. Package privileges are separate from the view and function privileges in section 4.
- If the DB2 version or platform needs a different bind list or utility, follow the IBM documentation for that version rather than the command above.
- Save the monitor again, or wait for the next poll, and confirm it recovers.
Contact Applications Manager support if the monitor still cannot be added after verifying the database configuration, network connectivity, credentials, SSL settings and required privileges.
Include the following information in your support request:
- Applications Manager build number.
- DB2 platform and version.
- DB2 hostname, port and database name.
- Whether SSL is enabled.
- The complete Applications Manager error message and the underlying DB2 or JDBC exception.
- Results of the connectivity tests run from the Applications Manager host.
db2 get dbm cfg output, specifically SVCENAME.- Relevant Applications Manager logs and DB2 diagnostic or listener logs, if available.
- A Support Information File (SIF) collected after reproducing the issue.