Home

	Expand Search

Enterprise SQL Server Manager Installation and Planning Guide

Chapter 3: Preparing to Install Enterprise SQL Server Manager

Chapter 3

This chapter describes what you should do before you install Enterprise SQL Server Manager.

Installation Overview

You install Enterprise SQL Server Manager as a management application in the Tivoli Management Environment (TME). This requires the following steps:

1. Install the TME server and clients.

   For information about installing the TME, see Enterprise SQL Server Manager Release Bulletin, Tivoli Management Platform Planning and Installation Guide and Tivoli Management Platform Release Notes (Tivoli documentation and media are included with Enterprise SQL Server Manager). Also, be sure that any Tivoli patches are installed as directed in Tivoli Management Platform Release Notes or Enterprise SQL Server Manager Release Bulletin.

2. If you are installing Enterprise SQL Server Manager from tape, extract the Enterprise SQL Server Manager files into an installation directory. (If you are installing from a CD, install directly from the CD.)

3. Install Enterprise SQL Server Manager and required patches on the TEM server and desired TME clients using the TME desktop's Product Install and Patch Install dialog boxes.

The remaining sections in this chapter describe what to do before you install Enterprise SQL Server Manager.

Fill out the Enterprise SQL Server Manager Installation Worksheet as you read through this chapter and refer to it as you install Enterprise SQL Server Manager. Keep the completed worksheet for future reference. You may need to refer to this information if you call Sybase Technical Support.

Note: As you read this chapter, watch for the pencil symbol . in the margin to identify information to record on the worksheet.

The Enterprise SQL Server Manager Installation Worksheet is on the next two pages. You can remove it from the manual or photocopy it to have it available when you install Enterprise SQL Server Manager.

Enterprise SQL Server Manager Installation Worksheet

Install the TME Before You Proceed

Enterprise SQL Server Manager is a TME management application, and you install it using the TME desktop's standard Install Product dialog box. Therefore, before installing Enterprise SQL Server Manager, you must have the TME server and clients already installed and running.

TME Software

Your Sybase package includes the Tivoli software and documentation compatible with this release of Enterprise SQL Server Manager. The TME software is on a Tivoli CD and ready to install. To install the TME, follow the directions in Tivoli Management Platform Planning and Installation Guide and Tivoli Management Platform Release Notes.

If you are already a Tivoli user and want to install Enterprise SQL Server Manager into an existing TME installation, verify that the TME release level and any installed TME patches meet the requirements printed in Enterprise SQL Server Manager Release Bulletin for this release of Enterprise SQL Server Manager.

If your existing TME installation meets these requirements (or you are installing from the Tivoli CD included with Enterprise SQL Server Manager), check off "TME version and installed patches meet requirements for this release of Enterprise SQL Server Manager." on your worksheet.

TMR License Keys

If you are installing the TME from the Tivoli CD included with Enterprise SQL Server Manager, your Tivoli Management Region (TMR) license key is on the packing slip accompanying your Sybase software and documentation.

If you plan to create additional regions, you will need a unique license key for each TMR. You can obtain additional keys by sending an e-mail request to essm@sybase.com. You will receive an e-mail reply with further instructions.

Documentation to Read

Before you install the TME server and clients, read:

• Enterprise SQL Server Manager Release Bulletin (for last minute updates to the Tivoli installation procedure)
• Tivoli Management Platform Release Notes
• Tivoli Management Platform Planning and Installation Guide
• Your Sybase packing slip (to obtain your TMR license key)

Preparing to Install Enterprise SQL Server Manager

Before installing Enterprise SQL Server Manager from the TME desktop, verify that:

• The TME server and clients are installed and running (see "Install the TME Before You Proceed")
• You have backed up the TMR in which you are installing Enterprise SQL Server Manager (see Chapter 6, "TME Maintenance and Troubleshooting," in the Tivoli Management Platform Planning and Installation Guide for information on how to back up a TMR)

Verify these prerequisites, then check off the corresponding items on your worksheet before beginning the Enterprise SQL Server Manager installation (Chapter 4, "Installing Enterprise SQL Server Manager").

If you are installing from tape, go to "Preparing to Install Enterprise SQL Server Manager From Tape".

CD-ROM Device Names

Different operating systems use different device naming conventions. If you have trouble finding the names of available CD-ROM devices on your system, see your operating system documentation or system administrator for specific device naming conventions.

Note: 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.

For each platform on which you are installing Enterprise SQL Server Manager, use your worksheet to record the CD-ROM directory name you intend to use.

Documentation to Read

When you are ready to install Enterprise SQL Server Manager from the TME desktop, read:

• Chapter 4, "Installing Enterprise SQL Server Manager"
• Enterprise SQL Server Manager Release Bulletin

Preparing to Install Enterprise SQL Server Manager From Tape

If you are installing Enterprise SQL Server Manager from tape, you must first extract the product files from the tape for each platform into a common installation directory.

The installation directory can be anywhere you choose, and you can give it any name. However, it is important that you:

• Verify that the TME administrator installing Enterprise SQL Server Manager from the TME desktop has permission to read from the Enterprise SQL Server Manager installation directory.
• Verify that there is enough space to hold the Enterprise SQL Server Manager files. The amount of space you need depends on the platforms for which you are extracting files. You can calculate the amount of disk space you need by adding together the disk space estimates for each platform as listed in the Enterprise SQL Server Manager Release Bulletin.

To verify that there is adequate space for the Enterprise SQL Server Manager installation directory, use the UNIX df command (or bdf for HP-UX). For example, if you plan to create the installation directory within the /nfs directory, you can list the available free space by entering:

df /nfs

or, for HP-UX:

bdf /nfs

Compare the free space reported by this command with the required space calculated from the Enterprise SQL Server Manager Release Bulletin. After verifying that there is adequate space, check off "Adequate space exists for the Enterprise SQL Server Manager installation directory (for all platforms; tape install only)" on your worksheet.

Next, provided there is adequate space, create the installation directory to hold the Enterprise SQL Server Manager files. For example:

mkdir /work/essm_install

Record the full directory path name of the Enterprise SQL Server Manager installation directory on your worksheet.

Tape Device Names

When you extract Enterprise SQL Server Manager files from a tape, you must specify the appropriate device name of the tape drive.

Different operating systems use different device naming conventions. If you have trouble finding the names of available tape devices on your system, see your operating system documentation or system administrator for specific device naming conventions.

For each platform on which you are installing Enterprise SQL Server Manager, use your worksheet to record the device name of the tape device you intend to use.

Local and Remote Tape Media

You can load files from local or remote tape media.

• The media is local if the tape device is connected to the computer on which you are extracting the Enterprise SQL Server Manager files.
• The media is remote if the tape device is connected to another computer. In this case, you must know the name of the computer to which the media device is connected and the name of the device.

For either remote or local devices, verify your networking connection to the host machine to which the media device is connected. Do this verification for each platform on which you are installing Enterprise SQL Server Manager. For verification instructions, see Appendix A, "Troubleshooting."

Documentation to Read

When you are ready to install Enterprise SQL Server Manager from the TME desktop, read:

• Chapter 4, "Installing Enterprise SQL Server Manager"
• Enterprise SQL Server Manager Release Bulletin

Extracting Enterprise SQL Server Manager Files from Tape

Follow this procedure to extract files from the Enterprise SQL Server Manager tape:

1. Change to the installation directory.

   If you are not currently in the Enterprise SQL Server Manager installation directory, change to that directory. Refer to your installation worksheet for the specific directory name to use. For example:

   cd /work/essm11

2. Load the platform-specific Sybase tape into the tape drive on the corresponding platform.

3. Extract the Enterprise SQL Server Manager files from tape media, into the current directory.

4. For local media devices, enter one of the commands that appear in Table 3-1, according to the Sybase media platform you are using

5. For remote media devices, enter one of the commands that appear in Table 3-2, according to the Sybase media platform you are using

   For more information about local or remote media, see "Local and Remote Tape Media" on page 3-9.

   In the following tables, remote_machine is the name of the host machine to which the tape device is connected (for remote media). For HP-UX, device_name is the media device name, and slot_number is the number of the slot in which the cartridge is loaded in the autochanger.

   Refer to your installation worksheet for the specific device and host machine names to use.

   Table 3-1: Extracting ESSM from local tape media

   Platform	Commands to extract files
   IBM RS/6000 AIX	dd if=device_name ibs=48k | tar xvf -
   HP9000 HP-UX (cartridge, 9-track, DAT)	tar Nxvbf 20 /dev/device_name
   HP9000 HP-UX (autochanger)	tcio -uV -l slot_number device_name tar Nxvbf 20 device_name
   Sun SPARC Solaris	tar xvbf 20 /dev/device_name

Table 3-2: Extracting ESSM from remote tape media

Platform	Commands to extract files
IBM RS/6000 AIX	rsh remote_machine dd if=device_name ibs=48k | tar xvf -
HP9000 HP-UX (cartridge, 9-track, DAT)	remsh remote_machine dd if=device_name ibs=10k | tar Nxvbf 20 -
HP9000 HP-UX (autochanger)	remsh remote_machine tcio -uV -l slot_number remsh remote_machine dd if=device_name ibs=10k | tar Nxvbf 20 -
Sun SPARC Solaris	rsh remote_machine dd if=device_name ibs=20b | tar xvf -

Step 4: Unload the Sybase Tape

Remove the Sybase tape from the tape drive and store it in a safe place.

Preparing to Install Patches

This release of Enterprise SQL Server Manager may include Enterprise SQL Server Manager patches or TME patches (or both) that you need to install before using the product. Enterprise SQL Server Manager Release Bulletin lists all required patches included with the Enterprise SQL Server Manager files on the Sybase distribution media.

Before installing any of the patches, verify the names of the patches you need to install.

On your worksheet, record the IDs of any required patches included with the Enterprise SQL Server Manager files before beginning patch installation (see Chapter 6, "Installing Patches").

Note: When you extract Enterprise SQL Server Manager files from tape, patches are also extracted. They are in a directory called patches.

Documentation You Need to Read

When you are ready to install any required patches included with Enterprise SQL Server Manager, read:

• Chapter 6, "Installing Patches"
• Enterprise SQL Server Manager Release Bulletin