Return
-
Title
DB2 agents unable to monitor "user id revoked" -
Description
The DB2 database dashboard was not showing Workload for a monitored DB2 instance.
A review of the DB2 agent log found the following messages
Connection authorization failure occurred. Reason: User ID revoked. ERRORCODE=-4214, SQLSTATE=28000- Profile:DB2Profile{host='MYHOSTNAME', port='50000', databaseName='MYDATABASE', username='MYUSERID', password='xxxxxxx', socketTimeout (sec)='900, authenticationType='SERVER'
followed by
Failed to get new connection on Usability-Response collection on database MYDATABASE. For security reasons, the user account "MYUSERID" is locked by the agent due to invalid login credentials. Module: "DB2Pool-e8c55264-f05a-4902-a03b-5b66126f4da5-db2d07luw-db2-MYDATABASE". Error Message: "[jcc][t4][2017][11253][4.12.98] Connection authorization failure occurred. Reason: User ID revoked. ERRORCODE=-4214, SQLSTATE=28000". Suggestions:1. Verify agent connectivity via the Connection Details dashboard.2. Use the "Databases/Support Dashboard/Database Technical Support" dashboard, "Unlock Agents" page to unlock the user account. -
Cause
The userid was locked at the Foglight level after changes were made in the DB2 instance. -
Resolution
- Resolve the issue with the DB2 userid and password in DB2
- Test the login to DB2 on the host instance
- Go to "Database" dashboard
- Select the problematic agent and click on "Settings | Administration"
- Select "Database Connectivity Details" left hand side
- Then "Validate connectivity" here
- If this fails with permission issues, follow the procedure to grant the missing permissions on the DB2 instance.
- Click the Save button at the bottom of the page
- Navigate to Databases | Support Dashboard | Databases Technical Support
- Click Unlock Agents
- Select the agent name
- Click the Unlock DB button
- Navigate to Administration | Agents | Agent Status
- Highlight the Agent
- Click the Activate button
If there is an issue with Step 16 where the Unlock DB button does not work and "Failed to unlock agent - check logs for more details" appears in a popup message, please see KB article 112282