Tivoli Manager for Oracle** Release Notespublib.boulder.ibm.com/tividd/td/oracle2/GI10-0519-03/en_US/PDF/GI10... · Tivoli Manager for Oracle Version 2.0 Release Notes This document

Tivoli Manager for Oracle**Release NotesVersion 2.0

Tivoli Manager for Oracle**Release NotesVersion 2.0

Tivoli Manager for Oracle** Release Notes (December 2000)

Copyright Notice

© Copyright IBM Corporation 2000 All rights reserved. May only be used pursuant to aTivoli Systems Software License Agreement, an IBM Software License Agreement, orAddendum for Tivoli Products to IBM Customer or License Agreement. No part of thispublication may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated into any computer language, in any form or by any means, electronic, mechanical,magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBMCorporation. IBM Corporation grants you limited permission to make hardcopy or otherreproductions of any machine-readable documentation for your own use, provided that eachsuch reproduction shall carry the IBM Corporation copyright notice. No other rights undercopyright are granted without prior written permission of IBM Corporation. The document isnot intended for production and is furnished “as is” without warranty of any kind. Allwarranties on this document are hereby disclaimed, including the warranties ofmerchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSAADP Schedule Contract with IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli,RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, and TME are trademarks orregistered trademarks of International Business Machines Corporation or Tivoli Systems Inc.in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Oracle is a registered trademark of Oracle Corporation.

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services donot imply that they will be available in all countries in which Tivoli Systems or IBMoperates. Any reference to these products, programs, or services is not intended to imply thatonly Tivoli Systems or IBM products, programs, or services can be used. Subject to validintellectual property or other legally protectable right of Tivoli Systems or IBM, anyfunctionally equivalent product, program, or service can be used instead of the referencedproduct, program, or service. The evaluation and verification of operation in conjunction withother products, except those expressly designated by Tivoli Systems or IBM, are theresponsibility of the user. Tivoli Systems or IBM may have patents or pending patentapplications covering subject matter in this document. The furnishing of this document doesnot give you any license to these patents. You can send license inquiries, in writing, to theIBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York10504-1785, U.S.A.

Contents

Tivoli Manager for Oracle Version 2.0 Release Notes . . . 1Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Tivoli Management Agent Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Database Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Parallel Server Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

New Oracle Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Extensions to “By Tablespace” Monitors . . . . . . . . . . . . . . . . . . . . . . . . 5

New Oracle Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

National Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Best Practices Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Oracle Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Tivoli Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation and Migration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Adding the Policy Role to Administrator . . . . . . . . . . . . . . . . . . . . 7

Migrating the RDBMS State Monitor . . . . . . . . . . . . . . . . . . . . . . 8

Editing Database Properties After Migration . . . . . . . . . . . . . . . . . 8

Defects Fixed in Version 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Defects, Limitations, and Workarounds in Version 2.0 . . . . . . . . . . . . . . . . . . 9

Hints and Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Registering Databases in Non-English Locales . . . . . . . . . . . . . . . . . . . 13

Creating the EVERYONE Group . . . . . . . . . . . . . . . . . . . . . . . . . 14

Sending Events to TEC from OracleManagerAsync Monitors . . . . . . . . 15

iiiTivoli Manager for Oracle** Release Notes

Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Enabling Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Translation Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

TBSM Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Software Version Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 19

TBSM Instrumentation Usage Prerequisites . . . . . . . . . . . . . . . . . 19

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installation Procedure Summaries . . . . . . . . . . . . . . . . . . . . . . . . 21

SIS Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Overview of Tivoli TBSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

TBSM and the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Discovering the Oracle Components . . . . . . . . . . . . . . . . . . . . . . 27

Setting Up TBSM Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Initiating Component Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . 28

Subscribing Endpoints and Distributing File Packages . . . . . . . . . 32

Subscribing Resources and Distributing Monitoring Profiles . . . . . 33

Unsubscribing Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configuring TEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Turning on TBSM Instrumentation Debugging . . . . . . . . . . . . . . . 39

If TBSM Instrumentation log shows that the heartbeat event wasnot generated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

If TBSM Events are not getting to TEC. . . . . . . . . . . . . . . . . . . . 41

If tasks fail to execute from the topology console . . . . . . . . . . . . 42

Uninstalling TBSM Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

iv Version 2.0

Programming Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Connections to TBSM Components . . . . . . . . . . . . . . . . . . . . . . . 42

Defining Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

vTivoli Manager for Oracle** Release Notes

vi Version 2.0

Tivoli Manager for OracleVersion 2.0 Release Notes

This document provides important information about Tivoli Managerfor Oracle, Version 2.0. It augments the Tivoli Manager for OracleUser’s Guide, the Tivoli Manager for Oracle Reference Guide, andthe Tivoli Manager for Oracle User Management Guide.

These documents are also available on the product CD in PDFformat. Look in the /DOCS directory. HTML versions of thesedocuments are available on the Tivoli Customer Support home page(see “Customer Support” on page 2).

Please read these notes thoroughly before installing or using thissoftware. Always check the product web site for the latest versionof the release notes.

These release notes cover the following topics:

¶ “Customer Support” on page 2

¶ “New Features” on page 3

¶ “System Requirements” on page 6

¶ “Defects Fixed in Version 2.0” on page 8

¶ “Defects, Limitations, and Workarounds in Version 2.0” on page9

¶ “Hints and Tips” on page 13

1

1Tivoli Manager for Oracle** Release Notes

1.R

eleaseN

otes

¶ “Internationalization” on page 15

¶ “Documentation Changes” on page 18

For complete instructions on preparing for, installing, upgrading, andconfiguring Tivoli Manager for Oracle, Version 2.0, see the TivoliManager for Oracle User’s Guide.

Customer SupportIf you are entitled to Tivoli customer support, you can findfrequently updated information about configuring and using Tivoliproducts from the Tivoli Customer Support home page athttp://www.tivoli.com/support/. This site includes the following links:

¶ Updated versions of these release notes:http://www.tivoli.com/support/Prodman/html/RN.html

Note: Release notes are only updated online.

¶ Updated versions of Tivoli documentation:http://www.tivoli.com/support/documents/

¶ Searchable support databases:http://www.tivoli.com/teamtivoli/asktivoli/

¶ Access to product patches:http://www.tivoli.com/support/patches/

¶ Access to training schedules:http://www.tivoli.com/services/education/

¶ Access to Tivoli documentation survey:http://www.tivoli.com/support/survey/

Visit the Tivoli Customer Support site for this information andadditional customer services. These URLs do require a password andID. If you do not have access privileges or are unsure of your ID orpassword, send e-mail [email protected]. Include your nameand your company name in this correspondence.

2 Version 2.0

You can order additional copies of product documentation bysending e-mail or calling one of the following locations:

¶ U.S. Customer E-mail: [email protected]

¶ U.S. Telephone: 1-800-879-2755

¶ Canada Telephone: 1-800-426-4968

¶ International Telephone: (770) 863-1234

Please provide the title and version number of the document that youare ordering.

New FeaturesThis release of Tivoli Manager for Oracle offers the following newfeatures:

¶ Support for the new three-tiered Tivoli Management Agentarchitecture

¶ National language support

¶ Parallel Server support

¶ Best Practices script

¶ New Oracle monitors

¶ New Oracle tasks

Tivoli Management Agent SupportTivoli Manager for Oracle supports the new three-tiered Tivoliarchitecture. This architecture enhances the scalability of the Tivoliproducts and provides ease-of-deployment by reducing the systemresources required for managing client systems.

Database DiscoveryThe OracleDiscovery managed resource provides a convenient wayof registering multiple databases on one or more endpoints in asingle operation. Discovery registers all databases listed in the oratabfile on the specified endpoints. See the Tivoli Manager for OracleUser’s Guide for more information.


1.R

eleaseN

otes

Parallel Server SupportTivoli Manager for Oracle, Version 2.0, supports Oracle’s parallelserver functionality, which enables multiple instances to be mountedon the same database. See the Tivoli Manager for Oracle ReferenceGuide for detailed information. The following monitors are availablefor the parallel instances:

¶ Percentage of False Pings

¶ Ping Rate

¶ PCM Locks Used

¶ Global Lock Converts

¶ SCN Global Lock Converts

¶ Lock Hit Ratio

¶ PCM Lock Conversion Time

¶ PCM Conversion Waits

New Oracle MonitorsTivoli Manager for Oracle, Version 2.0, provides 12 new monitors.See the Tivoli Manager for Oracle Reference Guide for completedescriptions of these new monitors.

¶ Detect Dangling REFs

¶ Average Message Propagation Rate across Schedule

¶ Advanced Queue Propagation Status

¶ AQ Schedule Propagation Errors

¶ Average Waiting Time of Ready Messages

¶ Total Waiting Time of Messages

¶ Current Data Block Corruptions

¶ Currently Running Heterogeneous Services

¶ Long Running Transaction Status

¶ Blocked Transactions

4 Version 2.0

Extensions to “By Tablespace” MonitorsThe “by Tablespace” monitors in the OracleDatabaseManagercollection now accept a space-separated list of tablespaces instead ofonly one tablespace. This enhances the flexibility of the monitors.See the Tivoli Manager for Oracle Reference Guide for completedescriptions of these enhanced monitors.

¶ Extents by Tablespace

¶ Free Space Deficit by Tablespace

¶ Free Space Fragmentation by Tablespace

¶ Free Tablespace by Tablespace

¶ Maximum Extents by Tablespace

¶ Temporary Extents by Tablespace

New Oracle TasksTivoli Manager for Oracle, Version 2.0, includes the following newtasks. These tasks are automatically installed in theOracleManagerTasks task library in the OracleManager policyregion. See the Tivoli Manager for Oracle Reference Guide forcomplete descriptions of these new tasks.

¶ ConfigureTECOracle automatically configures the TivoliEnterprise Console to receive Oracle events.

¶ Listener starts and shuts down the Oracle Listener using thelsnrctl utility.

National Language SupportTivoli Manager for Oracle meets standard internationalizationrequirements. The languages for this release are: BrazilianPortuguese, French, Spanish, Simplified Chinese, TraditionalChinese, Korean, Japanese, and German.

Best Practices ScriptThe Best Practices script installs a set of preconfigured database andinstance monitors. These monitors are a good starting point forsetting up Oracle database monitoring.


1.R

eleaseN

otes

System RequirementsThe following section details supported platforms, hardwarerequirements, and software requirements for Tivoli Manager forOracle, Version 2.0.

Supported PlatformsThe following table lists the platforms that are supported by TivoliManager for Oracle, Version 2.0. If you have questions about aplatform or software that is not listed here, contact Tivoli CustomerSupport.

Platform Tivoli Supported Configuration

AIX IBM RS/6000 series running AIX 4.3.x

HP-UX HP9000/700 and 800 series running HP/UX10.20 and 11.00

Solaris Sun SPARC series running Solaris 2.6 and 2.7

Windows NT/2000 IBM-compatible Pentium PCs runningMicrosoft Windows NT version 4.0 (or higherwith relevant service packs) and Windows 2000

Hardware RequirementsThe minimum disk space and memory required to install and runTivoli Manager for Oracle, Version 2.0, were not available in timefor inclusion in this document. This information will be added to theonline release notes on the product web site(http://www.tivoli.com/support/Prodman/html/RN.html) when it isavailable.

Software Requirements

Oracle SoftwareTivoli Manager for Oracle, Version 2.0, supports the followingversions of Oracle:

¶ Oracle Enterprise Edition, Versions 8.0.5, 8.1.5, and 8.1.6.

¶ Oracle Parallel Server, Versions 8.0.5, 8.1.5, and 8.1.6.

6 Version 2.0

Tivoli SoftwareOne of the following configurations of Tivoli software must beinstalled. Before installing Tivoli Manager for Oracle, check theproduct website to see if any additional patches are required.

Tivoli Software Configuration Requirements forTivoli Manager for Oracle 2.0

Tivoli ManagementFramework

Tivoli DistributedMonitoring

Tivoli EnterpriseConsole

Tivoli ApplicationServices

3.6.1

3.6.2 with patch3.6.2-TMF-0008

3.6.3

3.6.4

3.6.1 with thefollowing patches:3.6.1-DMN-00083.6.1-DMN-00133.6.1-DMN-00183.6.1-DMN-0022

3.6.2

3.6.1

3.6.2

1.1 with 1.2 upgradepatch*

1.2

*The Tivoli Application Services upgrade patch can be found on the Tivoli Manager forOracle CD in the following directory: ApplicationServices/patches/APPLSV12.image

Installation and Migration Issues

Instructions for installing and migrating to Tivoli Manager forOracle, Version 2.0, are given in the Tivoli Manager for OracleUser’s Guide. This section provides additional information that wasdiscovered after the user’s guide was sent to print.

Adding the Policy Role to AdministratorIf you are running Tivoli Management Framework, Version 3.6.2 orlater, you must assign the policy role to the administrator of theTMR region before you can install Tivoli Manager for Oracle,Version 2.0. Follow these steps:

1. From the TME desktop, double-click the Administrators icon.

2. Right-click the icon for the administrator of the TMR region andselect Edit TMR Roles.

3. In the Available Roles list, select the policy role and click theleft arrow button to move it to the Current Roles list. Click OKto close the window.


1.R

eleaseN

otes

4. Shut down and restart the TME desktop.

5. Proceed with the installation.

Migrating the RDBMS State MonitorDo not attempt to migrate the Version 1.2 RDBMS State monitor toVersion 2.0. Doing so will cause the migration script to fail. Instead,add the RDBMS State monitor after you have completed themigration. (Defect 110949. A fix for this problem is being developedand will be available on the Tivoli Support web site.)

Editing Database Properties After MigrationAfter you migrate a database from Version 1.2 to Version 2.0 ofTivoli Manager for Oracle, you may need to edit the databaseproperties for the database to be registered correctly. This isespecially true for the user name and password properties inWindows NT. Refer to Chapter 6 of the Tivoli Manager for OracleUser’s Guide for information about editing database properties.

Defects Fixed in Version 2.0This section lists the defects that were fixed in Tivoli Manager forOracle, Version 2.0.

APARNumber

Description

IX74899 Allow the TNS Listener monitor to access listener.ora viathe $TNS_ADMIN directory or the default directory.

IX77752 Unable to read in /etc/group longer than 2048 characters.

IX78274 Incorrect (percent) user values reported for sometablespaces when Tablespace selected from databasepop-up menu.

IX80513 The Freespace monitors do not take into consideration thefilext $ table when doing the calculations.

IX81240 Customer needs the Discovery function for Oracledatabases for Windows NT.

IX82222 The requirement for 755 permissions on ORACLE_HOMEis seen as a security problem.

IX83444 Registering a database should not require senior role.

8 Version 2.0

APARNumber

Description

IX83798 Alerts monitor only looks at the last error, not the mostsevere.

IX83984 Use of @ for ORACLE_SID in background_dump_destcauses Alert and Background Dump Space monitors to fail.

IX84557 The SQL in some of the Oracle monitors performscomplex sorts that require a lot of space in the TEMPtablespace.

IX87496 Cannot start or stop Oracle databases from Tivoli Managerfor Oracle on the HP-UX 10.20 platform.

IY01109 RDBMS State monitor fails with exit code 29 whendatabase is down.

IY02082 SQL*Net V2 Listener monitor can occasionally fail evenwhen the lsnrctl status command completes quickly andcorrectly.

Defects, Limitations, and Workarounds in Version 2.0This section lists known defects in Tivoli Manager for Oracle,Version 2.0.


1.R

eleaseN

otes

CMVCDefectNumber

Description

87394 In the Database User Profile window, the View → Find option cannot findusers with certain attributes. There are two workarounds:

¶ Use the Contains operator instead of Exact match.

–OR–

¶ Type a comma after the attribute name (or after the last attribute name ina list).

The following examples show how to find all users who have the rolesCONNECT and RESOURCE:

¶ Change the operator to Contains and enter CONNECT,RESOURCEfor the attribute.

–OR–

¶ Leave the operator as Exact match and enter CONNECT,RESOURCE,for the attribute.

Also, note that the Find option is case-sensitive.

94066 It isn’t always possible to drag-and-drop database or profile manager iconsfrom one policy region to another.

If you can’t drop an icon into an open policy region window, try dropping iton the policy region icon on the desktop.

An alternative is to use the wmv command from the CLI. The syntax forthis command is:

wmv /Regions/<policy-region>/<object-name> /Regions/<new-policy-region>

For example, to move a database named v815@manzana from theOracleManager policy region to the London policy region, enter thefollowing command:

wmv /Regions/OracleManager/v815@manzana /Regions/London

10 Version 2.0

CMVCDefectNumber

Description

99647 If you try to perform a parallel startup on a database and you don’t haveParallel Server installed, the startup will fail. A message will appear statingthat the instance has been started, but mount failed due to a missing lockmanager. If you perform a Check State from the GUI, the database icon willbe displayed in the suspect state.

To recover from this situation, select Shutdown → Immediate and wait forthe database to shut down. Then select Startup → Exclusive to start thedatabase.

103398 If you grant the DBA role to a user from the CLI, that user is given only theDBA role. If you grant a user the DBA role from the GUI, it also grants thesystem privilege of unlimited tablespace.

103514 The following command options were listed in the commands’ synopses butwere not implemented in Tivoli Manager for Oracle, Version 2.0:

¶ wosetuser -u new_user_name profile_name old_user_name

¶ wosetrole -n new_role_name profile_name old_role_name

¶ wosetresource -n new_resource_name profile_name old_resource_name

108405,109106

Running the following monitors with versions of Oracle prior to 8.1.x maycause serious performance degradation on large databases because of thelarge amount of data they pull from the database. The monitors have beenoptimized to prevent this problem in Oracle 8.1.x and later.

¶ Free Space Deficit

¶ Free Space Deficit by Tablespace

¶ Maximum Extents

108765 If you select View Properties from a User Profile or Role Profile icon, thenselect a row and click the View button, the View User/Role Profile dialogfails to appear. Instead, the message Dialog Database(User/Role)View notfound is displayed. The workaround is to select Edit Properties instead ofView Properties.


1.R

eleaseN

otes

CMVCDefectNumber

Description

110735 In Windows NT, the output of the OracleManagerAsync monitors does notinclude the user information that is normally appended onto the end of theresults. (The user information does appear in the output on UNIX-basedsystems.)

The user information is logged to the OracleManagerCollection.log file. Towrite this information to the log file, add the following lines to theOracleManagerCollection.sh file:

COLLECTION_LOG_LEVEL=2export COLLECTION_LOG_LEVEL

If you edited the OracleManagerCollection.sh file in the lcf_bundle directoryon the gateway, you will need to call the InitializeEndpoint method on theOracleInstanceManager object you are running the monitors on (or theOracleInstanceManager object which belongs to the OracleDatabaseManagerobject the monitors are running on) in order to push out the updated files.You can accomplish this by making an idlcall to the OID of theOracleInstanceManager object with InitializeEndpoint as the method to beexecuted.

Alternatively, you can edit the script on the endpoint. It lives under$LCF_DATDIR/generic/OracleManagerMonitoring. You don’t need torestart either the oserv or the lcfd, these settings are picked up dynamically.

The logs can be found under $LCF_DATDIR/AmsMonitorLogging.

111045 The Best Practices script prompts you to enter the name of an existingprofile manager. If you are running on UNIX and you specify a profilemanager that has a space in its name, the script will fail. The workaround isto enclose the name of the profile manager in double quotes.

None (Windows NT only.) The database registration process (either from the GUIor using the woregdb command) expects to find a local group namedEVERYONE. This local group is created automatically on all systems, but innon-English locales the word “EVERYONE” is translated to the localequivalent. When you attempt to register a database on a non-Englishsystem, the registration process begins normally but fails when it tries tocreate a database in the nonexistent EVERYONE group.

Refer to “Registering Databases in Non-English Locales” on page 13 forinformation on working around this problem.

12 Version 2.0

CMVCDefectNumber

Description

Discovery

102916,103215

The OracleDiscovery managed resource cannot discover databases if twodifferent versions of Oracle Database Server (for example, 8.0.4 and 8.1.6)are installed on a Windows NT endpoint.

110092 The OracleDiscovery managed resource cannot discover databases in aParallel Server environment.

None After you discover a database, you may need to edit the database propertiesbefore it will be registered correctly. This is especially true for the user nameand password properties in Windows NT. Refer to Chapter 6 of the TivoliManager for Oracle User’s Guide for information about editing databaseproperties.

None The greater the number of endpoints Discovery is run against, the longer itwill take. You may want to consider running Discovery multiple times onsubsets of endpoints.

Hints and Tips

Registering Databases in Non-English Locales(Windows NT only.) The database registration process (either fromthe GUI or using the woregdb command) expects to find a localgroup named EVERYONE. This local group is created automaticallyon all systems, but in non-English locales the word “EVERYONE”is translated to the local equivalent. When you attempt to register adatabase on a non-English system, the registration process beginsnormally but fails when it tries to create a database in thenonexistent EVERYONE group.

The following example shows the last four lines of the log generatedin this situation. After the last message, the registration processhangs and produces no further messages.Oct 04 18:55:50 3 EPA_DM_EndpointInit EPA_DM_EndpointInit - NT -Creating [D:\Programme\Tivoli\lcf\dat\1\AmsMonitorLogging]

Oct 04 18:55:50 3 EPA_DM_EndpointInit CreateDirectoryWithSecurity –Entering [D:\Programme\Tivoli\lcf\dat\1\AmsMonitorLogging][EVERYONE]


1.R

eleaseN

otes

[<NULL>]

Oct 04 18:55:50 3 EPA_DM_EndpointInit CreateDirectoryWithSecurity -GetComputerName returned [QZK14]

Oct 04 18:55:50 3 EPA_DM_EndpointInit CreateDirectoryWithSecurity -Creating Sid object

The following section describes how to create the EVERYONEgroup needed to register databases.

Creating the EVERYONE GroupPerform the following steps prior to registering an Oracle database ina non-English environment running Windows NT:

1. On the NT LCF endpoint, select Start → Programs →Administrative Tools (Common) → User Manager.

2. In the User Manager dialog, select User → New Local Group.

Create a local group with the following details:

Group Name: EVERYONEDescription: EVERYONE because none exists

3. Press the Add button. The Add Users and Groups dialogappears.

4. In the List Names From menu, select the \\$LOCAL machine(the one with an asterisk).

5. Select all the names listed in the Names field.

6. Click Add, then click OK.

7. Click OK to close the New Local Group dialog

8. In the bottom pane of the User Manager dialog, select theEVERYONE group.

9. Select Policies → User Rights. The User Rights Policy dialogappears.

10. Select the Show Advanced User Rights check box.

11. From the Right menu, select Access this computer fromnetwork.

14 Version 2.0

12. Click the Add button. The Add Users and Groups dialogappears.

13. In the List Names From menu, select the \\$LOCAL machine(the one with an asterisk).

14. Select the EVERYONE group, then click Add and OK toreturn to the User Rights Policy dialog.

15. In the User Rights Policy dialog, select EVERYONE and clickOK to close the window.

16. Repeat steps 11 through 15 to add the following additionalrights:

Bypass traverse checkingLog on locallyShut down the system

Note that these rights already exist for the EVERYONE groupin some NT locales.

17. Click OK in the User Rights Policy dialog.

18. Now register the Oracle database from the GUI, or from theCLI using the woregdb command.

Sending Events to TEC from OracleManagerAsyncMonitors

During TEC configuration, no event classes are defined for thebackground monitors of the OracleManagerAsync monitor pairs. DMResponse Actions should be specified for the asynchronous monitorand not the background monitor.

Internationalization

Enabling Language Support

Note: Language support is included on a separate CD, which will beavailable shortly after the general release of Tivoli Managerfor Oracle, Version 2.0.


1.R

eleaseN

otes

Tivoli Manager for Oracle, Version 2.0, language support is availablefor the following languages:

¶ Brazilian Portuguese

¶ Chinese (simplified)

¶ Chinese (traditional)

¶ French

¶ German

¶ Japanese

¶ Korean

¶ Spanish

To enable these languages, install the appropriate language supportpack from the Tivoli Manager for Oracle Language Support CD pluspatch 2.0-ORA-0001 from the Customer Support web site. Forexample, install the following pack for German language support:Tivoli Manager for Oracle Version 2.0 (de)

You can install multiple language support packs for a single product.To get full language enablement, however, you must install theTivoli Framework language support pack as well as the languagesupport pack for Tivoli Manager for Oracle, Version 2.0, plus patch2.0-ORA-0001 from the Customer Support web site.

See the TME 10 Software Installation Service User’s Guide Version3.6 for instructions on installing products. If you do not have thisguide, see the TME 10 Framework Planning and Installation GuideVersion 3.6. For information on setting up a non-Englishenvironment, see the TME 10 Framework Release Notes Version3.6.1.

Translation DefectsEvery effort is made to translate the documentation clearly andaccurately, but terminology changes between versions of a productmay cause inconsistencies in the documentation.

16 Version 2.0

Occasionally you may notice that the text in a procedure doesn’tagree with the accompanying screen capture. If this happens, alwaysfollow the instruction in the text.

A similar problem occurs between different Tivoli products. Forexample, in Spanish the term “supervisor” as used in TivoliFramework is synonymous with the word “monitor” in TivoliManager for Oracle.

CMVC DefectNumber

Description

109126, 109173,109213, 109357,109967, 108838,108820, 108798,108739, 108670,108575, 108535,108503, 108468

Tivoli Manager for Oracle, Version 2.0, usesprocesses to query the status of the Oracle database.The terminology used to indicate thestatus/configuration is not translated.

110108, 108466,111121

Character corruption is apparent but does not limit theuse of the product.

For some double-byte countries on certain platformsof UNIX, the CLI may be corrupted.

Changing the LANG variable to C is a workaround tothe problem.

110201, 110327 Output from Tivoli Manager for Oracle, Version 2.0,contains English strings.

109282 English radio buttons, drop-down menus, and titlesare present in the product but don’t prevent use.

110036 Command line commands in the Unix environmentdisplay in English.

108580 The date format is not localized in Tivoli Manager forOracle, Version 2.0.


1.R

eleaseN

otes

CMVC DefectNumber

Description

108681, 108789,108890, 108891,108896, 108897,108919, 110446,108815, 108816,108818, 109112,109523, 109110

Distributed Monitoring, Version 3.6.2, translationdefects are visible in Tivoli Manager for Oracle,Version 2.0. These defects mainly affect thedouble-byte languages.

Documentation ChangesThe Tivoli Manager for Oracle manuals have been rewritten andrepublished with the release of Version 2.0.

Page Revision or Correction to Tivoli Manager for OracleReference Guide

119 The example output for the NT Service Status monitorshows an E.EXEC error message instead of a normalmonitor completion message.

304 – 305 In the monitor summary table, the monitor number isfollowed by “n/a.” The “n/a” (not applicable) was meant toindicate that the async monitor does not have a monitornumber, but due to a formatting error it appears on the sameline as the monitor number for the background monitor.

TBSM Instrumentation

This section provides important information about Tivoli Managerfor Oracle – TBSM Instrumentation, Version 2.0 on UNIX andWindows NT. Please review these notes thoroughly before installingor using this product.

This section includes the following topics:

¶ System requirements

¶ Installation

18 Version 2.0

¶ Known defects

¶ Overview of TBSM

¶ Setting up TBSM Instrumentation

¶ Troubleshooting

¶ Uninstalling TBSM Instrumentation

¶ Programming interfaces

System RequirementsThis section describes the software, hardware, and memoryrequirements for Tivoli Manager for Oracle – TBSMInstrumentation, Version 2.0.

Software Version RequirementsThe following software must be installed before you install TBSMInstrumentation:

¶ TEC Adapter Configuration Facility, 3.6 or later

¶ Tivoli SIS, 3.6 or 3.6.1

¶ Tivoli Software Distribution, 3.6 or later

¶ Software Distribution Gateway, 3.6 or later (gateway only)

¶ Tivoli Manager for Oracle

The following software can be installed after TBSM Instrumentationbut must be installed before component discovery:

¶ Oracle

¶ TME 10 Enterprise Console (TEC)

¶ TBSM Server

TBSM Instrumentation Usage PrerequisitesThe following conditions must be satisfied before you initiatecomponent discovery in TBSM. They may be satisfied before orafter installation of the TBSM Instrumentation component.

¶ TEC must be installed and be configured for TBSM.


1.R

eleaseN

otes

¶ Tivoli TBSM Event Enablement 1.1 must be installed andconfigured on the node where the TEC server is installed. TivoliTBSM Event Enablement includes the following:

v Configuring the APM_HEARTBEAT,APM_THRESHOLD, APM_CI_CHANGE, andAPM_CONNECTION_CHANGE event classes at the TEC.

v Defining the topology server or servers to which the TivoliTBSM events will be forwarded.

¶ One of the following Java packages must be installed on allendpoints where Oracle database resources to be managed byTBSM reside.

v Java Development Kit (JDK). For the levels of JDK, refer tothe Tivoli Business Systems Manager Release Notes, Version1.1.

v Java Runtime Environment (JRE).

Hardware RequirementsThe following table displays the estimated disk space and memoryrequired for Tivoli Manager for Oracle – TBSM Instrumentation,Version 2.0. The estimated disk space includes space for the TivoliManagement Region (TMR) server and clients.

The disk space requirements are in addition to those required byTME 10 Framework and Distributed Monitoring products. Consultthe appropriate application guide for application planninginformation and space requirements.

Platform Disk Space Memory

AIX 4 4MB 8 MB

HP-UX 4MB 15 MB

Solaris 4MB 30 MB

Windows NT 4MB 10 MB

The memory requirements displayed in the previous table:

20 Version 2.0

¶ Represent the requirements for each registered Oracle database.For example, if a host machine supports two Oracle databases,you should double the minimum additional memoryrequirements.

¶ Are in addition to the memory required by TME 10 Frameworkand TME 10 Distributed Monitoring products.

¶ Depend on the workload of each Tivoli Distributed Monitoringagent component. Large and complex profile distributions mayrequire more memory than the minimum figures listed.

In addition, the swap space for each architecture should be doublethe amount of RAM on each machine.

InstallationThis section summarizes the installation procedures. It includesinformation about prerequisites, installation procedures, and using theTivoli Software Installation Service.

Installation Procedure SummariesThe following sections summarize the installation procedures for anew installation. See Chapter 3, “Installing the Software,” in theTivoli Manager for Oracle User’s Guide for complete instructions.

Installation from the Desktop

1. Back up the Tivoli database, so you can restore it from a previousversion, if you encounter a problem during installation. Do one ofthe following:

Select Backup from the Desktop menu on the Tivoli desktop.

—OR—

Use the wbkupdb command. See the TME 10 Framework ReferenceManual for more information on the wbkupdb command, which alsohas a restore option.

2. Choose Install → Install Product option from the Desktop menu.

3. Use the File Browser dialog to identify or specify the path to theinstallation media.

4. Select the component to install from the Select Product to Installlist:


1.R

eleaseN

otes

Tivoli Manager for Oracle – TBSM Instrumentation, Version 2.0

5. Select the clients to install the product on from the Available Clientsscrolling list.

The TBSM Instrumentation component should be installed on theTMR server host only.

6. Click the Install button or the Install & Close button.

7. Click the Continue Install button to start the installation.

8. Press the Close button to close the Product Install dialog.

Installation from the Command LineYou can use the winstall command to install Tivoli Manager forOracle – TBSM Instrumentation from the command line. For moreinformation about this command, see the TME 10 FrameworkReference Manual.

winstall SyntaxThis is the syntax for the winstall command.

winstall [–y] [–c dir] [–s managed node][–i ORACLE | OSENTRY | ORAINST] [–n] [managed_node...]

The following list describes each argument for the winstallcommand.

–y Installation continues without prompting or confirmation.

–c dir Complete path to the installation files (images) for thisproduct.

–s managed nodeManaged node in the Tivoli region that has the directory thatyou specified with dir.

–i ORACLE|OSENTRY|ORAINSTSpecifies the product that you want to install:

¶ ORACLE.IND for the Framework component

¶ OSENTRY.IND for the Distributed Monitoringcomponent

22 Version 2.0

¶ ORAINST.IND for the TBSM Instrumentationcomponent

A product installation index file ends with the extension .IND, butyou do not need to specify the .IND extension.

–n Installs the product on all managed nodes that do notcurrently have the product installed. This argument isignored if you enter a value for managed_node.

managed_nodeSpecifies the managed node on which you want to install theproduct. You can specify multiple managed nodes. If you donot specify a managed node, Tivoli installs the product on allmanaged nodes in the TMR.

Command Line ExampleThe following command installs Tivoli Manager for Oracle – TBSMInstrumentation on the TMR server donald. The installation does notprompt for confirmation. The install files are in the directory/oracle2.0/install/tbsm on solaris251. The product installation indexfile is ORAINST.winstall -y -c /oracle2.0/install/tbsm -s solaris251 -i ORAINST donald

SIS InstallationsTivoli Software Installation Services (SIS) can be used to install thisproduct. You need to import the desired components into theInstallation Repository (IR) from the installation CD.

1. On the desktop, choose Install → Software Installation Services.

2. Go to the Install Repository window

3. In the Install Repository window, click the Import CD Imagesbutton. The Import Product window appears, showing severalchoices, including the following choice:

Tivoli Manager for Oracle – TBSM Instrumentation, Version2.0

Choose TBSM Instrumentation, select the desired interps, andfinish importing the CD images into the Installation Repository.


1.R

eleaseN

otes

For more information, see the TME 10 Software Installation Service(SIS) User’s Guide, Version 3.6.

Overview of Tivoli TBSMThe following sections describe the components of Tivoli TBSM.For more information, refer to the Tivoli Business Systems ManagerInstallation and User’s Guide, Version 1.1.

TBSM and the Tivoli DesktopWhen the TBSM Instrumentation for Tivoli Manager for Oracle isinstalled, the following desktop components are created:

¶ Top Level Policy Region:Applications_hostname-region

¶ Policy Region:PR_Oracle_Default_hostname-region

¶ Profile Managers:PM_ Component_2.0

¶ Task Libraries:TL_Oracle_2.0_Default_Component_2.0_hostname-region

¶ File Packages (containing instrumentation code):FP_Oracle_2.0_Default_Component_2.0_hostname-region

¶ Sentry Profiles (containing instrumentation monitors):SN_Oracle_2.0_Default_Component_2.0_hostname-region

TasksComponent tasks are contained in component task libraries, asdescribed in “Overview of Tivoli TBSM” on page 24.

Instrumentation tasks may be run from the Tivoli desktop or fromthe command line. Tivoli recommends running all instrumentationtasks from the TBSM server console.

Note: The instrumentation library may time out when a task is runthat returns no output or causes aggregation not to occur.

The tasks supported by each instrumented component are outlinedbelow:

24 Version 2.0

¶ Query_State — Returns the status of the instrumentedcomponent. Returns UP if status is available, or DOWN if not.

¶ Query_Thresholds — Sends one or more threshold events tothe TEC for use by the Tivoli TBSM environment.

¶ Query_Threshold_Settings — Returns current thresholdsettings.

¶ Query_Values — Returns the current value for a specifiedmonitor.

¶ Set_Polling_Interval — Sets the monitoring schedule to thespecified interval in minutes.

¶ Set_Pulse — Adjusts the frequency at which the heartbeatmonitor is run.

¶ Set_Thresholds — Defines the circumstances under whichthreshold events are sent to the topology server.

¶ Start — Starts the instrumented component and sends an eventto update the TBSM console view.

¶ Stop — Stops the instrumented component with the shutdownimmediate option and sends an event to update the TBSMconsole view.

¶ ViewAlertLog — Displays the last 75 lines of the instrumentedcomponent’s Alert Log.

Note: The OracleDatabaseManager component does not supportthe ViewAlertLog task.

¶ ViewProperties — Displays the instrumented component’sTivoli Manager for Oracle – TBSM Instrumentation registrationand other details.

MonitorsYou can use both TBSM monitors and some of the tasks availablethrough Tivoli Manager for Oracle – TBSM Instrumentation.


1.R

eleaseN

otes

TBSM MonitorsThe following TBSM monitors are supported by each instrumentedcomponent:

¶ APMConnectionChangeMonitor — Detects and notifies thetopology server about new and deleted connections of aparticular instrumented component connection type by sendingan APM_CONNECTION_CHANGE event.

¶ APM_HEARTBEAT — Informs the topology server of theexistence of an instrumented component by sending anAPM_HEARTBEAT event.

¶ CompInfoChangeMonitor — Informs the topology server thatan instrumented component’s information has changed bysending an APM_CI_CHANGE event.

¶ State — Informs the topology server of the state of aninstrumented component by sending an APM_THRESHOLDevent.

Note: You might need to redistribute TBSM monitors after an oservshutdown.

Supported Monitors from Tivoli Manager for OracleThe following Tivoli Manager for Oracle monitors are supported.The monitors appear in TBSM by their CLI names. The tables showthe CLI name and the corresponding GUI name.

Database Monitors (OracleDatabaseManager Collection)

CLI Name GUI Name

alerts Alerts

archivespacerl Archive space (Number of redo logs)

backgrounddumpspace Background dump space

freespacedef Free space deficit

freespacefragmentation Free space fragmentation

freetablespace Free tablespace

maximumextents Maximum extents

26 Version 2.0

CLI Name GUI Name

nettwolistener Unix SQL*Net V2 listener

rowsindual Rows in DUAL table

Instance Monitors (OracleInstanceManager Collection)

CLI Name GUI Name

bufcachehitratio Buffer cache hit ratio

bufcachehitratioi Buffer cache hit ratio (Interval)

callrate Call rate

continuedrowratio Continued row ratio

dictcachehitratio Dictionary cache hit ratio

dictcachehitratioi Dictionary cache hit ratio (Interval)

enqueuetimeouts Enqueue timeouts

freelistwaits Freelist waits

libcachehitratio Library cache hit ratio

libcachehitratioi Library cache hit ratio (Interval)

physicalreads Physical I/O reads

physicalwrites Physical I/O writes

processratio Process ratio

readsysstatd Number of Deadlocks

redologwaits Redo log space waits

rollbackwaits Rollback waits

sortoverflowratio Sort overflow ratio

Discovering the Oracle ComponentsOracle components are discovered by means of events sent as aresult of monitors distributed to the component of interest.

The OracleInstanceManager and OracleDatabaseManagercomponents are each discovered by monitors distributed to theOracle resource profile endpoint. These monitors are typed;therefore, it is not possible to discover an OracleDatabaseManager


1.R

eleaseN

otes

component by distributing the OracleInstanceManager monitors to anOracleDatabaseManager profile endpoint.

On the TBSM console view, all the logically relatedOracleDatabaseManager components have lines drawn to theirassociated OracleInstanceManager component to show theirrelationships. For more information, see “Connections to TBSMComponents” on page 42.

Setting Up TBSM InstrumentationThis section describes the procedures you use to set up TBSMInstrumentation after you have installed it on the TMR server.

Initiating Component DiscoveryComponent discovery is the means of informing the topology serverof the existence of components. Tivoli Distributed Monitoring is themeans of discovery for Oracle components. A heartbeat event, whichspecifies information that uniquely identifies a component, isgenerated and sent to the TEC. This event is forwarded to thetopology server. The topology server then makes available themanagement capabilities defined for this component in its descriptionfiles.

Prior to initiating the discovery of Oracle components procedure,make sure all the Oracle components you wish to manage usingTivoli TBSM have been registered using Tivoli Manager for Oracle– TBSM Instrumentation. For information on registering Oraclecomponents, see “Registering an Oracle Database” in the TME 10Module for Oracle Framework User’s Guide.

It is important to perform this action because the means of discoveryof these components by the topology server depends on them havingbeen registered by Tivoli Manager for Oracle – TBSMInstrumentation.

To initiate the discovery of Tivoli Manager for Oracle – TBSMInstrumentation components, do one of the following:

¶ Auto-initiate Oracle component discovery. See “Auto-initiatingComponent Discovery” on page 29.

28 Version 2.0

—OR—

¶ Manually initiate Oracle component discovery. See “ManuallyInitiating Component Discovery” on page 32.

Note: Information in the following subsections assumes that youhave installed Tivoli Manager for Oracle – TBSMInstrumentation and registered all Oracle resources to bemanaged from Tivoli TBSM.

Auto-initiating Component DiscoveryYou can initiate the discovery of components with theDiscoverOracleComponents.sh script. This script is located in thetivoli_install_dir/bin/generic/OracleManagerScripts directory onthe TMR server. The product CD-ROM also contains theDiscoverOracleComponents.sh script in the SUPPORT directory(however, you will need to rename DISCORA.SH toDiscoverOracleComponents.sh).

This script automates the Oracle component discovery initiationprocess by doing the following:

1. Lists all the available profile endpoints for an Oracle componenttype.

2. Prompts for user input for endpoints to discover. Accepts allselected endpoints by default.

3. Subscribes specified endpoints to their appropriateTBSM-specific component profile managers.

4. Subscribes appropriate endpoints to TBSM-specific componentprofile manager.

5. Distributes component File Package profiles to specified profileendpoints.

6. Unsubscribes endpoints from a TBSM-specific profile manager.

7. Distributes Sentry profiles to profile-selected endpoints.

8. Reports all status to the following log file:$wtemp/DiscoverOracleComponents_$timestamp.log


1.R

eleaseN

otes

To successfully run the DiscoverOracleComponents.sh script, thefollowing prerequisites must be met:

¶ You have configured your Tivoli environment by runningsetup_env.sh.

¶ Oracle is installed and all resources for which componentdiscovery initiation is required are registered.

¶ Tivoli Manager for Oracle – TBSM Instrumentation is installedon the TMR server.

¶ The oserv process is running.

¶ You are running a Korn or Bash shell.

To run the script, enter the following at a command prompt on theTMR server:bash$ cd <tivoli_install_dir>/bin/generic/OracleManagerScripts

bash$ sh DiscoverOracleComponents.sh

The following menu is displayed:

1. PRODUCTIndicates that the product for which component discoverywill be made is Oracle. The default setting is Oracle.

2. COMPONENTIndicates that the component type for which discovery willbe made is OracleInstanceManager. Valid entries areOracleInstanceManager and OracleDatabaseManager.

3. PROFILE MANAGERIndicates the valid TBSM-specific profile manager for theOracleInstanceManager component.

4. SENTRY PROFILEIndicates the valid Sentry profile for theOracleInstanceManager component.

5. PROFILE ENDPOINT(S)Indicates the valid profile endpoints for theOracleInstanceManager component. This list is dynamic and

30 Version 2.0

will change depending on the available registered Oracleresources and the component option selected.

6. DISCOVER COMPONENTSInitiates discovery for the options selected, gives the statusof action being taken, and writes detailed output to a log file.

7. EXITQuits menu option selection.

Note: Entries for the DiscoverOracleComponents.sh script are casesensitive; therefore, an entry for COMPONENT such asoracleinstancemanager is not valid.

ENTER OPTIONPrompts you to select the desired option by typing in itsoption number. Then press Enter.

For example, to select the v815@v815@obi-wan resource as theendpoint for the OracleInstanceManager component, enter 5 at theENTER OPTION prompt and press Enter.

A message appears listing the current values for the selectedresource, and prompts you to either enter one of the resource namesor press Enter to accept all of the resources. For this example, enterv815@v815@obi-wan and press Enter.

The menu is then redisplayed with the resource you selected listed asthe only profile endpoint.

To discover the OracleInstanceManager component, for example,enter 6 at the ENTER OPTION prompt and press Enter.

A message asks you to wait while the OracleInstanceManagercomponent is discovered, followed by another message when thediscovery is complete. It also displays steps for you to complete thediscovery.

Shortly after this action, events will be sent to the TEC that are thenforwarded to the specified topology server for component discoveryto complete.


1.R

eleaseN

otes

You can also initiate component discovery manually. See thefollowing subsection, “Manually Initiating Component Discovery”.

Manually Initiating Component DiscoveryThis subsection describes the manual method for discovering Oraclecomponents.

Note: The following procedure assumes that you have installedTivoli Manager for Oracle – TBSM Instrumentation andregistered all the Oracle resources to be managed from TBSMServer using Tivoli Manager for Oracle – TBSMInstrumentation.

Perform the following steps:

1. Distribute the Tivoli Manager for Oracle – TBSMInstrumentation file packages. See the following subsection,“Subscribing Endpoints and Distributing File Packages”.

2. To discover the Oracle components on the topology server,distribute the appropriate Tivoli Manager for Oracle – TBSMInstrumentation monitoring profiles to those components. See“Subscribing Resources and Distributing Monitoring Profiles” onpage 33.

3. Make sure the TBSM Administrators have valid Tivoli logins andare assigned the appropriate Tivoli Manager for Oracle – TBSMInstrumentation roles.

Subscribing Endpoints and Distributing File PackagesAfter you install Tivoli Manager for Oracle – TBSMInstrumentation, you can distribute the following file packages:FP_Oracle_2.0._Default_OracleInstanceManager_2.0._\hostname-region

FP_Oracle_2.0._Default_OracleDatabaseManager_2.0._\hostname-region

Distribute these file packages to the endpoints on which the Oraclecomponents exist in order to have the instrumentation code availablefor local execution. The order of distribution is not important.

32 Version 2.0

Note: Distribute all file packages to all nodes where Tivoli Managerfor Oracle – TBSM Instrumentation objects exist that youwish to manage from the topology server.

Subscribing Resources and Distributing Monitoring ProfilesAfter you install Tivoli Manager for Oracle – TBSMInstrumentation, subscribe and distribute the component Sentryprofiles as follows.

1. Subscribe the OracleInstanceManager endpoint to profilemanager PM_OracleInstanceManager_2.0. and distribute theOracle monitoring profile to the OracleInstanceManagerresources you wish to manage from the topology server:SN_Oracle_2.0_Default_OracleInstanceManager_2.0_\hostname-region

2. Subscribe the OracleDatabaseManager endpoint to profilemanager PM_OracleDatabaseManager_2.0. and distribute theOracleDatabaseManager monitoring profile to theOracleDatabaseManager resources you wish to manage from thetopology server:SN_Oracle_2.0_Default_OracleDatabaseManager_2.0_\hostname-region

TBSM receives the monitor status through TEC events forwarded tothe topology server.

To subscribe and distribute the TBSM Instrumentation profiles to anOracleInstanceManager endpoint, do the following:

1. Double-click the PM_OracleInstanceManager_2.0. profilemanager icon.

2. Add the OracleInstanceManager endpoints you wish to managefrom Tivoli TBSM to the list of subscribers.

Do this by dragging and dropping the OracleInstanceManagercomponent on the Profile Manager window’s Subscriberspalette.

—OR—

On the Profile Manager window’s main menu, choose ProfileManager → Subscribers.


1.R

eleaseN

otes

3. On the Subscribers dialog, make sure yourOracleInstanceManager components are in the CurrentSubscribers list. Otherwise, select your targetOracleInstanceManager instances from the Available to becomeSubscribers list and click the left-arrow button to transfer theentries to the Current Subscribers list.

4. Click the Set Subscriptions & Close button.

5. Set the Sentry profile distribution defaults.

6. On the Profile Manager window, double-click on the followingprofile icon:SN_Oracle_2.0_Default_OracleInstanceManager_2.0_\hostname-region

7. On the TME 10 Distributed Monitoring Profile Propertiesdialog’s main menu, chose Profile → Distribution Defaults.

8. On the Distribution Defaults dialog, make sure the followingoptions are selected:

a. All Levels Of Subscribers

b. Make subscribers’ profile an EXACT COPY of thisprofile

9. Click the Set & Close button to return to the TME 10Distributed Monitoring Profile Propertiesdialog.

10. Distribute the Sentry profile for:SN_Oracle_2.0_Default_OracleInstanceManager_2.0_hostname-region

to the subscribing OracleInstanceManager instances.

Do this by dragging and dropping the Sentry profile on theOracleInstanceManager instances you wish to manage usingTBSM.

—OR—

Double-click the Sentry profile icon.

11. On the Profile Manager window’s main menu, choose ProfileManager → Distribute.

34 Version 2.0

12. On the Distribute Profile dialog, make sure only theOracleInstanceManager components you wish to manageusing TBSM are in the Distribute To These Subscribers list.

13. Click the Distribute & Close button to distribute the profileand return to the TME 10 Distributed Monitoring ProfileProperties dialog.

Note: The monitors contained in these profiles are typed; therefore,a component discovery will not occur if a specific componentprofile is distributed to the wrong endpoint. For example, ifan OracleInstanceManager profile is distributed to theOracleDatabaseManager component, a successful discoveryof the OracleDatabaseManager component will not be madeby TBSM. The Oracle Sentry profiles should not bedistributed to endpoints.

For individual components, the order of subscription anddistribution is not important. However, Tivoli advises that youinclude the OracleInstanceManager component in alldiscoveries because:

¶ All other Oracle components have a relationship to theOracleInstanceManager component

¶ All external components wishing to connect to Oraclecomponents must do so through theOracleInstanceManager component.

Unsubscribing MonitorsStop the monitors before unsubscribing them. To stop monitors, doone of the following:

¶ Unsubscribe the Oracle resources from the profile manager byselecting the Delete all profile copies option.

–OR–

¶ Use the DiscoverOracleComponents.sh script to unsubscribethe resources for which components have been deleted.

To unsubscribe resources from the TBSM-specific monitors and stopcomponent monitors:


1.R

eleaseN

otes

1. Make sure that the resources to unsubscribe from theTBSM-specific profile manager are those listed in option 5. Ifthis is not so, select option 5 and enter the resource names youwant to unsubscribe.

2. At the ENTER OPTION prompt, enter u as shown above andpress Enter.

The script displays the status of each listed resource as it isunsubscribed from the TBSM-specific profile manager.

After you unsubscribe the resources from the TBSM-specific profilemanagers, heartbeat events are no longer sent. The resources must bediscovered again in order to have TBSM send heartbeat events forthem.

See also “Initiating Component Discovery” on page 28.

Configuring TECIf you want events sent by the TBSM Instrumentation monitors toaffect the displayed status of Oracle components on the topologyconsole, you must configure the TEC to forward events sent by thesemonitors to the topology server.

IntroductionPerforming this configuration ensures that TBSM heartbeat, state,connection, and component information events are supported by theTEC and that the TEC forwards these events successfully to thetopology server. For more information on configuring a topologyserver, refer to the Tivoli Business Systems Management Installationand User’s Guide.

MethodsYou can configure the TEC using either of the following methods:

¶ Use TEC facilities on the Tivoli Desktop.

¶ Use TEC commands on the command line.

In the following subsctions, procedures are given for each method.

36 Version 2.0

PrerequisitesBefore you configure the TEC server, the following software mustbe installed on the host where the TEC server runs:

¶ TBSM Event Enablement 1.1

AuthorizationThe following table provides the context and authorization rolesrequired for configuring the TEC.

Activity Context Required Role

Configure the TEC Managed node (wherethe TEC server isinstalled)

senior

Assumptions Used in the ExamplesThe following assumptions are used in the examples:

¶ The rule base configured to support TBSM events is namedGemEvent.

¶ The event server is in the local TMR.

Summary of Configuration StepsIf you choose to configure the TEC from the Tivoli Desktop or usingTEC commands on the command line, you perform the same generalsteps in both cases:

¶ Import class files.

¶ Import rule sets.

¶ Compile and load the rule base.

¶ Stop and restart the event server.

Using TEC Facilities on the Tivoli DesktopThis section summarizes how to use the Tivoli Desktop to configureTEC to forward TBSM Instrumentation monitor events to thetopology server.

The steps you perform are:


1.R

eleaseN

otes

1. Import TEC class files:

a. Import the ESMSentry.baroc rule base and class definitions,positioning it after Sentry.baroc.

b. Import the OracleInstanceManager.baroc rule base andclass definitions, positioning it after ESMSentry.baroc.

c. Import the OracleDatabaseManager.baroc rule base andclass definitions, positioning it after ESMSentry.baroc.

2. Import rule sets:

Import the Oracle_gemevents1_0.rls rule set, positioning it afterthe interapp.rls rule set.

3. Compile and load the rule base.

4. Stop and restart the TEC server.

Events sent from the Tivoli Manager for Oracle – TBSMInstrumentation monitors should now be successfully sent to thetopology server.

Using TEC CommandsThe following sections demonstrate how to use TEC commands toconfigure the TEC for the topology server.

Importing TEC Class Fileswimprbclass -S @EventServer:EventServer \$BINDIR/../generic/OracleManagerMonitoring/ESMSentry.baroc GemEvent

wimprbclass -S @EventServer:EventServer \$BINDIR/../generic/OracleManagerMonitoring/OracleInstanceManager.barocGemEvent

wimprbclass -S @EventServer:EventServer \$BINDIR/../generic/OracleManagerMonitoring/OracleDatabaseManager.barocGemEvent

Importing the Rule Setwimprbrules -S @EventServer:EventServer \$BINDIR/../generic/OracleManagerScripts/oracle_gemevents2_0.rlsGemEvent

38 Version 2.0

Note: Use the oracle_gemevents1_1.rls rule set if you have TivoliManager for Oracle – TBSM Instrumentation, Version 2.0installed.

Compiling and Loading the Rule Basewcomprules -S @EventServer:EventServer GemEvent

Note: If you do not compile the rule base before attempting to loadit, you will get an error message.

wloadrb -S @EventServer:EventServer GemEvent

Stopping and Restarting the Event ServerTo stop the event server, use the following command:wstopesvr -S @EventServer:EventServer

To start the event server, use the following command:wstartesvr -S @EventServer:EventServer

TroubleshootingThe following sections provide instructions for helping you diagnoseand solve problems with TBSM Instrumentation.

Turning on TBSM Instrumentation DebuggingTo turn on TBSM instrumentation debugging, do the following:

1. Edit the gemilib.properties file in the following directory, wherecomponent is either OracleInstanceManagerorOracleDatabaseManager.

$BINDIR/../generic_unix/TME/TBSM/Oracle/Oracle/V1_1_/Oracle/component/V1_1_/

Add or change edit the Log.State setting as follows:Set Log.State=ON

2. “Touch” the set2112.dbg file in the following directory

$BINDIR/../generic_unix/TME/TBSM/Oracle/Oracle/V1_1_/Oracle/component/V1_1_/


1.R

eleaseN

otes

This enables some TBSM instrumentation debugging if youdidn’t get far enough to get log files written out to$wtemp/GEM_Instrumentation_Logs.

Example:$bash touch set2112.dbg

The touch command creates a zero-length file of the specifiedname if it does not exist; it updates the last-modified date to thecurrent time if the file exists.

If TBSM Instrumentation log shows that the heartbeat eventwas not generated

1. Make sure that the monitors are actually distributed. Note thatmonitors should be running on the endpoint where the resource isinstalled. Use wlseng to determine this.

2. If the events are still not generated, you may want to unsubscribethe Oracle resource, then discover components again. Use theDelete all profile copies option when unsubscribing. That optionshould clear the distributed monitoring engine of any runningmonitor for that Oracle resource. Use one of the followingmethods to unsubscribe the Oracle resource:

¶ Use the u option of DiscoverOracleComponents.sh tounsubscribe Tivoli Manager for Oracle – TBSMInstrumentation resources for TBSM-specific profilemanagers.

-OR-

¶ Stop the Sentry engine, clear the Sentry engine, andredistribute monitors.

wstopeng stops the Sentry engine.

wclreng clears the Sentry engine.

wlseng lists monitors (should show no monitors running).

After the Oracle resource has been unsubscribed or theSentry engine has been cleared, reinitiate componentdiscovery. (See “Discovering the Oracle Components” onpage 27.)

40 Version 2.0

3. Verify that CLASSPATH and PATH environment variables areset. These variables should include the following:CLASSPATH=jdk1.1.x/lib/classes.zip

PATH=jdk1.1.x/bin

4. Verify that Tivoli Administrator has appropriate authorities. Tosuccessfully execute tasks, the TBSM user must be assigned theoracle_dba role.

5. Verify that Tivoli Administrator has login names for managednodes.

6. Edit HeartBeat.sh to enable additional debugging if needed.

If TBSM Events are not getting to TEC1. Run wtdumprl to see if heartbeat event got to the reception log.

2. If APM classes are undefined, run the TBSM Event Enablementconfiguration script.$BINDIR/TDS/EventService/ihsttec.sh

Note that the TBSM server name should be the hostname wherethe TBSM server resides. Also note that Tivoli Manager forOracle – TBSM Instrumentation is supported only inconfigurations where the event server is local to the TMR.

Enter YES when prompted to forward events to the TBSMServer from the TEC. Default is NO.

3. Check defined TEC classes and rules.

a. Run the following command to find out the active rule basename:wlscurrb

b. Run the following command to list the defined event classes.wlsrbclass active_rulebase_name

c. Ensure that APM_HEARTBEAT is defined. Run thefollowing command to list the defined rules. Be sure thatinterapp.rls is defined.wlsrbrules active_rulebase_name


1.R

eleaseN

otes

4. Rerun the heartbeat monitor from command line:wrunprb "$component" "APMHeartbeatMonitor" "*"

Note: $component represents the OracleInstanceManager orOracleDatabaseManager component.

If tasks fail to execute from the topology consoleEnsure that the user logged in to the topology console has a validTivoli login with the oracle_dba role defined.

Note: All Tivoli Manager for Oracle – TBSM Instrumentation tasksmust run in the oracle_dba privileged context.

Uninstalling TBSM InstrumentationTo remove Tivoli Manager for Oracle – TBSM Instrumentation, runthe InstallOracleInstrumentation script with the -u option, asshown:$ sh $BINDIR/../generic/OracleManagerScripts/InstallOracleInstrumentation -u

This option deletes the Tivoli Manager for Oracle – TBSMInstrumentation profile managers, task libraries, and Sentry and FilePackage profiles.

Programming InterfacesThis section is intended for programmers who want to designinterfaces to Oracle TBSM Instrumentation components. It describesthe following topics:

¶ The approach to designing connections to Tivoli Manager forOracle – TBSM Instrumentation components.

¶ The means by which external components can be connected toOracle components.

¶ The connection types supported.

Connections to TBSM ComponentsThis section deals with the approach taken in designing connectionsto Oracle TBSM components.

42 Version 2.0

Connections from External ComponentsIn order to connect to an Oracle server (instance) or database,external applications must connect to the OracleInstanceManagercomponent. Direct external connections to Oracle components otherthan the OracleInstanceManager component are not supported. Theview is taken that all interactions with the Oracle RDBMScomponents are managed by the OracleInstanceManager. Showingdirect connections to the actual Oracle component is not relevant, orelse presents an incomplete view of component interrelations.

For example, a client application that uses a Oracle schema calledtec connects to the tec schema by way of theOracleInstanceManager component with which the tec schema isassociated, not the tec schema itself.

Relationship InitiationApplications are responsible for initiating the relationship. It is notpractical for the Oracle RDBMS server component to initiate therelationship since the external component might not exist in themanagement tool’s database, or might not actually be instrumented.

The OracleInstanceManager component has no way to determinewhat components are attempting to connect to it, nor any way ofvalidating a connection. It is the developer’s responsibility to ensurethat the connection to the database component is valid.

Defining RelationshipsThe identity of a relationship between the OracleInstanceManagercomponent and an external component is indicated by:

¶ Connection type

¶ Object information (name/value pairs for event origin andsub-origin slots)

¶ Connection direction

Relating ComponentsIn order to establish a relationship, the initiator of the relationshipmust provide information on the connection type, communicationobject, and the connection direction.


1.R

eleaseN

otes

Specifically, the relationship initiator must provide the followingdetails:

¶ Connection type must be a supported type.

¶ Object information refers to a valid name/value information pairthat matches what is in the origin and sub-origin slots of theheartbeat event for the component to which the initiator wishesto connect. This information may be obtained dynamically byimplementing the AppDriver.java methodgetInstanceRelations() to return a relation array containing thisinformation.

¶ Connection direction must be a valid value. The connectiondirection is represented by a number, as follows:

v 1 for origin

v 2 for destination

v 3 for conversational or bidirectional

Note: All Oracle connections supported for externalconnections are bidirectional.

Connection TypesThe following table lists the connection types supported by theOracleInstanceManager component.

Connection Type Origin Destination Conversational

DBConnectiona X

Oracle_DBa X

ServedByb X

Servesb X

a. DBConnection and Oracle_DB connection types are bidirectional(conversational) and are defined as interfaces by which externalcomponents can connect to the OracleInstanceManager component.

b. ServedBy and Serves connection types are reserved for use as theOracle component intra-connection types.

44 Version 2.0

Communication InformationThe OracleInstanceManager component supports the followingtable of name/value information pairs in its heartbeat event originand sub-origin slots.

Name/Value Pair Variable Description

Origin - Hostname, hostname

Sub-origin - OracleInstanceManager,instanceID_

The hostname is the name of the host theOracleInstanceManager resides on (in lowercase).

The instanceID_ is the object identity (OID) ofthe OracleInstanceManager as determined by:wlookup –r OracleInstanceManagernemuchay@nemuchay.

Origin - OracleInstanceManagerLabel,labelString

Sub-origin - OracleInstanceManager,instanceID_

The labelString is the object label of theOracleInstanceManager as determined by the_get_label method. For example, idlcall -v$OracleInstanceManagerOID _get_label.

The instanceID_ is the object identity of theOracleInstanceManager as determined by:wlookup –r OracleInstanceManagernemuchay@nemuchay.


Sub-origin - OracleInstanceManagerID,oracleinstancemanagerID


The oracleinstancemanagerID is the identity (orname) of the Oracle installation. This is the SID(Server ID) of the Oracle installation.


Sub-origin - RDBMSIdentifier,oracleinstancemanagerID




1.R

eleaseN

otes

Name/Value Pair Variable Description

Origin - TCPIPAddress

Sub-origin - RDBMSIdentifier,oracleinstancemanagerID

The TCPIPAddress is the TCP/IP address of thehost that the OracleInstanceManager resides on.This may be determined using the Java utility,TCPIPAddress.getLocal().


Note: The italicized words above are variables, whose values must be valid as described inthe right column.

All of the name/value pairs above are as listed in the origin and sub-origin slots of theOracleInstanceManagerheartbeat event. See “OracleInstanceManager Heartbeat Event” onpage 48.

Implementing the RelationshipTo initiate a connection to any component, you need to implementthe getInstanceRelations() method in AppDriver.java. ThegetInstanceRelations() method returns a list representing therelationships in which the initiator is currently participating.

In order to establish a relationship with the OracleInstanceManagercomponent, an external application must match at least one of thename/value pairs specified in the previous table.

Note: Values for origin and sub-origin event slots are case-sensitiveand matches must be exact.

In implementing the getInstanceRelations() method, the objective isto return a relation array that contains the information relevant toforming a relationship with the desired OracleInstanceManagercomponent (see the example “OracleDatabaseManagergetInstanceRelations() Method” on page 47). The informationrelevant to forming this relationship must be at least one of the pairsreturned in the origin/sub-origin heartbeat event (see the example“OracleInstanceManager Heartbeat Event” on page 48).

46 Version 2.0

OracleDatabaseManager getInstanceRelations() MethodIn the following example, the Perl scriptrelate_to_oracleinstancemanager.pl expects the initiator’sinstanceID as an argument and returns the label and OID of theOracleInstanceManager that the initiator wishes to form arelationship with.

Note: The initiator may form relationships with multiplecomponents, or other components may form relationships withit.

### EVENT ###

APM_HEARTBEAT;

source='Oracle;Oracle;2.0';

severity=HARMLESS;

msg='Oracle;OracleDatabaseManager;2.0: v806@train-18 is Down';

apm_data1=v806@train-18;

adapter_host=train;

sub_origin='0=OracleDatabaseManager=1380391268.6.61;

0=OracleDatabase=1380391268.6.61;0=OracleDatabase=1380391268.6.61;

0=OracleDatabase=1380391268.6.61;';

apm_hbinterval=360;

apm_endpoint_oid=1380391268.6.61;

apm_display_name=v806@train-18;

sub_source='Oracle;

OracleDatabaseManager;2.0';

apm_es_managed_node='1=train';

apm_application_status=1;

origin='0=OracleDatabaseManager=train.austin.lab.tivoli.com;

0=Hostname=train.austin.lab.tivoli.com;


1.R

eleaseN

otes

0=OracleDatabaseLabel=v806@train-18;1=69.1.8.68;';

END

OracleInstanceManager Heartbeat Event### EVENT ###

APM_HEARTBEAT;

hostname='obi-wan.dev.tivoli.com';

adapter_host='obi-wan';

source='Oracle;Oracle;1.1';

apm_old_source='';

origin='0=OracleInstanceManager=obi-wan.dev.tivoli.com;0=Hostname=obi-wan.dev.tivoli.com;0=Hostname=obi-wan.dev.tivoli.com;0=Hostname=obi-wan.dev.tivoli.com;0=OracleInstanceManagerLabel=v815@[email protected];1=146.84.23.157;';

sub_origin='0=OracleInstanceManager=1671340084.1.1342;0=OracleInstanceManager=1671340084.1.1342;0=OracleInstanceManagerID=v815;0=RDBMSIdentifier=v815;0=OracleInstanceManager=1671340084.1.1342;0=RDBMSIdentifier=v815;';

severity='HARMLESS';

msg='Oracle;OracleInstanceManager;1.1: v815@[email protected] Down';

apm_hbinterval=360;

apm_old_origin='';

apm_old_sub_origin='';

apm_endpoint_oid='1671340084.1.1342#M7Instance::Instance#';

apm_display_name='v815@[email protected]';

sub_source='Oracle;OracleInstanceManager;1.1';

apm_data4='';

apm_data3='';

48 Version 2.0

apm_data2='';

apm_data1='';

apm_old_sub_source='';

apm_es_managed_node='1=obi-wan.dev.tivoli.com';

apm_application_status=1;

END

;

### END EVENT ###

PROCESSED


1.R

eleaseN

otes

50 Version 2.0

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GI10-0519-03

Documents

Tivoli Manager for Oracle** Release Notespublib.boulder.ibm.com/tividd/td/oracle2/GI10-0519-03/en_US/PDF/GI10... · Tivoli Manager for Oracle Version 2.0 Release Notes This document