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.


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



Extending the database space on Sybase ASE

You notice in DBACOCKPIT that you are running out of space on your data/log files of Sybase ASE database.

Below procedure explains the procedure to extend the space on the data/log volume.

Login to dbsql using SA or SAPSA user:

In Sybase data and log files are organize in the form of Devices. Search for the device you should be extending first before allocating the space the data or log file using below command:

use master

sp_helpdb <DBID>


Ex:   sp_helpdb ERP

In the Result Set 2, you can find the related devices.


Next find the device location using the below command:

use master

sp_helpdevice <data_file_device/log_file_device>



Now resize the device using the below command:

use master

disk resize

name = “<device_name>”,

size = “<size>”


Now assign the extended device to the database:

For data files:

user master

alter database <DBSID> on <device_name> = <Size>


For log file:

use master

alter database <DBSID> log on <device_name> = <Size>