Configuring the agent through the Manage Tivoli Monitoring Services tool on Windows systems: http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.1/oracleextended/fac_config_agentspecific_local_tms_win.html
you should launch the Manage Tivoli Monitoring Services as “Run as administrator” like below:
You should not use special characters as part of agent instance name or database connection name like *, $, +. Only letters, Arabic numerals, the underline character, and the minus character can be used.
You can select using existing Oracle Home or download to use Oracle Instant Client. If you select using Oracle Home, then the bit of Oracle database in the Oracle Home should be consistent with Agent’s bit number. In another word, 32-bit Agent should be configured with 32-bit Oracle Home, 64-bit agent should be configured with 64-bit Oracle Home.
At least one database connection needs to be configured for agent to monitor.
Change configuration from configure file manually.
You can modify other agent configuration variables like Listener Monitoring interval, whether or not to load listener.ora and tnsnames.ora from %ORACLE_HOME%/network/admin directory from agent’s configure file %ITMHOME%\TMAITM6(_X64)\KRZENV_.
The full environment variable list can be found from link:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.1/oracleextended/fac_config_agentspecific_setenvars.html For example:
If the agent is 32bit which is installed in the directory like C:\IBM\ITM\TMAITM6\KRZAGENT.exe, then you should download 32bit Oracle Instant Client for Windows: http://www.oracle.com/technetwork/topics/winsoft-085727.html
If the agent is 64bit which is installed in the directory like C:\IBM\ITM\TMAITM6_X64\KRZAGENT.exe, than you should download 64bit Oracle Instant Client for Windows:
Number of agent instances and database connections on one system. We suggest configuring no more than 5 database connections in one Agent instance.
The best practice involves considering the number of agent instances and database connections on one system. 10 agent instances times 5 database connections (monitoring 50 databases on one system) is optimal. The performance of the agent depends on system performance, network performance, and most importantly the number of data requests, including situation and historical data collection. With fewer data requests for one database, more databases can be monitored on one system. As a best practice, first configure 10 agent instances times 5 database connections, and observe performance, such as the length of the response time for the data request. If the performance is acceptable, you can consider monitoring more databases on the system; if not acceptable, set up another system with the Oracle Database Extended agent installed.
Using “Test Connection” to verify the database connectivity.
There are many agent events like "ORA-1006 Too many request". It looks there are timeout conditions when the agent attempts connection to the DB, extend the timeout value from the default value (60 seconds) to a greater one as per following parameter: CDP_COLLECTION_TIMEOUT=180 in the KRZENV_ configuration file.
CTIRA_HOSTNAME cannot take effective for Oracle Agent in Windows.
Append below agent’s affinity into the TEPS’s variable KFW_TOPOLOGY_CLUSTER_LIST, separated by blank space. KFW_TOPOLOGY_CLUSTER_LIST= %IBM.OracleAgents
This variable is added to the \cnps\kfwenv file (Windows) or to /config/cq.ini (Linux/UNIX).
Reference the link: http://www-01.ibm.com/support/docview.wss?uid=swg21326517