Tivoli Manager for Sybase Release Notespublib.boulder.ibm.com/tividd/td/sybs/sybase11rn/en_US/PDF/sybase… · c. Press the Unsubscribe button. 4. Backup all top level Sentry profiles

Tivoli Manager for Sybase** Release Notes

Version 1.1March 1999

ement may ter al, or

ur own rights t

2, ase,

of

SQL

gh

y that se

other ad of ction ility of

this n send

Tivoli Manager for Sybase Release Notes (March 1999)Copyright NoticeCopyright © 1999 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreor Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any compulanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manuotherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for youse, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No otherunder copyright are granted without prior written permission of Tivoli Systems. The document is nointended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/RS/6000, Tivoli Enterprise Console (TEC), Tivoli Management Environment, Tivoli Manager for SybTME 10, TME 10 Distributed Monitoring, and TME 10 Framework.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarksMicrosoft Corporation.

Sybase, the Sybase logo, Adaptive Server, Adaptive Server Enterprise, Adaptive Server Monitor, Server, and Transact-SQL are trademarks of Sybase, Inc.

UNIX is a registered trademark in the United States and other countries licensed exclusively throuX/Open Company Limited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not implthey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theproducts, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli Systems’ or IBM’s valid intellectual property or legally protectable right, any functionally equivalent product, program, or service can be used instethe referenced product, program, or service. The evaluation and verification of operation in conjunwith other products, except those expressly designated by Tivoli Systems or IBM, are the responsibthe user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter indocument. The furnishing of this document does not give you any license to these patents. You calicense inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

Tivoli Manager for SybaseRelease Notes

New Features ..........................................................................................................1

GEM Instrumentation.....................................................................................2

General Features.............................................................................................2

Monitoring Collection Changes .....................................................................3

System Requirements..............................................................................................4

Software Requirements ..................................................................................4

Hardware Requirements .................................................................................5

Procedure for Installing an Upgrade .......................................................................6

Software Defects, Limitations and Workarounds for Version 1.1..........................9

Documentation Defects.........................................................................................14

Documentation Additions .....................................................................................14

Using Tivoli Software Installation Service to Install Tivoli Manager for Sybase............................................................14

Importing Into the IR Directory...........................................................15

Installing Tivoli Manager for Sybase ..................................................22

Tivoli Manager for Sybase Release Notes v

vi Version 1.1

1Release Notes

The following Release Notes provide important information about using Tivoli Manager for Sybase, Version 1.1. These notes are the most current information for the product and take precedence over all other documentation.

Please read these notes thoroughly before installing or using this software.

These release notes contain important information about the following:

■ New Features

■ System Requirements

■ Procedure for Installing an Upgrade

■ Software Defects, Limitations, and Workarounds

■ Documentation Defects

■ Documentation Additions and Changes

New FeaturesTivoli Manager for Sybase, Version 1.1, has new and changed features described in the following subsections:

■ GEM Instrumentation

■ General features

■ Monitoring collection changes

Tivoli Manager for Sybase Release Notes 1

New Features

he

GEM InstrumentationTivoli Manager for Sybase, Version 1.1, is now bundled with GEM Instrumentation, which is fully documented in Chapter 7, "Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation,” and Appendix D, "Supporting Connections to Sybase Components,” of tTivoli Manager for Sybase User’s Guide.

This is the first instrumentation to be wholly based upon the Tivoli object architecture, giving it the advantages of the Tivoli Framework, including security, delegation, and platform independence.

General FeaturesYou can now do the following:

■ Obtain detailed instance information with the Properties dialog

■ View the last 75 lines of the error log of any server

■ View the detailed state of any instance in the status bar by placing the mouse cursor over the instance icon

■ Locate Tivoli Manager for Sybase instances with the Navigator

■ Install with Tivoli Software Installation Server 3.6 or 3.6.1

Tivoli Manager for Sybase now supports Adaptive Server, versions 11.5 and 11.9.2.

The documentation has been extended and enhanced considerably.

New, internationally recognizable and simpler icons have been introduced to the product.

2 Version 1.1

New Features

n

g to been

r

e rate

All options available from the object icons are also available from the object’s collection window (with the exception of the SybaseEngine, which has no collectiowindow).

Many optimizations have been incorporated into the product increasing performance and desktop responsiveness, including enhanced connection cachinSybase servers. The number of running processes has reduced where possible.

The product has increased interactivity and better errohandling, providing the user with detailed information regarding the Sybase objects being managed.

Monitoring Collection ChangesSupport for TME 10 Distributed Monitoring, Versions 3.6and 3.6.1.

The following monitors have been removed from the SybaseServer monitoring collection. These monitors used Sybase global variables that do not always providup-do-date values and, hence, were unreliable as accumonitoring sources.

■ Average Server CPU Busy

■ Average Server CPU Idle

■ Average Server IO Busy

■ Connection Attempts

■ Engine Physical IO Busy

■ Maximum Open Databases

■ Total Device Errors

■ Total Device Reads

■ Total Device Writes

■ User Physical IO Busy


System Requirements

The following monitors in the SybaseServer monitoring collection have had their names changed:

■ Transaction Log Space Used is now Percent Transaction Log Space Used By Server

In addition, the operator groups have been changed and are now fully documented in the following locations in the Tivoli Manager for Sybase Reference Guide:

■ Device Mirror Status, page 2-61

■ Server Status, page 2-153

■ Database State, page 3-3

System RequirementsThis section describes the software, hardware, and system memory requirements for Tivoli Manager for Sybase.

Software RequirementsThis product requires the following software:

■ TME 10 Framework, Version 3.1 or higher

■ TME 10 Distributed Monitoring, Version 3.02 or higher

■ Tivoli Enterprise Console (TEC), Version 3.1 or higher, if you plan to integrate with the TEC

If you plan to use Tivoli Manager for Sybase - GEM Instrumentation, Version 1.1, you must first install the following software in addition to those listed above:

■ Tivoli Global Enterprise Manager (Tivoli GEM), Version 2.2

■ Tivoli Software Distribution, Version 3.1

This product supports Sybase Adaptive Server, versions 11.01, 11.02, 11.03, 11.5, and 11.9.2.

4 Version 1.1

System Requirements

Hardware RequirementsThe following table provides estimated disk space requirements for Tivoli Manager for Sybase. The space requirements are for the Tivoli Management Region (TMR) server and clients.

Note: The space requirements in the following table are in addition to the space requirements for TME 10 Framework and other products. See the TME 10 Framework Planning and Installation Guide for TME server and client hardware requirements.

Memory also depends on the work load for each Tivoli agent component. Large and complex profile distributions may require additional memory.

Platform

Disk Space TMR

Server Frame- work

Disk Space TMR Client

Frame- work

Disk Space TMR

Server DM*

Disk Space TMR Client DM*

Disk Space GEM

Instru- menta-

tion

Memory

AIX 4.x 52 MB 50 MB < 1 MB < 1 MB 4 MB 8 MB

HP-UX 10.x

30 MB 28 MB < 1 MB < 1 MB 4 MB 15 MB

Solaris 25 MB 23 MB < 1 MB < 1 MB 4 MB 30 MB

Windows NT

20 MB 18 MB < 1 MB < 1 MB 4 MB 10 MB

* DM = Distributed Monitoring


Procedure for Installing an Upgrade

o e

t

Procedure for Installing an UpgradeTo install an upgrade for a previous version of Tivoli Manager for Sybase, perform the following procedure from the Tivoli desktop.

Note: Before running any of the scripts in this procedure, ensure that the Tivoli environment is configured by running the setup_env.sh script.

1. Backup the Tivoli database on all nodes for which the upgrade will be performed so you can restore it from a previous version if you encounter a problem during installation. Do one of the following:

Select Backup from the Desktop menu on the Tivoli desktop.

—OR—

Use the wbkupdb command. For more information,refer to the TME 10 Framework Reference Manual. The wbkupdb command also has a restore option tallow you to revert to an earlier state of a TMR in thcase of an upgrade failure, for example.

2. Disconnect any TMRs that are interconnected. Todisconnect TMRs, do one of the following:

From the Desktop menu on the Tivoli desktop, selecthe TMR Connections –> Disconnect... option to display the Disconnect from remote TMRs dialog. Select the interconnected TMRs, then click the Disconnect & Close button.

—OR—

Use the wdisconn command to disconnect any interconnected TMRs.

6 Version 1.1


Note: The wdisconn command disconnects two TMRs. Disconnecting TMRs after they have exchanged resources is a time-consuming process and should be done with care. To ensure database consistency, you should run the wchkdb command after disconnecting the TMRs.

For more information on the wdisconn and wchkdb commands, refer to the TME 10 Framework Reference Manual.

3. Unsubscribe any distributed monitoring profiles that contain Sybase monitors, servers, or databases.

Note: If you do not unsubscribe, the Sentry engine fails because it still tries to run obsolete monitors.

To unsubscribe the databases from the profile managers, do the following:

a. From the Profile Manager dialog, select the Edit –> Subscribers –> Unsubscribe option to display the Unsubscribe Subscriber dialog.

b. Select the Delete all profile copies option.

c. Press the Unsubscribe button.

4. Backup all top level Sentry profiles that contain Tivoli Manager for Sybase monitors by typing the following from a command line prompt:

wlsmon -sa profilename > outputfilename.sh

Note: If you experience a failure after running the SybaseSentryMonitors1.1sh script, delete all monitors from the affected profiles, restore the Tivoli database, and recreate the profiles by running the scripts from wlsmon command.



e

is

5. From the Desktop menu, use the Install –> Install patch option to install each of the following upgrades on the TMR server and on each managed node on which Version 1.0 was installed:

• Tivoli Manger for Sybase – Framework, Upgradto Version 1.1

• Tivoli Manager for Sybase – Distributed Monitoring, Upgrade to Version 1.1

For information on using the Install Patch dialog, refer to the TME 10 Planning and Installation Guide.

Note: Immediately after completing the upgrade,you cannot edit distributed monitoring profiles that contain Tivoli Manger for Sybase monitors because of internal nameand argument changes. Step 7 below will correct this situation.

6. Use the SybaseInterfaceFiles.sh script to upgrade all Tivoli Manager for Sybase instances with new interface file information, which is now a new attribute and used for connectivity checks.

a. If you are using UNIX, go to step b. If you are using Windows NT, open the bash shell by entering sh.exe at the command line.

b. Enter the following:

<TMEServerInstallDir>/bin/generic/ \SybaseScripts/SybaseInterfaceFiles.sh

Note: If you make any mistakes while entering interface file information, you may run this script as many times as you like. The script self documenting.

8 Version 1.1

Software Defects, Limitations and Workarounds for Version 1.1

7. Use the SybaseSentry1.1.sh script to upgrade each profile manager that contains distributed monitoring profiles with Tivoli Manager for Sybase monitors. This script will remove unused arguments from existing profiles, and delete obsolete monitors.

a. If you are using UNIX, go to the next step. If you are using Windows NT, open the bash shell by entering sh.exe at the command line.

b. For each relevant profile manager enter the following:

<TMEServerInstallDir>/bin/ \generic/SybaseScripts/ \SybaseSentryMonitors1.1.sh \<ProfileManager>

Where:

<TMEServerInstallDir> Is the directory in which Tivoli Manager for Sybase is installed.

<ProfileManger> Is the name of the individual profile manager.

c. Repeat step b for each profile manager that needs to be upgraded.

8. Subscribe Sybase databases or servers to the profile managers which were unsubscribed in step 3.

9. Distribute the profiles to all levels.


This section describes known defects in this release of

Tivoli Manager for Sybase. Where applicable and known,

suggested workarounds are identified. This may not be a

complete list of defects.



CMVC Defect

NumberDescription Workaround

None Multiple log file entries appear in Sybase server logs on UNIX platforms

When Sybase servers are not running on a terminal, they append their output to the log file, causing duplicate entries. Tivoli Manager for Sybase tries to prevent this by redirecting the output to /dev/console, but it will need to be writable by user nobody, group nobody.

64479 Framework: On Windows NT, the status bar message of the Policy Region displaying detailed state of icons does not update on status change.

Select the View −> Refresh option to update the detailed state message or view the properties of the desired object to find its detailed state.

None Framework: BackupServer is suspect on Windows NT when shut down.

No workaround available. The backup server incorrectly does not make an error log file entry when it is shutdown, so it is impossible for Tivoli Manager for Sybase to determine whether it has been shut down properly.

62376 GEM Instrumentation: Query_Thresholds, Query_Threshold_Settings, and Query_Values component tasks are not scoped on an instance basis. Running these tasks against a component instance returns results for all know instances.

No workaround available.

10 Version 1.1


63202 GEM Instrumentation: File package no_overwrite flag fails to protect the existing file and causes DiscoverSybaseComponents.sh to overwrite already existing files at the node. This becomes an issue, for example, if DiscoverSybaseComponents.sh is run to discover components for which logging has been turned "ON" in gemilib.properties. The log option in gemilib.properties is set to "OFF" by default.

Do not redistribute file package after editing these files. Redistribute monitors manually.

PMR number 0418X9

Framework: On the Profile Manager window, the server icon does not toggle to reflect a changed state, such as from SHUTDOWN to AVAILABLE. Selecting the Check State option or selecting the pop-up menu Start and Stop options do not change this. This is a known defect in TME 10 Framework.

From the Profile Manager window, select the View −> Refresh option to synchronize the subscriber state with the original object.

64463 GEM Instrumentation: Set_Thresholds task fails with an error, when it should return no value.

Do not run the Set_Thresholds monitor task against APMHeartbeatMonitor, APMConnectionChangeMonitor, or CompInfoChangeMonitor monitors. Tivoli Manager for Sybase GEM Instrumentation does not have any thresholds to be set.

CMVC Defect




64377 Distributed Monitoring: TEC events will not be processed if the probe_arg monitor argument is the literal string "default". This causes a problem in Used Segment Space By Segment and Free Segment Space By Segment monitors where "default" is the pre-filled-in value for the Segment Name argument.

None available at this time. Contact Tivoli Technical Support for further information.

None Framework and Distributed Monitoring: The following Sybase bug affects all Tivoli Manager for Sybase - Framework and monitor processes that access the master database sysengines table in the following circumstance:When a sybaseengine process is killed externally to the Sybase Adaptive Server; for example, by using on the command line "ps" and then "kill" on the process ID of the engine process, the master database sysengines table does not get updated.In this circumstance, any attempt to access that table, for example, by issuing a "checkstate" on an engine or running the Engine Status monitor, will result in hanging and the Adaptive Server will have to be restarted.


CMVC Defect


12 Version 1.1


None Framework and Distributed Monitoring: When a multi-engined Sybase Adaptive Server is shutdown, sometimes due to a Sybase bug, Sybase engine processes will remain running. However, the checkstate methods used by Tivoli Manager for Sybase - Framework and the SQL Server Status monitor use a cached connection to the Adaptive Server, where possible. During a checkstate, this can result in a connection to an orphaned engine being used, and the Adaptive Server status being returned as AVAILABLE when, in fact, the server is shutdown.


None Distributed Monitoring: The Backup Server Errors, Dataserver Errors, and Dataserver Errors By Severity monitors make use of a file which they create in the /tmp directory. This file is used to keep track of the position in the error log file up to which it has scanned so far. If /tmp is cleared, these monitors will behave in the same way as when the monitor is run for the first time, returning trigger values of zero.


CMVC Defect



Documentation Defects

,”

n.

s r

Documentation DefectsIn the Tivoli Manager for Sybase Reference Guide, the Free Form SQL String monitor description on page 2-79 in Chapter 2, "The SybaseServer Monitoring Collectionand on page 3-14 in Chapter 3, "The SybaseDatabaseMonitoring Collection,” does not mention that a Default value (if no rows found) argument beginning with a leading hash character ("#") is disallowed. If it were allowed, Distributed Monitoring would consider the output to be user information for the monitor and wouldfail to find the trigger value, thus failing with an E.EXEC error.

Documentation AdditionsThis section includes late additions to the documentatioIn Chapter 3, "Installing Tivoli Manager for Sybase,” of the Tivoli Manager for Sybase User’s Guide, insert the following subsection and its two subsections:

■ Using Tivoli Software Installation Server to Install Tivoli Manager for Sybase

• Importing Into the IR Directory

• Installing Tivoli Manager for Sybase

Using Tivoli Software Installation Service to Install Tivoli Manager for Sybase

Introduced in Tivoli Manager for Sybase, Version 1.1, isthe ability to install with TME 10 Software Installation Service (SIS), Version 3.6, or 3.6.1. This section coverthe installation of Tivoli Manager for Sybase with SIS. Fomore detailed information on using SIS, refer to the TME 10 Software Installation Service User’s Guide.

14 Version 1.1

Documentation Additions

Importing Into the IR Directory

Before you can install, you must first import the Tivoli Manager for Sybase CD image into the Image Repository (IR) directory. To import the product images, perform the following procedure from the Tivoli desktop:

1. Select the Install –> Software Installation Service... option from the Desktop menu.

The Get installation password dialog is displayed.



2. Enter the TME 10 Framework installation password for your TMR server, if applicable, and click the OK button. This is the same password you specified when you installed the TMR server.

The TME 10 Software Installation Server dialog and tile bar are displayed.

16 Version 1.1


3. Select the Install option for the TME 10 Software Installation Server dialog to display the Install details dialog.

4. From the Install details dialog, click the Select Product button to display the Install Repository - Select Product dialog.



The Select Product dialog shows all products imported into the Install Repository (IR).

5. Click the Import CD Images button to add the Tivoli Manager for Sybase product to the IR.

18 Version 1.1


The Import Product dialog displays the available products contained in each .LST file in the specified directory and its subdirectories.

6. From the list, select one or more products to be imported into the IR directory.



7. Click the Select Interps button, which displays the Select interps dialog.

8. Use the slider bar to unselect the interp types for the available products that you do not want to import from the Import Product dialog.

9. Click the OK button to return to the Import Product dialog.

10. After you select the products and interp types that you want to import, click the Import button.

20 Version 1.1


The Product Import Progress dialog is displayed, which allows you to view the status of each product as it is imported into the IR directory.

Click the OK button when the process is completed. Once the products are successfully imported into the IR directory, they are listed in the Available Products list on the Select Product dialog.



Installing Tivoli Manager for Sybase

Once the product images are imported into the IR directory, you can select the products to install and which hosts to install on. To install Tivoli Manager for Sybase, perform the following procedure:

1. From the Select Product dialog, select one or more products from the Product list and click the OK button.

2. The selected products are then listed in the Install Details dialog.

22 Version 1.1


3. From the Install Details dialog, click the Select Machine button to view the list of machines available for product installation.



Select one or more machines from the Machine Name list and click the OK button.

24 Version 1.1


The selected machines and products are displayed in a table of installation information in the Install Details dialog.

The table cells are color-coded to indicate the status of the product on that machine.

Green Indicates that the product is already installed, or that a later version of the product is already installed or selected to be installed.

Dark Gray Indicates that you cannot install the product because a prerequisite product must first be installed, or the product image for that machine’s operating system (interp type) was not imported into the IR directory. Select the cell to view the prerequisite product or missing operating system.



Light Gray Indicates that you can install the product.

4. Select the appropriate cell for the product you want to install by clicking on it.

Notes: You must select Tivoli Manager for Sybase – Framework, Version 1.1 prior to selecting Tivoli Manager for Sybase – Distributed Monitoring, Version 1.1 for a given machine. Likewise, Tivoli Manager for Sybase – GEM Instrumentation, Version 1.1 can only be selected after Tivoli Manger for Sybase – Distributed Monitoring, Version 1.1 has been selected.

5. From the Install Details dialog, click the Install button to begin the product installation.

The Select Installation Mechanism dialog is displayed.

26 Version 1.1


6. Select the manner in which the installation is to be performed and click the OK button to initiate installation. The Installation Progress dialog is displayed.

You can select the radio button to the left of the status bar to list the progress log for each node.

An Install Complete message is displayed when the installation process is finished.



28 Version 1.1

Documents

Tivoli Manager for Sybase Release Notespublib.boulder.ibm.com/tividd/td/sybs/sybase11rn/en_US/PDF/sybase… · c. Press the Unsubscribe button. 4. Backup all top level Sentry profiles