> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/sybase-ase-adaptive-server-enterprise.md).

# Sybase ASE (Adaptive Server Enterprise)

This article outlines the integration with the Sybase ASE (Adaptive Server Enterprise) connector, enabling metadata management through features such as crawling, profiling, querying, data preview, and automatic and manual lineage building. The connector extracts metadata for schemas, tables, views, columns, procedures, functions, triggers, indexes, and relationships.

The connector establishes connectivity to Sybase ASE using the jTDS JDBC driver. It authenticates using a service account configured with the required database credentials and permissions to access system catalog tables for metadata extraction and user tables and views for profiling, data preview, and lineage source code retrieval.

<img src="/files/dQE5DneGoPriKhcuR8wl" alt="" height="356" width="624">

## Overview

### Connector Details

<table data-header-hidden><thead><tr><th width="351.6666259765625"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>RDBMS</td></tr><tr><td>OvalEdge Release Supported</td><td>Release6.3.4 and later</td></tr><tr><td><p>Connectivity</p><p>[How the connection is established with Sybase ASE (Adaptive Server Enterprise)]</p></td><td>JDBC Driver</td></tr></tbody></table>

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Profiling                                    |       ✅      |
| Query Sheet                                  |       ✅      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ❌      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

### Metadata Mapping

The following objects are crawled from Sybase ASE (Adaptive Server Enterprise) and mapped to the corresponding UI assets.

| Sybase ASE Object | Sybase ASE Attribute | OvalEdge Attribute | OvalEdge Category | OvalEdge Type      |
| ----------------- | -------------------- | ------------------ | ----------------- | ------------------ |
| Schema            | Schema name          | Schema             | Databases         | Schema             |
| Schema            | Schema comment       | Source Description | Databases         | Schema             |
| Table             | Table Name           | Table              | Tables            | table              |
| Table             | Table Type           | Type               | Tables            | table              |
| Table             | Table Comments       | Source Description | Descriptions      | Source Description |
| Columns           | Column Name          | Column             | Table Columns     | -                  |
| Columns           | Data Type            | Column Type        | Table Columns     | -                  |
| Columns           | Description          | Source Description | Table Columns     | -                  |
| Columns           | Ordinal Position     | Column Position    | Table Columns     | -                  |
| Columns           | Length               | Data Type Size     | Table Columns     | -                  |
| Views             | View Name            | View               | Tables            | view               |
| Views             | text                 | View Query         | Views             | View               |
| Procedures        | ROUTINE\_NAME        | Name               | Procedures        | -                  |
| Procedures        | DESCRIPTION          | Source Description | Descriptions      | -                  |
| Procedures        | ROUTINE\_DEFINITION  | Procedure          | Procedures        | -                  |
| Functions         | ROUTINE\_NAME        | Name               | Functions         | -                  |
| Functions         | ROUTINE\_DEFINITION  | Function           | Functions         | -                  |
| Functions         | DESCRIPTION          | Source Description | Descriptions      | -                  |
| Triggers          | Trigger Name         | Name               | Triggers          | -                  |
| Triggers          | Trigger Definition   | Trigger Data       | Triggers          | -                  |
| Triggers          | Trigger Type         | Type               | Triggers          | -                  |
| keys              | Keys                 | -                  | -                 | -                  |
| Indexes           | Index name           | Index              | Indexes           | Index              |
| Indexes           | If unique            | Yes /No            | Indexes           | Index              |

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

#### **Whitelisting Ports**

Make sure that inbound port “5000” is whitelisted to enable successful connectivity with the Sybase ASE.

{% hint style="warning" %}
The default port number for Sybase ASE is 5000. If a different port is used, ensure that the updated port number is specified during connection setup, the port is whitelisted, and communication between the system and Sybase ASE is properly established.
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
**👨‍💻 Who can provide these permissions?** The Sybase ASE (Adaptive Server Enterprise) administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

| Operations                  | Objects                                     | Sys Tables                                       | Access Permissions |
| --------------------------- | ------------------------------------------- | ------------------------------------------------ | ------------------ |
| Crawling                    | Schema                                      | sysusers                                         | Select             |
| Crawling & Profiling        | Tables & Views                              | sysobjects, sysusers                             | Select             |
| Crawling & Profiling        | Table Columns                               | sysobjects, syscolumns, systypes                 | Select             |
| Crawling                    | Foreign Keys / Relationships                | sysreferences, sysobjects, syscolumns            | Select             |
| Crawling                    | Indexes                                     | sysindexes, sysindexkeys, syscolumns, sysobjects | Select             |
| Crawling & Lineage Building | Views (Source Code)                         | sysobjects, syscomments                          | Select             |
| Crawling & Lineage Building | Stored Procedures & Functions (Source Code) | sysobjects, syscomments                          | Select             |
| Crawling                    | Triggers (Source Code)                      | sysobjects, syscomments                          | Select             |
| Profiling                   | User Tables / Views (Data)                  | Target user tables and views                     | Select             |

{% hint style="info" %}

* The connector requires SELECT permission on the listed SAP ASE system tables to retrieve metadata required for schema discovery, object crawling, relationship extraction, index extraction, and source code retrieval.
* SELECT permission on the target user tables and views is required to perform profiling operations, including row count, data preview, sample data retrieval, and column statistics.
* Lineage building for views, stored procedures, and functions requires access to the object definitions stored in the syscomments system table.
  {% endhint %}

### Connection Configuration Steps

{% hint style="warning" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log into **OvalEdge**, go to **Administration** > **Connectors**, click **+ (New Connector)**, search for **Sybase ASE (Adaptive Server Enterprise),** and enter the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="219.66668701171875">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "SAP ASE (Adaptive Server Enterprise)" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><p>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Sybase ASE (Adaptive Server Enterprise) connection              </p><p>(Example: "Sybase ASE (Adaptive Server Enterprise)_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</p></td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Server*</td><td>Enter the Sybase server hostname or IP address of the target data source (Example: sybase.example.com or 192.xxx.xx.20).</td></tr><tr><td>Port*</td><td>By default, the port number for Sybase ASE (Adaptive Server Enterprise), "5000" is auto-populated. If required, the port number can be modified as per the custom port number that is configured for Sybase ASE (Adaptive Server Enterprise).</td></tr><tr><td>Database*</td><td>Enter the name of the Sybase database to which the service account user has access.</td></tr><tr><td>Driver*</td><td>By default, the Sybase JDBC driver details are auto-populated and cannot be modified. The connector uses the jTDS driver to establish the connection.</td></tr><tr><td>Username*</td><td>Enter the service account username configured to access the Sybase database. Ensure that the account has the required permissions to access the database metadata and data.</td></tr><tr><td>Password*</td><td>Enter the password associated with the configured service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Oracle database:</p><ul><li>Automatic mode: The system generates a connection string based on the provided credentials.</li><li>Manual mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to the database name.</p></td></tr><tr><td>Plugin Server</td><td>Enter the server’s name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="219.6666259765625"></th><th></th></tr></thead><tbody><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles*</td><td>Select one or more users from the drop-down list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr><tr><td><strong>No of Archive Objects</strong></td><td></td></tr><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr><tr><td><strong>Bridge</strong></td><td></td></tr><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl/Profile

{% hint style="warning" %}
To perform crawl and profile operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling and profiling.

1. Navigate to the **Connectors** page and click **Crawl/Profile.**
2. Select the schemas to crawl.
3. The **Crawl** option is selected by default. To perform both operations, select the **Crawl & Profile** radio button.&#x20;
4. Click **Run** to collect metadata from the connected source and load it into the Data Catalog.
5. After a successful crawl, the information appears in the **Data Catalog** > **Databases** tab.

The Schedule checkbox allows automated crawling for a selected timeframe, from a minute to a year.

1. Click the **Schedule** checkbox to enable the Select Period drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the selected operation (**Crawl or Crawl & Profile**) at the scheduled time.

### Other Operations

The Connectors page provides a centralized view of all configured connectors and their health status.

**Managing connectors includes:**

* **Connectors Health:** Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including databases, tables, columns, and codes.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Profiler**: Customize data profiling rules and methods.&#x20;
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings:** Manage term associations at the connector level.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage:** Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="83">S. No</th><th width="145.66668701171875">Error Message</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td>1</td><td>JZ00L: Login failed / Login failed for user</td><td><p>Description: This error occurs when the supplied username or password is incorrect, the account is locked or expired, or the authentication configuration is invalid.</p><p>Resolution:</p><ul><li>Verify the username and password by connecting through a SQL client such as isql or DBeaver.</li><li>Ensure the login account exists, is unlocked, and the password has not expired.</li><li>Confirm that the login has access to the target database.</li></ul></td></tr><tr><td>2</td><td>JZ006: Caught IOException: java.net.ConnectException: Connection refused</td><td><p>Description: This error indicates that the application cannot establish a connection to the Sybase server because the host or port is incorrect, the database service is unavailable, or network traffic is blocked.</p><p>Resolution:</p><ul><li>Verify that the server name and port number are correct.</li><li>Check network connectivity using tools such as telnet or nc.</li><li>Ensure the Sybase server is running and firewall rules allow the connection.</li></ul></td></tr><tr><td>3</td><td>JZ006: Caught IOException: java.net.SocketTimeoutException: Read timed out</td><td><p>Description: This error occurs when the database server does not respond within the configured timeout period due to network latency, heavy server load, or unstable connectivity.</p><p>Resolution:</p><ul><li>Increase the connection or socket timeout value.</li><li>Verify network latency and stability between the application and database server.</li><li>Review database server performance and firewall idle timeout settings.</li></ul></td></tr><tr><td>4</td><td>UnknownHostException</td><td>Description: This error indicates that the configured hostname cannot be resolved to an IP address from the application server.Resolution:• Verify the hostname is entered correctly.• Validate DNS resolution using tools such as nslookup or dig.• Use the server IP address temporarily or update the DNS configuration if required.</td></tr><tr><td>5</td><td>No suitable driver / ClassNotFoundException: net.sourceforge.jtds.jdbc.Driver</td><td><p>Description: This error occurs when the required Sybase JDBC driver is unavailable, or the configured driver class is incorrect.</p><p>Resolution:</p><ul><li>Ensure the Sybase-compatible JDBC driver is available in the application classpath.</li><li>Verify that the configured driver class and JDBC URL are correct.</li><li>Restart the application after updating the driver configuration.</li></ul></td></tr><tr><td>6</td><td>JZ0C0: Connection is already closed / Stale pooled connection errors</td><td><p>Description: This error occurs when the connection pool attempts to reuse database connections that have already been closed due to database or network interruptions.</p><p>Resolution:</p><ul><li>Enable connection validation before reusing pooled connections.</li><li>Configure appropriate connection idle timeout and maximum lifetime settings.</li><li>Enable connection keepalive to prevent stale connections.</li></ul></td></tr><tr><td>7</td><td>Database '' not found / Cannot open database requested by login</td><td><p>Description: This error occurs when the specified database does not exist or the login account does not have permission to access it.</p><p>Resolution:</p><ul><li>Verify that the database name is correct.</li><li>Ensure the login is mapped to the specified database.</li><li>Grant the required database access permissions if necessary.</li></ul></td></tr><tr><td>8</td><td>Permission denied while metadata crawl (tables/views/procedures)</td><td><p>Description: This error occurs when the service account can connect to the database but lacks sufficient permissions to access system catalog tables or database objects required for metadata extraction.</p><p>Resolution:</p><ul><li>Grant the required SELECT permissions on the necessary system catalog tables.</li><li>Verify metadata access using the same service account.</li><li>Use a service account with appropriate metadata access privileges.</li></ul></td></tr><tr><td>9</td><td>SSL/TLS handshake failures (handshake_failure, certificate path errors)</td><td><p>Description: This error occurs due to SSL/TLS configuration issues such as untrusted certificates, protocol mismatches, or certificate validation failures.</p><p>Resolution:</p><ul><li>Import the required certificate chain into the application's truststore.</li><li>Verify that the client and server use compatible TLS versions and cipher suites.</li><li>Ensure the certificate hostname matches the configured server name.</li></ul></td></tr><tr><td>10</td><td>Intermittent failures only from the application node</td><td><p>Description: This error indicates that connectivity issues exist only from the application environment due to network policies, firewall rules, proxies, or security group restrictions.</p><p>Resolution:</p><ul><li>Compare firewall, proxy, and security group settings between working and failing environments.</li><li>Test database connectivity directly from the application server.</li><li>Work with the network team to review routing rules and connection logs.</li></ul></td></tr></tbody></table>

***

&#x20;Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/sybase-ase-adaptive-server-enterprise.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.