Parameters for MDA tables are not set.
UnsetMDAParams:Exception
Exiting callback.
YYYY-MM-DD 14:53:38.942 WARN [Sybase_MDA Socket Listener] com.quest.spi.jfogbank.AgentWrapper - Agent log: Index_callback: Parameters for MDA tables are not set.
UnsetMDAParams:Exception
Exiting callback.
YYYY-MM-DD 14:53:38.944 WARN [Sybase_MDA Socket Listener] com.quest.spi.jfogbank.AgentWrapper - Agent log: Exception:
ct_command() failed
returned from BenchmarkTimes
Aborting callback.
YYYY-MM-DD 14:53:38.947 WARN [Sybase_MDA Socket Listener] com.quest.spi.jfogbank.AgentWrapper - Agent log: Exception thrown in callback function BenchmarkTimes.
This seems to be suspending collections.
Sybase_MDA agent requires the following configuration for it to run correctly and gather the specified data for the Foglight Management Server. The values shown for the following parameters are the minimum required values that the Foglight Cartridge for SAP ASE needs for proper data collection and reporting. Any of these parameter values could be increased if necessary. (You can copy, paste, and execute the following script into an ISQL or other client session.)
sp_configure "errorlog pipe max message",1000 go sp_configure max SQL text monitored,256 go sp_configure sql text pipe max messages,3000 go sp_configure statement pipe max messages,3000 go -- Flags sp_configure enable monitoring, 1 go sp_configure sql text pipe active, 1 go sp_configure errorlog pipe active, 1 go sp_configure per object statistics active,1 go sp_configure statement statistics active,1 go sp_configure statement pipe active,1 go sp_configure wait event timing,1 go sp_configure SQL batch capture,1 go sp_configure process wait events,1 go
The following tables list proprietary Sybase flags and the Sybase_MDA agent tables dependent upon them. If any of the settings do not have values that fall in the recommended value range, data collection will issue complaints and fail to successfully collect; indicating that some MDA table collection was canceled as a result of the flags being set incorrectly. To prevent these alerts from occurring, use the appropriate Data Management properties to disable the collection that is failing to collect. Below is a listing of Sybase_MDA agent tables and the configuration settings they depend on:
| Foglight Table | Sybase MonTable (MDA) Configuration Settings |
|---|---|
| TopHash |
enable stmt cache monitoring = 1 statement cache size = size_of_cache enable literal autoparam = 0 or 1 NOTE: Setting enable literal autoparam to 0 causes Sybase to treat each SQL statement separately; setting it to 1 produces bind variables for each search argument in an SQL statement |
| TopSQL |
enable monitoring = 1 statement statistics active = 1 per object statistics active = 1 statement pipe active = 1 SQL batch capture = 1 max SQL text monitored > 0 statement pipe max messages > 0 sql text pipe max messages > 0 |
| UsersBlocked |
enable monitoring = 1 wait event timing = 1 SQL batch capture = 1 max SQL text monitored > 0 |
| UsersLogCache |
enable monitoring = 1 wait event timing = 1 per object statistics active = 1 |
| TopApplications |
enable monitoring = 1 wait event timing = 1 per object statistics active = 1 |
| Index |
enable monitoring = 1 wait event timing = 1 per object statistics active = 1 |
| TopUsers |
enable monitoring = 1 wait event timing = 1 per object statistics active = 1 SQL batch capture = 1 statement pipe active = 1 max SQL text monitored > 0 sql text pipe max messages > 0 |
