PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


The monitoring user needs SYSMON authority and connect privileges to monitor. In general, this user must be a part of the sysmon_group.

DB2 version 9.7 and greater

For complete Database Visibility functionality, the following monitoring switches of the DB2 server need to be enabled: "TIMESTAMP".

You can enable the "TIMESTAMP" monitoring switch by the following commands:

update dbm cfg using dft_mon_timestamp on;

Privileges

  • grant select on SYSIBMADM.MON_CURRENT_SQL to user DBMon_Agent_User
  • grant select on SYSIBMADM.MON_LOCKWAITS to user DBMon_Agent_User
  • grant execute on function SYSPROC.MON_GET_CONNECTION to user DBMon_Agent_User
  • grant select on SYSIBMADM.SNAPAPPL_INFO to user DBMon_Agent_User
  • grant EXECUTE on function SYSPROC.MON_GET_PKG_CACHE_STMT to user DBMon_Agent_User
  • (version 10.5 and above) grant execute on function SYSPROC.MON_GET_TRANSACTION_LOG to DBAgent_User
  • (version 10.5 and above) grant execute on function SYSPROC.MON_GET_DATABASE to DBAgent_User

*where DBMon_Agent_User is the user name under which you run the Database Visibility Agent.

 

DB2 version 9.5

For complete Database Visibility functionality, the following monitoring switches of the DB2 server need to be enabled: "STATEMENT", and "TIMESTAMP".

You can enable these monitoring switches by the following commands:

update dbm cfg using dft_mon_stmt on;

update dbm cfg using dft_mon_timestamp on;

Privileges

grant select on SYSIBMADM.mon_current_sql to DBMon_Agent_User 

grant select on SYSIBMADM.SNAPSTMT to user DBMon_Agent_User 

grant select on SYSIBMADM.SNAPAPPL_INFO to user DBMon_Agent_User 

grant execute on function SYSPROC.MON_GET_PKG_CACHE_STMT to user DBMon_Agent_User

grant select on table SYSIBMADM.ENV_PROD_INFO to user DBMon_Agent_User 

where DBMon_Agent_User is the user name under which you run the Database Visibility Agent.

  • No labels