How to analyze saptools database growth in Sybase ASE database and contain it

SAPTOOLS database mainly contains the monitoring data for Sybase ASE database.

You can decide the duration this data can be retained by configuring the collector parameters in DBACOCKPIT.

Ensure that the message level is set to error. If not this may significantly increase the growth of this database.

If the history of monitoring is not required anymore, you can also delete the data and log using the prune option.

SQL0204N

The retention policy can be set individually by selecting each data collector and changing the “Days Kept In History” parameter.

Below are some SAP Notes related to SAPTOOLS database:

2100175 – SYB: Increased space allocation of data collectors ‘Tables’ and ‘Indexes’

1927012 – DBA Cockpit shows warnings “Required data collector xxx is not set up properly” – SAP ASE for Business Suite

1615695 – SYB: ‘saptools’ database running out of space

1687320 – SYB: ‘saptools’ database running out of space (2)

2006899 – How to configure reorg on saptools database in DBA Cockpit – SAP ASE for Business Suite

2497314 – How to recreate database saptools when it is corrupted and no clear backup – SAP ASE for Business Suite

2381666 – How to enlarge saptools database through DBA Cockpit – SAP ASE for Business Suite

 

 

Scheduling failed on Sybase ASE

Error in DB13 while running SAP on Sybase database – “Scheduling Failed”.

These errors are intermittent and not reproducible.

Below I outline some steps to troubleshoot this issue:

Check for errors in log files (<SID>, <SID>_BS, <SID>_JSAGENT> under installation directory:

Ex: “D\:sybase\<SID>\ASE-15_0\install.

If you cannot read these files (Because it is in use), copy it to another directory .

Try to dump the transaction log using below command:

dump transaction <SID> to “<Dump Directory>”.

If you are able to successfully dump or truncate the log file, then try to delete the further schedules and try to reschedule the backup again from DB13.

If you are not able to dump or truncate the transaction log , database might be in a standstill (Root cause explained at the end).

In that case, stop SAP and restart the DB services (SQL Server and Backup Server).

In our case, we found following errors in the <SID> log file when the issue happened.

Error: 8213, Severity: 20, State: 3
server Failed to acquire address lock on object DDLOG

Note: There were no Dump DATABASE or Create INDEX were running on the database during that time.

This is caused by a bug in the ASE database as explained in the SAP Note 2337582.

Database had to be updated to one of the release mentioned in the note to resolve the issue.

Important Notes:

2178977 – Job scheduling fails on DBA Planning Calendar – SAP ASE for Business Suite

 

2477608 – DBA Planning Calendar shows duplicate entries with status scheduling failed – SAP ASE for Business Suite

 

2688308 – How to troubleshoot Job Scheduler issues in Standalone ASE

 

2249796 – Unable to create SAP schedules from DBA Cockpit – SAP ASE for Business Suite

 

2692998 – Unable to schedule database job due to ASE Error SQL4002

 

2099027 – Database Extractor Setup Failed for SAP ASE for Business Suite

 

2494044 – Unable to setup job scheduler Solution manager 7.2