Sybase Technical Library - Product Manuals Home
[Search Forms] [Previous Section with Hits] [Next Section with Hits] [Clear Search] Expand Search
Chapter 7: Getting Started with Enterprise SQL Server Manager [Table of Contents]

Enterprise SQL Server Manager Installation and Planning Guide

[-] Appendix A: Troubleshooting

Appendix A

Troubleshooting

This appendix contains possible remedies for common problems you may encounter when installing Enterprise SQL Server Manager. It also contains information that may be helpful if you have problems installing the Tivoli Management Platform. If you cannot resolve a problem after trying the solutions listed here, ask the designated person at your site to call Sybase Technical Support for help.

Installing the Tivoli Management Platform

This section discusses Tivoli installation issues:

Installing the Tivoli Management Platform from a Remote CD-ROM Drive

If you try to install the TMP from a CD-ROM drive on a remote machine that is mounted on the local machine, and the two machines are on different platforms, the installation may fail due to a mismatch of file permissions and naming conventions. On Sun SPARC Solaris machines, Tivoli filenames must be in uppercase for the installation process to work.

If you have this problem, there are two courses of action:

Copying Tivoli Files to a Hard Disk

If you want to install the TMP from a hard disk rather than the Tivoli CD, copy the files from the Tivoli CD to a directory on a server. Use a command similar to the following:

cp -rp /cdrom/* /install/tivoli2.5

On IBM RS/6000 AIX and Sun SPARC Solaris machines, Tivoli filenames must be in uppercase for the installation process to work. List the files on the CD using the ls command. If the file names are in lowercase, you can convert the filenames from lowercase to uppercase with a script provided on the Tivoli CD. The script is /bin/wcpcdrom.

  1. From the Tivoli CD, run wpreinst.sh. This command creates the /bin directory in which wcpcdrom is located.

  2. Execute wcpcdrom as follows:

    wcpcdrom source target
    where source is the CD or the directory into which you copied the files, and target is an empty directory on your hard disk. The command creates links from the target directory to the CD or other directory with all the filenames being uppercase.

  3. Continue the TMP installation process by running
    /absolute pathname/WPREINST.SH as described in the Tivoli Management Platform Planning and Installation Guide.

    Note: You must run the WPREINST.SH and wserver commands from the Tivoli installation directory, treating the directory into which you copied the files as a CD-ROM.

Installing Tivoli in a Directory Other than the Default

To install Tivoli software in a directory other than the default, use the -p argument to the wserver command. This flag prefixes the Tivoli default directory paths with the pathname you specify. If you install Tivoli in a directory other than the default, you can remove Tivoli files by deleting the installation directory and all subdirectories.

Verifying the TMR License Key

If Tivoli and Enterprise SQL Server Manager appear to install correctly, but you cannot manage SQL Server, it is possible that you entered the TMR license key incorrectly. To verify that you correctly typed the TMR license key when you installed TME, compare the license key currently registered in the TMR with the one printed on your Sybase packing slip (or with the license key supplied by your Tivoli support provider). Follow these steps:

  1. Display the license key currently registered in the TMR using the following Tivoli command (you must have super or senior role to do this):

    odadmin get_platform_license
  2. Compare the TMR license key on your packing slip or installation worksheet with the one displayed by the odadmin command. The two keys should match exactly. If they differ, you must change the license key currently registered in the TMR. You can change the current TMR license key using the following Tivoli command (you must have super or senior role to do this):

    odadmin set_platform_license license_key
    where license_key is the new TMR license key you want to register.

    For more information about viewing and changing current license information, see Chapter 4, "TME Installation," in the Tivoli Management Platform Planning and Installation Guide. For more information about the odadmin command, see the Tivoli Management Platform Reference Manual.

Problems in Chapter 4, "Installing Enterprise SQL Server Manager"

You experience CD-ROM reading errors.

The Sybase CD-ROM format is ISO 9660. Your operating system reads this format by default. However, if you experience CD-ROM reading errors, check your operating system to verify that the ISO 9660 option is set.

An error message box appears when you choose the Install Product menu command.

When you choose Desktop® Install® Install Product, the following message box may appear:

Figure A-1: Installation media settings error
raster

In most cases, this error message appears because the default media path is set to a directory that does not contain any products to install.

Choose OK to close the message box. When you do this, the File Browser dialog box opens. Continue the normal installation procedure from step 3.

No products appear in the Select Product to Install list box on the Install Product dialog box.

Try the following procedure:

  1. In the Install Product dialog box, choose Select Media to open the File Browser dialog box.

  2. Remove "/auto" if it appears in the beginning of the string in the Path Name text box.

  3. Choose Set Media & Close.

"Sybase Enterprise SQL Server Manager" should now appear in the Select Product to Install list box.

You have trouble installing Enterprise SQL Server Manager on multiple hosts in one operation.

You may be trying to install on the wrong operating system. Check the Enterprise SQL Server Manager CD to be sure it is the correct operating system for the machine on which you are installing.

The Sybase environment may be different on the different machines on which you are installing. If this is the case, start the installation again for the machines with different Sybase environment locations and change the information in the Install Options dialog box.

Note: If some Enterprise SQL Server Manager files were installed on a client before the installation failed, you must remove all Enterprise SQL Server Manager files from the client before you start the installation process again.

You specify the wrong Sybase Environment or the Sybase Environment changes.

Install Enterprise SQL Server Manager again. In the Install Options dialog box enter the correct Sybase Environment. The installation procedure changes the Sybase Environment, but does not affect any other aspects of your installation.

Problems in Chapter 6, "Installing Patches"

An error message box appears when you choose the Install Patch menu command.

When you choose Install and then Install Patch from the Desktop menu, the following message box may appear:

Figure A-2: Installation media settings error
raster

In most cases, this error message appears because the default media path is set to a directory that does not contain any patches.

Choose OK to close the message box. When you do this, the File Browser dialog box opens. Continue the normal patch installation procedure from step 3 on .

Problems in Chapter 7, "Getting Started with Enterprise SQL Server Manager"

You have trouble connecting to SQL Server.

Verify that the ESSM_INTERFACES object dispatcher environment variable is set correctly. This variable identifies the full path name of the interfaces file that Enterprise SQL Server Manager is using to locate the SQL Server. To check this, issue the odadmin environ get command at the UNIX prompt:

odadmin environ get

The output from the command shows the file name currently assigned to ESSM_INTERFACES. If it is not correct, you can reset the variable to a new name using the odadmin environ set command.

For example:

odadmin environ get >myfile

lists all object dispatcher environment variables and their values, and saves the listing in the file myfile. You can edit this file to alter the line:

ESSM_INTERFACES=interfaces

where interfaces is the full path name of the interfaces file that Enterprise SQL Server Manager is currently using to locate SQL Server. You can change this path name to identify a different interfaces file, save your changes to myfile, and then enter:

odadmin environ set <myfile

to update the object dispatcher environment so that Enterprise SQL Server Manager will use the new ESSM_INTERFACES value.

For information on the odadmin command, see the Tivoli Management Platform Reference Manual.

You have trouble creating a managed SQL Server resource.

Try one or more of the following procedures:

Strange characters appear when you type in text boxes in the GUI.

Try the following procedure:

  1. Find the location of the XKeysymDB file on your system.

  2. Enter the following C shell command:

    setenv XKEYSYMDB /usr/lib/X11/XKeysymDB
    or for Bourne shell or Korn shell enter:

    XKEYSYMDB=/usr/lib/X11/XKeysymDB
    export XKEYSYMDB
    This example assumes the XKeysymDB file is in the /usr/lib/X11 directory¾modify the command as necessary if your XKeysymDB location is different.

  3. Shut down the Tivoli desktop and restart it.

If this solves the problem, you may want to set this environment variable permanently in your login file.

You get an error message relating to a SQL Server login.

Try one or more of the following procedures:

The Sybase logo no longer appears on the Tivoli desktop or the Set SQL Server Logins button no longer appears on the Edit Logins dialog box.

Installing an additional TME management application after installing Enterprise SQL Server Manager may have overwritten Sybase customizations to the TME desktop. To restore the customizations, enter the following command:

$BINDIR/SSM/essm_cust_after.sh $BINDIR/SSM

Verifying Remote Media Networking

If you are using a remote media device, verify that you can log in remotely to the machine to which the tape device is connected.

For each platform for which you are extracting Enterprise SQL Server Manager files from a remote media device, use the following procedure to verify that you connect to the remote host machine:

  1. Log in to the local machine.

  2. Run the command:

    telnet remote_machine_name
    where remote_machine_name is the name of the machine to which the tape device is connected.

    If the telnet command is successful, you will get a login prompt. Log out and record the remote host machine name on your worksheet (raster).

    If telnet does not allow you to log in to the remote machine from the local machine, see your network software documentation for remedies.

  3. Verify that your login has permission to connect to the remote machine using the rsh command (or remsh for HP-UX). To check this, enter:

    rsh remote_machine_name "ls"
    or, for HP-UX:

    remsh remote_machine_name "ls"
    where remote_machine_name is the name of the machine to which the tape device is connected.

    If the rsh or remsh command is successful, you will see a directory listing produced by ls. Continue to verify the media networking for any remaining platforms.

    If rsh or remsh does not allow your login to connect to the remote machine, see your network software documentation for remedies.


      
      

      

        
          Chapter 7: Getting Started with Enterprise SQL Server Manager
          
              [Table of Contents]