Integrating ASE systems into DBA Cockpit, including set up proecdures for ATM

Some SAP Applications which are supported to run on ASE but are not designed to do so by default may be still integrated into DBA Cockpit for the ease of maintenance.

There is an official documentation set on integrating ASE systems into DBA Cockpit (1593987 – SYB: Monitoring non-SAP ASE databases with the DBA Cockpit).

There is also and official document for setting up ATM feature for ASEs (DBA Cockpit – Automatic Table Maintenance for Sybase ASE).

There are, though, a few things taken for granted by these documents which makes integration of ASE into DBA Cockpit prone to errors.

I have collected here a set of configuration changes that need to be applied in order to make sure that integration of an ASE into DBA Cockpit runs smoothly.

These are the steps to follow:

1.  Connect to your ASE server and add sapsa login.

exec master..sp_addlogin sapsa, {SAPSAPWD}, saptools

go

2.  Connect to your ASE server and fix missing database option on tempdb which DBA Cockpit pre-supposes:

exec master..sp_dboption tempdb, “ddl”, true

go

checkpoint all

go

3. Connect to your ASE and reset the default locking scheme to row level (SAP note 1880931).

master..sp_configure “lock scheme”,0,”datarows”

go

4. Connect to your ASE server and add sapsa missing privileges in the note above (the guide presupposes existence of sap_adm and sap_mon custom roles).  Without these roles DBA Cockpit will not be able to add the jobs it has to run to ASE Job Scheduler.

–a must

grant role js_admin_role to sapsa

go

exec master..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 master..sp_modifylogin sapsa, ‘add default role’, sybase_ts_role

go

5.  Connect to your ASE server and add the external login to job scheduler configuration. Without these roles DBA Cockpit will not be able to activate the jobs it has to run on ASE Job Scheduler.

exec master..sp_addexternlogin SYB_JSTASK, sapsa, sapsa, {SAPSAPWD}

go

6.  Configure ASE to work with xml.   Without these roles DBA Cockpit will not be able to activate the jobs it has to run on ASE Job Scheduler.

exec master..sp_configure “enable xml”, 1

go

7.  Only after the steps above are performed, follow the 1593987 – SYB: Monitoring non-SAP ASE databases with the DBA Cockpit note to integrate ASE into DBA Cockpit.

8.  Navigate to Configuration->Automatic Table Maintenance in DBA Cockpit and setup ATM (follow the official document specified above).

9.  Add manually 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.  See SAP Note:  2043922 – SYB Support of cross database ATM profiles).

10.  Start the regular 24×7 maintenance window manually and navigate to Diagnostics->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 integrating ASE into DBA Cockpit and configuring ATM.

HTH,

Andrew