Home

	Expand Search

Installation Guide Adaptive Server Enterprise for IBM RISC System/6000 AIX

Chapter 10 Troubleshooting

Chapter 10

Troubleshooting

This chapter provides instructions for troubleshooting installation error messages.

If this chapter does not describe the error message you are encountering, see the Error Messages and Troubleshooting Guide.

Overview

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 "Error log locations" for the location of the error log files for the installation utilities and the servers.

Table 10-1 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 svrbuild unexpectedly quits, or if you cannot correct the problem, see the Error Messages and Troubleshooting Guide.

Error log locations

The information in the error logs can help you determine the reason and possible solution for an error message.

For installation utilities

Table 10-2 lists the default error log locations for the installation, upgrade, and setup utilities.

For Sybase servers

Table 10-3 lists the default error log locations for each Sybase server.

Solutions to common installation problems

If this section does not describe the problem you are experiencing, see the Error Messages and Troubleshooting Guide.

Unable to use X-Windows

If the setup and installation utilities do not display correctly, you may have to adjust the resolution on your monitor.

To change to a smaller font size issue the following UNIX commands:

% cd $SYBASE
% chmod +w xappdefaults
% cd xappdefaults
% chmod +w *
% foreach i(*) 
? cat $i | sed -e "s/140/100/g" | sed -e "s/^#D/D/g" | sed -e "s/^#S/S/g" > p
? mv p $i
? end
%

The installation utilities will use approximately 25 percent less screen space.

Fatal Error: Cannot Map libct.so

If you execute srvbuild and get this message:

22900:srvbuild: /sbin/loader: Fatal Error: cannot map libct.so

You need to set the shared library environment variable. For more information on setting this environment variable, see Chapter 5, "Post-Installation Tasks."

Depending upon your platform, the file names and the error message may vary slightly.

Cannot eject the CD from the drive

If you cannot eject the CD from the drive:

• Check to see whether the CD drive path is the current directory (pwd) in a UNIX terminal window. If it is, change (cd) to another directory.

• Check for sybhelp processes. If these processes exist, kill them using the UNIX kill command.

DISPLAY environment variable not set correctly

If you run Studio Installer and you get this error message:

The DISPLAY environment variable is not set correctly. 

it means that the DISPLAY environment variable on the remote machine is not set correctly to display the Studio Installer user interface to your local machine.

To correct the problem, enter the following command at the UNIX prompt of the remote machine: For C shell:

setenv DISPLAY host_name:0.0 

DISPLAY=host_name:0.0; export DISPLAY

where host_name is the name of the machine on which you want the Studio Installer interface to appear (that is, on your local machine).

Client not authorized to connect to server

If you run Studio Installer and you get this error message:

Xlib: connection to "host_name" refused by server
Xlib: Client is not authorized to connect to Server
xhost: unable to open display "host_name"

it means the remote machine does not have permissions to display the user interface on the local machine where you are working.

To correct the problem, enter the following command at the UNIX prompt of your local machine:

xhost +remote_machine 

where remote_machine is the machine on which you are running Studio Installer.Restart Studio Installer.

Address already in use

If you receive the following message from srvbuild:

kernel: ninit: bind, Address already in use 

To correct the problem, enter a different port number on the srvbuild screen. The command netstat -a produces a list of port numbers in use.

Adaptive Server failed to start

The shared memory of the operating system may not be set high enough.

To correct the problem, see Chapter 4, "Installing Sybase Servers " for instructions on adjusting the shared memory value and restart the installation or upgrade process.

Cannot start XP Server

You may receive the following message from XP Server, when it is invoked by xp_cmdshell or some other extended stored procedure:

Msg 11018, Level 16, State 1:
Procedure "xp_cmdshell", Line 2:
XP Server must be up for ESP to execute.
(return status = -6)

Verify that there is an XP Server entry in Adaptive Server's sysservers table. If you created XP Server separately (in a different srvbuild session) from Adaptive Server and you did not specify a related Adaptive Server, srvbuild cannot update the sysservers table.

Use sp_addserver to add an entry to the sysservers table.

Configuration failed

Check the location of the system shared libraries.

The shared libraries libXt.a and libX11.a are normally stored in /usr/lpp/X11/lib/R5. The libXm.a library is normally located in either /usr/lpp/X11/Motif1.2/lib or /usr/lpp/X11/R5/Motif1.2.

If these shared libraries are located in directories different from the above, set the LIBPATH environment variable to indicate these other directories.

See "Environment variables " for instructions on how to set LIBPATH.

Stopping Adaptive Server after a failure

If the installation or upgrade session fails after you start Adaptive Server, use the shutdown command:

1. Log on as "sa".

2. Shut down Adaptive Server using the shutdown with nowait command. Using the with nowait option stops the Adaptive Server immediately, without waiting for currently executing SQL statements to finish:

   1> shutdown with nowait
   2> go

Recovering from a failed installation

If the installation does not succeed, the installation program displays error messages. Review the error messages and your Adaptive Server error log to determine the cause of the installation failure. For default error log locations, see Table 10-3.

If the installation program quits while you are configuring Adaptive Server, perform the following steps:

1. View the contents of the log file generated by Adaptive Server. For default error log locations, see Table 10-3.

2. Take any suggested actions to correct the problem.

3. If the installation fails after the installation program has created any operating system files, such as the master device or system procedures device files, delete those files.

4. If the installation fails after the installation program starts the Adaptive Server that you are attempting to install, shut down that server. Follow the procedure under "Stopping Adaptive Server" before performing step 5.

5. Use asecfg to restart the configuration.

Troubleshooting resource file installations

If you encounter problems during the build, configure, or upgrade of Adaptive Server using the srvbuild[res], sqlloc[res], or sqlupgrade[res], it may be that these utilities did not allow enough time for Adaptive Server to shut down properly.

You can set the environment variable SYBSHUTWAIT to force the utilities to wait for Adaptive Server to shutdown. For example:

% setenv SYBSHUTWAIT 120

This forces the utility to wait for 2 minutes to allow Adaptive Server to shut down before proceed with the next task.

If Adaptive Server or SQL Server fails the pre-upgrade test, sqlupgrade displays:

Server SERVER_NAME failed preupgrade eligibility test. See log for more information.

1. From the Upgrade window, select Exit.

2. Examine the log file created in the $SYBASE/$SYBASE_ASE/init/logs directory to find out why Adaptive Server or SQL Server failed the pre-upgrade eligibility test.

   If the log contains messages about insufficient space in sybsystemprocs, follow the instructions in "Increasing the size of the sybsystemprocs database" to correct the problem.

   After you resolve any problems, shut down Adaptive Server or SQL Server and use sqlupgrade to complete the upgrade session.

Recovering from a failed upgrade

If the upgrade process does not succeed, the installation program displays error messages. Review the error messages and the Adaptive Server error log to determine the cause of the upgrade failure. For default error log locations, see Table 10-2.

You may need to restore your databases due to a failed upgrade.

If you think the upgrade failure or its cause may have damaged your databases, restore the databases from backups. For information on restoring databases, see the System Administration Guide.

If you are concerned about the possible corruption of your databases, exit sqlupgrade, but do not attempt to restart the upgrade session until you have restored the databases from backup. After restoration is complete, retry the upgrade.

Whether you can safely re-run the upgrade depends on when the failure occurred in the upgrade process. If the failure occurs while the message: "Starting to upgrade Adaptive Server" is displayed, it is safe to re-run the upgrade program.

1. Try to fix the problem that caused the upgrade to fail.

2. Run the upgrade again.

If the upgrade fails:

• Before returning the message "Setting upgrade version to 12.5", you may need to restore your latest database backup, and restart the upgrade.

• After returning the message "Setting upgrade version to 12.5", it is not necessary to restart the upgrade. The installation utility considers the upgrade to be complete.

Also, it is not necessary to restore a database from a backup unless that database failed during the upgrade.

If Adaptive Server did not finish recording the upgrade in the sysattributes table before the failure occurred.

1. Fix the problem that caused the failure.

   The first error message indicates the cause of the failure. If you can, solve the problem and proceed to step 2. For example, you can usually correct an 1105 error with a dump transaction command. However, more complex problems may have to be referred to Sybase Technical Support.

2. Execute the following SQL statements to allow Adaptive Server to complete recording the upgrade:

   1> declare @dbname varchar(30)
   2> select @dbname = min(name)
   3> from sysdatabases
   4> while @dbname is not null
   5> begin

   6> online database @dbname
   7> select @dbname = min(name)
   8> from sysdatabases
   9> where name > @dbname
   10> end

If the error logs or messages clearly indicate the cause of failure, and you do not believe your databases were damaged, you can attempt to fix the problem and re-run the upgrade immediately.

1. Exit the sqlupgrade program.

2. Perform the necessary actions to fix the problem.

   For example, if the error log indicates that the upgrade failed because your existing databases do not contain enough space, use the alter database command to increase the available space.

3. It may be necessary to shut down Adaptive Server. Follow the instructions for "Stopping Adaptive Server".

   Shutting down the server enables the installation program to start the server and re-run the upgrade session.

4. Start sqlupgrade again.

5. Select Upgrade Adaptive Server, and proceed with the upgrade.

If the upgrade fails again, and you cannot determine the cause of failure, check the error log file to find out when and where the upgrade failed, and contact Sybase Technical Support.

By default, the log file is located in $SYBASE/$SYBASE_ASE/install/errorlog.

Troubleshooting SySAM

When you start Adaptive Server with SySAM support, problems acquiring licenses or contacting the asset management software appear in the Adaptive Server error log file, lmgrd.log ($SYBASE/$SYBASE_SYSAM/log).

Authorization code input error

When you purchase licenses for Sybase Adaptive Server products, you are issued a Sybase Software Asset Management Certificate. The certificate has the following information for each product:

• Order Number

• Feature Name

• Feature Count

• Software Version

• Authorization Code

• Product Description

This information is used by SySAM to build the license file, with new licensed features appended to the end of the file. Here is a sample license file, license.dat:

SERVER server1 ANY 4100

VENDOR SYBASE $SYBASE/$SYBASE_SYSAM/bin/SYBASEUSE_SERVERINCREMENT ASE_SERVER SYBASE 12.5 PERMANENT 1000 123456789123 SN=10001 OVERDRAFT=10000 ck=0INCREMENT ASE_JAVA SYBASE 12.5 PERMANENT 1000 123456789123 SN=10001 OVERDRAFT=10000 ck=0INCREMENT ASE_DTM SYBASE 12.5 PERMANENT 1000 123456789123 SN=10001 OVERDRAFT=10000 ck=0INCREMENT ASE_HA SYBASE 12.5 PERMANENT 1000 123456789123 SN=10001 OVERDRAFT=10000 ck=0

• ASE_<FEATURE> is the feature name, such as ASE_SERVER, ASE_JAVA, and so on.

• 12.5 is the version number.

• Feature Count immediately follows the license type, PERMANENT.

• SN=10001 is the Order Number.

• OVERDRAFT= ### is the maximum licenses that can be checked out.

• 123456789123 is a 12-digit number representing the authorization code.

The authorization code is case sensitive. If you make a mistake while entering the authorization code, correct it by accessing the license file with a text editor, making the necessary changes, and saving the file.

The file is located in $SYBASE/$SYBASE_SYSAM/licenses/license.dat.

Warning!

Tampering with any portion of the licenses file other than the authorization code invalidates the license.