Sybase ASE Requirements
This section describes the requirements, access privileges, and other features of Fivetran HVR when using Sybase Adaptive Server Enterprise (ASE) for replication.
Supported Platforms
- Learn about the Sybase ASE versions compatible with HVR on our Platform Support Matrix page (6.3.5, 6.3.0, 6.2.5, 6.2.0, 6.1.5, and 6.1.0).
Supported Capabilities
- Discover what HVR offers for Sybase ASE on our Capabilities for Sybase ASE page (6.3.5, 6.3.0, 6.2.5, 6.2.0, 6.1.5, and 6.1.0).
Data Management
Learn how HVR maps data types between source and target DBMSes or file systems on the Data Type Mapping page. For the list of the supported Sybase ASE data types and their mapping, see Data Type Mapping for Sybase ASE.
Understand the character encodings HVR supports for Sybase ASE on the Supported Character Encodings page.
Supported Editions
HVR supports the following Sybase ASE editions:
- Developer Edition
- Enterprise Edition
- Express Edition
SAP Open Server SDK
Since v6.3.5/6
To run HVR operations, such as Capture, Integrate, Refresh, and Compare against a Sybase ASE location, you must install the SAP Open Server SDK at the location you specify in the Sybase_CT_Library location property. HVR loads the Open Server SDK libraries at runtime together with the Open Client (CT Library) libraries.
The required Sybase environment variables ($SYBASE, $SYBASE_OCS, and $LD_LIBRARY_PATH) must be set on each machine running an HVR process that connects to a Sybase ASE location.
You can configure the Sybase runtime environment in either of the following ways:
- Before starting HVR, run the Sybase initialization script for your shell from the applicable Sybase installation directory (SYBASE.sh for bash, sh, or ksh; SYBASE.csh for csh or tcsh), so that the environment variables it sets apply to the HVR process.
- Define action Environment for the required environment variables, setting Name to the variable name and Value to the corresponding value from the Sybase runtime environment.
For LTL and RTL capture, follow the requirements in Runtime Environment for LTL and RTL Capture.
Runtime Environment for LTL and RTL Capture
Initialize the Sybase runtime environment using the appropriate initialization script from the SAP Replication Server installation.
After sourcing the initialization script, verify that:
- $SYBASE refers to the SAP Replication Server installation.
- $SYBASE_OCS identifies the Open Client/Open Server installation used by Replication Server.
- $LD_LIBRARY_PATH includes the required Open Client/Open Server library directories, including the lib and lib3p64 subdirectories of $SYBASE/$SYBASE_OCS.
Do not initialize the LTL or RTL Capture environment using the initialization script from a standalone SAP ASE installation. Using an ASE-based runtime environment may cause connection failures or cause the Capture job to terminate when SAP RepAgent or Replication Server connects.
If an LTL or RTL Capture job terminates during encrypted password authentication, see LTL or RTL Capture Crashes During Encrypted Password Login.
Kerberos Authentication
Before you configure HVR for Kerberos authentication with Sybase ASE, refer to the Sybase ASE documentation for information about how to configure Kerberos for Sybase ASE.
HVR supports two ways for Kerberos authentication:
Accessing the kerberized Sybase ASE server with the User and Key Tab parameters supplied. In this case, HVR will run kinit to authenticate itself. To use a keytab file with HVR, enter the details in the User and Key Tab fields of the Location Connection dialog.
Additionally, the following action must be defined for a Sybase ASE location:
Group Table Action Parameter(s) Sybase ASE * Environment Name=KRB5_CONFIGValue=full path to the krb5.conf file Accessing the kerberized Sybase ASE server without supplying the User and Key Tab parameters. In this case, the HVR Agent Listener (in case of a remote HVR Agent connecting to Sybase ASE) or the Scheduler (in case of a local HVR connecting to Sybase ASE) should be started from an already Kerberos-authenticated environment.
Limitation
HVR does not support bi-directional DDL replication if action AdaptDDL is defined on a Sybase ASE location.