Jeff / Jan / Tilman,
Thank you for prompt reply. I will proceed to install ATM then. I will follow Andreas Zimmermann paper on ATM for ASE. If there is any other material related to installing/configuring ATM for ASE I'd be grateful if you might point me to it.
In addition, we will follow the procedures in SAP notes you've mentioned. Some systems were not intended to be included in DBA cockpit and they integrated following SAP note on monitoring non-SAP ASE databases (1593987). Actually I'd add a corrective to that note - DBA cockpit expects ASE tempdb's to allow ddl in transactions to be turned on - otherwise it's collectors crash. This is not specified in the note and I had to read through the log files to identify the cause of crashing collectors.
There is also some strange behaviour with process activity collectors. I receive message once in a while complaining on an attempt to do dirty read on an MDA table that fails:
Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
Kernel Error ID:
DB Error: Yes
SQL Code: 313
SQL Message: [ASE Error SQL313][SAP][ASE ODBC Driver][Adaptive Server Enterprise]The optimizer could not find a unique index which it could use to perform an isolation level 0 scan on table 'master..monProcessActivity'.
Is there a fix for that? Dirty reads on MDA tables will fail in general - regardless of having been run from DBA cockpit collectors or manually.
Thank you,
Andrew