4 4 3:SAP ASE Configuration

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English
Copyright © SEP AG 1999-2021. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo V2. For previous documentation version(s), check Documentation archive.


This article describes prerequisites and configuration requirements for SAP ASE environment (formerly SAP Sybase ASE). Note that the procedures introduced in this article are only the required pre-configuration steps. For details on SAP ASE integration key features, available backup methods and backup configuration, see SAP ASE Backup.

Depending on your SEP sesam version and the backup method you use (integrated SAP ASE backup via SEP sesam GUI or external backup via isql), the required configuration steps for SAP ASE integration may vary. The following applies for SAP ASE integration:

  • As of SEP sesam v. 4.4.3 Tigon, SEP sesam installation contains the library needed for the SAP ASE API integration with the local operating system.
  • As of 4.4.3 Grolar, SEP sesam automatically retrieves the required system environment variables used by your SAP ASE software from the $SYBASE/SYBASE.env (Linux) or %SYBASE%\SYBASE.env (Windows). The root directory settings and the SYBASE.env file are created during the SAP ASE installation (on both, Linux and Windows) and the SYBASE.env contains all required environment settings.


To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:

  • Check the support matrix for the list of supported SAP ASE versions.
  • Download SEP sesam version 4.4.3 Tigon or higher. It is highly recommended to use the latest SEP sesam version. The server that is hosting the SAP ASE database must have a SEP sesam Client installed and added to SEP sesam environment. For details, see SEP Sesam Quick Install Guide.
  • Verify that your network is set up correctly and that DNS name resolution is successful. Note that forward and reverse DNS resolution is required by SEP sesam. For details, see How to check DNS configuration.
  • It is recommended that 10 gigabit Ethernet (10GbE) is available for larger backups.
  • Once your SEP sesam is installed, import your SEP sesam license. For details, see Licensing.
  • Configure SEP sesam and ensure that a data store has sufficient space. For general details, see SEP sesam data store. For more details on SEP sesam configuration, see SEP sesam first steps.

Configuration procedure

Note that the following procedure depends on the SEP sesam version and the backup method you intend to use; some of the steps may also be operating system specific (Linux or Windows).

For example, if you are using SEP sesam version 4.4.3 which only provides SAP ASE external backup via isql, you have to follow the procedure as set out below. However, v. ≥ 4.4.3 Grolar already provides most of the required SAP ASE configuration; whether you need to perform additional steps depends also on the used backup method.

Once you have downloaded the SEP sesam package, proceed as follows. Note that if you intend to manually install the library, the following prerequisites must be met:

  • You must know where your SAP ASE database server is installed (for example, <DRIVE>:\sybase\<SID>).
  • Ensure that you have read/write permissions to access your $SYBASE_ASE or %SYBASE_ASE% directory.
  • You must know your database server administrator (SA) password.


  1. Locate the libsepsybase.so (Linux) or libsepsybase.dll (Windows) file in your SEP sesam installation path. The default installation path on Linux is /opt/sesam/bin/sesam and on Windows C:\Program Files\SEPsesam\bin\sesam.
  2. Copy the file to your $SYBASE/$SYBASE_ASE folder on Linux or %SYBASE%\%SYBASE_ASE% on Windows.
  3. Linux specific: Make sure that the file is executable for the user that runs your SAP ASE database process.
  4. If you intend to use integrated SAP ASE backup and you are using version ≤ 4.4.3. TigonV2, you have to set the required system environment variables used by your SAP ASE software manually, as described below in Setting SAP ASE environment variables.
  5. If you intend to use external backup via isql, you have to enable dump history file. Note that this is not required with integrated SAP ASE backup as sbc_proxy automatically enables backup history.
  6. To protect your SAP ASE databases, you must configure SAP Adaptive Server as a SEP sesam Client. For details, see Configuring Clients.

Setting SAP ASE environment variables

If you are using version ≤ 4.4.3. TigonV2, you have to set the required system environment variables used by your SAP ASE software manually. According to your operating system, proceed as follows.

On Linux

The environment variable SYBASE must be set in the program environment. See SAP Adaptive Server Enterprise 16.0 > Configuration Guide for UNIX Adaptive Server Enterprise 16.0 > About SAP ASE Environment Variables. If it is not set, modify the <SESAM ROOT>/var/ini/sm.ini file on a client by modifying or adding the [ENVIRONMENT] section. The value for SYBASE depends on the SAP ASE installation; use a value that applies to your environment.


Afterwards, restart the SEP sesam daemon:

 /etc/init.d/sesam restart

On Windows

SAP ASE configuration is extracted from the Windows registry. The values of RootDir and CurrentVersion are read under HKEY_LOCAL_MACHINE\SOFTWARE\SYBASE\SQLServer to set the OCS binary directory. For details, refer to Configuration Guide for Windows Adaptive Server Enterprise 16.0: SAP ASE Registry Keys.

Enabling dump history file

This step is only required if you intend to use external backup via isql, for example, to use multiple stripes and backup your data in concurrent streams. This is not required with integrated SAP ASE backup as sbc_proxy automatically enables backup history.

SAP Adaptive Server maintains the history of all backups from dump database and dump transaction commands in a dump history file. By default, the backup history is not enabled. To enable the dump history feature for your SAP ASE instance, use the following command:

sp_configure "enable dump history",1

The default dump history file name is dumphist. For details, refer to SAP ASE article: Enhancements to Dump and Load.