Skip to Content

Monitoring non-SAP ASE databases with the DBA Cockpit - garbled ATM installation

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Dec 05, 2014 at 01:10 AM

    The ATM scheduling part for non-SAP ASEs is resolved. The note for integrating ASE into DBA Cockpit does not specify the need for sapsa login to have the js_admin_role. Whoever is responsible for the note - can you please update it?

    1593987 - SYB: Monitoring non-SAP ASE databases with the DBA Cockpit

    Thank you.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 08, 2014 at 12:02 AM

    Ok.

    So in order to have ATM functional for ASE's which are not installed by SAP installation routines you have:

    1. Add sapsa login

    sp_addlogin sapsa, *******, saptools

    go

    2. Follow the 1593987 - SYB: Monitoring non-SAP ASE databases with the DBA Cockpit note (and the note that resets the default locking scheme no row level specified in that document).

    3. Fix the missing db option on tempdb:

    sp_dboption tempdb, "ddl", true

    go

    4. Add sapsa missing privileges in the note above

    --a must

    grant role js_admin_role to sapsa

    go

    exec sp_modifylogin sapsa, 'add default role', js_admin_role

    go

    -- default installation has it, ATM seems to work without

    grant role sybase_ts_role to sapsa

    go

    exec sp_modifylogin sapsa, 'add default role', sybase_ts_role

    go

    5. Add the external login to job scheduler configuration

    sp_addexternlogin SYB_JSTASK, sapsa, sapsa, {SAPSAPWD}

    go

    6. Configure ASE to work with xml

    exec sp_configure "enable xml", 1

    go

    7. Navigate to Confniguration->Automatic Table Maintenance in DBA Cockpit and setup ATM.

    8. Add manually the maintenance tasks in case you have more than one database in you system which ATM should take care of (I've seen a note that this will be covered in future automatically - 2043922 - SYB Support of cross database ATM profiles.

    9. Start the regular 24x7 maintenance window manually and navigate to Diagnositcs->ATM->ATM Logs to see if the jobs really fired (If the status of the Maintenance Window turns to Running it is already a good sign.

    That seems to cover the installation requirements for ATM.

    Could anyone setup the documentation to cover all this please?

    Thank you,

    Andrew

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.