User's Guide
   PART 1. Working with Databases
     CHAPTER 1. Running the Database Server       

Troubleshooting server startup

This section describes some common problems when starting the database server.

  Ensure that your transaction log file is valid

During development, you may replace a database file with a new version. If you do not delete the transaction log at the same time, the existing transaction log file will not match the database. The server does not start under these conditions.

  Ensure that you have sufficient disk space for your temporary file

Adaptive Server Anywhere uses a temporary file to store information while running. This file is stored in the directory pointed to by the TMP or TEMP environment variable. This directory is typically c:\temp.

If you do not have sufficient disk space on the drive where the temporary directory is located, you will have problems starting the server.

  Ensure that network communication software is running

Appropriate network communication software must be installed and running before you run the database server. If you are running reliable network software with just one network installed, this should be straightforward. If you experience problems, if you are running non-standard software, or if you are running multiple networks, you may want to read the full discussion of network communication issues in Client/Server Communications.

You should confirm that other software that requires network communications is working properly before running the database server.

For example, if you are using NetBIOS under Windows 95, Windows for Workgroups, or Windows NT you may want to confirm that the chat or winpopup application is working properly between machines running client and database server software.

If you are running under the TCP/IP protocol, you may want to confirm that ping and telnet are working properly. The ping and telnet applications are provided with many TCP/IP protocol stacks.

  Debugging network communications startup problems

If you are having problems establishing a connection across a network, you can use debugging options at both client and server to diagnose problems. On the server, you use the -z command-line option. The startup information is displayed on the server window: you can use the -o option to log the results to an output file.