When configuring a DB2 agent to monitor a DB2 instance, the following error is displayed:
Failed to validate the DB2 installation directory
Please specify the DB2 installation directory:
Failed to validate DB2 instance [DB2], host [hostname]
The provided db2home belong to another instance
The WinRM service returns an empty result when the database agent installer executes code to query the DB2 instance name on Windows
You can try the following command on the host (where the bin folder corresponds to the appropriate location on the Windows host)
%comspec% /C ( cd "C:\PROGRA~1\IBM\SQLLIB\bin" && set "DB2INSTANCE=DB2" && db2cmd /c /w /i "db2 get instance" )
Differences caused by an International Operating System
Do not specify a DB2 home value in the DB2 installer.
Set the callback timeout in the DB2 installer agent to double the current size.
At the moment, there is no out of the box support for Chinese operating system. As a workaround, follow the below steps.
Create the agent manually from the 'Agent Status' page. See attached picture for the fields that needs to be modified. The monitored databases and members secondary properties should be cloned first.
Once the agent has been set, the following errors may occur:
1. The agent will fail to detect standby (HADR) databases, so our collections will fail for those databases.
2. DB2_Log_File_Size collection will fail
3. The agent will fail to detect number of active databases, so the metric 'con_local_dbases' in the instance activity will not be set
If the Db2 instance is on Windows environment, try to use the Windows option with user account with no domain to connect to the Db2 host during the Monitored Wizard. Then test the connection.
All WinRM related information are documented under the path: Advanced system configuration and troubleshooting - Configuring Windows Remote Management (WinRM).