ibm tivoli netcool performance manager: upgrade guide · stopping the sap monitor ... netcool...

IBM Tivoli Netcool Performance Manager 1.3.2Wireless ComponentDocument Revision R2E1

Upgrade Guide

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 97.

© Copyright IBM Corporation 2006, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this information . . . . . . . . vIntended audience . . . . . . . . . . . . vThe Tivoli Netcool Performance Manager - Wirelesscomponent user publications . . . . . . . . . v

Chapter 1. Pre-upgrade tasks . . . . . 1Supported upgrade path . . . . . . . . . . 1Upgrade considerations for the Tivoli IntegratedPortal. . . . . . . . . . . . . . . . . 1Overview of the Oracle 11g upgrade . . . . . . 1Server hardware and software requirements . . . . 2

Server hardware requirements . . . . . . . 2Server software requirements . . . . . . . . 3

Gateways . . . . . . . . . . . . . . . 7The Platform package . . . . . . . . . . . 7Stop Tivoli Netcool Performance Manager clients . . 8Stopping the application server and loaders . . . . 8Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . . 8Stopping the SAP manager . . . . . . . . . 9Stopping the SAP monitor . . . . . . . . . . 9Stopping the Tivoli Netcool Performance Managercron jobs . . . . . . . . . . . . . . . 10Checking the database status . . . . . . . . 10Run the Dependency Checker tool. . . . . . . 12Installing Oracle 11g . . . . . . . . . . . 15

Checking for free space . . . . . . . . . 15Performing a cold backup of the Oracle 10gdatabase . . . . . . . . . . . . . . 15Locate the prerequisite software before InstallingOracle 11 . . . . . . . . . . . . . . 16Installing Oracle 11g . . . . . . . . . . 16Installing the Oracle 11g Client . . . . . . . 17Installing Oracle 11g Instant Client (StandaloneServer or Database Server combined with TivoliCommon Reporting) . . . . . . . . . . 18Restarting the database . . . . . . . . . 19Checking that the database is ready for theupgrade . . . . . . . . . . . . . . 20

Upgrading the Tivoli Directory Server and IBM DB2 21Locating the required packages . . . . . . . 22Checking the installed versions . . . . . . . 23

Archiving the previous release . . . . . . . . 23Upgrading Tivoli Common Reporting installed by anon-root user . . . . . . . . . . . . . . 24

Chapter 2. Tivoli Netcool PerformanceManager Software Upgrade . . . . . . 27Pre-upgrade checklist . . . . . . . . . . . 27Upgrade scenarios . . . . . . . . . . . . 27Upgrading a stand-alone system . . . . . . . 27

Core software configuration . . . . . . . . 28Entering the Tivoli Common Reporting serverdetails . . . . . . . . . . . . . . . 29Upgrading the JBoss application server . . . . 31

Database upgrade to Oracle 11g - Phase 1 . . . 32Cronjob installation. . . . . . . . . . . 34Restoring configuration . . . . . . . . . 35Migrating loaders . . . . . . . . . . . 35Synchronizing users . . . . . . . . . . 35Encoding Passwords . . . . . . . . . . 36

Upgrading a distributed system . . . . . . . 36Running an interactive upgrade . . . . . . 36Upgrading the database server . . . . . . . 37Upgrading a separate directory server . . . . 41Upgrading the application server . . . . . . 45Upgrading the loader server . . . . . . . . 49Tivoli Common Reporting server upgrade . . . 52

Upgrading the Base Common Pack Suite . . . . 55The Base Common Pack Suite . . . . . . . 55

Chapter 3. Post-upgrade tasks . . . . 57Upgrading to Tivoli Integrated Portal 2.2 . . . . 57Updating Oracle settings for Tivoli CommonReporting users . . . . . . . . . . . . . 58Run the deploy_war.sh script . . . . . . . . 59Customized JBoss settings . . . . . . . . . 60Process checks for Solaris . . . . . . . . . . 61Process checks for Linux . . . . . . . . . . 62Process checks for AIX. . . . . . . . . . . 62SAP process check . . . . . . . . . . . . 63Rebooting the server . . . . . . . . . . . 64Tivoli Netcool Performance Manager core processesstop/start . . . . . . . . . . . . . . . 64Starting the loaders . . . . . . . . . . . . 65Populating wireless data after upgrade . . . . . 65

Wireless Component only: Populating thedatabase schema tables . . . . . . . . . 65

Chapter 4. Enabling Tivoli CommonReporting on Tivoli NetcoolPerformance Manager . . . . . . . . 69

Chapter 5. Rolling back to the previousTivoli Netcool Performance Managerversion . . . . . . . . . . . . . . 71Stopping Tivoli Netcool Performance Managerclients . . . . . . . . . . . . . . . . 71Stopping the Tivoli Netcool Performance Managerframework . . . . . . . . . . . . . . 71Stopping the SAP manager . . . . . . . . . 72Stopping the SAP monitor . . . . . . . . . 72Stopping Tivoli Common Reporting . . . . . . 73Rollback Tivoli Directory Server and DB2 . . . . 73Stopping the directory server . . . . . . . . 74Downgrade the database version . . . . . . . 74

Getting started with database downgrade . . . 74Testing the database connection . . . . . . 75Rolling back the database. . . . . . . . . 75

© Copyright IBM Corp. 2006, 2012 iii

Resolving invalid database objects or components 76Restore old previous version of software . . . . 76Process checks . . . . . . . . . . . . . 77

Process status checks . . . . . . . . . . 78Stop and start the Tivoli Netcool PerformanceManager core processes . . . . . . . . . 80

Start the Tivoli Netcool Performance Manager cronjobs . . . . . . . . . . . . . . . . . 81

Chapter 6. Removing the previousTivoli Directory Server and IBM DB2Version . . . . . . . . . . . . . . 83

Chapter 7. Complete the Oracle 11gupgrade . . . . . . . . . . . . . . 85Process checks . . . . . . . . . . . . . 85Finalizing the Database Upgrade - Phase 2 . . . . 85Stop all application services . . . . . . . . . 85

Stopping the application server and loaders . . 85

Stopping the Tivoli Netcool PerformanceManager framework . . . . . . . . . . 86Stopping the SAP manager . . . . . . . . 86Stopping the SAP monitor . . . . . . . . 87

Finalize the database upgrade . . . . . . . . 87Restarting the database . . . . . . . . . . 88Starting the remaining processes . . . . . . . 89

Chapter 8. Troubleshooting tasks . . . 91After upgrading Tivoli Common Reporting, it is notpossible to log into Tivoli Integrated Portal . . . . 91When Tivoli Common Reporting upgrade fails, theinstallation cannot be rerun . . . . . . . . . 91

Appendix. Dependency Checker errors 93

Notices . . . . . . . . . . . . . . 97

Trademarks . . . . . . . . . . . . 101

iv IBM Tivoli Netcool Performance Manager: Upgrade Guide

About this information

The Upgrade Guide provides instructions for upgrading IBM® Tivoli® Netcool®

Performance Manager- Wireless Component 1.3.1, to Tivoli Netcool PerformanceManager 1.3.2.

Intended audienceRead this information if you want to upgrade Tivoli Netcool Performance Manager- Wireless Component. This information is intended for:v Experienced system administratorsv Database administratorsv Product installers

Required skills and knowledge

Readers need to be familiar with the following topics:v Hardware:

– IBM PowerPC– Oracle Sun Microsystems– x86-64

v Operating System:

– IBM AIX

– Oracle Solaris

– Red Hat Enterprise Linux

– Microsoft Windowsv Database:

– Oracle database

The Tivoli Netcool Performance Manager - Wireless component userpublications

IBM Tivoli Netcool Performance Manager consists of two main components. Awireline component (formerly Tivoli Netcool/Proviso), and a wireless component(formerly Tivoli Netcool Performance Manager for Wireless).

Tivoli Netcool Performance Manager - Wireless component consists of thefollowing publications:

Table 1. Tivoli Netcool Performance Manager - Wireless component user documentation

Document Description

IBM Tivoli Netcool Performance Manager:Administration Guide - Wireless Component

Instructions and general information on how tomaintain and support Tivoli Netcool PerformanceManager.

IBM Tivoli Netcool Performance Manager: IBMTivoli Monitoring Integration Guide - WirelessComponent

Provides instructions for integrating IBM TivoliMonitoring with Tivoli Netcool PerformanceManager.

© Copyright IBM Corp. 2006, 2012 v

Table 1. Tivoli Netcool Performance Manager - Wireless component userdocumentation (continued)

Document Description

IBM Tivoli Netcool Performance Manager:Installation Guide - Wireless Component

Instructions for installing and configuring theTivoli Netcool Performance Manager software.

IBM Tivoli Netcool Performance Manager:ModelMaker Installation Guide - WirelessComponent

Provides instructions for installing theModelMaker BusinessObjects Edition application.

IBM Tivoli Netcool Performance Manager:ModelMaker User Guide - Wireless Component

Provides information and procedures for creatingand modifying Business Objects universes to beused with Tivoli Netcool Performance Managerdatabases.

IBM Tivoli Netcool Performance Manager: TivoliNetcool/OMNIbus Web GUI Integration Guide-Wireless Component

Provides instructions for integrating NetcoolOMNIbus/Webtop with Tivoli NetcoolPerformance Manager.

IBM Tivoli Netcool Performance Manager: ReleaseNotes - Wireless Component

Additional release-specific information not in theguides.

IBM Tivoli Netcool Performance Manager:Upgrade Guide - Wireless Component

Instructions for upgrading Tivoli NetcoolPerformance Manager software.

IBM Tivoli Netcool Performance Manager: UserGuide - Wireless Component

Conceptual information and procedures for usingTivoli Netcool Performance Manager software forperformance, trending analysis and performancealarms.

vi IBM Tivoli Netcool Performance Manager: Upgrade Guide

Chapter 1. Pre-upgrade tasks

Before starting the upgrade, acquire all of the prerequisite software andinformation, and complete each of the pre-upgrade tasks.

Supported upgrade pathThe supported upgrade path is from IBM® Tivoli® Netcool® Performance Manager- Wireless Component 1.3.1 with the latest fix pack level only. Upgrading fromproduct versions before Tivoli Netcool Performance Manager 1.3.1 is notsupported.

If your system is on a version before 1.3.1, you must first upgrade your system toversion 1.3.1 and apply the latest fix pack level. Then you can upgrade to version1.3.2.

Upgrading to Tivoli Netcool Performance Manager 1.3.2 is supported on thefollowing platforms:v Oracle Solaris SPARCv Red Hat Enterprise Linux (RHEL) x86-64v IBM AIX®

Upgrading only to the same configuration is supported.v A single-server platform deployment can be upgraded only to a single-server

deployment.v Distributed deployments can be upgraded only to the same distributed

configuration. For example, a separated database deployment can be upgradedonly to a separated database deployment.

Upgrade considerations for the Tivoli Integrated PortalUpgrading Tivoli Common Reporting does not upgrade the Tivoli IntegratedPortal. After upgrading Tivoli Common Reporting, you must decide whether tostay on Tivoli Integrated Portal 2.1, or upgrade to Tivoli Integrated Portal 2.2,depending on the other products in your environment.

Overview of the Oracle 11g upgradeOracle recommends that the Oracle database upgrade to version 11g takes place intwo steps, Phase 1 and Phase 2. Installing in two phases ensures system stabilityand avoids a long application downtime when restoring a database from a backuptaken before the upgrade.

As the first step of database upgrade, the Oracle RDBMS Server software isupgraded to version 11g, but database compatibility remains set to an original(pre-upgrade) compatibility level of '10.2.x'.

During the upgrade trial period, monitor the application and database to ensurethat it is operating correctly. When you have assessed the system, you can either

© Copyright IBM Corp. 2006, 2012 1

commit the upgrade by altering the database compatibility mode to '11.2.x', or do afull rollback returning the system to the original configuration using the Oracle 10gsoftware.

Once you change database compatibility mode to '11.2.x', the new databasefeatures became available. Quick downgrade is no longer available, and you mustperform a full database restore from a previously taken database backup to returnto pre-upgrade application configuration.

The Tivoli Netcool Performance Manager upgrade follows the Oraclerecommended upgrade path for the database upgrade. When installing the TivoliNetcool Performance Manager software, Phase 1 upgrades the database to 11g, butthe compatibility mode remains set to an original (pre-upgrade) compatibility level'10.2.x'.

After an upgrade trial period of your choice (two weeks of monitoring isrecommended), in Phase 2 you can accept and complete the upgrade or roll backto the previous version.

Note: Do not remove or alter any files or directories under the Oracle 10g homedirectory until the database upgrade is committed in Phase 2. If you want toremove Oracle 10g directories, then archive all files in the Oracle 10g homedirectory to permanent storage before removing the Oracle 10g software. Ensurethat the 11g Oracle Installer is used to correctly uninstall the Oracle 10g softwareand keep the Oracle software inventory in synchronization. For more details, seethe Oracle documentation.

Server hardware and software requirements

Ensure that you have the necessary server hardware and softwarerequirements.

Server hardware requirementsThe minimum hardware requirements for a Tivoli Netcool Performance Managerinstallation.

The minimum hardware requirements for a Tivoli Netcool Performance Managerserver are as follows:

v 2 x UltraSPARC IV, IV+ or UltraSPARC T2+/T2/T1 processors

v 2 x x86-64 dual-core processors

v 2 x PowerPC Power5 processorsv 16 GB core memoryv 4 x 72 GB and 6 x 146 GB hard disksv Optical drive (DVD ROM/R/RW)

2 IBM Tivoli Netcool Performance Manager: Upgrade Guide

Server software requirementsThe minimum software requirements for a Tivoli Netcool Performance Managerinstallation.

To install a Tivoli Netcool Performance Manager system, you need the appropriatenumber of AIX, Solaris, or Linux servers, plus additional IBM and third-partysoftware for each server. Depending on the server type, you need some or all ofthe following additional software.

Prerequisite softwareThe prerequisite software for a Tivoli Netcool Performance Manager installation.

Product Version

Operating systemv Oracle Solaris 10 Update 8

v Red Hat Enterprise Linux(RHEL) 5.1 or 5.5

v IBM AIX 6.1 or later

v Oracle Enterprise Edition withpartitioning option

v Oracle Client

v Oracle Instant Client

v Oracle Instant Client SQL*PlusExtension package

v Oracle 32-bit libraries

v Oracle Database 11.2.0.2 with partitioningoption.

v Oracle 11.2.0.2 Patch Set; it is a full installation(you do not need to download 11.2.0.1 first).

v At the time of publication, the followingOracle patches are required:

– 6880880 (OPatch patch)

– 10248523 (Patch Set Update 1, PSU)

Before proceeding with the upgrade, check theOracle documentation for the latest Oraclepatches.

v You must install The Oracle 32-bit librariesthat are contained in the Oracle 32 bit instantclient package.

JBoss Application Server 4.0.3 Service Pack 1

Perl 5.6.1 for Solaris or RHEL

Bundled softwareThe following software is bundled with Tivoli Netcool Performance Manager.

Product Version

IBM Tivoli Directory Server (required) 6.3.0.0

IBM DB2 (required) 9.7 Fix pack 2 (version 9.7.0.2)

IBM Tivoli Common Reporting 2.1.1

IBM Tivoli Monitoring (optional) 6.2.1

Uninstalling Tivoli Common Reporting interim fixesBefore upgrading Tivoli Common Reporting, you must uninstall any TivoliCommon Reporting interim fixes that you have installed. Uninstall each of the theinterim fixes according to the instructions in the interim fix documentation.

Chapter 1. Pre-upgrade tasks 3

Procedure1. You must run the following command to list installed fixes:

/usr/ibm/common/acsi/bin/listIU.sh

Note: For Tivoli Common Reporting installations that are done by non-rootusers, run the following command as the Tivoli Common Reporting owner:$HOME/.acsi_$HOSTNAME/bin/listIU.sh

2. Remove any fixes that are listed in the output of the listIU.sh command.These are prefixed with 'Fix' and the name of the fix is listed as Fix Name:TCR-2100-xxx.

Locating the Tivoli Netcool Performance Manager softwareNote the location of the Tivoli Netcool Performance Manager software before youstart the installation.

In addition to the Tivoli Netcool Performance Manager software, the followingIBM products are included: IBM Tivoli Directory Server, IBM DB2, and IBM TivoliMonitoring.

You can install Tivoli Netcool Performance Manager either by using the productmedia, or by downloading it from the IBM Passport Advantage website:http://www.ibm.com/software/howtobuy/passportadvantage/

The following is a list of the core package files:v vallent-vt-ant-<version>.tar.gz

v vallent-vt-as-core-<version>.tar.gz

v vallent-vt-common-<version>.tar.gz

v vallent-vt-core-<version>.tar.gz

v vallent-vt-db-conf-<version>.tar.gz

v vallent-vt-db-install-<version>.tar.gz

v vallent-vt-ds-conf-<version>.tar.gz

v vallent-vt-java-libs-<version>.tar.gz

v vallent-vt-jre-<version>.tar.gz

v vallent-vt-njloader-<version>.tar.gz

v vallent-vt-sap-<version>.tar.gz

v vallent-vt-tcr-<version>.tar.gz

v pmw_install

v default.rsp

v dependency_checker

Locating the Oracle Solaris software

For each server that runs on Oracle Solaris, a full installation (all components) ofSolaris 10 must be available on the server.

Note the location of the Solaris software before starting the installation.

Additional Solaris packages required for installing Oracle 11g:


http://www.ibm.com/software/howtobuy/passportadvantage/

The following packages (or later versions) are required for Oracle Database 11gRelease 2 (11.2) for Oracle Solaris.SUNWarcSUNWbtoolSUNWheaSUNWlibCSUNWlibmSUNWlibmsSUNWsprotSUNWtooSUNWi1ofSUNWi1cs (ISO8859-1)SUNWi15cs (ISO8859-15)SUNWxwfntSUNWcsl

Locating the Red Hat Enterprise Linux software

For each server that runs on Red Hat Enterprise Linux (RHEL), you need a basicRHEL installation. In addition, depending on the server type, install all of thespecified additional RHEL packages.

To check if a package is installed, run the following command:rpm -qa | grep <package_name>

The dependency_checker tool also reports any missing packages. See “Run theDependency Checker tool” on page 12 for details of the tool.

Any additional required packages should be located in the Server directory of theRHEL installation media.

If any packages are missing, install them by running the following command asuser root:rpm -i <RPM package file>

All the additional packages listed in the following sections are x86_64 versionsunless otherwise stated.

You need to have all the packages installed, regardless of whether they are 32 bitor 64 bit.

For example, the libXp package has two packages listed, the i386 and the x86_64version; you must install both.

The architecture is displayed in bold for each package listed.

Additional RHEL packages required for installing Oracle 11g:

Before you install Oracle 11g on an RHEL server, install each of the followingpackages (specified versions or higher) on the server.binutils-2.17.50.0.6-2.el5 x86_64compat-db-4.1.25-9 x86_64compat-libstdc++-33-3.2.3-61 x86_64compat-libstdc++-33-3.2.3-61i386compat-libstdc++-296(i386)control-center-2.16.0-14.el5 x86_64elfutils-libelf-0.125


elfutils-libelf-devel-0.125gcc-4.1.1-52.el5 x86_64gcc-c++-4.1.1-52.el5 x86_64glibc-2.5-12 x86_64glibc-2.3.4-2 (i686)glibc-common-2.5-12 x86_64glibc-devel-2.5-12 x86_64glibc-devel-2.5-12(i386)glibc-headers-2.5-12 x86_64libaio-devel-0.3.106libgcc-4.1.1-52.el5 x86_64libgcc-4.1.1-52.el5(i386)libaio-0.3.96-3 x86_64libgcc-4.1.1-52.el5(x86_64)libgcc-4.1.1-52.el5(i386)libstdc++-3.4.3-9.EL4 x86_64libstdc++-devel-3.4.3-22.1 x86_64libgomp-4.1.1-52.EL5 x86_64libXp-1.0.0-8.el5 (i386)libXp-1.0.0-8.el5 (x86_64)make-3.81-1.1 x86_64sysstat-7.0.0-3.el5 x86_64

Additional RHEL packages required for installing Tivoli Directory Server and

IBM DB2:

Before you install Tivoli Directory Server and IBM DB2 on an RHEL server, youmust install each of the following packages (specified versions or higher) on theserver.compat-libstdc++-296-2.96-138 i386compat-libstdc++-33-3.2.3-61 x86_64compat-libstdc++-33-3.2.3-61 i386compat-gcc-34-3.4.6-4 x86_64compat-gcc-34-c++-3.4.6-4 x86_64compat-libf2c-34-3.4.6-4 x86_64compat-libf2c-34-3.4.6-4 i386kernel-headers-2.6.18-53.el5 x86_64glibc-headers-2.5-18 x86_64glibc-devel-2.5-18 x86_64glibc-devel-2.5-18 i386libgomp-4.1.2-14.el5 x86_64

Additional RHEL packages required for installing Tivoli Common Reporting:

Before you install IBM Tivoli Common Reporting on an RHEL server, you mustinstall each of the following packages (specified versions or higher) on the server:compat-libstdc++-33-3.2.3 x86_64compat-libstdc++-33-3.2.3 i386compat-glibc-2.3.4-2.26 x86_64compat-glibc-2.3.4-2.26 i386openmotif22-2.2.3-18 x86_64openmotif22-2.2.3-18 i386

Locating the AIX software

For each server that runs on AIX, a full installation (all components) of AIX 6.1 orgreater, must be available on the server. Ensure that you have the required AIXsoftware before starting the installation.


Additional AIX packages required for installing Oracle 11g:

Before you install Oracle 11g on an AIX server, install each of the followingpackages (specified versions or higher) on the server.bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctoolsxlC.aix61.rte:9.0.0.1 or later (AIX 6.1)xlC.rte:9.0.0.1 or later (AIX 6.1)

Additional AIX packages required for installing Tivoli Directory Server and IBM

DB2:

Before you install Tivoli Directory Server and IBM DB2 on an AIX server, installeach of the following packages (specified versions or higher) on the server.rsct.basic.rtersct.opt.storagerm

Locating the Oracle RDBMS and Oracle Client softwareNote the location of the Oracle RDBMS and Client software before starting theinstallation.

Locating the Perl softwareThe following section describes the location of the Perl software.

Note: The location of the Perl software before starting the installation.

If necessary, download the Perl 5.6.1 source code (perl-5.6.1.tar.gz) fromhttp://www.perl.com/CPAN/src.

GatewaysGateway upgrades are not part of the core upgrade procedure.

For information about upgrading gateways, see the IBM Tivoli Netcool PerformanceManager Gateways Installation Note.

The Platform packageBefore starting the upgrade, you must install the latest version of the Platformpackage provided with your software distribution. The Platform package containsscripts that help you to prepare your system for an upgrade, and some systemadministration functions.

About this task

Note: In a distributed installation, the Platform package must be installed on allTivoli Netcool Performance Manager servers.

There is no need to remove the old Platform package.

The name of the Platform package file is ibm-tn-plat-install-PLAT<version>.tar.gz.


http://www.perl.com/CPAN/src

The Platform package consists of the files:v ibm-tn-plat-install.install

v ibm-tn-plat-install.remove

v ibm-tn-plat-install.sw

v ibm-tn-plat-install.license

Procedure1. Copy the package file into a directory on the Tivoli Netcool Performance

Manager server.2. Extract the package contents as user root:

gzip -dc ibm-tn-plat-install-PLAT<version>.tar.gz | tar xf -

3. Run the installation script as user root:./ibm-tn-plat-install.install now

The platform package is installed under: /var/install.

Stop Tivoli Netcool Performance Manager clientsAll Tivoli Netcool Performance Manager clients should be stopped beforecontinuing with the upgrade. Notify all users that an upgrade is taking place.

Stopping the application server and loadersRun the required CLI commands to stop the application server and loaders.

Before you begin

Note: In a distributed installation, this procedure must be performed for theapplication server only.

Procedure1. To stop the application server and loaders processes, run the following

command as user virtuo:sap stop -f

2. To check that all the processes are stopped, run the following command as uservirtuo:sap disp

Stopping the Tivoli Netcool Performance Manager frameworkRun the required CLI commands to stop and to monitor the process state of theTivoli Netcool Performance Manager framework.

About this task


Procedure1. Run the following command as user virtuo:

sap stop -f

2. To monitor the process state, execute the command as user root:


v svcs sap-na

v service sapvirtuo status

v /etc/rc.d/init.d/sapvirtuo status

Stopping the SAP managerStopping the SAP manager and confirming that it is stopped.

About this task


Procedure1. Run the command as user root:

v svcadm disable sapmgr-na

v service sapmgrvirtuo stop

v /etc/rc.d/init.d/sapmgrvirtuo stop


v svcs sapmgr-na

v service sapmgrvirtuo status

v /etc/rc.d/init.d/sapmgrvirtuo status

Stopping the SAP monitorStopping and monitoring the SAP monitor for the application and loader serveronly.

About this task

Note: In a distributed installation, this procedure must be performed for theapplication and loader server only.

To stop the SAP monitor:


v svcadm disable sapmon-na

v service sapmonvirtuo stop

v /etc/rc.d/init.d/sapmonvirtuo stop

2. To monitor the process state, execute the command:

v svcs sapmon-na

v service sapmonvirtuo status

v /etc/rc.d/init.d/sapmonvirtuo status


Stopping the Tivoli Netcool Performance Manager cron jobsStop all of the Tivoli Netcool Performance Manager cron jobs on each server.

About this task

To edit the crontab directly, the files to modify are:

Procedure1. Edit the following files:

v /var/spool/cron/crontabs/virtuo


v /var/spool/cron/virtuo

2. Edit the virtuo crontab and insert a comment (#) at the start of the lines thatcontain the jobs listed below:v /appl/virtuo/bin/alarmapi_admin -da

v /appl/virtuo/bin/run_loader_cleanup

v /appl/virtuo/bin/run_itm_rawcoverage_logger

v /appl/virtuo/bin/run_itm_usage_logger

3. Restart the cron daemons:

v

ps -ef | egrep [c]ron | awk ’{ print $2 }’ | xargs kill

v

svcadm restart cron

v

service crond restart

Checking the database statusYou must check the current state of the Tivoli Netcool Performance Managerdatabase before performing the upgrade. Do not proceed with the databaseupgrade if any database components or objects are in an INVALID state or if anyconstraints are in DISABLED state.

About this task

Note: In a distributed installation, this procedure must be performed for thedatabase server only.

You use the dbstatus_report script to check the database.

Procedure1. As user root, ensure that the log and tmp directories used by the script are

owned by the Oracle:<database> owner user, by default oracle:dba.cd <WMCROOT>/admin/oracle/upgrade

chown oracle:dba log tmp

2. As user oracle, enter the following command to ensure that the environmentvariable ORACLE_SID is set.


export ORACLE_SID=<SID>

3. As the oracle user, run the dbstatus_report script:cd <WMCROOT>/admin/oracle/upgrade/bin./dbstatus_report -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>

Where <sysdba PASSWORD> is the password for the Oracle sysdba user and<virtuo PASSWORD> is the password for the Oracle virtuo user.The script generates a log file in <WMCROOT>admin/oracle/upgrade/log with thename dbstatus_report_<timestamp>.log.

Review this log file to check the status of the database.The current state of the database schema is reported. The reports appears:*** Constraints ***

Schema constraints summary

DB_SCHEMA C_STATUS TOTAL

============================== ======== ==========

VIRTUO ENABLED 12151

Disabled schema constraint details

*** Objects ***

DB_SCHEMA OBJECT_TYPE O_STATUS TOTAL

==================== =================== ======== ========

VIRTUO FUNCTION VALID 31

VIRTUO INDEX VALID 3800

VIRTUO INDEX PARTITION VALID 9180

VIRTUO JAVA CLASS VALID 21

VIRTUO JAVA RESOURCE VALID 3

VIRTUO LIBRARY VALID 1

VIRTUO LOB VALID 22

VIRTUO PACKAGE VALID 158

VIRTUO PACKAGE BODY VALID 157

VIRTUO PROCEDURE VALID 61

VIRTUO QUEUE VALID 18

VIRTUO SEQUENCE VALID 304

VIRTUO SYNONYM VALID 3


VIRTUO TABLE VALID 5017

VIRTUO TABLE PARTITION VALID 17695

VIRTUO TRIGGER VALID 107

VIRTUO TYPE VALID 22

VIRTUO TYPE BODY VALID 4

VIRTUO VIEW VALID 1781

List of invalid objects in application schema (NONE if list below is empty)

*****************************************************************************

Note, please contact feature development team for any constraints remaining

in ’DISABLED’ state or for any package that has ’INVALID’ state !

*****************************************************************************

Script completed.

CAUTION:Do not proceed with the database upgrade if any database components orobjects are in an INVALID state or constraints are in DISABLED state.

Important: Check if any database components or objects appear in a reportwith an INVALID status, or if some constraints are in a DISABLED state. If so, runthe following commands as the database owner and check the log fileproduced:cd <WMCROOT>/admin/oracle/upgrade/bin./recompile_invalid -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>./enable_constraints -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>./dbstatus_report -sysdba_pwd <sysdba PASSWORD> -appusr_pwd <virtuo PASSWORD>

If the problem persists, contact your support representative to identify thecause and resolve the problem.

Run the Dependency Checker toolThe dependency_checker tool helps you to validate the configuration of a serverbefore you begin an installation or upgrade. It detects any problems with theplatform configuration.

About this task

The dependency_checker performs the following checks:v Operating system type and versionv Existing file systems and available disk spacev Installation of prerequisite packagesv Location of Tivoli Netcool Performance Manager packagesv Oracle configuration, if Oracle is already installed

For installation, on distributed servers, use the -t option to specify the type ofserver you are checking.


Procedure1. Copy all of the Tivoli Netcool Performance Manager package files to a

designated target directory on the server. The recommended location for thepackage files is /appl.

2. Set the permissions on dependency_checker before you run by giving thefollowing command:chmod u+x dependency_checker

3. Run the following commands as user root:cd <package location>./dependency_checker [ -t app|db|ds|ldr|tcr ]-upgrade

For upgrade, run the dependency checker with the -upgrade option on eachserver before upgrading the server.v -t app (Application server)v -t db (Database server)v -t ds (Directory server)v -t ldr (Loader server)v -t tcr (Tivoli Common Reporting server)v -upgrade (All servers)

Results

The script performs a number of checks on the system. The following exampleoutput shows a successful check with no reported problems:======================================================================Tivoli Netcool Performance Manager pre-installation check======================================================================

Checking PATH.../usr/sbin: OK/usr/bin: OK

Performing checks for server type: all

-------------------------------------------------------------Perform Operating System configuration checks-------------------------------------------------------------

Hostname: server-zone2Processor type sparc is supported.Platform supports 64-bit kernel.Operating system version Solaris 10 5/08 is at supported level.

-------------------------------------------------------------Perform Host Setup configuration checks-------------------------------------------------------------

Fully Qualified Domain name: server-zone2.comChecking IP address... OKChecking root user umask...OKChecking package SUNWarc...OKChecking package SUNWbtool...OKChecking package SUNWhea...OKChecking package SUNWlibm...OKChecking package SUNWlibms...OKChecking package SUNWsprot...OKChecking package SUNWtoo...OKChecking package SUNWi1of...OKChecking package SUNWi1cs...OKChecking package SUNWi15cs...OKChecking package SUNWxwfnt...OK


Checking package SUNWsprot...OK

-------------------------------------------------------------Perform Filesystem configuration checks-------------------------------------------------------------

Checking space on / partition...OKChecking space on /appl partition...OKChecking space on /export/home partition...OKChecking space on /data/trace_log1 partition...OKChecking space on /data/trace_archive1 partition...OKChecking space on /opt partition...OKChecking space on /oradata01 partition...OKChecking space on /oradata02 partition...OKChecking space on /oradata03 partition...OKChecking space on /oradata04 partition...OKChecking space on /oralogs1 partition...OKChecking space on /oralogs2 partition...OKChecking space on /oradump partition...OK

-------------------------------------------------------------Perform Oracle configuration checks-------------------------------------------------------------

Checking if Oracle User exists... no oracle user on this server.

-------------------------------------------------------------Perform TNPM core package checks-------------------------------------------------------------

Checking for core packages in /applChecking for package jre... OKChecking for package ant... OKChecking for package java-libs... OKChecking for package as-core... OKChecking for package core... OKChecking for package sap... OKChecking for package njloader... OKChecking for package ds-conf... OKChecking for package db-install... OKChecking for package db-conf... OKChecking for pmw_install... OKChecking for Platform package... OK

-------------------------------------------------------------Checking for JBoss package-------------------------------------------------------------

-------------------------------------------------------------Perform TDS / DB2 package checks-------------------------------------------------------------

Checking for TDS packages in /appl/depends/tds63Checking for TDS package base... OKChecking for TDS package db2... OKChecking for TDS package gskit... OK

The script reports a FAIL message for any checks which return an invalid result. Asummary of these errors displays when the script completes. The followingexample output shows a number of fail messages:-------------------------------------------------------------The following tests failed -- you must investigate and fixthese failures before beginning the installation-------------------------------------------------------------

FAILURE: 1


GYMWI0054E Invalid umask for root user: 077The umask for the root user must be set to 022-------------------------------------------------------------FAILURE: 2GYMWI0017E Insufficient space on / partition.Space required on this partition: 14155776 KB

Space available: 8391242 KBThe following required directories are mountedon this partition:/var /oradata01 /oradata02 /oratemp

-------------------------------------------------------------FAILURE: 3GYMWI0047E TNPM core packages not foundThe following core packages could not be found: jre ant java-libsas-core core sap njloader ds-conf db-install db-conf

A full list of error messages is given in “Dependency Checker errors,” on page 93.

Installing Oracle 11gInstall the Oracle 11g RDBMS software on a stand-alone system or on the databaseserver in a distributed system.

Checking for free spaceBefore upgrading the database to Oracle 11g, complete this task as a workaroundfor Oracle upgrade issues. On the Appserver, check that there is at least 1 GB of afree space available in SYSTEM table space and OS disk partition wherecorresponding datafiles are located.

Procedure1. As user virtuo, run the following command:

dbspace_admin -stats

You must look at the FREE(MB) column for the SYSTEM row under theTABLESPACE STATISTICS section to know the available free space.

2. If necessary, ensure that there is at least 1 GB by resizing up existing datafilesor increasing MAX datafile size. Also, the new datafiles can be added to aSYSTEM table space.

Performing a cold backup of the Oracle 10g databaseYou must back up the Oracle 10g database before installing the Oracle 11gdatabase. The database backup is required if it is necessary to roll back thesoftware upgrade to the previous version. It is recommended that a cold backup istaken of the database.

About this task

Make a copy of all database files, including datafiles (*.dbf) files, online redologfiles (*.log) and database control files (*.ctl) associated with the Oracle 10g databaseinstance.

Important: Before continuing with the upgrade it is necessary to do a full backupof the <DB name> database.


Procedure1. Run the following command as user root to shut down the database instance,

v svcadm disable database-na

v service dboravirtuo stop

v /etc/rc.d/init.d/dboravirtuo stop

2. Check that the database has shut down, execute the command as user root:

v svcs database-na service

v service dboravirtuo status

v /etc/rc.d/init.d/dboravirtuo status

Important: You must ensure that the database is shut down before starting toback up the database. Failure to do so results in a corrupted database backup.

3. Make a copy of all database files, including database files, log files and controlfiles associated with the database instance.You must ensure that there is sufficient space on the backup media for thesefiles.

Locate the prerequisite software before Installing Oracle 11You must have the prerequisite software before installing the Oracle software.

Before you begin, note the location of the software:v Oracle 11.2.0.2 Patch Set softwarev Oracle one-off patches (Opatch and PSU)v Oracle 11.2.0 client software:

– Oracle 11.2.0 Client– Oracle Instant Client basic– Oracle Instant Client SQL*Plus

Installing Oracle 11gInstall Oracle 11g by using the scripts provided in the platform package. TheOracle installation takes approximately 30 minutes, depending on the specificationof the server.

Procedure1. Run the commands as user root on the server with the -upgrade option:

#/var/install/sbin/oracle11gR2_install -upgrade

The installation conducts a number of checks:Check Oracle User exists.......DoneCheck oinstall group exists...OKCheck database group exists...OK...................................................Please select the Type of Install you wish to executeby entering the number associated with the Install Type:Full install (Oracle 11.2.0.2 + 11.2.0.x.x patch set update) (1)Oracle 11.2.0.2 Client only (2)Oracle 11.2.0.2 Instant Client only (3)11.2.0.x Patch Set (4)


11.2.0.x.x Patch Set Update (5)Oracle 11.2.0.x oneoff patches (6)..................................................[1//2/3/4/5/6] :

2. For a full installation, select option 1.3. At the prompts, specify the location of the Oracle Software and where you

want to install the software. Enter the paths to the Oracle software distributionas requested.Please enter the location of the Oracle 11.2.0.2 Software[/cdrom/cdrom0/database]:

4. Enter the destinations for the Oracle software. In most cases, the defaults areacceptable.Please enter the install location of the Oracle Base [/appl/oracle]:Please enter the value of ORACLE_HOME [/app/oracle/product/11.2.0/db_1]:Please enter the value of ORACLE_HOME_NAME [OraDBHome11R2]:

When the Oracle Software installation is finished, the installation continues onto run the Oracle root.sh script.

Note: If Oracle was previously installed on the server, you might have torespond to additional questions. Default values are displayed and, if filesalready exist, it is recommended that you overwrite the files.

5. The Oracle installation proceeds to install the required opatch patch. At theprompt, enter the location of the Oracle opatch patch:Please enter the location of the Oracle 11.2.0.2 compressed OPatch patch zip(’none’ for none) [/cdrom.cdrom0/patches/opatch]:

6. The Oracle installation proceeds to install the 11.2 Patch Set Update (PSU). Atthe prompt, enter the location of the uncompressed PSU patch:Please enter the location of the Oracle PSU 11.2.0.x.x uncompressed patches(’none’ for none) [/cdrom/cdrom0/patches/psu]:Installing Oracle PSU patch 10248523...|done.

7. The Oracle installation prompts for the location of one-off patches. Check theOracle documentation for details of the latest one-off patches. If there are norequired one-off patches, enter none at the prompt:Please enter the location of the Oracle 11.2.0.2 uncompressed one-off patches(’none’ for none) [/cdrom/cdrom0/patches/oneoff]: noneNo one-off patches to be installed.........................................Oracle 11g installation completed........................................

Installing the Oracle 11g ClientInstall Oracle 11g Client on the server by using the scripts provided in theplatform package. In a distributed system, install the Oracle 11g Client on eachserver except for the Database server (where the Oracle 11g server is installed). Donot install the Oracle 11g Client software on a stand-alone system.

Procedure1. Run the commands as user root on the server with the -upgrade option:

#/var/install/sbin/oracle11gR2_install -upgrade

The installation conducts a number of checks:Check Oracle User exists.......DoneCheck oinstall group exists...OKCheck database group exists...


OK...................................................Please select the Type of Install you wish to executeby entering the number associated with the Install Type:Full install (Oracle 11.2.0.2 + 11.2.0.x.x patch set update) (1)Oracle 11.2.0.2 Client only (2)Oracle 11.2.0.2 Instant Client only (3)11.2.0.x Patch Set (4)11.2.0.x.x Patch Set Update (5)Oracle 11.2.0.x oneoff patches (6)..................................................[1//2/3/4/5/6] :

2. To install the Oracle 11g Client, select option 2.3. At the prompts, specify the location of the Oracle Software and where you

want to install the Oracle Client. Enter the paths to the Oracle softwaredistribution as requested.Please enter the location of the Oracle 11.2.0.2 Software[/cdrom/cdrom0/database]:

4. Enter the destinations for the Oracle Client. In most cases, the defaults areacceptable.Please enter the install location of the Oracle Base [/appl/oracle]:Please enter the value of ORACLE_HOME [/app/oracle/product/11.2.0/db_1]:Please enter the value of ORACLE_HOME_NAME [OraDBHome11R2]:

Note: If the Oracle Client was previously installed on the server, you mighthave to respond to additional questions. Default values are displayed and, iffiles already exist, it is recommended that you overwrite the files.

5. When the Oracle Software installation is finished, the installation continues onto run the Oracle root.sh script. When prompted, enter the location of theOracle Instant Client and the SQL*Plus extension .zip files. In most cases, thedefaults are acceptable.Please enter the location of the Oracle Instant Client ziparchive(s): [/cdrom/cdrom0/Instant_Client]

6. When prompted, enter the location of the Oracle 32 Bit Instant Client ziparchive.Please enter the location of the Oracle 32 Bit Instant Clientzip archive(s): [/cdrom/cdrom0/Instant_Client]

Installing Oracle 11g Instant Client (Standalone Server orDatabase Server combined with Tivoli Common Reporting)

Install the Oracle Database 11g Instant Client on the server where Tivoli CommonReporting is to be installed or upgraded. The Instant Client must be accompaniedby either the Oracle Client or Oracle Server.

Procedure1. Copy the required Oracle files to the Tivoli Common Reporting server.2. To install the Oracle 11g Instant Client, run the following command as user

root on the server:# /var/install/sbin/oracle11gR2_install -upgrade

The installation conducts a number of checks:Check Oracle User exists....... DoneCheck oinstall group exists....... OKCheck dba group exists...


.... OK-----------------------------------------------------------------------Please select the Type of Install you wish to executeby entering the number associated with the Install Type :

Full install (Oracle 11.2.0.2 + 11.2.0.x.x patch set update) (1)Oracle 11.2.0.2 Client only (2)Oracle 11.2.0.2 Instant Client only (3)11.2.0.x Patch Set (4)11.2.0.x.x Patch Set Update (5)Oracle 11.2.0.x oneoff patches (6)oh-----------------------------------------------------------------------[ 1 / 2 / 3 / 4 / 5 ] : 3

3. To install the Oracle Instant Client only, select option 3.4. Enter the destinations for the Oracle software. In most cases, the defaults are

acceptable.Please enter the install location of the Oracle Base [/appl/oracle]:Please enter the value of ORACLE_HOME [/appl/oracle/product/11.2.0/db_1]:The directory /appl/oracle/product/11.2.0/db_1 does not exist and will be createdPlease enter the value of ORACLE_HOME_NAME [OraDBHome11R2]:

5. When prompted, enter the location of the Oracle Instant Client and theSQL*Plus extension .zip files. In most cases, the defaults are acceptable.Please enter the location of the Oracle Instant Client ziparchive(s): [/cdrom/cdrom0/Instant_Client]

6. When prompted, enter the location of the Oracle 32 Bit Instant Client ziparchive.Please enter the location of the Oracle 32 Bit Instant Clientzip archive(s): [/cdrom/cdrom0/Instant_Client]

What to do next

Note: If you have a problem during the installation, you can remove the <Oraclebase> directory and restart the Oracle 11g installation by running theoracle11gR2_install command again.

You can see the Oracle Installation log output in the /var/install/logs/oracle11g_install_<PID>.log file.

Restarting the databaseIn a distributed installation, this procedure must be performed for the databaseserver only.

About this task

Use the command to verify if the database is running or not:

svcs database-na

service dboravirtuo status

/etc/rc.d/init.d/dboravirtuo status

To restart the database:


Procedure

Run the command as user root:

v Stop a database service:svcadm disable database-na

Wait until the database instance is down; the command returns no rows:ps -ef|grep smon

Start a database instance:svcadm enable database-na

v Stop a database service:service dboravirtuo stop


Start a database instance:service dboravirtuo start

v Stop a database service:/etc/rc.d/init.d/dboravirtuo stop


Start a database instance:/etc/rc.d/init.d/dboravirtuo start

Checking that the database is ready for the upgradeBefore upgrading Tivoli Netcool Performance Manager, check that the database isready.

About this task

Note: In a distributed installation, this procedure must be performed on thedatabase server only.

Procedure1. As database owner, check that database instance is running and you can log in:

$sqlplus virtuo/<Virtuo PASSWORD>@<DB name>

2. As database owner, run the Oracle 11g script, utlu112i.sql$export ORACLE_SID=<DB name>$sqlplus / as sysdbaSQL> spool /tmp/upgrade_check.logSQL> @<ORACLE_HOME_11g>/rdbms/admin/utlu112i.sqlSQL> spool offSQL> exit

Where <ORACLE_HOME_11G> is the location where the Oracle 11g softwarewas installed, by default: /appl/oracle/product/11.2.0/db_1;<virtuo PASSWORD> is the password of the virtuo database user.<DB name> is a database name, by default is vtdb.

3. Check the /tmp/upgrade_check.log output log file and ensure that there are noerrors.Note the following items in the upgrade_check.log file:


v Obsolete/Deprecated Parameters: The background_dump_dest anduser_dump_dest parameters are deprecated. These parameters are handledautomatically by the upgrade and can be safely ignored.

v Oracle XML Database: This database is installed automatically by theupgrade and can be safely ignored.

v EM Database Control Repository downgrade is not supported. See the OracleDocumentation if you require the EM data to be saved before the upgrade.

Note: TNPM for Wireless does not require OEM data. This save operationwill only be needed if the customer has a need for that data that is apartfrom the TNPM application.

v Gather Dictionary Statistics: These statistics are gathered automatically by theupgrade and can be safely ignored.

v Events: Tivoli Netcool Performance Manager does not use events so eventscan be safely ignored.

Upgrading the Tivoli Directory Server and IBM DB2Tivoli Directory Server and IBM DB2 must be upgraded to Tivoli Directory Server6.3/DB2 9.7. You can upgrade Tivoli Directory Server and IBM DB2 by using thescripts provided in the platform package as detailed in the procedure.

Before you begin

The required packages for the installation are distributed on the Tivoli NetcoolPerformance Manager installation media. For more information, see “Locating therequired packages” on page 22.Tivoli Directory Server and IBM DB2 requires certain minimum versions on theserver before upgrade. For more information, see “Checking the installed versions”on page 23.

About this task

Note: Perform these procedures on a stand-alone server, directory server, orapplication server.

The upgrade procedure installs the required Tivoli Directory Server and DB2software versions on the system and migrates the DB2 instance from the previousversion. The previous Tivoli Directory Server and DB2 versions remains on thesystem so that they can be rolled back if necessary. If the new version validates onthe system and it is certain that a rollback is not required, remove the old versionfrom the system. See “Removing the previous Tivoli Directory Server version”.

Procedure1. Run the following command as user root:

/var/install/sbin/tds_install -base <target directory> -product virtuo-version 6.3 -upgrade

It is recommended to use the /appl directory as the <target directory> value.2. Provide the absolute path names of the Tivoli Directory Server, DB2, and GSK

packages at the prompts:Enter the full path name of the DS package:/var/install/packages/tds63-<OS>-<arch>-base.tarEnter the full path name of the DS DB2 package:


/var/install/packages/tds63-<OS>-<arch>-db2.tarEnter the full path name of the GSK package:/var/install/packages/tds63-<OS>-<arch>-gskit.tar

3. When you are prompted for the locations of Tivoli Directory Server and DB2patch packages, press Enter at each of these prompts. At time of publication,no patches are required.

Note: Tivoli Directory Server and DB2 do have patches for their versions.Currently, IBM does not recommend installing these patches. In future. IBMmay recommend any patches through technical notes if required.Enter the full path name of the Tivoli Directory Server patch package,if required:Enter the full path name of the DB2 patch package, if required:

4. The tool proceeds to install the new DB2 and Tivoli Directory Server versionsand migrate the DB2 instance....performing pre-install steps for Tivoli Directory ServerDOMAIN set to server.ibm.com from /etc/resolv.confShutting down Tivoli Directory Server....... Unpacking Tivoli Directory Server.-Backing up the DB2 database...DoneBacking up configuration and schema files...DoneInstalling IBM DB2 ESE. Installation can take several minutes....... log can be seen in/var/install/logs/tds_install_<pid>.log and /tmp/db2_install.log.<pid>.... Installing IBM GSKIT.......done....done....Installing Tivoli Directory Server. Installation can take several minutes.......Done. Log can be seen in /var/install/logs/tds_install_25804.log-Removing temporary installation files...-Migrating Tivoli Directory Server instance from version 6.2.Migration can take several minutes...-DoneImporting /tmp/tdsvirtuo-na.xml into SMF repository... done

Locating the required packagesThe required packages for the installation are distributed on the Tivoli NetcoolPerformance Manager installation media in the folder depends/tds63.

v IBM Tivoli Directory Server 6.3 Client-Server with entitlement Solaris(tds63-solaris-sparc-base.tar)

v IBM Tivoli Directory Server 6.3 GSkit Solaris (tds63-solaris-sparc-gskit.tar)

v IBM Tivoli Directory Server 6.3, DB2 v 9.7 Solaris (tds63-solaris-sparc-db2.tar)

v IBM Tivoli Directory Server 6.3 Client-Server with entitlement Linux x86-64(tds63-linux-x86_64-base.tar)

v IBM Tivoli Directory Server 6.3 GSkit Linux x86-64 (tds63-linux-x86_64-gskit.tar)


v IBM Tivoli Directory Server 6.3, DB2 v 9.7 Linux x86-64 (tds63-linux-x86_64-db2.tar)

v IBM Tivoli Directory Server 6.3 Client-Server with entitlement AIX(tds63-aix-ppc64-base.tar)

v IBM Tivoli Directory Server 6.3 GSkit AIX (tds63-aix-ppc64-gskit.tar)

v IBM Tivoli Directory Server 6.3, DB2 v 9.7 AIX (tds63-aix-ppc64-db2.tar)

Checking the installed versionsIBM Tivoli Directory Server and DB2 must be installed with the certain minimumversions on the server before they can be upgraded:

About this task

Note: If the required patch levels are not installed, you must install the requiredTivoli Directory Server and DB2 patches before upgrading the software.

The following patch levels of Tivoli Directory Server and DB2 must be installed:

v Tivoli Directory Server 6.2 Fix Pack 1 IF 4 (Version 6.2.0.7)

v DB2 9.5 Fix Pack 3 (Version 9.5.0.3)

Procedure1. Check the Tivoli Directory Server version installed by running the following

command as userroot:# /opt/IBM/ldap/V6.2/bin/idsversion

2. Check the DB2 version installed by running the following command asuserroot:# /usr/local/bin/db2ls

Archiving the previous releaseTo archive the previous release, you must remove the previous release of IBMTivoli Netcool Performance Manager and move the release contents to an archivedirectory.

About this task

Important: In a distributed installation, this procedure must be performed on allIBM Tivoli Netcool Performance Manager servers. In a distributed installation, nospecific sequence needs to be followed for archiving servers.


/var/install/sbin/archive_release -wmcr <WMCROOT> -productvirtuo

Output similar to the following is displayed:


-----------------------------------------------------------------------

WARNING!!!

This command will disable and archive the current software release.It should only be executed as part of an upgrade.

-----------------------------------------------------------------------

Are you sure you wish to continue? (Y/N) :

2. Enter y to continue.-----------------------------------------------------------------------

Please select the type of system you are upgrading by

entering the number associated with the system type :

All Inclusive (1)

Application (2)

Loader (3)

Directory Server (4)

Database (5)

-----------------------------------------------------------------------

[ 1 / 2 / 3 / 4 / 5 ] :

3. Enter the number corresponding to the type of system you are archiving.

Important: If more than one application resides on the same machine, archiveonce for all applications on that machine. For example, if the application server,the loader, and the directory server all reside on the same machine, select 2 forthe application server to be archived.Current release is PMW1.3.1.0.4

Checking processes...

Upgrading Tivoli Common Reporting installed by a non-root userIf you are planning to use an existing Tivoli Common Reporting installation whichwas installed by a non-root user, you must first upgrade it to Tivoli CommonReporting 2.1.1 using the Tivoli Common Reporting installation program.Otherwise, you can upgrade it as root using the Tivoli Netcool PerformanceManager upgrade procedure.

About this task

To upgrade TCR as a non-root user:

Procedure1. Extract the TCR installation package to disk into a temporary directory with

sufficient space.gzip -dc <tcr_package>.tar.gz | tar xf -

2. Start the launchpad:./launchpad.sh


3. Click Install IBM Tivoli Common Reporting 2.1.1.4. Select the language and click OK.5. Click Next on the Welcome page.6. Accept the terms of the license agreement and click Next.7. Choose Upgrade the existing instance of Tivoli Common Reporting.8. Provide the username and password for the Tivoli Integrated Portal admin user

when requested.9. Follow rest of the steps presented by the upgrade wizard to complete the

upgrade.


Chapter 2. Tivoli Netcool Performance Manager SoftwareUpgrade

Pre-upgrade checklistBefore continuing with the upgrade, ensure that the pre-upgrade steps have beencompleted without errors.

Procedure Topic

The correct platform package is installed. The Platform package

The database status has been checked. Checking the database status

A full backup of the database has beencreated.

Database backup

The previous software release has beenarchived.

Archiving the previous release

Important: Before attempting an upgrade of Tivoli Netcool Performance Manageryou are advised to read any Release Notes and any readme files distributed withyour Tivoli Netcool Performance Manager software. Release Notes and readmefiles can contain information specific to your upgrade not contained in this guide.Failure to consult the Release Notes or readme files may result in a corrupted,incomplete or failed installation. For all current known issues, see the followingIBM technote: http://www-01.ibm.com/support/docview.wss?rs=3256&uid=swg21407459

Upgrade scenariosThere are two scenarios for upgrading Tivoli Netcool Performance Manager:v Upgrading a standalone systemv Upgrading a distributed system

Determine which scenario applies and follow the appropriate procedure.

Upgrading a stand-alone systemOn a stand-alone system, copy the required files to the system and run theappropriate command to start the interactive installation scripts. Enter the requiredinformation at each of the prompts.

Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.3.2 software packages

into the target directory of the stand-alone server.The target directory is the parent directory of the $WMCROOT directory where thecurrent release is installed.For example, if $WMCROOT is set to /appl/virtuo , then the target directory is/appl.

2. Change to the target directory:cd <target_directory>

3. Run the following command as user root:ksh pmw_install -wmcr <WMCROOT> -upgrade


where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed.The default installation directory is /appl/virtuo.Output like the following output is displayed:Making PMW top-level directory: /appl/virtuo

Making installation tasks record: /appl/virtuo/admin/install_tasks

Making software archive directories: under/appl/virtuo/admin/software

Looking for bootstrap package

Found vallent-vt-common-<version>.tar.gz

Extracting and running bootstrap package

Looking for bootstrap script

Running vallent-vt-common.install

Copyright 2011 IBM Ireland PDL, All Rights Reserved

This installation script will install the Performance Managementfor Wireless common software version PMW1.3.2.xon your system.Do you wish to continue?

4. Enter yes to continue with the installation.5. The license agreement is displayed. You are prompted to accept the license

termsDo you agree with the terms of this license? Yes

Enter yes to agree to the license terms.6. The menu is displayed:

What Type of System Are you Installing ?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Tivoli Common Reporting Components only7. Skip package deployment8. Exit TNPMW Install---->

Select Standalone server.

7. Enter yes when prompted to deploy the packages:Do you want to deploy the packages? [yes/no] >yes

Core software configurationThe system proceeds to install and configure the core software. Check eachenvironmental variable as it is displayed.

About this task

The installation displays a list of Tivoli Netcool Performance Managerenvironmental variables and their default values.


Important: It is important that you check each of the environmental variables toensure that they are set to the correct value and update the value if appropriate.These variables set server hostnames and various TCP port numbers. They varyfrom location to location.

Procedure1. You are prompted to verify the environment variables for certain packages:

Please, Verify Environment Settings

.............

.............

A list of environment variables is displayed allowing you to accept the defaultvalues listed, or to edit individual values.

Note: The display time of the values depends on the speed of the server beinginstalled.v If you accept the default values, the installation proceeds.v If you choose not to not accept the defaults, a series of prompts is presented

for you to enter the variable values.2. When the variable values are correct, select the appropriate menu option to

accept the values.3. Repeat this procedure for each package that requires environment variables to

be configured.

Entering the Tivoli Common Reporting server detailsThe system proceeds to upgrade or install Tivoli Common Reporting on thesystem.

Procedure1. You are asked if you want to upgrade or integrate an installed Tivoli Common

Reporting instance on the system. Answer yes if Tivoli Common Reporting isinstalled on this server, this will upgrade Tivoli Common Reporting to version2.1.1.If you have previously upgraded an instance of Tivoli Common Reportinginstalled by a non-root user, answer yes here. The upgrade will create theconfiguration for this TCR instance and will not need to upgrade it.

Note: If you answer no, the system installs a new instance of Tivoli CommonReporting on the server. In this case, follow the steps in the installing TivoliCommon Reporting procedure to complete the installation. For moreinformation, see Installing Tivoli Common Reporting in IBM Tivoli NetcoolPerformance Manager: Installation Guide.Do you want to upgrade or integrate an existing instance of Tivoli Common Reporting?[yes/no] [no] >

2. The installation checks for the Tivoli Common Reporting installation package inthe location depends/tcr in the directory where the Tivoli Netcool PerformanceManager packages are located. If the Tivoli Common Reporting package is notfound here, you are prompted to enter the location of the package. If youreceive this prompt, enter the full path to where the Tivoli Common Reportinginstallation package is located.Please enter the path to the Tivoli Common Reporting package [/appl/depends/tcr]:

Chapter 2. Tivoli Netcool Performance Manager Software Upgrade 29

3. Enter the directory where the current version of Tivoli Integrated Portal isinstalled.Please enter the installation directory for Tivoli Integrated Portal:[/opt/IBM/tivoli/tipv2]---->

4. Enter the directory where the current version of Tivoli Common Reporting isinstalled.Please enter the installation directory for Tivoli Common Reporting:[/opt/IBM/tivoli/tcr]---->

5. Enter the user name of the Tivoli Integrated Portal administrator.Please enter the Tivoli Integrated Portal Admin User: [tipadmin]---->

6. Enter the password for the Tivoli Integrated Portal administrator. You areprompted to enter the password a second time for verification.Please enter the Tivoli Integrated Portal Admin User password: []---->Please enter the password a second time: []---->

7. The system proceeds to upgrade Tivoli Common Reporting to version 2.1.1.Upgrading Tivoli Common Reporting...Preparing to install...Extracting the JRE from the installer archive...Unpacking the JRE...Extracting the installation resources from the installer archive...Configuring the installer for this system’s environment...

Launching installer...

Preparing SILENT Mode Installation...

===============================================================================Tivoli Common Reporting (created with InstallAnywhere)-------------------------------------------------------------------------------

===============================================================================Installing...-------------

[==================|==================|==================|==================][------------------|------------------|------------------|------------------]

Installation Complete.Generating tcr1 startup scripts ....Updating configuration file with TIP credentials...DoneInstallation Complete.

8. After the upgrade is complete, completely close your browser and open itagain. This action clears the browser cache and avoids a known problem withlogging in to the Tivoli Integrated Portal after an upgrade.

9. You may be asked to perform further tasks, such as:v CORE_CRONJOB_INSTALL, which is described in “Cronjob installation” on page

47v ENCODE_PASSWDS, which is described in “Encoding passwords” on page 49


Upgrading the JBoss application serverThe system proceeds to upgrade the JBoss application server configuration.

Procedure

Enter yes when prompted to upgrade the JBoss application server:Would you like to perform task JBOSS_INSTALL ? [yes/no] >yes

The output is displayed:Deploying JBoss 4.0.3SP1...

Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml

init:

[echo] JBOSS VERSION=4.0.3SP1

[echo] JBoss Location=/appl

upgrade:

init:



copy-libs:

[copy] Copying 2 files to /appl/virtuo/as/server/default/lib

[copy] Copying 10 files to /appl/virtuo/lib/tp

init:



fix-alarm-war:

[mkdir] Created dir: /appl/virtuo/temp

[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib

[unjar] Expanding:/appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.earinto /appl/virtuo/

temp[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jarinto /appl/virtuo/temp

init:



signjarPMW:


[echo] Signing JBoss client jar

[copy] Copying 1 file to /appl/virtuo/temp/war/apps/lib

[jar] Updating jar:/appl/virtuo/temp/S02-na-alarm-manager.war

[jar] Updating jar:/appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.ear

BUILD SUCCESSFUL

Total time: 17 seconds

Database upgrade to Oracle 11g - Phase 1The system proceeds to Phase 1 of the database upgrade to Oracle 11g.

Procedure1. Enter yes when prompted to upgrade the database:

Would you like to perform task DB_UPGRADE ? [yes/no] >yes

2. Accept the default identifier when prompted for the database System Identifier(SID):Please enter the Database SID: [vtdb]

3. You are prompted for your Oracle ADDM license type. ADDM is an additionallicense required by Oracle for running Diagnostic or Tuning packs. The validoptions are NONE, DIAGNOSTIC, or DIAGNOSTIC+TUNING.Please enter the ADDM license Type [NONE | DIAGNOSTIC |DIAGNOSTIC+TUNING]: [NONE]

Accept the default or update it to the correct license type.4. You are prompted for the location of Oracle Home for 10g:

Please enter the Oracle 10G Home:[/appl/oracle/product/10.2.0/db_1]

Accept the default Oracle Home for 10g or update it to the correct location.5. You are prompted for the location of Oracle Home for 11g:


Accept the default Oracle Home for 11g or update it to the correct location.6. You are prompted for the password for the system database user.

Please enter the Database sys user password: [<password>]

Accept the default password or enter the correct password.7. You are prompted for the password for the database system user.

Please enter the Database system user password: [<password>]

Accept the default password or enter the correct password.8. The system proceeds to upgrade the database from 10g to 11g:

The time it takes to upgrade the schema depends on the size of the database.Upgrading a database from 10g to 11g takes a minimum of 2 hours.The upgrade log files can be found in the following locations:$WMCROOT/admin/logs/pmw_install.log

$ORACLE_BASE/cfgtoollogs/dbua/logs/silent<x>.log


Database status checkAfter completing the core database version upgrade, the upgrade checks the statusof the database.

About this task

If there are any database components or database objects with a status of INVALIDor constraints in a DISABLED state, the upgrade reports these errors. For example:ERROR: Disabled constraints found after DB upgrade:

Constraint name: <constraint>

...

The cause of these disabled constraints should be investigatedbefore continuing the upgrade.

See/appl/virtuo/admin/oracle/upgrade/log/upgrade_database_<timestamp>.logfor details.

ERROR: Invalid objects found after DB upgrade:

Object name: <object>

...

The cause of these invalid objects should be investigated beforecontinuing the upgrade.


Do you want to continue the upgrade? (Enter "Yes" to continue):

You must determine the cause of the errors before continuing the upgrade. See“Checking the database status” on page 10 for more details.

Procedure1. Indicate if you want to continue the upgrade:

v If the database errors have been satisfactorily investigated and you want tocontinue, enter Yes.

v If the database errors have not been satisfactorily investigated and you wantto exit the upgrade, enter No to exit the upgrade.

2. To resume an upgrade, rerun the pmw_install command as described inUpgrading a standalone system. You receive the prompt:

Note: You will get this prompt only if there are errors found in the databasestatus check.Would you like to perform task DB_UPGRADE? [yes/no]:yes

3. Enter yes at the prompt to upgrade the database.


Cronjob installationThe system proceeds to install the Tivoli Netcool Performance Manager cronjobs.

Procedure1. Enter yes when prompted to install the cronjobs:

Would you like to perform task CORE_CRONJOB_INSTALL ? [yes/no]>yes

2. You are prompted to select the type of system you are installing:Please select the type of PMW System you are installingby entering the number associate with the system type:All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

-----------------------------------------------------------------------

[ 1 / 2 / 3 / 4 / 5 / 6 ] :

Enter 1 for all inclusive.3. You are prompted to enter the location of the Oracle home directory:

Please enter the ORACLE_HOME Directory[/appl/oracle/product/10.2.0/db_1]:

(Enter . if unknown)

Accept the default.4. You are prompted to enter the location of the vtdb database archive directory :

Please enter the vtdb Database Archive Directory [/oradump/vtdb]:


Accept the default.5. You are prompted to enter the location of the directory server log directory:

Please enter the Directory Server log Directory[/appl/ldap/idsslapd-idsinst/logs]:


Accept the default.6. You are prompted to enter the location of the Tivoli Netcool Performance

Manager log directory:Please enter the PMW Log Directory [/appl/virtuo/logs]:



Manager archive logs directory:Please enter the PMW Archive Logs Directory[/data/trace_archive1]:


Accept the default.The installation proceeds to install the root user and virtuo user cronjobs.


The cronjob installation log file output can be found at the following location:$WMCROOT/admin/logs/pmw_install.log

Restoring configurationThis section of the upgrade allows you to automatically restore all of theconfiguration values which were archived from the previous release.

About this task

Restore all of the configuration values if there are specific changes made to theprevious configuration which you want to preserve in the new release . SeeArchiving the previous release. If you do not want to keep any of the previousconfiguration values enter no when prompted, and proceed to Migrating loaders.

Procedure

You are asked if you want to restore the configuration from the previous release.v Enter yes to restore all of the configuration settings from the previous release.v Enter no if you do not want to restore all of the configuration settings from the

previous release.

For a yes response, the system proceeds to restore configuration settings.

Migrating loadersThe system migrates the loaders from the previous release. The migration is doneautomatically and no user intervention is required.

The process is logged in the <WMCROOT>/admin/logs/pmw_install.log log file.Appserver ready.

Executing /appl/virtuo/admin/common/install/upgrade/scripts/

UPG01_loader_migrate...

UPG01_loader_migrate: INFO: Restarting sapmgr...

/appl/virtuo/admin/common/install/upgrade/scripts/UPG01_loader_migratecomplete.

Synchronizing usersThe system proceeds to synchronize Tivoli Netcool Performance Manager andLDAP users.

Procedure

You are prompted to enter or confirm the system administrator user name andpassword.Executing/appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admin...

UPG06_sync_tnpm_ldap_admin: INFO: syncing tnpm and ldap users

Enter administrator username: : [<username>]

---->

Enter administrator password: [<password>]


---->

UPG06_sync_tnpm_ldap_admin: INFO: syncing of tnpm and ldap userscomplete


Encoding PasswordsThe system proceeds to encode the passwords stored in the configuration files.

Procedure1. Enter yes when prompted to encode the passwords:

Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes

Encoding values in /appl/virtuo/conf/as/as-default.properties

Encoding values in /appl/virtuo/conf/as/as-default.properties.N

Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties

Encoding values in /appl/virtuo/conf/dbconnection/vtdb.properties.N

Encoding values in /appl/virtuo/conf/ldap/default.properties.N

Encoding values in /appl/virtuo/conf/ldap/default.properties

Passwords may also be stored in/appl/virtuo/admin/logs/pmw_install.log,

so it should be removed when not needed anymore.

2. The upgrade of the core software is complete. The upgrade output is logged inthe location:$WMCROOT/admin/logs/pmw_install.log

3. Proceed to Post-Upgrade, to complete the post-upgrade configuration tasks.

Upgrading a distributed systemTo upgrade a distributed system, copy the required files to the target server andrun the individual scripts on each server to upgrade the required components.

Running an interactive upgradeTo upgrade the required components, run the script on each individual server.

To upgrade a distributed system, run the pmw_install script on each individualserver to upgrade the required components. Enter information as required by theinstallation scripts. Upgrade the servers, or components on shared servers, in thefollowing order:1. Database server2. Directory server3. Application server4. Loader server

Application and loader serverIn a distributed system, the application server must also be configured as a loaderserver.


The pmw_install script must be run twice on this server:v The first time to upgrade the application componentsv The second time to upgrade the loader components

Upgrading the database serverTo upgrade the database server, all of the Tivoli Netcool Performance Manager1.3.2 core software packages must be copied to the target directory.

Procedure1. Copy all of the Tivoli Netcool Performance Manager 1.3.2 core software

packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed. For example, if $WMCROOT is set to /appl/virtuo , then thetarget directory is /appl.

2. Run the commands user root:

cd /<target_directory>

ksh pmw_install -wmcr <WMCROOT> -upgrade

Where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed. The default installation directory is: /appl/virtuo.The output is displayed:Making PMW top-level directory: /appl/virtuo









This installation script will install the Performance Managementfor Wirelesscommon software version PMW1.3.2.x on your system.

Do you wish to continue?

3. Enter yes to continue.4. Enter yes at the prompt to agree to the license terms.

Do you agree with the terms of this license? Yes

5. The menu is displayed:What Type of System Are you Installing ?

1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only


6. Tivoli Common Reporting Components only7. Skip package deployment8. Exit TNPMW Install---->

6. Select Database Components only.

7. The install asks whether you want to deploy packages:Do you want to deploy the packages? [yes/no] >yes

Enter yes.

Database configurationThe system proceeds to install and configure the core database software.

About this task

The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server host names and various TCP portnumbers and varies from location to location. You can accept the default values,restore values to their default settings or change individual values.Please, Verify Environment Settings

1. Accept Variable Values below

2. Reset Variables to Default values

3. Change WMCHOST=<server_name>

.............

Important: It is important that each of the variables is checked to ensure that theyare set to the correct value.

Procedure1. Select option 3, and change the value of WMCHOST to the hostname of the

application server.2. If required, change any other values.3. When the environment variable values are correct, accept the values and

proceed.

Database upgrade to Oracle 11g - Phase 1The system proceeds to Phase 1 of the database upgrade to Oracle 11g.

Procedure1. Enter yes at the prompt to upgrade the database:

Would you like to perform task DB_UPGRADE? [yes/no]: yes

2. When prompted for the database System Identifier (SID), accept the defaultidentifier.Please enter the Database SID: [vtdb]

3. You are prompted for the ADDM license type you have from Oracle. ADDM isan additional license required by Oracle for running Diagnostic or Tuningpacks. The valid options are NONE, DIAGNOSTIC, orDIAGNOSTIC+TUNING.Please enter the ADDM license Type [NONE | DIAGNOSTIC |DIAGNOSTIC+TUNING]: [NONE]

Accept the default or update it to the correct license type.4. You are prompted for the location of Oracle Home for 10g.



Accept the default Oracle Home for 10g or update it to the correct location.5. You are prompted for the location of Oracle Home for 11g.


Accept the default Oracle Home for 11g or update it to the correct location.6. You are prompted for the password for the system database user.

Please enter the Database sys user password:

Either accept the default password or enter the correct password.7. You are prompted for the password for the database system user.

Please enter the Database system user password:

Accept the default password or enter the correct password.8. The system proceeds to upgrade the database from 10g to 11g:

The time it takes to upgrade the schema depends on the size of the database.Upgrading a database from 10g to 11g takes a minimum of 2 hours.The upgrade log files can be found in the locations:$WMCROOT/admin/logs/pmw_install.log

$ORACLE_BASE/cfgtoollogs/dbua/logs/silent<x>.log

Database status check

The dbstatus_report script is automatically executed during the databaseengine version upgrade. Examine the results at: $WMCROOT/admin/oracle/upgrade/log/upgrade_database_<timestamp>.log for details.If there are any database components or objects with a status of INVALID orconstraints in a DISABLED state, the upgrade reports errors like the followingerrors.ERROR: Disabled constraints found after DB upgrade:

Constraint name: <constraint>

...

The cause of these disabled constraints should be investigatedbefore continuing the upgrade.


ERROR: Invalid objects found after DB upgrade:

Object name: <object>

...

The cause of these invalid objects should be investigated beforecontinuing the upgrade.


Do you want to continue the upgrade? (Enter "Yes" to continue): Yes

You must determine the cause of the errors before continuing the upgrade. See“Checking the database status” on page 10 for more details.


v If the database errors have been satisfactorily investigated and you want tocontinue:Enter Yes.

v If the database issues have not been satisfactorily investigated and you wantto exit the upgrade:Enter No to exit the upgrade.To resume the upgrade, re-run the pmw_install command as described inUpgrading a distributed system. You receive the prompt:

Would you like to perform task DB_UPGRADE? [yes/no]:

Enter yes at the prompt.


Procedure1. You are prompted to install cronjobs:


Enter yes.

2. You are prompted to select the type of system you are installing:Please select the type of PMW System you areinstalling by entering the number associate with the system type :

All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

-----------------------------------------------------------------------

[ 1 / 2 / 3 / 4 / 5 / 6 ] :

Enter 5 for database.3. You are prompted to enter the location of the Oracle home directory:

Server type selected: DBPlease enter the ORACLE_HOME Directory [/appl/oracle/product/11.2.0/db_1]:(Enter . if unknown)

Accept the default.4. You are prompted to enter the location of the Oracle base directory:

Please enter the ORACLE_BASE Directory [/appl/oracle]:(Enter . if unknown)

Accept the default.5. You are prompted to enter the ORACLE_SID parameter:

Please enter the ORACLE_SID Parameter [vtdbUPG]:(Enter . if unknown)

Accept the default.6. You are prompted to enter the location of the vtdb database archive directory

directory:Please enter the vtdb Database Archive Directory [/oradump/vtdb]:(Enter . if unknown)

Accept the default.The installation continues on to install the root user and virtuo user cronjobs.


The cronjob installation log output can be found at the following location:$WMCROOT/admin/logs/pmw_install.log

Encoding PasswordsThe system proceeds to encode the passwords stored in configuration files.

Procedure

You are asked if you want to encode the passwords:Would you like to perform task ENCODE_PASSWDS ? [yes/no] >yes

Enter yes.The system proceeds to encode the passwords in the configuration files:Encoding values in /appl/virtuo/conf/as/as-default.properties






Passwords may also be stored in/appl/virtuo/admin/logs/pmw_install.log,

so it should be removed when not needed anymore.

The upgrade output is logged in the location:$WMCROOT/admin/logs/pmw_install.log

Upgrading a separate directory serverThe installation of the directory server schema must be complete before upgradinga separate directory server.

About this task

Important: This section must only be completed if the directory server schema isinstalled on a separate directory server.

Note: If the directory server schema is instated on the application server, omit thissection and proceed to Upgrading the application server.

To determine if the directory server schema is installed on a directory server, checkfor the existence of the <WMCROOT> directory on the directory server. If the directoryexists then the schema is installed. The <WMCROOT> directory is the location whereTivoli Netcool Performance Manager, was previously installed. The defaultinstallation directory is: /appl/virtuo.


packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed. For example, if $WMCROOT is set to /appl/virtuo , then thetarget directory is /appl.

2. Run the following commands as user root:


cd /<target_directory>

ksh pmw_install -wmcr <WMCROOT> -upgrade [-a]

where <WMCROOT> is the location where Tivoli Netcool Performance Manager,was previously installed. The default installation directory is: /appl/virtuo.Use the -a option if you are installing a component in addition to an existingone. For example, a loader server in addition to a previously existingapplication server.The output is displayed:Making PMW top-level directory: /appl/virtuo











3. Enter yes to continue.4. The license agreement is displayed. You are prompted to accept the license

terms.Do you agree with the terms of this license? Yes



Select Directory Server Components only.

6. The install asks whether you want to deploy packages:Do you want to deploy the packages? [yes/no] >yes

Enter yes.

7. Verify the Environment Settings.


Please, Verify Environment Settings1. Accept Variable Values below2. Reset Variables to Default values3. Change WMCHOST=<server_name>..........................

The installation lists the default values of Tivoli Netcool Performance Managerenvironment variables. These variables set server hostnames and various TCPport numbers and will vary from location to location. You can accept thedefault values, restore values to their default settings or change individualvalues.

Important: It is extremely important that you set each of these environmentvariables to the correct value.

8. Select option 3 and change the value of WMCHOST to the hostname of theapplication server.

9. Change any other values that you want to change from the default values.10. When you are satisfied that the environment variable values are correct,

accept the values and proceed.




Enter yes.

2. You are prompted to select the type of system you are installing:Please select the type of PMW Systemyou are installing by entering the number associate with the system type :

All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

-----------------------------------------------------------------------

[ 1 / 2 / 3 / 4 / 5 / 6 ] :

Enter 5 for database.3. You are prompted to enter the location of the Oracle home directory:

Please enter the ORACLE_HOME Directory[/appl/oracle/product/10.2.0/db_1]:


Accept the default.4. You are prompted to enter the location of the vtdb database archive directory

directory:Please enter the vtdb Database Archive Directory [/oradump/vtdb]:


Accept the default.5. You are prompted to enter the location of the directory server log directory:


Please enter the Directory Server log Directory[/appl/ldap/idsslapd-idsinst/logs]:



Manager log directory:Please enter the PMW Log Directory[/appl/virtuo/logs]:


Accept the default.7. You are prompted to enter the location of the PMW archive logs directory:

Please enter the PMW Archive Logs Directory[/data/trace_archive1]:


Accept the default.The installation continues on to install the root user and virtuo user cronjobs.The cronjob installation log output can be found at the location:$WMCROOT/admin/logs/pmw_install.log

Encoding PasswordsThe system proceeds to encode the passwords stored in configuration files.

Procedure








Passwords may also be stored in/appl/virtuo/admin/logs/pmw_install.log.

It should be removed when not needed.

The upgrade output is logged in the location:$WMCROOT/admin/logs/pmw_install.log


Upgrading the application serverUpgrade the application server as described in the following procedure.

About this task


packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed.For example, when $WMCROOT is set to /appl/virtuo, then the target directory is/appl.

2. Run the commands user root:cd <target_directory>

ksh pmw_install -wmcr <WMCROOT> -upgrade

Where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed.The default installation directory is: /appl/virtuo.The output is displayed:Making PMW top-level directory: /appl/virtuo










3. Enter yes to continue.4. The license agreement is displayed. You are prompted to accept the license

terms.Do you agree with the terms of this license? Yes


What Type of System Are you Installing ?1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only


6. Tivoli Common Reporting Components only7. Skip package deployment8. Exit TNPMW Install---->

6. Select 2 for Application Server Components only.7. You are asked if you want to deploy packages:

Do you want to deploy the packages? [yes/no] >yes

Enter yes.

Core software configurationAbout this task

The system proceeds to install and configure the core software. You are promptedto verify the environment variables for certain packages:Please, Verify Environment Settings




4. Change VTDBHOST=<server_name>

5. Change LDAPHOST=<server_name>

Environmental variables: The installation displays a list of Tivoli NetcoolPerformance Manager variables. The variables have default values.

Important: It is important that each of the variables is checked to ensure that theyare set to the correct value and updated if appropriate. These variables set serverhostnames and various TCP port numbers. They varies from location to location.

A list is displayed allowing you to accept the default values listed, or to editindividual values.

Procedure1. Select option 4 and change the value of VTDBHOST to the hostname of the

database server.2. If a separate directory server is configured, select option 5 and set the value of

LDAPHOST to the hostname of the directory server.3. If required, change any other values.

JBoss application server updateThe system proceeds to update the JBoss application server configuration.

Procedure

You are asked if you would like to update the JBoss application server:Would you like to perform task JBOSS_INSTALL ? [yes/no] >yes

Enter yes .The output is displayed:The output is displayed:Deploying JBoss 4.0.3SP1...

Buildfile: /appl/virtuo/admin/common/install/scripts/build.xml

init:




upgrade:

init:



copy-libs:

[copy] Copying 2 files to /appl/virtuo/as/server/default/lib

[copy] Copying 10 files to /appl/virtuo/lib/tp

init:



fix-alarm-war:

[mkdir] Created dir: /appl/virtuo/temp

[mkdir] Created dir: /appl/virtuo/temp/war/apps/lib

[unjar] Expanding:/appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.earinto /appl/virtuo/

temp

[unjar] Expanding: /appl/virtuo/lib/na-alarm-service-server.jarinto /appl/virtuo/temp

init:



signjarPMW:

[echo] Signing JBoss client jar

[copy] Copying 1 file to /appl/virtuo/temp/war/apps/lib

[jar] Updating jar:/appl/virtuo/temp/S02-na-alarm-manager.war

[jar] Updating jar:/appl/virtuo/as/server/default/deploy_core/S02-na-alarm-manager.ear

BUILD SUCCESSFUL

Total time: 17 seconds




Enter yes.

2. You are prompted to select the type of system you are installing:Please select the type of PMW Systemyou are installing by entering the number associate with the system type:

All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)


-----------------------------------------------------------------------

[ 1 / 2 / 3 / 4 / 5 / 6 ] :

Enter 2 for application.3. You are prompted to enter the location of the Tivoli Netcool Performance

Manager log directory:Please enter the PMW Log Directory[/appl/virtuo/logs]:



Manager archive logs directory:Please enter the PMW Archive Logs Directory[/data/trace_archive1]:



Restoring configurationThis section of the upgrade allows you to automatically restore all of theconfiguration values that were archived from the previous release.

About this task

If you do not want to keep any of the previous configuration values, enter nowhen prompted, and proceed to Synchronizing users.

Procedure

You are asked if you want to restore the configuration from the previous release.v Enter yes to restore all of the configuration settings from the previous release.

For a yes response, the system proceeds to restore configuration settings.v Enter no if you do not want to restore the configuration settings from the

previous release.

Synchronizing usersThe system proceeds to synchronize Tivoli Netcool Performance Manager andLDAP users.

Procedure

You are prompted to enter or confirm the system administrator username andpassword.Executing/appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admin...

UPG06_sync_tnpm_ldap_admin: INFO: syncing tnpm and ldap users

Enter administrator username: : [<username>]

---->

Enter administrator password: [<password>]

---->



/appl/virtuo/admin/common/install/upgrade/scripts/UPG06_sync_tnpm_ldap_admincomplete.

Encoding passwordsThe system proceeds to encode the passwords stored in configuration files.

Procedure








Passwords may also be stored in/appl/virtuo/admin/logs/pmw_install.log.It should be removed if not needed.

Upgrade loader components on the application serverThe loader packages on the application server must be upgraded.

Procedure

Follow the instructions in Upgrading the loader server on the application server.When running the pmw_install script again, you must use the -a option.

Upgrading the loader serverTo upgrade the loader server, copy all the Tivoli Netcool Performance Manager1.3.2 core software packages to the target directory.

Before you begin

The target directory is the parent of the $WMCROOT directory where the currentrelease is installed. For example, when $WMCROOT is set to /appl/virtuo , then thetarget directory is /appl.

Procedure1. Run the following commands as user root:

cd <target_directory>

ksh pmw_install -wmcr <WMCROOT> -upgrade [-a]

Where <WMCROOT> is the location where Tivoli Netcool PerformanceManager was previously installed.Use the -a option if you are installing the component in addition to an existingone. For example, a loader server in addition to a previously existingapplication server.


The output is displayed:Making PMW top-level directory: /appl/virtuo








This installation script will install the Performance Managementfor Wireless common software version PMW9.2.1.xon your system.


2. Enter yes to continue.3. When prompted, enter yes to accept the license terms.

Do you agree with the terms of this license? Yes

The menu is displayed.What Type of System Are you Installing ?

1. Standalone server2. Application Components only3. Loader Components only4. Directory Server Components only5. Database Components only6. Tivoli Common Reporting Components only7. Skip package deployment8. Exit TNPMW Install---->

4. Select 3 for Loader Components only.5. You are asked if you want to deploy packages:

Do you want to deploy the packages? [yes/no] >yes

Enter yes.

Loader configurationThe system proceeds to install and configure the loader software.

About this taskPlease, Verify Environment Settings



3. Change LDRHOST=<server_name>


5. Change VTDBHOST=<server_name>

.............

Environment variables- The installation displays a list of Tivoli NetcoolPerformance Manager variables. The variables have default values. These variables


set server hostnames and various TCP port numbers. They vary from location tolocation. You can accept the default values, restore values to their default settingsor change individual values.

Important: It is important that each of the variables is checked to ensure that theyare set to the correct value and updated if needed.

Procedure1. Select option 4 and change the value of WMCHOST to the hostname of the

application server.2. Select option 5 and change the value of VTDBHOST to the hostname of the

database server.3. If required, change other values.4. When the values are correct, accept the values and proceed.




Enter yes.

Enter 3 for loader.(Enter . if unknown)

2. You are prompted to select the type of system you are installing:Please select the type of PMW System youare installing byentering the number associate with the system type :

All Inclusive (1)

Application (2)

Loader (3)


Database (5)

Gateway (6)

-----------------------------------------------------------------------

[ 1 / 2 / 3 / 4 / 5 / 6 ] :

3. You are prompted to enter the location of the Tivoli Netcool PerformanceManager log directory:Please enter the PMW Log Directory[/appl/virtuo/logs]:

Accept the default.4. You are prompted to enter the location of the PMW archive logs directory:

Please enter the PMW Archive Logs Directory[/data/trace_archive1]:




Migrating loadersThe system migrates the loaders from the previous release. The migration is doneautomatically and no user intervention is required. The process is logged in the file<WMCROOT>/admin/logs/pmw_install.log.

About this task

Note: Complete this task on the application server only, and not on standaloneloader servers.Appserver ready.

Executing /appl/virtuo/admin/common/install/upgrade/scripts/

UPG01_loader_migrate...

UPG01_loader_migrate: INFO: Restarting sapmgr...

/appl/virtuo/admin/common/install/upgrade/scripts/UPG01_loader_migratecomplete.

The upgrade of the core software is complete. The upgrade output is logged in thelocation:$WMCROOT/admin/logs/pmw_install.log

Proceed to Post-Upgrade, to complete the post-upgrade configuration tasks.

Tivoli Common Reporting server upgradePerform the following tasks to upgrade a separate Tivoli Common Reportingserver.

Upgrading a separate Tivoli Common Reporting serverPerform this task to upgrade Tivoli Common Reporting on a distributed system.


packages to the target directory.The target directory is the parent of the $WMCROOT directory where the currentrelease is installed. For example, if $WMCROOT is set to /appl/virtuo, then thetarget directory is /appl.

2. If you have installed Tivoli Common Reporting on a separate server from themain Tivoli Netcool Performance Manager components, the Tivoli NetcoolPerformance Manager software may not have previously been installed on theserver. If this is the case, the $WMCROOT directory does not exist on the server.You must create this directory before beginning the upgrade procedure. Enterthe following command as user root:mkdir <WMCROOT>

3. Run the following commands as user root:# cd /appl# ksh pmw_install -wmcr <WMCROOT> -upgrade [ -a ]

where <WMCROOT> is the location where Tivoli Netcool PerformanceManager is currently installed. The -a option is used when a different type ofTivoli Netcool Performance Manager server is to be installed on top of anexisting server, for example, if you are installing the Tivoli Common Reportingcomponent on top of a previously installed application server.

4. Read and accept the license agreement. The following menu is displayed:



5. Select option 6, Tivoli Common Reporting Components only.mkdir <WMCROOT>

6. At the prompt, enter yes to deploy the packages.Do you want to deploy the packages? [yes/no] >yes

7. Verify the Environment Settings.

Results

The system proceeds to upgrade Tivoli Common Reporting. Continue to respondto the prompts as described in the Upgrading Tivoli Common Reporting topic.

Entering the Tivoli Common Reporting server detailsThe system proceeds to upgrade or install Tivoli Common Reporting on thesystem.

Procedure1. You are asked if you want to upgrade or integrate an installed Tivoli Common

Reporting instance on the system. Answer yes if Tivoli Common Reporting isinstalled on this server, this will upgrade Tivoli Common Reporting to version2.1.1.If you have previously upgraded an instance of Tivoli Common Reportinginstalled by a non-root user, answer yes here. The upgrade will create theconfiguration for this TCR instance and will not need to upgrade it.

Note: If you answer no, the system installs a new instance of Tivoli CommonReporting on the server. In this case, follow the steps in the installing TivoliCommon Reporting procedure to complete the installation. For moreinformation, see Installing Tivoli Common Reporting in IBM Tivoli NetcoolPerformance Manager: Installation Guide.Do you want to upgrade or integrate an existing instance of Tivoli Common Reporting?[yes/no] [no] >

2. The installation checks for the Tivoli Common Reporting installation package inthe location depends/tcr in the directory where the Tivoli Netcool PerformanceManager packages are located. If the Tivoli Common Reporting package is notfound here, you are prompted to enter the location of the package. If youreceive this prompt, enter the full path to where the Tivoli Common Reportinginstallation package is located.Please enter the path to the Tivoli Common Reporting package [/appl/depends/tcr]:

3. Enter the directory where the current version of Tivoli Integrated Portal isinstalled.Please enter the installation directory for Tivoli Integrated Portal:[/opt/IBM/tivoli/tipv2]---->

4. Enter the directory where the current version of Tivoli Common Reporting isinstalled.


Please enter the installation directory for Tivoli Common Reporting:[/opt/IBM/tivoli/tcr]---->

5. Enter the user name of the Tivoli Integrated Portal administrator.Please enter the Tivoli Integrated Portal Admin User: [tipadmin]---->

6. Enter the password for the Tivoli Integrated Portal administrator. You areprompted to enter the password a second time for verification.Please enter the Tivoli Integrated Portal Admin User password: []---->Please enter the password a second time: []---->

7. The system proceeds to upgrade Tivoli Common Reporting to version 2.1.1.Upgrading Tivoli Common Reporting...Preparing to install...Extracting the JRE from the installer archive...Unpacking the JRE...Extracting the installation resources from the installer archive...Configuring the installer for this system’s environment...

Launching installer...

Preparing SILENT Mode Installation...

===============================================================================Tivoli Common Reporting (created with InstallAnywhere)-------------------------------------------------------------------------------

===============================================================================Installing...-------------

[==================|==================|==================|==================][------------------|------------------|------------------|------------------]

Installation Complete.Generating tcr1 startup scripts ....Updating configuration file with TIP credentials...DoneInstallation Complete.

8. After the upgrade is complete, completely close your browser and open itagain. This action clears the browser cache and avoids a known problem withlogging in to the Tivoli Integrated Portal after an upgrade.

9. You may be asked to perform further tasks, such as:v CORE_CRONJOB_INSTALL, which is described in “Cronjob installation” on page

47v ENCODE_PASSWDS, which is described in “Encoding passwords” on page 49


Upgrading the Base Common Pack SuiteTivoli Netcool Performance Manager 1.3.2 distribution CD also contains the BCPSuite (1.0.0.3-TIV-TNPM-BCPSUITE.tar.gz).

About this task

Upgrade a number of Base Common Packs (BCPs) from the Base Common PackSuite that is now available on Tivoli Netcool Performance Manager 1.3.2distribution DVD/CD. Base Common Packs (BCPs) are themselves common packsand you upgrade them exactly as you upgrade any other common pack. For moreinformation about BCPs, see “The Base Common Pack Suite.”

Note: IBM is not mandating the upgrade to the latest BCP Suite immediately.Upgrade can be performed as per your convenience.

Procedure1. Download and extract the latest Base Common Pack Suite from

1.0.0.3-TIV-TNPM-BCPSUITE.tar.gz file to a location of your choice.2. Uninstall the existing common packs. For instructions on uninstalling common

packs, see Uninstalling common packs in IBM Tivoli Netcool Performance Manager:Model Maker 1.2.0 Installation and User Guide.

3. Install the latest Base Common Pack Suite and the common packs that youuninstalled in step 2.For instructions on installing Base Common Packs, see Installing common packsin IBM Tivoli Netcool Performance Manager: Model Maker 1.2.0 Installation and UserGuide.

The Base Common Pack SuiteThe Base Common Pack Suite is a set of generic Base Common Packs (BCPs), someof which are mandatory requirements for working with common packs. Allcommon packs have a dependency on at least one BCP, the TCR Time BCP. ForWireless users, BCPs provide the cross-vendor technology support provided byGOMs and GOMlets for technology packs.

The Base Common Pack Suite is updated periodically with the latest versions ofthe BCPs. Before you install or create common packs, you must download thelatest version of the Base Common Pack Suite, and install the BCPs you require.

The Base Common Pack Suite consists of an archive file containing a set ofcommon pack JAR files, which you must download and extract before installing.v The TCR Time BCP is a mandatory dependent pack for all wireless and wireline

common packs, and provides a common time dimension for reporting. It mustbe installed before you can work with any common packs.

v The Wireline Common BCP is a mandatory dependent pack for all wirelinecommon packs. It must be installed before you can work with wireline commonpacks.

v Typically, a number of Wireless BCPs are dependent packs for a wirelesscommon pack. Wireless BCPs support a number of Global Object Model (GOM)and GOMlet technology packs. Refer to individual wireless common packrelease notes to see the list of dependent packs for a particular pack.

For current version information about the Base Common Pack Suite, see the Knownissues with Tivoli Netcool Performance Manager 1.3.2 technote in the Support


knowledge base.


Chapter 3. Post-upgrade tasks

After upgrading the database to Oracle 11g, complete the following post-upgradetasks.

Before you begin

Ensure that the Oracle environment variables point to Oracle 11 as user virtuo. Tocheck this, follow these steps:1. Use the following command to show if any environment variable points to

Oracle 10:’env|grep 10’

2. If any environment variable still points to Oracle 10, update the user's$HOME/.profile then log out and log back in.

3. Run ’env | grep 10’ again to make sure that there are no references to Oracle10.

4. Run the following command as user virtuo:ksh <package_location>/1.3.2_wireless_database_post_install.ksh

Note: <package_location> is the directory where the Tivoli Netcool PerformanceManager 1.3.2 Wireless packages are located.

What to do next

Complete the rest of the tasks as described in the sections below.

Upgrading to Tivoli Integrated Portal 2.2This is an optional step. Should you be running software that is incompatible withTivoli Integrated Portal 2.2, you should remain with Tivoli Integrated Portal 2.1and skip this step.

Procedure1. Login as the user with which you have installed Tivoli Integrated Portal.2. Obtain the software:

Download the version of TIP Feature Pack for your OS located at:http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=All&platform=All&function=all

3. Unzip the downloaded Feature Pack, for example, 2.2.0.1-TIV-TIP-AIXPPC32-RP0001.zip, in a temporary directory.

Note:

v Ensure the JRE in use is IBM Java 6, using 'java -version' and/or 'whichjava'. If not, then set the PATH environment variable to include the TIP javain the path, for example, export PATH=/opt/IBM/tivoli/tipvs/java/bin:$PATH

v There cannot be any JAVA processes running from the TIP directory or theupgrade will fail.


http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=All&platform=All&function=all



4. Stop Tivoli Common Reporting on different platforms, enter the followingcommand:Solaris: svcadm disable tcr<n>-naLinux: service tcr<n>virtuo stopAIX: /etc/rc.d/init.d/tcr<n>virtuo stop

5. Download 2.2.0.1-TIV-TIP-FITSuit-RP0001.zip from: http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=All&platform=All&function=all

6. Unzip 2.2.0.1-TIV-TIP-FITSuit-RP0001.zip into this directory/opt/IBM/tivoli/tip21/profiles/TIPProfile/etc

7. Follow the instructions in the README file for the FIT package that comeswith the TIP 2.2 Feature Pack.

8. For the Tivoli Integrated Portal 2.2 Feature Pack install, copy and modify thesample_response.txt to ensure, for example, the correct TIP_HOME andcorrect Tivoli Integrated Portal password.

9. Follow the instructions in the README file for the TIP 2.2 Feature Pack.For example:cd <unpacked TIP 2.2 Feature Pack folder location>./install.sh -i silent -f <path to response file>/tip2.2FeaturePack_response.txt

10. Stop the Tivoli Integrated Portal processes:<TIP_HOME>/bin/stopserver server1 -username tipadmin -password <tipadmin_password>

11. Ensure there are no running Tivoli Integrated Portal processes:ps -ef|grep -i tip

12. Start Tivoli Common Reporting on different platforms, enter the followingcommand:Solaris: svcadm start tcr<n>-naLinux: service tcr<n>virtuo startAIX: /etc/rc.d/init.d/tcr<n>virtuo start

Updating Oracle settings for Tivoli Common Reporting usersAfter upgrade, you must make some changes to the default Oracle configuration ifyou are a Tivoli Common Reporting user.

About this task

When you installed the Common Pack Service on Tivoli Netcool PerformanceManager 1.3.1, you modified some settings for Oracle 10g that you must nowupdate for Oracle 11g.

Note: If TCR was not used on TNPM 1.3.1, then refer to Model Maker Installationand User Guide for information on modifying the files mentioned in this section.

Procedure1. You set the required Oracle environment parameters for Oracle 10g in the Tivoli

Common Reporting startup script located at /opt/IBM/tivoli/tipv2Components/TCRComponent/bin/startTCRServer.sh. After upgrading toTivoli Common Reporting 2.1.1, you need to make the same changes to thenew version of the startup script. For example, ensure that the $ORACLE_HOMEparameter to points to the Oracle 11g home directory.

2. Run the command stopTCRserver tipadmin <tipadmin_password>, and ifnecessary run the command and startTCRserver tipadmin<tipadmin_password>.





3. When you set up the database connection for Oracle 10g, the$ORACLE_HOME/network/admin/tnsnames.ora file is updated with the tcraccessconnection. After upgrading to Tivoli Netcool Performance Manager 1.3.2, youmust copy the tnsnames.ora file into the new $ORACLE_HOME/network/admin/directory for Oracle 11g.

What to do next

Ensure the environment variables for each user on each server in the system arechanged to use Oracle 11g.1. Use the command env | grep 10 to show any environment variables that point

to oracle 10.2. Update the user's $HOME/.profile then log out and log back in.3. Run env | grep 10 again just to be sure there are no references to oracle 10.

Run the deploy_war.sh scriptAfter upgrade you must run the deploy_war.sh script, if cognos enablement orcommon pack service was installed on the previous version of Tivoli NetcoolPerformance Manager, that is, Tivoli Netcool Performance Manager 1.3.1;otherwise, user can skip this task.

About this task

Carry out the steps documented in this topic only if cognos enablement orcommon pack service was installed on the previous version of Tivoli NetcoolPerformance Manager, that is, Tivoli Netcool Performance Manager 1.3.1.

Procedure1. Navigate to <WMCROOT>/admin/tcr/install/scripts.

Where <WMCROOT> is the location where Tivoli Netcool Performance Managerwas previously installed. The default installation directory is: /appl/virtuo.

2. As the user which installed Tivoli Common Reporting,, run the./deploy_war.sh script

3. Enter TIP location, or press Return to use the default, at the following prompt:TIP Installation Directory [ /opt/IBM/tivoli/tipv2 ]:

4. Enter the Tivoli Integrated Portal Components location, or press Return to usethe default, at the following prompt:TIP Components Installation Directory [ /opt/IBM/tivoli/tipv2Components ]:

5. Enter the Oracle DB server hostname at the following prompt, input ismandatory for this item:ORACLE_HOSTNAME:

6. Enter ORACLE_HOME, or press Return to use the default, at the following prompt:ORACLE_HOME [ /opt/oracle/product/11.2.0-client32 ]:

7. Enter the appropriate ORACLE_SID at the following prompt:Oracle SID (wireline DEFAULT: pv; wireless DEFAULT: vtdb): vtdb

8. Enter the Oracle port, or press Return to accept the default, at the followingprompt:ORACLE_PORT [ 1521 ]:

9. Enter Tivoli Integrated Portal admin username, or press Return to accept thedefault, at the following prompt:

Chapter 3. Post-upgrade tasks 59

TIPADMIN_USER [ tipadmin ]:

10. Enter the password for tipadmin user at the following prompt:tipadmin user password:

11. Enter the password for bicontrol user at the following prompt:bicontrol user password:

12. Restart Tivoli Integrated Portal.

What to do next1. Configure TCR startup for non-root user.

Run this procedure if Tivoli Common Reporting has been installed andupgraded as a user other than root.As root, run the following command:cd $WMCROOT/admin/tcr/install/scripts./update_service -user <tcruser>

Where <tcruser> is the user which installed and upgraded Tivoli CommonReporting.

2. Restart TCR as root:v Solaris:

svcadm restart tcr<n>-na

v Linux:service tcr<n>virtuo stopservice tcr<n>virtuo start

v AIX:/etc/rc.d/init.d/tcr<n>virtuo stop/etc/rc.d/init.d/tcr<n>virtuo start

Where <n> is the numeric id of the TCR instance.

Customized JBoss settingsIf you have customized the log settings for the JBoss, you must redo these changes.

About this task

If you have modified the file $WMCROOT/as/server/default/conf/log4j.xml prior toupgrading, and if you want to retain these changes, then you must edit the fileagain to retain these changes.

Procedure1. Open the 1.3.1 version of the log4j.xml file.

The 1.3.1 version of the file is archived in /appl/archive/virtuo.PMW1.3.1.0/as/server/default/conf/log4j.xml.

2. Transfer all identified changes to the 1.3.2 log4j.xml contained in$WMCROOT/as/server/default/conf/log4j.xml


Process checks for SolarisCheck that all Tivoli Netcool Performance Manager processes have startedsuccessfully for the Solaris operating system.

Solaris

A single command can be used to check the status of the system, as user root::svcs -x appli*/virtuo*

Note: Separate services are created for each instance of Tivoli Common Reportingyou install on each server. Therefore if you have installed two instances of TivoliCommon Reporting, you will have the following services on a Solaris 10 server.# svc:/application/virtuo/tcr1-na:na# svc:/application/virtuo/tcr2-na:na

Sample output:svc:/application/virtuo/sap-na:na (Virtuo SAP server instance na)

State: online since Fri Oct 17 15:24:06 2011

See: /var/svc/log/application-virtuo-sap-na:na.log

Impact: None.

svc:/application/virtuo/sapmgr-na:na (Virtuo SAP manager instancena)


See: /var/svc/log/application-virtuo-sapmgr-na:na.log

Impact: None.

svc:/application/virtuo/sapmon-na:na (Virtuo SAP monitor instancena)


See: /var/svc/log/application-virtuo-sapmon-na:na.log

Impact: None.

svc:/application/virtuo/tds-na:na(PMW TDS instance na)


See: /var/svc/log/application-virtuo-tds-na:na.log

Impact: None.

svc:/application/virtuo/database-na:global (NetworkAssure Databaseinstance)


See: /var/svc/log/application-virtuo-database-na:global.log

Impact: None.

A status check can be run individually on each of the system's applications, thedirectory server, and the database.

For example:svcs -x /application/virtuo/sap-na

svcs -x /application/virtuo/database-na

svc:/application/virtuo/tcr1-na:na (PMW TCR instance na)State: online since Mon Oct 03 20:14:36 2011See: /var/svc/log/application-virtuo-tcr1-na:na.logImpact: None.


Process checks for Linux

Check that all Tivoli Netcool Performance Manager processes have startedsuccessfully for the Linux operating system.

Pass the status command to the init.d services, as user root:service dboravirtuo statusservice tdsna statusservice sapmonvirtuo statusservice sapmgrvirtuo statusservice sapvirtuo statusservice tcr1na status

Sample output:# service dboravirtuo statusDatabase listener is running.Database instance vtdb is running.

# service tdsna statusTDS LDAP server is runningTDS admin server is running

# service sapmonvirtuo statussapmon process running

# service sapmgrvirtuo statussapmgr process running

# service sapvirtuo statusNAME STATE SINCEas STARTED 17:21:28asd STARTED 17:25:04nc_cache STARTED 17:25:51alarm_cache STARTED 17:26:34load_ericssonbss_r10 STARTED 17:26:39load_nokiabss_oss31ed3 STARTED 17:26:44load_motorolabss_gsr7 STARTED 17:26:49load_motorolautran_usr10 STARTED 17:26:54load_ericssonutran_r30 STARTED 17:26:59

Process checks for AIX

Run process checks to ensure that the processes are running correctly.

On AIX, run the following commands to check the status of processes:/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/tdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status/etc/rc.d/init.d/tcr1virtuo status

Note: Separate services are installed for each instance of Tivoli Common Reportingyou have installed on each server. Therefore, if you have installed two instances ofTivoli Common Reporting on a server, enter the following commands to check thestatus of their services:


/etc/rc.d/init.d/tcr1virtuo status/etc/rc.d/init.d/tcr2virtuo status

Sample output:# /etc/rc.d/init.d/dboravirtuo statusDatabase listener is running.Database instance vtdb is running.

# /etc/rc.d/init.d/tdsna statusTDS LDAP server is runningTDS admin server is running

# /etc/rc.d/init.d/sapmonvirtuo statussapmon process running

# /etc/rc.d/init.d/sapmgrvirtuo statussapmgr process running

# /etc/rc.d/init.d/sapvirtuo status

............

............

NAME STATE SINCEas STARTED Oct 08, 2010asd STARTED Oct 08, 2010nc_cache STARTED Oct 08, 2010alarm_cache STARTED Oct 08, 2010load_erics_r10 STARTED Oct 08, 2010load_nok_oss31ed3 STARTED Oct 08, 2010load_motor_gsr7 STARTED Oct 08, 2010load_erics_r30 STARTED Oct 08, 2010

SAP process checkCheck that the Tivoli Netcool Performance Manager framework is started.

About this task

Process log files can be found in the location given by the value for WMCLOGDIR inthe $WMCROOT/conf/environment/default.properties file. Ensure that no exceptionshave occurred in these files. If the process has started successfully each process logfile returns a message indicating that the process started successfully.

Procedure

Run the commands as user virtuo on the Tivoli Netcool Performance Managerserver:sap disp

The status of each process displays.Start any process that has not started, as user virtuo:

stap start <process>


Rebooting the serverYou must reboot each server to ensure all of the processes start automatically andcorrectly.

About this task

Important: In a distributed installation, reboot each of the Tivoli NetcoolPerformance Manager servers in the following order:1. Database server2. Directory server3. Application server4. Loader servers

If any process is in a disabled state, it will not start automatically on reboot. If anySolaris SMF service is in a disabled state, it will not start automatically on reboot.

Procedure1. Check that all of the processes are running, see Process checks.2. Run the following command as user root on the server:

v

shutdown -Fr

v

/usr/sbin/shutdown -i6 -g0 -y

v

shutdown -r now

Tivoli Netcool Performance Manager core processes stop/startThe Tivoli Netcool Performance Manager core processes have a stop/start function

About this task

Stop the core framework:

Procedure1. Executing the commands as user virtuo on the Tivoli Netcool Performance

Manager server:sap stop

2. Enter y to the prompt:Stop all registered processes [y/n]?

3. Restart the framework, as user virtuo on the Tivoli Netcool PerformanceManager server:sap start as


Starting the loadersEach installed loader must be started for the upgrade to take effect.

Procedure

For each installed loader execute the command, as user virtuo:sap start <loadername>

Where <loadername> is the name of the installed loader.

Populating wireless data after upgradeThis step is required only if cognos enablement or common pack service wasinstalled on the previous version of Tivoli Netcool Performance Manager, that is,Tivoli Netcool Performance Manager 1.3.1; otherwise, user can skip this task.

To populate the wireless data, wireless users must run the commands specified in“Wireless Component only: Populating the database schema tables” beforeproceeding.

Wireless Component only: Populating the database schematables

Wireless users must populate the database schema tables by using the CommonPack Service pack_admin command.

Before you begin

When a parameter includes spaces, enclose the complete parameter in doublequotation marks or escape the parameter.

About this task

Typically, the data-refill action is run once when you deploy a pack. You use thedata-refill action to populate the database schema tables. The data-refill actionis defined in all common packs except tcr.time. The data-refill action populatesthe hierarchy tables on which the Cognos data models depend. The data-refillaction cleans out and fully populates the DM tables.

Procedure1. Log in to the Tivoli Common Reporting server.2. Change to the following directory:

$TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin

Where:TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated PortalComponents are installed. By default, /opt/IBM/tivoli/tipv2Components.

3. Populate schema tables in all Base Common Pack (BCP) and Vendor-Specificcommon packs by entering the following command:./pack_admin.sh -execute -action data-refill -logins ./logins.txt

Where:logins.txt is the logins file that you created in a previous task, see “Creating alogins file with the appropriate passwords” on page 66


Common Pack Service is processing request.CTGTRQ005I The operation executeAction successfully performed.

The data-refill action is defined in all Base Common Pack (BCP) andvendor-specific common packs.

Creating a logins file with the appropriate passwordsYou must create a logins file containing certain passwords that are required by thepack_admin command and Model Maker Manager for authentication purposes. Foryour security, please change the default passwords provided during installation. Ifyou update any of the passwords, ensure that you update the credentials file, orthe tcraccess data source, as appropriate.

Before you begin

The following passwords are required:

tipadminThe default Tivoli Integrated Portal administrator user.

bicontrolA control user that you must create on the database before running theinstaller.

birefreshThe birefresh user is created by the Common Pack Service Installer andhas a default password of birefresh.

About this task

The pack_admin command automatically encrypts the passwords when creating thelogins file.

For instructions on changing Oracle user or schema passwords, seehttp://www.orafaq.com/wiki/Oracle_database_Security_FAQ#How_does_one_change_an_Oracle_user.27s_password.3F.

If you change the Oracle tcraccess user password, then you must also change theCognos tcraccess data source.

If you change the Oracle bicontrol or birefresh user passwords, or the TivoliIntegrated Portal tipadmin user password, you must recreate the logins file withthe new credentials. The old logins file is no longer valid.

Procedure1. On the Tivoli Common Reporting server, change to the

$TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin directory.Where TIP_COMPONENTS_LOCATION is the location where the Tivoli IntegratedPortal Components were installed. By default, /opt/IBM/tivoli/tip21Components for wireline and /opt/IBM/tivoli/tipv2Components forwireless.

2. Enter the following command on one line and provide the passwords whenprompted:# ./pack_admin.sh -passwordfile ./logins.txt -tipuser tipadmin-dbusers tnpm:bicontrol tnpm:birefresh

BI Service Service is processing request.Please enter the password for user bicontrol:


http://www.orafaq.com/wiki/Oracle_database_Security_FAQ#How_does_one_change_an_Oracle_user.27s_password.3F

http://www.orafaq.com/wiki/Oracle_database_Security_FAQ#How_does_one_change_an_Oracle_user.27s_password.3F

bicontrol#]Please re-enter the password for user bicontrol:

bicontrolPlease re-enter the password for user bicontrol:

bicontrolPlease enter the password for user birefresh:

birefreshPlease re-enter the password for user birefresh:

birefreshPlease enter the password for user tipadmin:

tipadminPlease re-enter the password for user tipadmin:

tipadminThe following file was created: logins.txtCTGTRR205I The operation createLoginsFile successfully performed.

3. Optional: To see the contents of the logins.txt file, enter the followingcommand:# cat logins.txtTARGET tnpm bicontrol 6439448205275568047254553497058697800TARGET tnpm birefresh 22726015774105630813618842664095311722TIPUSER - tipadmin -89496516100624695361961177712212346580

The passwords have been encrypted for security.


Chapter 4. Enabling Tivoli Common Reporting on TivoliNetcool Performance Manager

Once you have upgraded the core system, install the latest version of Model Makertooling to enable Common Reporting on Tivoli Netcool Performance Manager.

If you have previously used the Model Maker tooling with your Tivoli NetcoolPerformance Manager 1.3.1 system, you must upgrade to the latest version.

For more information about installing or upgrading Model Maker IBM CognosEdition, see the latest versions of the following guides:v IBM Tivoli Netcool Performance Manager: Model Maker IBM Cognos Edition

Installation and User Guide

v IBM Tivoli Netcool Performance Manager Installation Guide - Wireless Component,Chapter 11. Enabling Common Reporting on Tivoli Netcool PerformanceManager.


Chapter 5. Rolling back to the previous Tivoli NetcoolPerformance Manager version

During the Oracle 11g database upgrade trial period, if the application's stability orperformance is negatively impacted, you can revert to Tivoli Netcool PerformanceManager Version 1.3.1 and downgrade the database to Oracle Server Version 10.2.

To reduce the application downtime required to roll back the database to theprevious version, Oracle provides a database downgrade procedure used by TivoliNetcool Performance Manager rollback routine that is outlined in the next sections.

Note: The procedure is applicable only if the database upgrade was notcommitted, making such changes as described in “Finalize the database upgrade”on page 87 and all directories and files in Oracle 10g home directory before the 11gupgrade was started are available.

The Tivoli Netcool Performance Manager downgrade consists of two steps.1. Downgrade the database to version 10.2 or restore the database from a database

backup taken before the upgrade.2. Restore Tivoli Netcool Performance Manager Version 1.3.1 from an archive

created during the application upgrade.

The exact database restore procedure from the full pre-upgrade database backupdepends on your backup environment and is not described in this guide.

Stopping Tivoli Netcool Performance Manager clientsAll clients should be notified that a rollback is taking place and all clients shouldbe stopped before continuing with the rollback.

Stopping the Tivoli Netcool Performance Manager frameworkRun the required CLI commands to stop and to monitor the process state of theTivoli Netcool Performance Manager framework.

About this task


Procedure1. Run the following command as user virtuo:

sap stop -f


v svcs sap-na




Stopping the SAP managerStopping the SAP manager and confirming that it is stopped.

About this task







v svcs sapmgr-na



Stopping the SAP monitorStopping and monitoring the SAP monitor for the application and loader serveronly.

About this task

Note: In a distributed installation, this procedure must be performed for theapplication and loader server only.







v svcs sapmon-na




Stopping Tivoli Common ReportingAbout this task

To stop the Tivoli Common Reporting:

Procedure


v svcadm disable tcr1-na

v /etc/rc.d/init.d/tcr1virtuo stop

v service tcr1na stop

Rollback Tivoli Directory Server and DB2Use this procedure to roll back the Tivoli Directory Server and DB2 software to theprevious supported versions (Tivoli Directory Server 6.2 and DB2 9.5). Thisprocedure can only be used if the previous software is still installed on the server.

Procedure1. Run the command as userroot :

# /var/install/sbin/tds_install -base <target directory> -product virtuo -version6.2 -rollback

2. At the prompts, enter and confirm the password for the DB2 Administrator(idsinst user).Please, enter the DB2 Administrator (idsinst user) password:[] ---->Please, enter the DB2 Administrator (idsinst user) password a second time:[] ---->

3. Enter the remaining information requested by the script. The defaults can beused.Please, Enter the LDAP instance location: [/appl/ldap]---->Instance location set to /appl/ldapPlease, Enter the encryption seed (12 digits): [158004832289]---->Encryption seed set to 158004832289Please, Enter the LDAP Administrator DN: [cn=Directory Manager]---->Administrator DN set to cn=Directory ManagerPlease, Enter the LDAP Administrator password: [Dirmgr01]---->Administrator password set to Dirmgr01Please, Enter the LDAP port number: [1389]---->Port number set to 1389Please, Enter the LDAP secure port number: [1636]---->

Chapter 5. Rolling back to the previous Tivoli Netcool Performance Manager version 73

Secure port number set to 1636Please, Enter the DB2 database name: [idsdb]---->The script proceeds to drop the current Tivoli Directory Server DB2 instance,recreates the instance with the previous version, and removes the TivoliDirectory Server 6.3 and DB2 9.7 software.

Stopping the directory serverStop the server acting as the directory server.

About this task

Note: In a distributed installation, this procedure must be performed on the serveracting as the directory server. This can be the application server or a separatedirectory server.

Stop the directory server.

Procedure


v svcadm disable tds-na

v service tdsna stop

v /etc/rc.d/init.d/tdsna stop

Downgrade the database versionDowngrade the database version on the stand-alone server, or in a distributedinstallation, on the database server only.

Getting started with database downgradeAbout this task

Before starting database downgrade, ensure that all application services are down,and then start database instance only.

Procedure1. To check that all application services are down, follow these commands:

v

AIX/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/tdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status/etc/rc.d/init.d/tcr1virtuo status/etc/rc.d/init.d/tcr1virtuo status

v

Linux


service sapvirtuo statusservice sapmgrvirtuo statusservice sapmonvirtuo statusservice tdsna statusservice dboravirtuo statusservice tcr1na status

v

Solarissvcs sap-nasvcs sapmgr-nasvcs sapmon-nasvcs database-nasvcs tds-nasvcs tcr1-na

2. When all application services are offline, start database service only. To do this,follow these commands:

v /etc/rc.d/init.d/dboravirtuo start

v service dboravirtuo start

v svcadm enable database-na

Wait till the database instance is started completely. For large implementations,the start up might take up to 20 minutes.

Testing the database connectionEnsure that you can reach the Tivoli Netcool Performance Manager database froma SQL*Plus CLI before starting a database downgrade.

Procedure1. To test the connection, enter the following command:

$ sqlplus virtuo/<virtuo PASSWORD>@<DB name>

2. If a connection can be established, proceed to downgrade the database.

Rolling back the databaseThe total database downgrade time depends on the hardware resources andgenerally takes about 2-3 hours.

Procedure1. As the root user, change to the following directory:

cd <WMCROOT>/admin/oracle/install/scripts

Where <WMCROOT> is the directory where the Tivoli Netcool PerformanceManager software is installed.

2. Run Tivoli Netcool Performance Manager database downgrade script:ksh ./database_downgrade -wmcr <WMCROOT>

3. Enter values at the prompts or accept the defaults.Please enter the Database SID: [vtdb]Database SID set to "vtdb"Please enter the Oracle 10g Home[/appl/oracle/product/10.2.0/db_1]Oracle 10g home is set to "/appl/oracle/product/10.2.0/db_1"Please enter the Oracle 11g home:[/appl/orace/product/11.2.0/db_1]---------------------------------/appl/orace/product/11.2.0/db_1Oracle 11g home is set to: "/appl/oracle/product/11.2.0/db_1"


Please enter the Database sys user password: [Sysdb01]Database user sys password set to: "Sysdb01"Please enter the Database system user password: [Sysdb01]Database user system password is set to: "Sysdb01"

4. The script validates if all conditions required to downgrade databases are met.If the script returns a message that invalid database objects or componentswere found, see “Resolving invalid database objects or components.”

5. When the database downgrade is completed, review the log files and addressany noted issues before continuing.

6. Modify the $HOME/.profile files for the oracle and virtuo users on all TivoliNetcool Performance Manager servers to remove all references to Oracle 11g.

Resolving invalid database objects or componentsThe database downgrade script validates if all conditions required to downgradedatabases are met. If the script returns a message that invalid database objects orcomponents were found and stops, then you must take the appropriate correctiveactions.

Procedure1. Generate a database status report as described in checking the database status.2. Send the generated report to IBM support for review.3. In some circumstances, and only with the previous approval of IBM support,

you can force the script to continue the database downgrade even if someobjects or components are in an invalid state. In this case, the command-lineswitch - force can be used.

Restore old previous version of softwarePrevious versions must be restored on all Tivoli Netcool Performance Managerservers.

About this task

Note: Distributed system only. On a distributed installation, this section must beperformed on all the Tivoli Netcool Performance Manager servers.

To restore the previous version of the software:

Procedure

As user root on the Tivoli Netcool Performance Manager server execute thecommands:/var/install/sbin/archive_release -wmcr <wmcroot> -productvirtuo -restore

The output is displayed:Process sap is not running

Process sap is not running

Process sapmgr is not running

Process database is not running

Previous release is PMW1.3.1.0.4

Backing up current release to/appl/archive/virtuo.PMW1.3.1.0.4......done


Starting tds...done

Restoring package files from/appl/archive/software.PMW1.3.1.0.4......done

Restoring user cron jobs......done

Restarting Cron ...

Stopping crond: [ OK ]

.... cron daemon stopped

Starting crond: [ OK ]

.... cron daemon started

Restoring user profiles......done

Starting database...done

Restoring release PMW1.3.1.0.4 complete

Process checksCheck all services and processes to ensure that they are running.

About this task

Note: In a distributed installation, this section must be performed for all the TivoliNetcool Performance Manager servers.

If some services or processes are not running, start them manually. Processes canbe checked using “Process status checks” on page 78.

To start processes manually:

Procedure1. Run the commands as user root:

Solarissvcadm enable tds-na

svcadm enable database-na

svcadm enable sapmon-na

svcadm enable sapmgr-na

svcadm enable sap-na

Linuxservice tdsna start

service dboravirtuo start

service sapmonvirtuo start

service sapmgrvirtuo start

2. Run the commands as virtuo:

sap start

3. Verify that all the processes have started successfully:sap disp

AIX/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/tdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status


Process status checksCheck processes using process status checks if some services or processes are notrunning.

About this task

Solaris

A single command can be used to check the status of the system, as user root:svcs -x appli*/virtuo*

v Sample output:svc:/application/virtuo/sap-na:na (Virtuo SAP server instance na)


See: /var/svc/log/application-virtuo-sap-na:na.log

Impact: None.

svc:/application/virtuo/sapmgr-na:na (Virtuo SAP manager instance na)


See: /var/svc/log/application-virtuo-sapmgr-na:na.log

Impact: None.

svc:/application/virtuo/sapmon-na:na (Virtuo SAP monitor instance na)


See: /var/svc/log/application-virtuo-sapmon-na:na.log

Impact: None.

svc:/application/virtuo/tds-na:na (PMW TDS instance na)


See: /var/svc/log/application-virtuo-tds-na:na.log

Impact: None.

svc:/application/virtuo/database-na:global (NetworkAssure Database instance)


See: /var/svc/log/application-virtuo-database-na:global.log

Impact: None.

A status check can be run individually for each of the system's applications, thedirectory server, and the database. For example:svcs -x /application/virtuo/sap-na

svcs -x /application/virtuo/database-na

Linux

Pass the status command to the init.d services , as user root:service dboravirtuo status

service tdsna status

service sapmonvirtuo status

service sapmgrvirtuo status

service sapvirtuo status

Sample output:# service dboravirtuo status

Database listener is running.


Database instance vtdb is running.

# service tdsna status

TDS LDAP server is running

TDS admin server is running

# service sapmonvirtuo status

sapmon process running

# service sapmgrvirtuo status

sapmgr process running

# service sapvirtuo status

NAME STATE SINCE

as STARTED 17:21:28

asd STARTED 17:25:04

nc_cache STARTED 17:25:51

alarm_cache STARTED 17:26:34

load_ericssonbss_r10 STARTED 17:26:39

load_nokiabss_oss31ed3 STARTED 17:26:44

load_motorolabss_gsr7 STARTED 17:26:49

load_motorolautran_usr10 STARTED 17:26:54

load_ericssonutran_r30 STARTED 17:26:59

AIX/etc/rc.d/init.d/dboravirtuo status/etc/rc.d/init.d/tdsna status/etc/rc.d/init.d/sapmonvirtuo status/etc/rc.d/init.d/sapmgrvirtuo status/etc/rc.d/init.d/sapvirtuo status

Sample output:# /etc/rc.d/init.d/dboravirtuo statusDatabase listener is running.Database instance vtdb is running.

# /etc/rc.d/init.d/tdsna statusTDS LDAP server is runningTDS admin server is running

# /etc/rc.d/init.d/sapmonvirtuo statussapmon process running

# /etc/rc.d/init.d/sapmgrvirtuo statussapmgr process running

# /etc/rc.d/init.d/sapvirtuo status

............

............

NAME STATE SINCEas STARTED Oct 08, 2010asd STARTED Oct 08, 2010nc_cache STARTED Oct 08, 2010alarm_cache STARTED Oct 08, 2010load_erics_r10 STARTED Oct 08, 2010load_nok_oss31ed3 STARTED Oct 08, 2010load_motor_gsr7 STARTED Oct 08, 2010load_erics_r30 STARTED Oct 08, 2010


Tivoli Netcool Performance Manager core processes checkCheck the status of the Tivoli Netcool Performance Manager core processes.

About this task


Procedure

Run the commands as user virtuo:

sap disp

The status of each process displays.Process log files can be found in the location set by the WMCLOGDIR value in the$WMCROOT/conf/environment/default.properties file.Ensure that no exceptions have occurred in these files. If the process has startedsuccessfully each process log file should return the line Process Startup donewhen it has started successfully.

Stop and start the Tivoli Netcool Performance Manager coreprocesses

The Tivoli Netcool Performance Manager core processes have a stop/start function

About this task

Note: In a distributed installation, this section must be performed for theapplication server only.

Stop the Tivoli Netcool Performance Manager for Wireless framework.

Procedure1. Run the commands as user virtuo:

sap stop

2. Restart the framework by executing the command as user virtuo on the TivoliNetcool Performance Manager for Wireless server:sap start as

What to do next

Tivoli Netcool Performance Manager rollback requires that you edit thestartTCRserver.sh script and then use it to start Tivoli Common Reporting.1. Edit the Tivoli Common Reporting startup script located at /opt/IBM/tivoli/

tipv2Components/TCRComponent/bin/startTCRServer.sh so that the$ORACLE_HOME parameter to points to the Oracle 10g home directory.

2. Ensure the environment variables for each user on each server in the systemare changed to use oracle 10.a. Use the command env | grep 11 to show any environment variables that

point to oracle 11.b. Update the user's $HOME/.profile then log out and log back in.c. Run env | grep 11 again just to be sure there are no references to oracle 11.

3. Restart of Tivoli Common Reporting is performed using the command:


<tipComponents>/TCRComponent/bin/startTCRserver.sh <username> <password>

Where:v user: the Tivoli Integrated Portal administrator name.v password: the Tivoli Integrated Portal administrator password.For example:/opt/IBM/tivoli/tip2Components/TCRComponent/bin/startTCRserver.sh tipadmin tipadmin

Start the Tivoli Netcool Performance Manager cron jobsStart all of the Tivoli Netcool Performance Manager cron jobs previously stoppedon each server.

About this task

For more information on stopping the cron jobs, see “Stopping the Tivoli NetcoolPerformance Manager cron jobs” on page 10.To edit the crontab directly, the files to modify are:

Procedure1. Edit the following files:



v /var/spool/cron/virtuo

2. Enable all those cron jobs that are commented out.3. Restart the cron daemons:

v

ps -ef | egrep [c]ron | awk ’{ print $2 }’ | xargs kill

v

svcadm restart cron

v

service crond restart


Chapter 6. Removing the previous Tivoli Directory Server andIBM DB2 Version

Remove the Tivoli Directory Server and DB2 versions from the system after theupgrade once it is confirmed that a rollback is not necessary.

About this task

Note: This step shuts down the Tivoli Directory Server service on the server. Theservice must be restarted once the procedure is complete. Ensure that users do notneed to access the system during this procedure.


# /var/install/sbin/tds_install -base <target directory> -product virtuo -version 6.2 -remove

The script proceeds to shut down the Tivoli Directory Server service andremove the previous versions of the Tivoli Directory Server and DB2 software.

2. Restart the Tivoli Directory Server service as userroot:

v #svcadm enable tds-na

v #service tdsna start

v #/etc/rc.d/init.d/tdsna start

Results

If you see an error such as the following:ERROR: Failed to remove DB2

Check the Tivoli Directory Server install log in /var/install/logs for errors. Also,check the DB2 uninstall log /tmp/db_deinstall.log.<pid>, where <pid> is theprocess ID of the uninstall process. Return these logs to IBM Tivoli support foranalysis.

You can manually remove the old version of DB2 from the system by running thefollowing command as root:<DB2_install_dir>/install/db2_deinstall -a

Where <DB2_install_dir> is the location of the previous version of DB2, forexample, /opt/IBM/tdsdb29.5.


Chapter 7. Complete the Oracle 11g upgrade

Once the Oracle 11g upgrade trial period (recommended minimum is 2 weeks) hascompleted, you can decide to commit the Oracle 11g upgrade or to downgrade thedatabase to the previous version.

Process checksTo perform process checks access the Oracle 11g system.

To assess the Oracle 11g system, you can:v Review log messages stored in the Oracle Database Diagnostic repository.v Compare application and system performance metrics with baseline metrics

from the previous system.

If system is stable and performing well, then proceed to the next step to finalizeupgrade. Otherwise consider extending the upgrade trial period or reverting to thepre-upgrade configuration.

Finalizing the Database Upgrade - Phase 2It is necessary to finalize the database upgrade.

Stop all application servicesComplete the following tasks to stop all application services.

Stopping the application server and loadersStop the application server and loader for the application server only.

About this task

Note: In a distributed installation, this section must be performed for theapplication server only.

To stop the application server and loaders, execute the commands as user virtuo:

Procedure1. Stop the processes:

sap stop -f

2. Check that all the processes are stopped:sap disp


Stopping the Tivoli Netcool Performance Manager frameworkStop and monitor the Tivoli Netcool Performance Manager framework.

About this task


To stop the Tivoli Netcool Performance Manager framework:


v svcadm disable sap-na

v service sapvirtuo stop

v /etc/rc.d/init.d/sapvirtuo stop


v svcs sap-na



Stopping the SAP managerStop the SAP manager and monitor the process state.

About this task


To stop the SAP manager:






v svcs sapmgr-na




Stopping the SAP monitorStop the SAP monitor and monitor the process state.

About this task

Note: In a distributed installation, this procedure must be performed for theapplication and loader servers only.







v svcs sapmon-na



Finalize the database upgradeCheck to ensure that the database upgrade is finalized.

Procedure1. As database owner check that database instance is running and you can log in:

$sqlplus virtuo/<virtuo PASSWORD>@<DB name>

2. Update database configuration and restart database:$ export ORACLE_SID=<DB name>

$sqlplus ’/ as sysdba’

3. Create a backup copy of PFILE from existing SPFILE:SQL> CREATE PFILE FROM SPFILE;

4. Alter the system to change the COMPATIBLE parameters to 11.2.0 in spfile:SQL> ALTER SYSTEM SET compatible="11.2.0" SCOPE=spfile;

5. Stop the database:SQL> SHUTDOWN IMMEDIATE

6. Start the database and exit SQL*Plus:SQL> STARTUP

SQL> SHOW PARAMETER compatible

SQL> EXIT

Chapter 7. Complete the Oracle 11g upgrade 87

Restarting the databaseIn a distributed installation, this procedure must be performed for the databaseserver only.

About this task

Use the command to verify if the database is running or not:

svcs database-na

service dboravirtuo status

/etc/rc.d/init.d/dboravirtuo status

To restart the database:

Procedure


v Stop a database service:svcadm disable database-na


Start a database instance:svcadm enable database-na

v Stop a database service:service dboravirtuo stop


Start a database instance:service dboravirtuo start

v Stop a database service:/etc/rc.d/init.d/dboravirtuo stop


Start a database instance:/etc/rc.d/init.d/dboravirtuo start


Starting the remaining processesStart all application services by starting the framework on the Tivoli NetcoolPerformance Manager server.

Before you beginv Start the SAP Manager by giving the following command as user root:

service sapmgrvirtuo start

v Start the SAP Monitor by giving the following command as user root:service sapmonvirtuo start

About this task


If some services or processes are not running, start them manually. For moreinformation, see “Process checks” on page 77.

Procedure1. Start the tcr1 process by giving the following command:

v svcadm enable tcr1-na

v /etc/rc.d/init.d/tcr1virtuo start

v

2. Start the framework by executing the command as user virtuo on the TivoliNetcool Performance Manager server:sap start as

Chapter 7. Complete the Oracle 11g upgrade 89

Chapter 8. Troubleshooting tasks

Some troubleshooting tasks in Tivoli Netcool Performance Manager are describedhere.

After upgrading Tivoli Common Reporting, it is not possible to log intoTivoli Integrated Portal

Symptoms

After upgrading Tivoli Common Reporting, it is not possible to log into TivoliIntegrated Portal.

Resolving the problem

After upgrade of Tivoli Common Reporting, if you are experiencing problemslogging into Tivoli Integrated Portal, do the following you need to and :

User response:

1. Clear your Browser cache for the Tivoli Integrated Portal serverFor example:v In Firefox (v3.6):

a. Click Tools > Options > Privacy

b. Remove individual cookies.c. Search using your Tivoli Integrated Portal server name and remove those

cookies.2. Restart your browser.3. log in to Tivoli Integrated Portal.

When Tivoli Common Reporting upgrade fails, the installation cannotbe rerun

Symptoms

If the Tivoli Common Reporting upgrade or installation fails on the system forsome reason, it is not possible to reinstall. If you rerun the pmw_install command,you might receive an error message as follows:No packages to install

Causes

This issue occurs because Tivoli Common Reporting is installed by the core TivoliCommon Reporting package. If Tivoli Common Reporting installation fails, theTivoli Common Reporting package is still on the system. When you try to reinstallby using pmw_install command, you might not be able to reinstall the TivoliCommon Reporting package.

Resolving the problem


To workaround this issue, manually remove the Tivoli Common Reporting packagebefore you rerun the installation or upgrade. To do this, follow these steps:

User response:

1. As root user, run the following command to remove the Tivoli CommonReporting package:$WMCROOT/admin/software/core/vallent-vt-tcr.remove now

2. Rerun pmw_install command to install the Tivoli Common Reporting package.


Appendix. Dependency Checker errors

This appendix shows the Dependency Checker errors.GYMWI0001E Directories missing from root user PATHThe following directories are missing from the root user PATH: <missing_dirs>

You must ensure that the root user profile is sourced before runningthe installation.Hint: If you use ’su’ to change to the root user, use the ’-’argument to source the profile, i.e. ’su -’

-------------------------------------------------------------GYMWI0002E No domain name configuredYou must set up a domain name on the server and ensure the fullyqualified hostname is valid-------------------------------------------------------------GYMWI0003E Hostname <FQDN> resolves to loopback IP address x.x.x.x -must be a real IP addressThe server hostname must resolve to a non-loopback IP address.Otherwise the alarms UI will not function correctly.-------------------------------------------------------------GYMWI0004E Hosts entry for <FQDN> not found

-------------------------------------------------------------GYMWI0054E Invalid umask for root user: 022The umask for the root user must be set to 0022-------------------------------------------------------------GYMWI0005E OS <OS> is not supported. Must be one of: Linux SunOSOnly Linux and SunOS (Solaris) are supported-------------------------------------------------------------GYMWI0006E SunOS version <OS_VER> is not supported. Must be 5.10Solaris 10 is the only supported version-------------------------------------------------------------GYMWI0007E Processor type <PROC_TYPE> is not supported for <OS>Solaris is only supported on SPARC processors-------------------------------------------------------------GYMWI0008E Platform must support 64-bit kernel

-------------------------------------------------------------GYMWI0009E Unable to determine release level for <OS>

-------------------------------------------------------------GYMWI0010E Unable to determine release level for <OS> from HW_REL: <HW_REL>

-------------------------------------------------------------GYMWI0011E HW_REL for <OS> is <HW_REL>: Required level is 8/07You must install the latest recommended patch cluster-------------------------------------------------------------GYMWI0012E Processor type <PROC_TYPE> is not supported for <OS>SunOS is only supported on x86_64 architecture-------------------------------------------------------------GYMWI0013E Linux distribution must be Red Hat

-------------------------------------------------------------GYMWI0014E Linux distribution must be Red Hat Enterprise Linux Server

-------------------------------------------------------------GYMWI0015E Red Hat Release <RHEL_VERSION> is not supported: must be 5.1 or later

-------------------------------------------------------------GYMWI0016E <dir> is not a directory

-------------------------------------------------------------GYMWI0017E Insufficient space on <fs> partition.


Space required on this partition: KBSpace available: KBThe following required directories are mounted on this partition:

-------------------------------------------------------------GYMWI0018E One or more required <OS> packages not installedMissing packages:-------------------------------------------------------------GYMWI0019E ERROR: invalid argument to linux_pkg_checks():

-------------------------------------------------------------GYMWI0049E ERROR: invalid format for package info: <pkg>

-------------------------------------------------------------GYMWI0050E ERROR: incomplete package information: <pkg>

-------------------------------------------------------------GYMWI0051E ERROR: invalid package version for <pkg>:

-------------------------------------------------------------GYMWI0052E ERROR: invalid package release for <pkg>:

-------------------------------------------------------------GYMWI0020E <tpp_type> <OS> packages are missing

-------------------------------------------------------------GYMWI0021E <tpp_type> <OS> packages require upgrade

-------------------------------------------------------------GYMWI0022E User oracle shell <ORACLE_USER_SHELL> is not supported:must be /bin/ksh

-------------------------------------------------------------GYMWI0055E Invalid oracle user umask: <ORACLE_USER_UMASK>The oracle user umask must be set to 022-------------------------------------------------------------GYMWI0023E ORACLE_BASE environment variable not set

-------------------------------------------------------------GYMWI0024E ORACLE_BASE directory /appl/oracle does not exist

-------------------------------------------------------------GYMWI0025E ORACLE_OWNER: <ORACLE_OWNER> is expected to be oracle

-------------------------------------------------------------GYMWI0026E ORACLE_HOME environment variable not set

-------------------------------------------------------------GYMWI0027E ORACLE_HOME directory ${ORACLE_HOME} does not exist

-------------------------------------------------------------GYMWI0028E PATH for oracle does not contain ${ORACLE_HOME}/bin

-------------------------------------------------------------GYMWI0029E LD_LIBRARY_PATH for oracle does not contain ${ORACLE_HOME}/lib

-------------------------------------------------------------GYMWI0030E NLS_LANG environment variable for oracle user must be set to_.WE8ISO8859P1

-------------------------------------------------------------GYMWI0031E Installed Oracle version is invalid

-------------------------------------------------------------GYMWI0032E Oracle oneoff patches not installedThe following oneoff Oracle patches are missing:-------------------------------------------------------------GYMWI0033E Oracle Partitioning is not installed


-------------------------------------------------------------GYMWI0034E ${dir} does not exist

-------------------------------------------------------------GYMWI0035E ${dir} must be owned by oracle

-------------------------------------------------------------GYMWI0036E ${dir} must be executable by owner oracle

-------------------------------------------------------------GYMWI0037E ${dir} must be executable for non-oracle users

-------------------------------------------------------------GYMWI0038E ${binary} does not exist

-------------------------------------------------------------GYMWI0039E ${binary} must be owned by oracle

-------------------------------------------------------------GYMWI0040E ${binary} must be executable by owner oracle

-------------------------------------------------------------GYMWI0041E ${binary} must be executable for non-oracle users

-------------------------------------------------------------GYMWI0042E ${ORACLE_HOME}/network/admin/${ora_file} must be owned by oracle

-------------------------------------------------------------GYMWI0043E ${ora_file} must be writable by owner oracle

-------------------------------------------------------------GYMWI0044E ${ora_file} must be readable for non-oracle users

-------------------------------------------------------------GYMWI0045E ${ORACLE_HOME}/network/admin/${ora_file} must be an empty fileDB creation may fail if this file has invalid contents.-------------------------------------------------------------GYMWI0046E ${pkg_count} versions of ${_core_pkg} foundThere can only be 1 version of each package in ${_pkg_dir}-------------------------------------------------------------GYMWI0047E TNPM core packages not foundThe following core packages could not be found: ${missing_pkgs}-------------------------------------------------------------GYMWI0053E JBoss archive not foundThe JBoss 4.0.3 SP1 package should be located in ${BASE_DIR}-------------------------------------------------------------GYMWI0046E ${pkg_count} versions foundThere can only be 1 version of each package in ${_pkg_dir}-------------------------------------------------------------GYMWI0048E TDS/DB2 packages not foundThe following TDS/DB2 packages could not be found:-------------------------------------------------------------

Appendix. Dependency Checker errors 95

Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM‘s application programming interfaces.


If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Notices 99

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at http://www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony ComputerEntertainment, Inc., in the United States, other countries, or both and is used underlicense therefrom.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries,or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

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

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

Other company, product, and service names may be trademarks or service marksof others.

For trademark attribution, visit the IBM Terms of Use Web site:http://www.ibm.com/legal/us/.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/us/

��

Printed in USA

ibm tivoli netcool performance manager: upgrade guide · stopping the sap monitor ... netcool...

Documents