"db2 get monitor switches" succeeds if I connect to instance X with id AAA and it fails if I attach to the same instance with same id with following message:

db2 attach to X user AAA using ******

Instance Attachment Information

Instance server = DB2/LINUX 8.2.3
Authorization ID = AAA
Local instance alias = X

$ db2 get monitor switches
SQL1092N "AAA " does not have the authority to perform the requested
command.

Pls help.

Thanks

If you are able to run the command at the right instance (X) then what is the need of attaching to the instance again locally and trying the command?

We are using FogLight for monitoring UDB instances. FogLight client from this host is failing to connect to FogLight server and tech support has pointed out this as the root cause. All other UDB instances being monitored by FogLight can run this command both by connecting & attaching. So, if someone can pls tell me how to fix this and what is the difference between the two as I am pretty much new to UDB.

log on as the instance owner and run the following:

db2 get dbm cfg

You will see several authorization groups that can be specified, and the foglight id probably needs to belong to one of these.

SYSADM group name (SYSADM_GROUP) = DB2IADM
SYSCTRL group name (SYSCTRL_GROUP) =
SYSMAINT group name (SYSMAINT_GROUP) =
SYSMON group name (SYSMON_GROUP) =

Does the permission matter at "connect" / "attach" level? If it is working when connected then what could be the reason for it not to be working when attached?

Anyway, thanks I am looking into it and appreciate your input.

Just because an id has authority to connect to a database or attach to an instance, does not mean that it has authority to issues the following command:

db2 get monitor switches

See the Command Reference manual for information on what authority you need to execute these commands.