Scheduling failed on Sybase ASE

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

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.

schedule again

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.





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>







System Copy – Sybase ASE

It is one of the most simplest system copies i have ever done. Ensure that Source and Target databases are running on the same release.

No need to uninstall the application or perform a rename using SWPM

I have not mentioned the pre and post processing steps as they are common to all databases and it will differ from customer and customer based on their system usage.

Once you have completed the pre-processing , perform the below steps.

I will assume “TRG” as your target database and “SRC” as your source database.

  • Copy the latest full backup file and required transaction backup files to the target server
  • Stop SAP Application on the target server.
  • Login to SQL/ISQL using “sa” or “sapsa” user ID on target server.
  • Drop the target database using below command. This might take few minutes based on database size.

drop database TRG

  • Create database TRG using below command.

create database TRG on TRG_data_001=’398743M’ log on TRG_log_001=’20480M’ for load


  1. Size used above are depiction only. This should be equal to or more than your source device sizes.
  2. Replace the device names TRG_data_001 and TRG_log_001 with appropriate device names.
  • Now load the created database using the source backup using below command.

load database TRG from “D:\backup\SRC.dmp”

Note: Assuming “D:\backup\SRC.dmp”. This might take some time based on the source backup size.

  • Now load the log backups to perform point in time recovery using below commands.

load transaction TRG from “D:\logbackup\SRC_001.trn”

load transaction TRG from “D:\logbackup\SRC_002.trn”


  • Bring the restored database online.

Online database TRG.

Now you are all set to start SAP and perform post processing.


Note: Even though i have not mentioned pre and post steps here, do remember to make the rdisp/wp_no_btc to 0 in your profile parameter before starting SAP.