Skip to main content

KBA1231 How to Discover SAP ASE Instances Which Use Multiple Network Handlers



When adding a SAP ASE or Sybase ASE environment, the Delphix Engine may be unable to discover ASE instances that are not listening on the same network address that was used for discovery. In these cases, you may receive the following warning:

WARNING: Error during discovery for instance "INSTANCENAME" : "Failed to 
connect to instance "INSTANCENAME over JDBC.". Skipping discovery for 
instance "INSTANCENAME".


There are several circumstances in which an ASE instance may be configured to listen on other network interfaces:

  • To support the use of clustering/failover technologies such as Veritas Cluster Server
  • To support the concept of "virtual host names" or "virtual IPs" (VIP) to provide abstraction for client applications
  • To facilitate a previous database migration to new infrastructure
  • As a result of manual configuration of the ASE instance by Database Administrators for other reasons


For guidance and best practices for configuring the Delphix Engine to work with clustering or failover technologies, please contact your Professional Services or Customer Success representative.

To verify whether an ASE instance is using different multiple network interfaces, use the sp_listener stored procedure when connected to the instance using isql:

1> sp_listener status
2> go
 proto   host                               port         status
 tcp     secondary-hostname-or-ip-address   4559         active

As described in ASE document Configuring the Server for Multiple Network Handlers, this configuration is read from the $SYBASE/interfaces file on your ASE server during instance startup.


To allow discovery of instances using multiple network interfaces, use the Add Environment dialog to add the environment once per network interface.

Each environment added in this way should have:

  • A unique Host Address; and
  • A unique Toolkit Path


The Delphix Engine expects that the files deployed to the Delphix Toolkit directory are persistent. Any failover of the ASE service to a different host must ensure that the Delphix Toolkit directory remains consistent between both hosts, with all files and permissions intact.

Deploying the Delphix Toolkit multiple times will result in increased disk space consumption, and may circumvent concurrency limitations that the Delphix Engine introduces to minimize the impact of the Delphix Engine on your Source Environments. If your environment requires you to add the host same several times using this process, please contact your Delphix Professional Services representative or Customer Success Manager to discuss best practices or alternative solutions.

Using the example interfaces file provided above, the following inputs could be used to add the INSTANCENAME instance:


Configuring the Server for Multiple Network Handlers (SyBooks Online)

sp_listener (SyBooks Online)