This section includes troubleshooting information about common errors.
Turn on debugging for Adaptive Server. Use trace flag 2205 to get high-availability-related debugging information. The following isql session turns on debugging and redirects messages to the console:
dbcc traceon(2205) dbcc traceon(3604)
When your system reports errors, first check the error log. Any error message with a message ID greater than 2,000,000 is an error message from the HAase agent.
The VCS error logs are located in /var/VRTSvcs/log/log_name.log. Among them, the engine_A.log is an important source of information.
The system error log is located in /var/log/syslog.
Sybase recommends that you use the following monitoring tools to find information about your system:
hagui – a GUI tool,
hastatus – a command line tool.
The following trigger scripts, which alert you of events on the VCS system: injeopardy, preonline, postonline, postoffline, resnotoff, resfault, sysoffline, violation.
When one service group fails over from the primary host to the secondary host, the Adaptive Server on the secondary host takes over all its resources, but the Adaptive Server on the failed-over group is not started, and VCS may indicate that the HAase resource is “faulted” on the secondary host. Use the following command on the secondary host to clear the state after fail over:
hares -clear sybase_res_name -sys secondary_host_name
