Troubleshooting

Before starting Adaptive Server for IPv6-aware operations, make sure that your infrastructure is correctly set up. Once your operating system is correctly configured, an IPv6 connection handler can be configured and enabled. Configuring and enabling the IPv6 connection handler requires adding an additional DCL entry. A single Adaptive Server configuration can typically carry up to 32 connection handler assignments within the DCL.

For example if you have a Site-local setup with two domains administrated under the nameserver setup:

sybase.com - being responsible for all IPv4 networking applications v6.sybase.com - being responsible for all IPv6 networking applications

The DCL entry for Adaptive Server to start named “SYBASE” on the host “revival” for port 17100 would typically look like:

SYBASE

master tcp ether revival.sybase.com 17100 query tcp ether revival.sybase.com 17100 master tcp ether revival.v6.sybase.com 17100 query tcp ether revival.v6.sybase.com 17100

In the above example, when Adaptive Server is started with IPv6-awareness it creates two connection handlers. One listens on port 17100 for incoming IPv4 Clients connection requests, and the other listens on port 17100 for incoming IPv6 Clients connection requests.

Troubleshooting

This section describes how to correct some common situations that may cause a server to not start.

Server fails to start

If a server fails to start with the following message, the port number specified in the interfaces file may be in use:

00:00000:00002:2003/09/22 12:37:23.63 kernel network name SERV_CORPNET, type ether, port 4559, filter NONE

00:00000:00002:2003/09/22 12:37:23.65 kernel ninit: bind, Address already in use

00:00000:00002:2003/09/22 12:37:23.68 server Error: 1602, Severity: 18, State:

66

Adaptive Server Enterprise

Page 82
Image 82
Sybase DC35823-01-1500-04 manual Troubleshooting, Server fails to start