-
标题
DB2 agent fails to connect when "Authentication Mode" is set to "Client" -
说明
The following scenario is present:
- Authentication mode for the DB2 instance is set to "Client".
- Database connection is successfully verified from "Settings | Administration | Database Connection Details".
- Manually running the DB2 grant scripts on the database instance for the user defined in the "Agent Status" properties shows that all the "GRANT" commands are completed successfully.
- Even when privileges and authorities have been granted to the monitoring account, the following errors can be seen on the agent logs for multiple collections:
ERROR [AGENTNAME-highPriorityPool-1] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DB2CatalogHostPartitionProcessor processor of DB2_Startup collection.java.lang.RuntimeException: Failed to execute collection [DB2_Startup], reason=[Foglight][DB2 JDBC Driver][DB2]FGLAMUSER DOES NOT HAVE PRIVILEGE TO PERFORM OPERATION EXECUTE ON THIS OBJECT SYSPROC.MON_GET_DATABASE- Profile:DB2Profile{host='hostname', port='50000', databaseName='DATABASENAME', username='agentuser', password='xxxxxxx', socketTimeout (sec)='900, authenticationType='CLIENT'} ......ERROR [AGENTNAME-lowPriorityPool-45-[DB2_Maintenance][YYYY/MM/DD HH:MM:SS]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DB2DatabaseStartTimeProcessor processor of DB2_Maintenance collection.java.lang.RuntimeException: Failed to execute collection [DB2_Maintenance], reason=[Foglight][DB2 JDBC Driver][DB2]FGLAMUSER does not have the authority to perform the requested command., SQL-Parameters = [DATABASENAME],[0],
- When trying to add a new database from the "Monitor DB2 Instance" wizard, the following error is displayed:
Failed to execute query on host hostname. Reason : [SQL10007N Message "-1390" could not be retrieved
ERROR [DB2Installer-1539657824415-1539658277473-1539658277485] com.quest.qsi.fason.db2.installer.callback.DB2DatabaseValidator - DB2 instance validation failure for instance [DB2] and database [DB]com.quest.qsi.fason.framework.installer.exceptions.InstallerServiceException: Failed to discover partitions...Caused by: java.sql.SQLNonTransientConnectionException: [Foglight][DB2 JDBC Driver][DB2]Error occured with SQLCode -30082 with the following parameters: 24, USERNAME AND/OR PASSWORD INVALID, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null -
原因
When authentication mode is set to "Client", the DB2 agent will use the user running the Foglight Agent Manager process to establish the connection against the target database. The credentials set in the "Agent Status" properties will not be used.
By validating DB2 database connections from the "Settings | Administration | Database Connection Details" dashboard, privileges will be granted to the user configured in the "Agent Status" properties. -
解决办法
RESOLUTION 1
The required privileges and authorities must be manually granted to the user running the Foglight Agent Manager process:
- Perform a manual creation of the DB2 agent from "Agent Status".
- Manually run the DB2 grant scripts for the user running the Foglight Agent Manager process.
- Grant the "SYSMON" authority to the user running the Foglight Agent Manager process.
RESOLUTION 2
- Ensure that the user running the Foglight Agent Manager service is the correct user you want to use to connect to the DB2 instance
- Manually run the DB2 grant scripts against this user if you have not done so and ensure that it can connect to the DB2 instance from the FglAM machine
- Rerun the DB2 agent wizard
RESOLUTION 3
When DB2 authentication type is CLIENT, the login credentials provided during installing for the database agent are overwritten with the username running the FglAM service (Windows) or process (Unix/Linux). Ensure that the FglAM user can connect to the DB2 instance and has all the relevant permissions as described in the Permissions section.
RESOLUTION 4
On a Linux or Unix OS, the DB2 instance name may be case sensitive. For example when validating DB2INSTANCE=db2inst1(lowercase) and the user enters DB2INST1 (uppercase) for the Instance name instead, in the DB2 Agent configuration details it will produce the same error. The user should use the DB2 instance name that matches the server exactly. -
其他信息
For granting permissions, please review the following article:
Missing privileges after DB2 agent installation (116492)
Additional details on how to manually create a DB2 agent can be found in the following article:
"The provided db2home belong to another instance" when adding a new DB2 agent (155824)