I'm setting up some custom SQLs to be executed by the ITM RZ agent. Such queries take time to complete, so I have set the SQL_TIMEOUT to 300 in order to avoid it failing for timeout, however when I check the workspace on TEP I always get a timeout after one minute. It seems the timeout I've set per query is not taken in consideration. Should I set the timeout somewhere else?
Answer by valemax (2189) | Nov 26, 2018 at 10:44 AM
There is another parameter in the agent that influences the timeouts in data collection, and it is CDP_COLLECTION_TIMEOUT, its default is 60 seconds
This value sets the maximum time the agent will wait for the data provider to complete a data collection, so the data provider part of the agent is waiting up to 300 seconds for the SQL to return but the "agent" part of the agent waits up to 60 seconds then timeouts. Try setting the CDP_DATA_COLLECTION variable to 300 for the instance involved, this will fix your issue.
Best practice to update an ITM Warehous Proxy Agent agent 6.3 fixpack 1 Answer
Can an Agent Builder monitor all types of HTTPS URLs ? 2 Answers
ITMv6 How to turn off or temporarily disarm Watchdog? 1 Answer
Does IBM Tivoli Monitoring supports Oracle Database Appliance Monitoring? 1 Answer
Why does the ITCAM Oracle Extended agent fail to show data in the TEP? 1 Answer