Issue in discovery of DB2 instances on AIX server

Gursimran Singh
Tera Contributor

‎08-03-2022 07:54 AM

Hello everyone,

There is one pattern "DB2 On Linux". This same pattern runs for the AIX server to discover DB2 instances, but it is not working. Almost all the commands are failing on the AIX server related to this, still ServiceNow documentation suggesting to use this OOB. "Name, version, TCP port, installed dir" - none of these attributes are discovered properly.

https://docs.servicenow.com/en-US/bundle/sandiego-it-operations-management/page/product/service-mapping/reference/ibm-db2-linux-discovery.html

Can anyone please guide how to deal with the situation? or what changes do we need to make in order to create a custom pattern to discover DB2 instances on AIX servers?

 

Thank You!!

Labels:
0 Helpfuls
  • 699 Views
1 REPLY 1

Jim Palmer
ServiceNow Employee
ServiceNow Employee

‎08-07-2022 04:46 PM

Gursimran,
 
I would hazard a guess that on this AIX system in question, running the db2profile environment would be the item failing.
 
In a normal install, DB2 puts all its server settings (or at least the parts that allow all the db2 commands to work) into: $HOME/sqllib/db2profile for the 'instance owner' db2inst1.
It's normally /home/db2inst1/sqllib/db2profile (the instance owner  actually db2instx depending on the number of DB2 instances installed, but there's normally only 1 instance). 
 
In some organisations, security tries to lock down the db2inst1 home directory without realising that by doing this, you effectively block any other accounts from using DB2 cli including discovery.
 
So things to check:
  • What user is running the discovery?
  • Does this use have access to traverse the directories, read & execute the $HOME/sqllib/db2profile script for the db2inst1 account?
    Either directly or through sudo...
  • Can it also execute the $HOME/sqllib/bin/db2level script?
0 Helpfuls