Troubleshoot the Server

For Sybase server products, there are two categories of errors:

Errors generated by the installation, upgrade, and setup utilities
Errors generated by the server (Adaptive Server, Backup Server, and so on)

To determine the cause of an error, first look in the log file of the utility being used, to identify the task the utility was performing when it failed. Then check the server error log. See the Error Log Locations topic for more information.

The table, Troubleshooting guidelines for UNIX platforms, lists possible causes and solutions for common problems that you might encounter during a first-time installation or upgrade. If you continue to have problems, retry the installation or upgrade.

If the installation program or srvbuild unexpectedly quits, or if you cannot correct the problem, see the Error Messages and Troubleshooting Guide.

Table 1. Troubleshooting guidelines for UNIX platforms
Problem	Possible cause and solution
The installation program cannot start Adaptive Server.	Failure to start Adaptive Server is generally caused by a lack of available RAM or disk space. Make sure you meet RAM requirements. If you have the required RAM, remove, then reinstall all applications to the hard drive and restart the installation process. After Adaptive Server is installed, there should be 25MB of free disk space left in the disk drive. Adaptive Server needs approximately 18MB for creating shared memory files. Verify that you are logged in as System Administrator. You must log in as an administrator to start Adaptive Server. Shut down Monitor Server before restarting Adaptive Server. Note: Adaptive Server may not start if it cannot find a SySAM license and if the grace period has expired. Check the Adaptive Server error log for the cause of the license checkout failure and fix the issues.
The installation program cannot start Adaptive Server – private installation only.	The second instance in the cluster may fail to start if its configuration file does not match that of the first instance. Adaptive Server keeps a master copy of the current configuration file on the quorum device along with a version number. If the version number on an instance does not match that stored on the quorum device, the instance fails to start. If Adaptive Server detects a nonmatching configuration file during the start process, the server extracts a copy of the current configuration file from the quorum device and copies it to the second instance. At this point the instance fails to start; you must restart the instance. If you know that the configuration file on the second or other instance is not current, you can use the qrmutil utility to extract a current copy of the configuration file from the quorum device, and then start the instance. Note: Sybase recommends that you do not change the config file version parameter in the configuration file. Doing so may cause the instance to fail to start as the configuration file version number on the master configuration file on the quorum device may no longer match that on the server configuration file.
The installation program detects reserved word conflicts.	See the Stopping Adaptive Server After a Failure topic.
The upgrade fails.	See the Recovering From a Failed Upgrade topic.