I have followed the two documents on integrating ASE systmes into DBA Cockpit:
*** 1593987 - SYB Monitoring non-SAP ASE databases with the DBA Cockpit
*** DBA Cockpit - Automatic Table Maintenance for Sybase ASE
For the ASE systems which have been integrated into DBA cockpit as part of installing SAP product, the installation and configuration of ATM was pretty straightforward. But:
+ Although the default updstat/reorg profiles are installed and the default maintenance windows are set up and are in the scheduled state, there are zero objects reported to be queued for maintenance
+ When started manually, the queue remains zero, although the ATM history displays that some objects were indeed maintained - based on the default maintenance window triggers defined as part of the installation.
For the ASE systems which have not been integrated into DBA cockpit as part of installing SAP product but are used by standard SAP application (SAP BO - which was meant to run on ASA but does support running on ASE as well), ATM configurations are garbled.
+ Default updstat/reorg profiles are are installed partially (some systems they are, some they aren't - installed only a single database in ASE, leaving others to be added manually, maintenance window is in "not scheduled" state and cannot be started (DBA cockpit gets error message stating that some jobs are missing from the job scheduler).
+ ASE integration into DBA cockpit seems to be partial.
A couple of questions:
a. Is there a procedure to self-test the DBA Cockpit configuration? A health-check for the spatools installation on an ASE box? How should we identify missing DBA Cockpit components in target ASE?
b. For the systems that are integrated into DBA Cockpit by default and after turning the ATM feature on, how to identify which objects are set up for the maintenance and when? Except for the standard windows to see ATM future queue, is there a way to test the maintenance window to see which object it will affect?
c. For the systems that aren't - are there corrective SAP notes available to fix the garbled DBA Cockpit integration? It looks like pulling the non-default ASE into DBA Cockpit leaves certain installation aspect in an unstable state (some of the components definitely mis-perform - System Load can be displayed for the current time only - no history seems to be collected, dashboard keeps complaining on dirty read from monProcessActivity MDA, IO controller window keeps crashing with ABAP OBJECTS_OBJREF_NOT_ASSIGNED error, SQL Statements complains on yet another dirty read errors from monCachedStatements MDA, &c).
d. Is there an extensive documentation on integrating an ASE into DBA Cockpit - other than the 1593987 SAP note?
e. Is there an extensive documentation on configuring ATM other than 2011 document specified in the beginning of this post?
f. What kind of support is available for fixing DBA Cockpit / ATM issues?
Appreciate your help.
Thank you,
Andrew