IBM Tivoli Netcool Performance Manager: Upgrade Guide: 4.4.1 to 1.3 · · 2011-01-14Tivoli ® Netcool Performance Manager 1.3.1 Wireline Component ... Chapter 1. Introduction

Tivoli® Netcool Performance Manager 1.3.1Wireline ComponentDocument Revision R2E1

Upgrade GuideTivoli Netcool Performance Manager4.4.1 to 1.3.1

��

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

© Copyright IBM Corporation 2006, 2011.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 productsuite . . . . . . . . . . . . . . . . . v

Chapter 1. Introduction . . . . . . . . 1Summary of upgrade tasks . . . . . . . . . 1Verifying your Tivoli Netcool Performance Managerenvironment . . . . . . . . . . . . . . 2

Supported upgrade paths for Tivoli NetcoolPerformance Manager . . . . . . . . . . 2Supported platforms. . . . . . . . . . . 3Supported topology . . . . . . . . . . . 4

Chapter 2. Patch Tivoli NetcoolPerformance Manager to 4.4.1.4 . . . . 5Check your system versioning . . . . . . . . 5Install fixpack 4.4.1.0-TIV-PROV-FP0004 . . . . . 6

Chapter 3. Upgrading Solaris 9 toSolaris 10 . . . . . . . . . . . . . . 9Solaris upgrade on multiple servers . . . . . . 9Standard Solaris upgrade . . . . . . . . . . 9Solaris Live Upgrade . . . . . . . . . . . 10Solaris upgrade best practices . . . . . . . . 10Mandatory Solaris 10 patches for Tivoli NetcoolPerformance Manager . . . . . . . . . . . 10

Chapter 4. Upgrade preparation . . . . 11Installing the prerequisite software . . . . . . 11Report and user name duplicate pre-check . . . . 12

Pre-checking for report duplicates . . . . . . 12Report user pre-check . . . . . . . . . . 14

Downloading the Tivoli Netcool PerformanceManager distribution to disk . . . . . . . . 15

Downloading the Tivoli Common Reportingdistribution . . . . . . . . . . . . . 15

Download the Oracle distribution and patch to disk 16

Chapter 5. Upgrading Oracle 9i toOracle 10g . . . . . . . . . . . . . 17Install Oracle 10g server . . . . . . . . . . 17

Verify the required operating system packages. . 18Run the Oracle server configuration script . . . 18Run the preinstallation script . . . . . . . 21Verify PATH and Environment for the Oraclelogin name . . . . . . . . . . . . . 22Install Oracle using the menu-based script . . . 22Run the root.sh script . . . . . . . . . . 24Install Oracle patches . . . . . . . . . . 25Relax permissions on ORACLE_HOME . . . . 26

Install Oracle 10g client . . . . . . . . . . 26Run the Oracle client configuration script . . . 27Run the preinstallation script . . . . . . . 29

Verify PATH and Environment for the Oraclelogin name . . . . . . . . . . . . . 29Install the Oracle client . . . . . . . . . 30Run the root.sh script . . . . . . . . . . 31Install Oracle patches . . . . . . . . . . 32Configure the Oracle Net Client . . . . . . 33Update the oracle user's .profile . . . . . . 33Relax permissions on ORACLE_HOME . . . . 33

Perform Oracle Upgrade Preparation . . . . . . 34Shutting down the Tivoli Netcool PerformanceManager components . . . . . . . . . . 34Backup database. . . . . . . . . . . . 36Create a system undo tablespace . . . . . . 37Check all kernel parameters . . . . . . . . 38Copy utlu102i.sql and utltzuv2.sql fromORACLE_HOME . . . . . . . . . . . . . 40Run and spool the utlu102i.sql file . . . . . 40Make sure the database starts and ends in asimilar state . . . . . . . . . . . . . 40Verify that there is no database data dictionarycorruption . . . . . . . . . . . . . . 42Stop the database listener. . . . . . . . . 42Verify no data files need recovery . . . . . . 43Verify that there are no pending DistributedTransactions . . . . . . . . . . . . . 43Verify SYS and SYSTEM users have a defaultSYSTEM tablespace. . . . . . . . . . . 43Verify the AUD$ table is located in the SYSTEMtablespace . . . . . . . . . . . . . . 44Make note of all sysdba users . . . . . . . 44Shut down database . . . . . . . . . . 45

Perform the Oracle upgrade . . . . . . . . . 45Modify the database initPV.ora file . . . . . 45Verify the NLS_LANG parameter is set toWE8ISO8859P1 . . . . . . . . . . . . . 46Copy tnsnames.ora, sqlnet.ora, andlistener.ora files to the new ORACLE_HOME . 47Copy the password file from the old home to thenew home . . . . . . . . . . . . . . 47Replace the 32-bit library with the new 64-bitversion . . . . . . . . . . . . . . . 47Create soft links in the new ORACLE_HOME . . 48Update the oratab entry for this database . . . 48Update the oracle user's .profile . . . . . . 48Confirm the environment variables have beenreset . . . . . . . . . . . . . . . . 49Startup upgrade . . . . . . . . . . . . 49Create a SYSAUX tablespace . . . . . . . . 49Enter a spool command, and run the upgradescript catupgrd.sql . . . . . . . . . . . 50Disable stats . . . . . . . . . . . . . 50Run utlu102s.sql . . . . . . . . . . . 51Shut down database . . . . . . . . . . 51Restart the database . . . . . . . . . . 52Run the utlrp.sql script . . . . . . . . . 52Check for invalid objects . . . . . . . . . 53

© Copyright IBM Corp. 2006, 2011 iii

Shut down database . . . . . . . . . . 53Modify the database initPV.ora compatibleparameter . . . . . . . . . . . . . . 54Relax permissions on ORACLE_HOME . . . . 54Restart the database . . . . . . . . . . 54Add Oracle 10g grants to the proviso admin user 54Change listener.ora to use the newORACLE_HOME . . . . . . . . . . . 55Restart the listener . . . . . . . . . . . 56Starting the Tivoli Netcool Performance Managercomponents . . . . . . . . . . . . . 56

Chapter 6. Upgrading Tivoli NetcoolPerformance Manager . . . . . . . . 59Gather topology data . . . . . . . . . . . 59

DataChannel upgrade preparation . . . . . . 59Shutting down the Tivoli Netcool PerformanceManager components . . . . . . . . . . 60

Upgrade Database from Tivoli Netcool PerformanceManager 4.4.1 to Tivoli Netcool PerformanceManager 1.3.1 . . . . . . . . . . . . . 64

Upgrade the database portion of Tivoli NetcoolPerformance Manager . . . . . . . . . . 64

Installing and starting the Topology Editor . . . . 65Starting the launchpad . . . . . . . . . 65Installing and starting the Topology Editor . . . 66

Loading the upgrade topology into the TopologyEditor . . . . . . . . . . . . . . . . 67

Load the topology from the database . . . . . 67Preparing the upgrade topology for deployment . . 69

Technology packs . . . . . . . . . . . 69Upgrading an existing Tivoli Integrated Portal. . 70Add the destination DataView Components . . 70Determining valid host definitions. . . . . . 70Moving Tivoli Netcool Performance Managercomponents between host definitions . . . . . 71Deleting extraneous host definitions . . . . . 72Renaming host definitions . . . . . . . . 72Verifying host properties . . . . . . . . . 72Verifying Tivoli Netcool Performance Managercomponent properties . . . . . . . . . . 73Removing unused custom properties . . . . . 73

Saving the upgrade topology . . . . . . . 74Deploying the upgrade topology . . . . . . . 74

Deploy the upgrade topology for all components 75Deploy the upgrade topology to minimizecollections loss . . . . . . . . . . . . 77

Starting the Tivoli Netcool Performance Managercomponents . . . . . . . . . . . . . . 80

Starting the cron jobs . . . . . . . . . . 80Starting DataMart . . . . . . . . . . . 80Starting DataChannel . . . . . . . . . . 81

Migrating User Data to TIP . . . . . . . . . 81Removing SilverStream . . . . . . . . . 81

Install a libcrypto.so . . . . . . . . . . . 82Resuming a partially successful first-time upgrade 83

Resuming a partial upgrade . . . . . . . . 83

Appendix A. Migrating DataViewcontent and users . . . . . . . . . . 85Upgrading DataView clusters . . . . . . . . 85Migrating SilverStream content to the TivoliIntegrated Portal. . . . . . . . . . . . . 85

SilverStream page conversion . . . . . . . 85The migrate command. . . . . . . . . . 87

Moving DataView content between Tivoli IntegratedPortal servers. . . . . . . . . . . . . . 88

The synchronize command . . . . . . . . 89

Appendix B. Backup Modification . . . 91Upgrading the database backup procedure . . . . 91

Appendix C. DeploymentConsiderations . . . . . . . . . . . 93FTP is possible, but REXEC or RSH are not. . . . 93Neither FTP nor REXEC/RSH are possible . . . . 93

Appendix D. Oracle Bug . . . . . . . 95

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

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

iv IBM Tivoli Netcool Performance Manager: Upgrade Guide: 4.4.1 to 1.3.1

About this information

IBM® Tivoli® Netcool® Performance Manager, Version 1.3.1 is a bundled productconsisting of two main components. A wireline component (formerly TivoliNetcool/Proviso), and a wireless component (formerly Tivoli Netcool PerformanceManager for Wireless).

The IBM Tivoli Netcool Performance Manager: Upgrade Guide describes how toupgrade your IBM Tivoli Netcool Performance Manager environment. This guideassumes you are a network administrator or operations specialist who hasknowledge of network management and installing applications on operatingsystems.

Intended audienceThe audience for this manual is the network administrator or operations specialistresponsible for installing the Tivoli Netcool Performance Manager product suite onan enterprise network. To install Tivoli Netcool Performance Manager successfully,you should have a thorough understanding of the following subjects:v Basic principles of TCP/IP networks and network managementv SNMP conceptsv Administration of the Solaris operating environmentv Administration of the Oracle database management systemv Tivoli Netcool Performance Managerv Administrators who assign permissions, create groups, and associate users with

reports.v Advanced users or content designers who work with style sheets and reporters

to extend the capabilities of Tivoli Netcool Performance Manager technologypacks.

The Tivoli Netcool Performance Manager product suiteTivoli Netcool Performance Manager is made up of the following components:v Tivoli Netcool Performance Manager DataMart is a set of management,

configuration, and troubleshooting GUIs that the Tivoli Netcool PerformanceManager System Administrator uses to define policies and configuration, as wellas verify and troubleshoot operations.

v Tivoli Netcool Performance Manager DataLoad provides flexible, distributeddata collection and data import of SNMP and non-SNMP data to a centralizeddatabase.

v Tivoli Netcool Performance Manager DataChannel aggregates the data collectedthrough Tivoli Netcool Performance Manager DataLoad for use by the TivoliNetcool Performance Manager DataView reporting functions. It also processesonline calculations and detects real-time threshold violations.

v Tivoli Netcool Performance Manager DataView is a reliable application serverfor on-demand, web-based network reports.

v Tivoli Netcool Performance Manager Technology Packs extend the Tivoli NetcoolPerformance Manager system with service-ready reports for network operations,business development, and customer viewing.

© Copyright IBM Corp. 2006, 2011 v

The following figure shows the different Tivoli Netcool Performance Managermodules.

Tivoli Netcool Performance Manager documentations consists of the following:v Release notesv Configuration recommendationsv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the infocenter athttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm.

vi IBM Tivoli Netcool Performance Manager: Upgrade Guide: 4.4.1 to 1.3.1

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm

Chapter 1. Introduction

This chapter provides information concerning requirements and considerations thatmust be satisfied before you upgrade your Tivoli Netcool Performance Managerenvironment.

Summary of upgrade tasksA summary of the Tivoli Netcool Performance Manager 4.4.1 to 1.3.1 upgradeprocess.

Before you begin

This guide assumes that you have a fully functioning Tivoli Netcool PerformanceManager 4.4.1 environment. In order to upgrade your environment to IBM TivoliNetcool Performance Manager, Version 1.3.1, you must:

Procedure1. Verify that your environment is suitable and ready for upgrade:

a. Check that your planned upgrade conforms to one of the supportedupgrade paths.

b. Check that you are targeting supported platforms.2. If your system is pre Tivoli Netcool Performance Manager 4.4.1 with Fix Pack

4, download and install Fix Pack 4.3. Upgrade Solaris 9 to Solaris 10.4. Carry out the required upgrade preparation:

a. Install the various software packages required to facilitate the upgrade andthe successful operation of Tivoli Netcool Performance Manager.

b. Download the Tivoli Netcool Performance Manager distribution to disk.c. Download the Tivoli Common Reporting distribution to disk.d. Download the Oracle distribution and Patch to disk.

5. Update Oracle as per the Oracle support note 272413.1. This update is onlyrequired if your Oracle version was previously at version 8i.The appendix Oracle support note 272413.1, documented in Appendix D,“Oracle Bug,” on page 95, describes how to make the appropriate changes.

6. Perform upgrade of Oracle:a. Install Oracle 10g Serverb. Install Oracle 10g Clientc. Perform Oracle upgrade.

7. Gather existing topology data.8. Shut down Tivoli Netcool Performance Manager components.9. Upgrade the database from Tivoli Netcool Performance Manager 4.4.1 to 1.3.1.

10. Install the Topology Editor.11. Load the topology to the database, and from the database to the Topology

Editor.12. Prepare the topology for deployment.13. Deploy the upgrade topology.

© Copyright IBM Corp. 2006, 2011 1

14. Start all Tivoli Netcool Performance Manager components.15. Migrate user data from SilverStream to Tivoli Integrated Portal.

Verifying your Tivoli Netcool Performance Manager environmentTo complete a Tivoli Netcool Performance Manager upgrade, your system mustmeet certain requirements.

Before beginning an upgrade procedure, verify that your environment meets therequirements set out in this document.

Supported upgrade paths for Tivoli Netcool PerformanceManager

The applications and procedures described in this guide are intended to support alimited number of upgrade paths to IBM Tivoli Netcool Performance Manager,Version 1.3.1.

To find version information for the Tivoli Netcool Performance Managercomponents installed in your environment, use the Tivoli Netcool PerformanceManager Info Tool as described in “Check your system versioning” on page 5.

Consult the table below to determine the upgrade process for your environment:

Table 1. Supported upgrade paths

Tivoli Netcool Performance Managerversion Supported Upgrade Path

Tivoli Netcool Performance Manager 4.4.1with FixPack 3 or earlier.

To upgrade to IBM Tivoli NetcoolPerformance Manager, Version 1.3.1 youmust:

v Install FixPack 4.

v Upgrade your platform from Solaris 9 toSolaris 10.

v Upgrade your database server and clientsfrom Oracle 9i to Oracle 10

v Upgrade Tivoli Netcool PerformanceManager

Tivoli Netcool Performance Manager 4.4.1with FixPack 4 or 4.4.1 with FixPack 5.Running on Solaris 9.


v Upgrade your platform from Solaris 9 toSolaris 10.



Tivoli Netcool Performance Manager 4.4.1with FixPack 4 or 4.4.1 with FixPack 5.Running on Solaris 10.




2 IBM Tivoli Netcool Performance Manager: Upgrade Guide: 4.4.1 to 1.3.1

Table 1. Supported upgrade paths (continued)

Tivoli Netcool Performance Managerversion Supported Upgrade Path

Tivoli Netcool Performance ManagerTechnology Packs

You do not have to upgrade yourtechnology packs to upgrade to IBM TivoliNetcool Performance Manager, Version 1.3.1.

Supported platformsThe upgrade of Tivoli Netcool Performance Manager is limited to a number ofplatforms.

The following table lists the platforms supported by component under TivoliNetcool Performance Manager version 1.3.1.

Table 2. Supported Platforms

Tivoli Netcool Performance Managercomponent Required Platform

Tivoli Netcool Performance ManagerDatabase

v Solaris 10 64-bit

v AIX 5.3 64-bit

v AIX 6.1 64-bit

v RHEL 5.5, 64-bit

Tivoli Netcool Performance ManagerDataView

v Solaris 10 64-bit

v AIX 5.3 64-bit

v AIX 6.1 64-bit

v RHEL 5.5, 64-bit

Tivoli Netcool Performance ManagerDataChannel

v Solaris 10 64-bit

v AIX 5.3 64-bit

v AIX 6.1 64-bit

v RHEL 5.5, 64-bit

Tivoli Netcool Performance ManagerDataLoad

v Solaris 10 64-bit

v AIX 5.3 64-bit

v AIX 6.1 64-bit

v RHEL 5.5, 64-bit

Tivoli Netcool Performance ManagerDataMart

v Solaris 10 64-bit

v AIX 5.3 64-bit

v AIX 6.1 64-bit

v RHEL 5.5, 64-bit

Chapter 1. Introduction 3

Supported topologyThe upgrade procedure supports a typical deployment of Tivoli NetcoolPerformance Manager where one SNMP collector runs per physical host.

If you find that your environment does not meet this requirement, please contactProfessional Services for more information.

Upgrade is also supported for environments that use the following optionaladvanced configurations:v Remote collector or remote Complex Metric Engine (CME).

No special actions are required to upgrade an environment that contains aremote CME deployment.

v DataLoad High Availability Manager (HAM).No special actions are required to upgrade an environment that contains aDataLoad HAM deployment.

v DataView Clusters.To upgrade an environment that uses DataView Cluster Database Installations,you must perform the tasks described in Appendix A, DataView UpgradeTopics.

Note: If you plan to make any changes to your Tivoli Netcool PerformanceManager environment, such as adding or removing hosts, components, ordeploying an advanced configuration, you must upgrade your existingenvironment first before making these changes.


Chapter 2. Patch Tivoli Netcool Performance Manager to4.4.1.4

Your system must be at Tivoli Netcool Performance Manager version 4.4.1.4 orversion 4.4.1.5 before you upgrade your system.

Check your system versioningCheck your system version before installing any Tivoli Netcool PerformanceManager patch.

About this task

It is important that you check the current version of your system before youattempt the steps outlined here. If your system is already at version 4.4.1.4 or4.4.1.5, there is no reason for you to carry out the steps outlined in this section,and you can skip straight to Solaris upgrade, as described in Chapter 3,“Upgrading Solaris 9 to Solaris 10,” on page 9.

To check your systems version information, run the Tivoli Netcool PerformanceManager ProvisoInfo tool:

Procedure1. Log in as pvuser on the server where DataMart is installed.2. Ensure that your DISPLAY variable is set.3. Change to the DataMart home directory (by default, /opt/datamart).4. Run the DataMart environment file (dataMart.env).5. To run the ProvisoInfo tool:

a. Enter the provisoinfo command.b. Enter the pvm command to start the DataMart application. In DataMart,

select the Monitor tab and double-click Database Information.

The ProvisoInfo Browser window opens.6. In the left pane, select the Proviso Version folder. Summary version

information for all the registered components is displayed in the right pane.7. Scroll through the list in the right pane to see the registered components. The

information is grouped and summarized by application. Within eachapplication group, the left column indicates the name of the component and theright column indicates the version currently registered for that component. Anumber in parenthesis means that there is more than one component currentlyregistered with that version.

Results

If your system is pre version 4.4.1.4, continue and install the patch as is describedin “Install fixpack 4.4.1.0-TIV-PROV-FP0004” on page 6.


Install fixpack 4.4.1.0-TIV-PROV-FP0004Fixpack 4.4.1.0-TIV-PROV-FP0004 provides support for Solaris 10, which is essentialfor your upgrade to Tivoli Netcool Performance Manager version 1.3.1.

About this task

The details contained in this task can also be obtained from the IBM Supportwebsite, http://www-01.ibm.com/support/docview.wss?uid=swg24018636.

To install Fixpack 4.4.1.0-TIV-PROV-FP0004:

Procedure1. Create a staging directory for the Netcool/Proviso 4.4.1.0-TIV-PROV-FP0004

installation.Log in as pvuser and execute the following commands:mkdir /tmp/fixpack4

2. Using the FTP "get" sub-command, FTP the Tivoli Netcool PerformanceManager 4.4.1.0-TIV-PROV-FP0004 distribution from the IBM Software -Netcool/Proviso - Support site to the directory you created in Step 1.The FTP target is as follows:ftp://public.dhe.ibm.com/software/tivoli_support/patches/patches_4.4.1.0/4.4.1.0-TIV-PROV-FP0004/4.4.1.0-TIV-PROV-FP0004.tar.gz

3. Log in as pvuser.4. Unpack the Tivoli Netcool Performance Manager 4.4.1.0-TIV-PROV-FP0004

distribution:gunzip -c 4.4.1.0-TIV-PROV-FP0004.tar.gz | tar xf -

5. Select the DataMart patch appropriate to the version of Oracle being used.v For Oracle 8:

mv 4.4.1.0-TIV-PROV-FP0004-DM-Oracle-8.tar.gz 4.4.1.0-TIV-PROV-FP0004-DM.tar.gzrm 4.4.1.0-TIV-PROV-FP0004-DM-Oracle-9.tar.gz

v For Oracle 9:mv 4.4.1.0-TIV-PROV-FP0004-DM-Oracle-9.tar.gz 4.4.1.0-TIV-PROV-FP0004-DM.tar.gzrm 4.4.1.0-TIV-PROV-FP0004-DM-Oracle-8.tar.gz

6. Stop cron, DataChannel, DataView, and DataMart.For more information about stopping these components, see Shutting downthe Tivoli Netcool Performance Manager componentsThis step creates a backup of crontab in a file named <backup-dir>/pre.4.4.1.0-TIV-PROV-FP0004.crontab.This step also creates a backup of dc.cfg in a file named <backup-dir>/pre.4.4.1.0-TIV-PROV-FP0004.dc.cfg.

Note: Specifying a directory shared between systems for <backup-dir> willresult in the backup files being overwritten. Do not specify a shared<backup-dir> unless you want this overwriting behavior.

Note: Do not delete these backup files. You are required to update or restorethese files later in the installation.

Note: To ensure the following command does not run off the page, carriagereturns have been inserted. A forward slash, “/", identifies where a carriagereturn has been added.


http://www-01.ibm.com/support/docview.wss?uid=swg24018636

ftp://public.dhe.ibm.com/software/tivoli_support/patches/patches_4.4.1.0/4.4.1.0-TIV-PROV-FP0004/4.4.1.0-TIV-PROV-FP0004.tar.gz



cd <fix-pack-dir>mkdir <backup-dir>gunzip -c 4.4.1.0-TIV-PROV-FP0004-install.tar.gz | tar xf -./stop.sh [-dc <datachannel-home-dir>] [-dm <datamart-home-dir>] -backup /<backup-dir>

7. Back up <datachannel-home-dir> and <datamart-home-dir> directories.8. Patch SNMP collectors. Log in as root and execute the following commands

for each SNMP collector system:cd <fix-pack-dir>./dl.sh <dataload-home-dir>

9. Patch the database.Log in to the Database server and execute the following commands:cd <fix-pack-dir>./db.sh <database-install-cfg-dir> <PV_ADMIN-password>

Note: Do not execute the commands more than once.10. Patch DataChannel.

Log in as pvuser on the DataChannel system where the DataChannelInstallation configuration file is available and execute the followingcommands:cd <fix-pack-dir>./dc.sh <datachannel-home-dir> <datachannel-install-cfg-file>

Note: Do not execute the commands more than once.11. Update DataChannel Management and Application Watcher.

a. Log in as pvuser to <datachannel-mgmt-sys> and execute the followingcommands:cd <datachannel-home-dir>. ./dataChannel.envcd binchmod +x pvexec visual./cnsw./logw./cmgrw./amgrw

b. Log in as pvuser to all other DataChannel and Discovery systems thatwere configured during the original Netcool/Proviso installation(Netcool/Proviso Installation Guide Step 11.2) and execute the followingcommands:cd <datachannel-home-dir>. ./dataChannel.envcd binchmod +x pvexec visual./amgrw

12. Patch DataMart.Log in as root and execute the following commands for each DataMartsystem:cd <fix-pack-directory>./dm.sh <datamart-home-dir>

13. Re-enable cron.a. If necessary, update the <backup-dir>/pre.4.4.1.0-TIV-PROV-

FP0004.crontab file you created to include the use of the dataChannel.envfile. If this update is deemed necessary, it must be done for every systemthat was using cron.For example:

Chapter 2. Patch Tivoli Netcool Performance Manager to 4.4.1.4 7

Note: To ensure the following command does not run off the page,carriage returns have been inserted. A forward slash, “/", identifies wherea carriage return has been added.0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/datachannel/bin/cnsw > //dev/bull 2>&1

Becomes:0,5,10,15,20,25,30,35,40,45,50,55 * * * * . ./opt/datachannel/dataChannel.env /&& /opt/datachannel/bin/cnsw > /dev/null 2>&1

b. Log in as pvuser on every system that was using cron and insert crontabinto cron:cat <backup-dir>/pre.4.4.1.0-TIV-PROV-FP0004.crontab | crontab

14. Patch DataView.This patch must be performed on all DataView systems. If DataView isinstalled as a cluster, the secondary DataView system must be installed first.Log in as root and execute the following commands:

Note: If non-standard accounts and passwords are used, see Section IIVAdditional information within the IBM Support page: http://www-01.ibm.com/support/docview.wss?uid=swg24018636.cd <fix-pack-dir>./dv.sh

15. (Optional) A SilverStream iFix exists, which is recommended for application toyour system. This iFix is not part of this Fixpack and can be obtainedfrom:ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_4.4.1.0/4.4.1.0-TIV-PROV-IF0076/

16. Merge the dc.cfg that you backed up in with the dc.cfg that now exists in<datachannel-home-dir>/conf. This merge must be done for eachDataChannel system. Take care to ensure integrity of the merge, since thedc.cfg that was backed up may vary from system to system. Contact Servicesif you require assistance.

17. Restart DataChannel.Log in as pvuser on any DataChannel system and execute the followingcommands:cd <datachannel-home-dir>. ./dataChannel.envdccmd start all

Note: Do not execute the commands more than once.18. Restart DataMart.

Log in as pvuser on the DataMart system and execute the followingcommands for each DataMart system:cd <datamart-home-dir>. ./dataMart.envpismgr start




ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_4.4.1.0/4.4.1.0-TIV-PROV-IF0076/

ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_4.4.1.0/4.4.1.0-TIV-PROV-IF0076/

Chapter 3. Upgrading Solaris 9 to Solaris 10

IBM Tivoli Netcool Performance Manager, Version 1.3.1 requires the 64 bit versionof Solaris (Solaris 10).

Sun Microsystems provides documentation on how to upgrade a server fromSolaris 9 to Solaris 10. IBM Tivoli Netcool Performance Manager, Version 1.3.1requires the 64-bit version of Solaris (Solaris 10). You can either perform a standardSolaris upgrade or a Solaris Live Upgrade. The following topics are provided asguidance only, as it is the responsibility of the customer to perform a Solarisoperating system upgrade.

Note: IBM cannot be held responsible if the Solaris operating system upgrade doesnot run successfully. If you need support or assistance, contact Sun Microsystems.

Solaris upgrade on multiple serversWhen upgrading from Solaris 9i to Solaris 10g on multiple servers, there are anumber of issues to consider.

When upgrading from Solaris 9 to Solaris 10 on multiple servers, bear thefollowing in mind:v Upgrade the server running the Oracle database to Solaris 10.v Upgrade the server running Tivoli Netcool Performance Manager DataChannel,

DataMart, and DataView.v Do not upgrade the server running Tivoli Netcool Performance Manager

DataLoad.

By upgrading all Tivoli Netcool Performance Manager components exceptDataLoad, you minimize data loss.

Standard Solaris upgradeYou can perform a standard upgrade using a number of methods.

The following methods are available to perform a standard upgrade:v Solaris™ Web Start program

Graphical Interface program. Useful for Solaris servers with an attachedkeyboard, mouse, and monitor.

v Solaris suninstall programText-based installation program for Solaris servers without an attachedkeyboard, mouse, and monitor.

v Custom JumpStart™ methodAutomated upgrade using customized pre-built configuration files. Moreup-front effort, but useful in upgrading many Solaris servers quickly.

By upgrading all Tivoli Netcool Performance Manager components exceptDataLoad, you minimize data loss.


Solaris Live UpgradeLive Upgrade technology enables Solaris 9 systems to continue to run normallywhile an administrator installs and configures Solaris 10 software.

After the installation of Solaris 10, the administrator reboots the system to run theupgraded environment. Solaris Live Upgrade also supports fallback to helpmitigate any risk.

Solaris Live Upgrade requires a separate disk that can serve as a boot device, andso may not be appropriate for all situations.

Information can be found at the following link:

http://www.sun.com/software/solaris/liveupgrade/

To get documentation on the live upgrade procedure, go to the following link:

http://docs.sun.com/app/docs/doc/806-7933

Solaris upgrade best practicesBest practices for upgrading a Solaris operating system in a Tivoli NetcoolPerformance Manager environment.

The following list identifies best practices for upgrading a Solaris operating systemin a Tivoli Netcool Performance Manager environment:v Ensure that you have a backup of your system and the existing Tivoli Netcool

Performance Manager configuration.v Apply the upgrade procedures provided by Sun.

Mandatory Solaris 10 patches for Tivoli Netcool Performance ManagerTo get the latest list of mandatory Solaris patches needed to run IBM TivoliNetcool Performance Manager, Version 1.3.1, see the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide.


http://www.sun.com/software/solaris/liveupgrade/

http://docs.sun.com/app/docs/doc/806-7933

Chapter 4. Upgrade preparation

Performing as many of the required upgrade tasks as possible before you begin theupgrade procedure ensures you minimize the total collection loss.

There are a number of tasks that must be completed before you can begin theupgrade procedure.

Summary of upgrade preparation tasks

In order to prepare your system for upgrade, you must carry out the followingtasks:1. Install the prerequisite software.2. Check for report and report user duplicates.3. Download the Tivoli Netcool Performance Manager distribution.4. Download the Tivoli Common Reporting distribution.5. Download the Oracle distribution.

Installing the prerequisite softwareBefore beginning to upgrade your Tivoli Netcool Performance Managerenvironment, you must install the prerequisite software.

Before beginning to upgrade your Tivoli Netcool Performance Managerenvironment, you must install the prerequisite software listed in the IBM TivoliNetcool Performance Manager: Configuration Recommendations Guide, including:

Oracle

You must upgrade Oracle before you can begin to upgrade your Tivoli NetcoolPerformance Manager environment.

You must upgrade the Oracle Server software and the Oracle Client software oneach system that hosts a Tivoli Netcool Performance Manager component. Forinstructions, see the Oracle documentation that accompanies the Oracle Server andOracle Client software. The system hosting the Tivoli Netcool PerformanceManager Database must have installed the Oracle Server: 64 bit Oracle 10.2.0 withthe 10.2.0.4 patch set. Any system hosting any of the other components, must haveinstalled the Oracle Client: 64 bit Oracle 10.2.0 with the 10.2.0.4 patch set.

OpenSSH

If you plan to use Remote Command Execution or transfer files using SCP/SFTP,you must install and configure OpenSSH before upgrading Tivoli NetcoolPerformance Manager. For more information, see the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide for supportedversions and the Secure File Transfer Installation chapter of the IBM Tivoli NetcoolPerformance Manager: Installation Guide.

Linux systems require the installation of VSFTP (Very Secure FTP).


Web browser

The launchpad requires a web browser. IBM recommends using Mozilla with thelaunchpad. For a list of supported browsers, see the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide.

Java

Java is used by DataMart, DataLoad, and technology packs. For more information,see the IBM Tivoli Netcool Performance Manager: Configuration RecommendationsGuide for supported versions.

Report and user name duplicate pre-checkThe report and user name duplicate pre-check is a manual step to be performedbefore the upgrade.

In the 1.3.1 upgrade there are two required pre-checks:v A check for reports that are duplicated across multiple report groups.v A check for duplicate report user names.

Note: The upgrade process runs each pre-check to verify that you can proceedwith the upgrade.

Pre-checking for report duplicatesA report should only be referenced in one report group.

About this task

Locate any duplicate reports that occur on your system. Determine which reportgroups must contain the report, and delete the report from all other report groupsby completing the following steps:

Procedure1. Login as the oracle unix user.2. Search for duplicate report references by logging on to sqlplus as PV_ADMIN

and issuing the following query:


$ sqlplus PV_ADMIN/PV@PV

SQL*Plus: Release 9.2.0.8.0 - Production on Thu Feb 19 17:13:57 2009

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:Oracle9i Enterprise Edition Release 9.2.0.8.0 - ProductionWith the Partitioning optionJServer Release 9.2.0.8.0 - Production

SQL> Select Idx_Group LeafGrp,(Select Str_Name From APP_GRP_DESC Where Idx_Ind = Idx_Group) As AppGrpName,Idx_App,(Select Str_Name From APP_DESC Where Idx_Ind = Idx_App) As AppName

From APP_GRP_APP_MEMBERWhere Idx_App In ( Select Idx_App

From APP_GRP_APP_MEMBERGroup By Idx_AppHaving Count(*) > 1 );

LEAFGRP APPGRPNAME IDX_APP APPNAME---------- -------------------- ---------- ----------------------------------------

998 Sample3 49000033 Metric Diagnostic Report999 Sample4 49000033 Metric Diagnostic Report

3. Determine the full path for the report group by executing the following queryfor each group found in the previous query. This query generates a simple‘stepped' output starting with the root node for the group. Each subsequentgroup is then indented two spaces. This information assists in determining thegroups from which to remove the report.

SQL> Select LPAD(’ ’, 2*(Rownum-1)) || Str_Name as AppGrpNameFrom ( Select lvl, agd.Str_Name

From ( Select Level as Lvl, Idx_Group_ChildFrom APP_GRP_GROUP

Connect By Prior Idx_Group_Parent = Idx_Group_ChildStart With Idx_Group_Child = 999) agg,

APP_GRP_DESC agdWhere agg.Idx_Group_Child = agd.Idx_IndOrder By agg.Lvl Desc);

STR_NAME------------------------------GSTSample4

4. Delete the appropriate report-report group linkage:

SQL> Delete From APP_GRP_APP_MEMBERWhere Idx_App = 49000033And Idx_Group = 999;

1 row deleted.

SQL> Commit;

5. Retest by issuing the search query in step 1. Success is indicated by a return of‘no rows selected'. If more data is returned, then repeat the cycle until you haveremoved all duplicates.

Chapter 4. Upgrade preparation 13

Report user pre-checkThere may be duplicate report usernames.

About this task

Locate any duplicate report user names that exist in your system and renamethem, then use the normal interface to update the user. This can be achieved bycompleting the following steps:

Procedure1. Search for duplicate report user names by logging on to sqlplus as PV_ADMIN

and issuing the following query

$ sqlplus "/ as sysdba"




SQL> Select Idx_ind, Str_Name, Str_Email_Address, Str_User_TypeFrom RUSER_DESCWhere Str_Name IN ( Select Str_Name

From RUSER_DESCGroup By Str_Name

Having Count(*) > 1 );

IDX_IND STR_NAME STR_EMAIL_ADDRESS STR_USER_TYPE---------- ------------------------------ ------------------------------ ----------------100037133 John Doe [email protected] EMAIL RECIPIENT100021639 John Doe [email protected] EMAIL RECIPIENT

2. Rename the User:

SQL> Update RUSER_DESCSet Str_name = ’Jane Doe’

Where Idx_Ind = 100021639;

1 row updated.

SQL> Commit;

3. Retest by issuing the search query in step 1. Success is indicated by a return of‘no rows selected'. If more data is returned, then repeat the cycle until you haverenamed all of the duplicates.


Downloading the Tivoli Netcool Performance Manager distribution todisk

How to set up the Tivoli Netcool Performance Manager distribution for theupgrade process.

About this task

Whether you are installing the product from an electronic image or from DVD/CD,you must copy the distribution to a writeable location on the local filesystembefore beginning the installation.

To download the Tivoli Netcool Performance Manager distribution to a directoryon the host from which you intend to run the Topology Editor:

Procedure1. On the target host, log in as the Tivoli Netcool Performance Manager user, such

as pvuser.2. Create a directory to hold the contents of your Tivoli Netcool Performance

Manager distribution. For example:$ mkdir /var/tmp/cdproviso/131

Note: Any further references to this directory will be made using <DIST_DIR>.The addition of the “131” directory is to ensure that the download of the newdistribution does not overwrite existing files, and to ensure that it does not sitin the same directory as the previous distribution.

3. Download the Tivoli Netcool Performance Manager distribution to the hostdirectory created in the previous step and expand the contents of thedistribution package.

4. Change to the following directory:On Solaris systems:$ cd <DIST_DIR>/proviso/SOLARIS/DataChannel/SOL10/sparc

5. Untar the dc.tar file. For example:tar -xvf dc.tar

Downloading the Tivoli Common Reporting distributionYou must download the Tivoli Common Reporting distribution to the target serverand place the file in a specific directory.

About this task

Note: If you extract the tar directly into the same root location as the TivoliNetcool Performance Manager Components then the Tivoli Common Reportinglaunchpad.sh will overwrite the Tivoli Netcool Performance Manager Installerlaunchpad.sh, meaning that the launchpad cannot be started for the installer.

The Tivoli Common Reporting driver must be untarred so it can be used by theTivoli Netcool Performance Manager Common Installer.

Should you decide not to extract the tar as a peer to the other components, a TCRfolder must still be created having a path to the Tivoli Common Reportinginstall.sh the same as: ./TCR/TCRInstaller/install.sh

Chapter 4. Upgrade preparation 15

The following process ensures that you specify the Tivoli Common Reportingmedia location only once:

Procedure1. Create a directory named TCR as a peer to the other Tivoli Netcool Performance

Manager Components, that is, DataView, DataChannel, etc. For example:<DIST_DIR>/proviso/SOLARIS/TCR

2. Extract the Tivoli Common Reporting 1.3 inside this folder.

Download the Oracle distribution and patch to diskThe Oracle installation files must be in place before you can begin the installationof Oracle.

Procedure1. Log in as root.2. Set the DISPLAY environment variable.3. Create a directory to hold the contents of the Oracle distribution. For example:

# mkdir /var/tmp/oracle10201# mkdir /var/tmp/oracle10204

4. Download the Oracle files to the /var/tmp/oracle10201 directory.5. Locate the appropriate upgrade patch file for your version of Oracle on the

Oracle website and download it to your /var/tmp/oracle10204 directory.6. Extract the oracle distribution files that now exist in the /var/tmp/oracle10201

and /var/tmp/oracle10204 directories.

What to do next

Before you proceed to the next step, make sure that you obtain the upgradeinstructions provided by Oracle for the patch. The instructions contain informationabout performing steps required for the upgrade that are not documented in thisguide.


Chapter 5. Upgrading Oracle 9i to Oracle 10g

The following tasks assume that you have a fully functioning Tivoli NetcoolPerformance Manager 4.4.1.4 or later environment with Oracle 9i database runningon a Solaris 10 platform.

Summary of Oracle upgrade tasks

In order to upgrade your database, you must perform the following steps:1. Install Oracle 10g Server.2. Install Oracle 10g Client.3. Back up all servers hosting Tivoli Netcool Performance Manager components

and the Oracle 9i database.4. Back up the Oracle 9i database.5. Shut down Tivoli Netcool Performance Manager components.6. Upgrade the Tivoli Netcool Performance Manager database from Oracle 9i to

Oracle 10g.7. Back up the upgrade.

Note: Before you begin the Oracle upgrade, if your Oracle version was previouslyat version 8i, it is important that you carry out the instructions documented in theappendix Oracle support note 272413.1, Oracle Bug.

Install Oracle 10g serverTo install Oracle 10g Server, you can use the scripts provided as part of TivoliNetcool Performance Manager.

Before beginning this task, make sure that you have:v downloaded the Oracle 10g distribution to disk, as described in Download the

Oracle distribution and patch to disk.The directory created and to which the Oracle 10g distribution was downloadedwill from now on be referred to using <ORA_DIST_DIR>.

v downloaded the Tivoli Netcool Performance Manager distribution to disk, asdescribed in “Downloading the Tivoli Netcool Performance Manager distributionto disk” on page 15.The directory created and to which the Tivoli Netcool Performance Managerdistribution was downloaded will from now on be referred to using<DIST_DIR>.

Note: Oracle 10.2.0.4 must be installed into a new ORACLE_HOME. Make surethat you install Oracle into a different ORACLE_HOME than the one used for9.2.0.


Verify the required operating system packagesBefore installing the Oracle server, make sure the following Solaris packages areinstalled on your system.

About this task

Table 3. Required Solaris Packages

Package Description

SUNWarc Archives and Libraries/Generic

SUNWbtool CCS tools bundles with SunOS/Generic

SUNWhea SunOS Header Files/Generic

SUNWlibm Forte Developer bundled libraries

SUNWlibms Forte Developer bundled shared libraries

SUNWsprot Solaris bundled tools

SUNWtoo Programming tools

To verify that the required Solaris packages are installed:

Procedure1. Enter the following command at the shell prompt:

# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprotSUNWtoo SUNWuiu8

The following output confirms that the specified Solaris packages are installedcorrectly:

system SUNWarc Archive Librariessystem SUNWbtool CCS tools bundled with SunOSsystem SUNWhea SunOS Header Filessystem SUNWlibm Forte Developer Bundled libmsystem SUNWlibms Forte Developer Bundled shared libmsystem SUNWsprot Solaris Bundled toolssystem SUNWtoo Programming Toolssystem SUNWuiu8 Iconv modules for UTF-8 Locale

2. If these packages are not on your system, see the Solaris Installation Guide forinstructions on installing supplementary package software.

Run the Oracle server configuration scriptIn this step, you set up the Oracle environment using the script provided with theTivoli Netcool Performance Manager DataMart files on the Tivoli NetcoolPerformance Manager distribution.

About this task

This script automatically creates the following configuration:v Adds the dba and oinstall groups to /etc/group

v Adds the login name oracle, whose primary group membership is dba andsecondary group membership is oinstall

v Creates the Oracle directory structurev Creates startup and shutdown scripts for Oracle server processes


Note: If you have not created the oracle user, the script creates this user for you,and ORACLE_BASE is set as the user home directory. If you would prefer to use adifferent home directory for the oracle user, create the oracle user before runningthe script. The script does not create an oracle user if one already exists.

Note: It is likely you have already created the dba and oinstall groups and theoracle user. However, this script must still be run to create the required Oracledirectory structure.

To configure the Oracle installation environment using the script:

Procedure1. As root, set the ORACLE_BASE environment variable to point to the top-level

directory where you want the Oracle server files installed. The defaultinstallation directory is /opt/oracle.For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

Note: The script places this variable into the oracle login account's .profilefile.To check that the variable is set correctly, enter the following command:# env | grep ORA

2. Change to the following directory:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance

3. Run the Oracle configuration script by entering the following command:# ./configure_ora

The following screen is displayed:

--------------------------------------------------Setting the Oracle environment<Current Date>--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ delphi ]Logname ...... : [ root ]ORACLE_BASE .. : [ /opt/oracle ]DBA group ................. : [ dba ]OUI Inventory group ....... : [ oinstall ]Oracle Software owner ..... : [ oracle ]Configure Oracle release .. : [ 10.2.0 ]Menu :1. Modify Oracle software owner.2. Next supported release3. Check environment.0. ExitChoice:

4. Type 3 at the Choice prompt and press Enter.The script creates the dba and oinstall groups and the ORACLE_BASE directory,unless they exist:

Chapter 5. Upgrading Oracle 9i to Oracle 10g 19

Checking environment...Checking for group [ dba ] --> Created.Checking for group [ oinstall ] --> Created.Checking ORACLE_BASE** WARNING** ORACLE_BASE directory does not exist.** [ /opt/oracle ]**** Create it ? (n/y) y

5. Type y and press Enter.The script creates the /opt/oracle directory and continues as follows:

Checking for user [ oracle ]** WARNING** User [ oracle ] does not exist.**** Create it locally ? (n/y) y

6. Type y and press Enter.The script creates the oracle user and continues as follows:

--> Created.Checking for oracle directory tree :[ /opt/oracle/product ] --> Created.[ /opt/oracle/product/10.2.0 ] --> Created.[ /opt/oracle/product/10.2.0/dbs ] --> Created.[ /opt/oracle/admin ] --> Created.[ /opt/oracle/admin/skeleton ] --> Created.[ /opt/oracle/admin/skeleton/lib ] --> Ok.[ /opt/oracle/admin/skeleton/lib/libpvmextc.so ] --> Created.[ /opt/oracle/admin/skeleton/lib/libmultiTask.so ] --> Created.[ /opt/oracle/admin/skeleton/lib/libcmu.so ] --> Created.[ /opt/oracle/admin/skeleton/bin ] --> Ok.[ /opt/oracle/admin/skeleton/bin/snmptrap ] --> Created.[ /opt/oracle/local ] --> Created.Checking for oracle .profile file --> Created.Checking for dbora file --> Created./etc/rc0.d/K10dbora link --> Created./etc/rc1.d/K10dbora link --> Created./etc/rc2.d/S99dbora link --> Created.Checking for dbora configuration files :/var/opt/oracle/oratab --> Created./var/opt/oracle/lsnrtab --> Created.Press Enter to continue...

7. Press the Enter key to continue. The main screen is refreshed.8. Type 0 and press Enter to exit the script.

Note: You must set a password for the oracle login name.

Structure created by the configure_ora scriptThe script creates the Oracle directory structure.

The following example shows the directory structure created for Oracle, whereORACLE_BASE was set to /opt/oracle:/opt/oracle/product/opt/oracle/product/10.2.0/opt/oracle/product/10.2.0/dbs/opt/oracle/admin/opt/oracle/admin/skeleton/opt/oracle/admin/skeleton/bin/opt/oracle/local


The script creates the following setup files:v /etc/init.d/dbora, which starts the Oracle Listener and database server

automatically on each system bootv Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.d

v Oracle configuration files /var/opt/oracle/oratab and lsnrtab

v A .profile file for the oracle user containing the following lines:

# -- Begin Oracle Settings --umask 022ORACLE_BASE=/opt/oracleORACLE_HOME=$ORACLE_BASE/product/9.2.0NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/dataLD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/adminPATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/binEXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.soexport PATH ORACLE_BASE ORACLE_HOME NLS_LANGexport ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS# -- End Oracle Settings --

Note the following points:v The value of ORACLE_HOME must not contain soft links to other directories or file

systems. Be sure to specify the entire absolute path to Oracle.v The value of ORACLE_HOME must refer to the original 9.2.0 directory.v The ORACLE_SID variable is added to this file at a later stage.

Run the preinstallation scriptRun the preinstallation script to verify your readiness to install Oracle.

Procedure1. As root, change directory using the following command:

# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer

2. Set the ORACLE_BASE environment variable. For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

Note: You must use the same ORACLE_BASE setting that you specified in“Run the Oracle server configuration script”.

3. Enter the following command:# ./pre_install_as_root

The following messages indicate success:

Checking that you are logged in as root --> Ok.Checking ORACLE_BASE --> Ok.Checking oraInst.loc file --> Ok.

If the script shows an error, correct the situation causing the error beforeproceeding to the next step.


Verify PATH and Environment for the Oracle login nameBefore proceeding to install Oracle files, make sure the /usr/ccs/bin directory is inthe PATH environment variable for the oracle login name.

About this task

To verify the PATH and environment:

Procedure1. Log in as oracle. Set and export the DISPLAY environment variable.

If you are using the su command to become oracle, use a hyphen as the secondargument so the oracle user login environment is loaded:# su - oracle

2. Verify that the environment variable ORACLE_BASE has been set by enteringthe following command:$ env | grep ORA

If the response does not include ORACLE_BASE=/opt/oracle, stop and make surethe .profile file was set for the oracle user, as described in “Run the Oracleserver configuration script” on page 18.

3. To verify the path, enter the following command:$ echo $PATH

The output must show that /usr/ccs/bin is part of the search path. Forexample:

/usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin

a. If this directory is in the path, add it by entering the following commands:$ PATH=$PATH:/usr/ccs/bin$ export PATH

Install Oracle using the menu-based scriptTo install the Oracle database files using a menu-based system.

About this task

It is recommended that you use the menu-based script method.

Note: The Oracle installation script provided by IBM is used to install Oracleserver, Oracle client, and upgrade patches to an existing Oracle server or Clientinstallation.

To install the Oracle server using the menu-based script:

Procedure1. As oracle, change to the following directory:

$ cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer

2. Enter the following command to start the installer:$ ./perform_oracle_inst

The installation menu is displayed:


--------------------------------------------------perform_oracle_instInstallation of oracle binaries<Current Date>--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ delphi ]Logname ...... : [ oracle ]Install Oracle release .... : [ 10.2.0 ]Installation type.......... : [ Server ]Enter the appropriate letter to modify the entries below:a) ORACLE_BASE .. : [ /opt/oracle ]b) ORACLE_HOME .. : [ /opt/oracle/product/10.2.0 ]c) DBA group ..................... : [ dba ]d) OUI Inventory group ........... : [ oinstall ]e) Oracle Software owner ......... : [ oracle ]f) Directory where CDs were copied:[ ]Menu :1. Next supported release2. Set install type to: Client3. Perform install0. ExitChoice :

3. Verify the following settings:v The Oracle release number is 10.2.0.v The Installation type field is Server.This field cycles between three settings: Server, Client, and Patch. Type 2 atthe Choice prompt and press Enter until Server is displayed.

4. Type f at the Choice prompt and press Enter.5. At the Choice prompt, enter the full path to the directory containing the

installation files, <ORA_DIST_DIR>. For example:

Choice: fEnter new value for CD directory: /var/tmp/Oracle10201

6. Type a at the Choice prompt and press Enter.7. At the Choice prompt, enter the full path to the oracle base directory created

for Oracle 10g, the default is /opt/oracle.8. Type b at the Choice prompt and press Enter.9. At the Choice prompt, enter the full path to the oracle home directory created

for Oracle 10g, the default is /opt/oracle/product/10.2.0.10. Edit other menu settings as required. For example, if you used non-default

values for ORACLE_BASE or ORACLE_HOME, enter your settings until the menushows they correctly point to the directories created for Oracle 10g.

11. To begin the Oracle installation, type 3 at the Choice prompt and press Enter.The installation script checks the environment, then asks if you want toperform the installation.

12. Type Y at the Choice prompt and press Enter. The installation script startsinstalling Oracle and displays a series of status messages.

Note: You can safely ignore any “font.properties not found” messages in theoutput.When the installation reaches the In Summary Page stage, the installationslows down significantly while Oracle files are copied and linked.

13. When the installation is complete, messages like the following are displayed:


In End of Installation PageThe installation of Oracle10 Database was successful.Please check /opt/oracle/oraInventory/logs/silentInstall2004-09-28_04-23-53PM.logfor more details.The Oracle installation has completed. Please check themessages above to determine if the install completedsuccessfully. If you do not see successful completionmessages, consult the install log at:/opt/oracle/oraInventory/logsPress C to continue...

Note: Write down the log file location to aid in troubleshooting if there is aninstallation error.

14. Type C and press Enter to return to the installation menu.15. Type 0 and press Enter to exit the installation menu.

Run the root.sh scriptAfter successfully running an Oracle client or server installation, you must run theroot.sh script.

About this task

This step is also required after an Oracle patch installation. See “Install Oraclepatches” on page 25.

To run the root.sh script:

Procedure1. Log in as root or become superuser. Set the DISPLAY environment variable.2. Change to the directory where Oracle server files were installed. (This is the

directory as set in the ORACLE_HOME environment variable.) For example:# cd /opt/oracle/product/10.2.0

3. Run the following command:./root.sh

Messages like the following are displayed:

Running Oracle10 root.sh script...The following environment variables are set as:ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/10.2.0Enter the full pathname of the local bin directory: [/usr/local/bin]:

4. If the default entry, /usr/local/bin, is writable by root, press Enter to acceptthe default value. The default entry might be NFS-mounted at your site so itcan be shared among several workstations and therefore might bewrite-protected. If so, enter the location of a machine-specific alternative bindirectory. (You might need to create this alternative directory at a shell promptfirst.) For example, enter /usr/delphi/bin.

5. The script continues as follows:


...Adding entry to /var/opt/oracle/oratab file...Entries will be added to the /var/opt/oracle/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root.sh script.Now product-specific root actions will be performed.#

The script runs to completion with no further prompts.

Install Oracle patchesAfter you install Oracle, you must install the patch set for your version of Oracleto bring the Oracle version up to the IBM-validated patch level.

About this task

See the IBM Tivoli Netcool Performance Manager: Configuration RecommendationsGuide document for up-to-date information about the required patches.

Before you complete this step, make sure that you obtain the upgrade instructionsprovided by Oracle for the patch that you wish to install. The instructions containinformation about performing the steps required for the upgrade that are notdocumented in this guide.

Note: Do not skip this step. Upgrade the Oracle version before you install theTivoli Netcool Performance Manager database.

To install the Oracle patch set:

Procedure1. As oracle, change to the following directory:



3. Verify the following settings:v The Oracle release number is set to 10.2.0.v The Installation type field is set toPatch.This field cycles between three settings: Server, Client, and Patch. Type 2 at theChoice prompt and press Enter until Patch is displayed.

4. To specify the path, type f at the Choice prompt and press Enter.5. Enter the full path to the patch directory you created to hold the contents of the

patch release at the Choice prompt. See “Download the Oracle distribution andpatch to disk” on page 16 for more information. For example:

Choice: fEnter new value for CD directory: /var/tmp/oracle10204

6. To begin the upgrade installation, type 3 at the Choice prompt and press Enter.The installation script checks the environment, then asks whether you want toperform the installation.

7. Type y at the Choice prompt and press Enter. The script proceeds to install thepatch release files, showing a long series of messages much like the ones shownduring installation of the base release.


Note: You can safely ignore any “font.properties not found” messages in theoutput.In the messages, look for “success” notifications. If the script showsunsuccessful installation messages, check the installation log file specified in themessage. Correct the error conditions identified in the log file, then rerun thepatch installation and double-check all menu settings.

8. When the installation is complete, type C and press Enter.

Note: The message telling you to press C might have already scrolled past,because messages from several installation threads are written to the samescreen.

9. Exit from the menu.

Note: If you try to start Oracle as the database administrator (DBA), thestartup will fail because the file initPV.ora does not yet exist. This file iscreated during the Tivoli Netcool Performance Manager installation.

Relax permissions on ORACLE_HOMEWhen the installation has finished, you must change permissions on the directoriesunder ORACLE_HOME.

About this task

During the installation, Oracle sets restrictive permissions on ORACLE_HOME. Oracleprovides a script that can be run after the installation to change these permissions.

Procedure1. Log in as the oracle user.2. Make sure that ORACLE_HOME points to $ORACLE_BASE/product/10.2.0.3. Change to the directory $ORACLE_HOME/install.4. Run the script changePerm.sh.

Install Oracle 10g clientYou must specify a different directory path for the Oracle 10g Client from thedirectory specified when installing the Oracle 9i Client. For example, assuming thatOracle 9i is installed in /opt/oracle/product/9.2.0 then you should install theOracle 10g Client in /opt/oracle/product/10.2.0.

Note: Before beginning this task, make sure that you have:v downloaded the Oracle 10g distribution to disk, as described in Download the

Oracle distribution and patch to disk.The directory to which the Oracle 10g distribution was downloaded will fromnow on be referred to using <ORA_DIST_DIR>.


Run the Oracle client configuration scriptThe Oracle client configuration shell script creates the environment for the clientsoftware installation on the local system.

About this task

This script is named configure_client and is located with the Tivoli NetcoolPerformance Manager files downloaded as part of the Tivoli Netcool PerformanceManager distribution. If you are performing this step as part of an upgradeprocedure, make sure that you run the configuration script provided with thetarget version of Tivoli Netcool Performance Manager.

The client configuration script makes the following changes to the local system:v Adds the dba and oinstall groups to /etc/group.v Adds the Solaris login name oracle, whose primary group membership is dba,

and secondary group membership is oinstall.v Creates the Oracle client directory structure. When you create the environment

for patch version 10.2.0.4, the default location for this directory structure is$ORACLE_BASE/product/10.2.0. You specify this directory as the target locationwhen you install the Oracle client.

To configure the Oracle installation environment:

Procedure1. Log in as root.2. Set the ORACLE_BASE environment variable to point to the top-level directory

where you want the Oracle client files installed. The default installationdirectory is /opt/oracle.For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

Note: The configure_client script places this variable into the oracle loginname's .profile file.To check that the variable is set correctly, enter the following command:# env | grep ORA

3. Change to the following directory:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance

4. Run the Oracle configuration script using the following command:# ./configure_client

The following screen is displayed:


--------------------------------------------------configure_client

Setting the Oracle client environment<Current Date>

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ corinth ]Logname ...... : [ root ]

ORACLE_BASE .. : [ /opt/oracle ]

DBA group ................. : [ dba ]OUI Inventory group ....... : [ oinstall ]Oracle Software owner ..... : [ oracle ]

Configure Oracle release .. : [ 10.2.0 ]

Menu :1. Modify Oracle software owner.2. Next supported release.3. Check environment.0. Exit

Choice:

5. Type 3 at the Choice prompt and press Enter.The script creates the dba and oinstall groups, and the ORACLE_BASE directory,unless they already exist.

Checking environment...Checking for group [ dba ] --> Created.Checking for group [ oinstall ] --> Created.Checking ORACLE_BASE

** WARNING** ORACLE_BASE directory does not exist.** [ /opt/oracle ]**** Create it ? (n/y) y

If prompted, type y and press Enter.The script creates the /opt/oracle directory and continues as follows:

Checking for user [ oracle ]** WARNING** User [ oracle ] does not exist.**** Create it locally ? (n/y) y

If prompted, type y to create the oracle user and press Enter.The script creates the oracle user and continues as follows:

--> Created.Checking for oracle directory tree :

[ /opt/oracle/product ] --> Created.[ /opt/oracle/product ] --> Created.[ /opt/oracle/product/10.2.0 ] --> Created.

Checking for oracle .profile file --> Created.

Press Enter to continue...

6. Press Enter to continue. The configure_client main screen is displayed.7. Type 0 and press Enter to exit the script.


Run the preinstallation scriptRun the preinstallation script to verify your readiness to install Oracle.

Procedure1. As root, change directory using the following command:

# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer

2. Set the ORACLE_BASE environment variable. For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

Note: You must use the same ORACLE_BASE setting that you specified in“Run the Oracle server configuration script”.

3. Enter the following command:# ./pre_install_as_root

The following messages indicate success:

Checking that you are logged in as root --> Ok.Checking ORACLE_BASE --> Ok.Checking oraInst.loc file --> Ok.

If the script shows an error, correct the situation causing the error beforeproceeding to the next step.

Verify PATH and Environment for the Oracle login nameBefore proceeding to install Oracle files, make sure the /usr/ccs/bin directory is inthe PATH environment variable for the oracle login name.

About this task

To verify the PATH and environment:

Procedure1. Log in as oracle. Set and export the DISPLAY environment variable.

If you are using the su command to become oracle, use a hyphen as the secondargument so the oracle user login environment is loaded:# su - oracle

2. Verify that the environment variable ORACLE_BASE has been set by enteringthe following command:$ env | grep ORA

If the response does not include ORACLE_BASE=/opt/oracle, stop and make surethe .profile file was set for the oracle user, as described in “Run the Oracleserver configuration script” on page 18.

3. To verify the path, enter the following command:$ echo $PATH

The output must show that /usr/ccs/bin is part of the search path. Forexample:

/usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin

a. If this directory is in the path, add it by entering the following commands:$ PATH=$PATH:/usr/ccs/bin$ export PATH


Install the Oracle clientThe Oracle installation script is a shell script that you can use to install the Oracleserver, Oracle client software, or patches to existing installations of the Oracleserver and client.

About this task

This script is named perform_oracle_inst and is located with the Tivoli NetcoolPerformance Manager files that you obtained in “Download the Oracle distributionand patch to disk” on page 16. This script is provided by IBM as part of the TivoliNetcool Performance Manager installation package.

An Oracle client installation is not usable until the following Net configurationfiles are configured and installed:v tnsnames.ora

v sqlnet.ora

These files are configured in later steps.

To install the Oracle client:

Procedure1. Log in as oracle.2. Change to the following directory:



The installation menu is displayed:

--------------------------------------------------perform_oracle_inst

Installation of oracle binaries<Current Date>

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ delphi ]Logname ...... : [ oracle ]

Install Oracle release .... : [ 10.2.0 ]Installation type.......... : [ Client ]

Enter the appropriate letter to modify the entries below:

a) ORACLE_BASE .. : [ /opt/oracle ]b) ORACLE_HOME .. : [ /opt/oracle/product/10.2.0 ]c) DBA group ..................... : [ dba ]d) OUI Inventory group ........... : [ oinstall ]e) Oracle Software owner ......... : [ oracle ]f) Directory where CDs were copied:

[ ]Menu :

1. Next supported release2. Set install type to: Client3. Perform install0. Exit

Choice :

4. Enter f at the Choice prompt and press Enter.


5. Enter the full path to the <ORA_DIST_DIR>, as created in “Download theOracle distribution and patch to disk” on page 16. For example:

Choice: fEnter new value for CD directory: /var/tmp/oracle10201

6. Edit any other menu settings as necessary. Make sure that the values forORACLE_BASE and ORACLE_HOME correspond to the locations you specified whenyou ran the Oracle client configuration script.

7. To start the Oracle installation, type 3 at the Choice prompt and press Enter.8. The installation script checks the environment, then asks whether you want to

perform the installation. Type Y at the Choice prompt and press Enter. Theinstallation script starts installing Oracle and displays a series of statusmessages.

Note: You can safely ignore any “font.properties not found” messages in theoutput.When the installation reaches the In Summary Page stage, the installationslows down significantly while Oracle files are copied and linked.

9. When the installation process is finished, the installation displays a successmessage. Write down the log file location to aid in troubleshooting if there isan installation error.

10. Type C and press Enter to return to the installation menu.11. Type 0 and press Enter to exit the installation menu.12. Perform the steps in Run the root.sh script on page 104.

Run the root.sh scriptAfter successfully running an Oracle client or server installation, you must run theroot.sh script.

About this task

This step is also required after an Oracle patch installation. See “Install Oraclepatches” on page 25.

To run the root.sh script:

Procedure1. Log in as root or become superuser. Set the DISPLAY environment variable.2. Change to the directory where Oracle server files were installed. (This is the

directory as set in the ORACLE_HOME environment variable.) For example:# cd /opt/oracle/product/10.2.0

3. Run the following command:./root.sh

Messages like the following are displayed:

Running Oracle10 root.sh script...The following environment variables are set as:ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/10.2.0Enter the full pathname of the local bin directory: [/usr/local/bin]:

4. If the default entry, /usr/local/bin, is writable by root, press Enter to acceptthe default value. The default entry might be NFS-mounted at your site so it


can be shared among several workstations and therefore might bewrite-protected. If so, enter the location of a machine-specific alternative bindirectory. (You might need to create this alternative directory at a shell promptfirst.) For example, enter /usr/delphi/bin.

5. The script continues as follows:

...Adding entry to /var/opt/oracle/oratab file...Entries will be added to the /var/opt/oracle/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root.sh script.Now product-specific root actions will be performed.#

The script runs to completion with no further prompts.

Install Oracle patchesAfter you install the Oracle client software, you must install patch version 10.2.0.4.

About this task

Note: Do not skip this step. Upgrade the Oracle version before you install theTivoli Netcool Performance Manager database.

To install the Oracle patch set:

Procedure1. Follow the instructions to run the perform_oracle_inst script, as shown in

“Install Oracle patches” on page 25. Go through the menus as described in thatsection, with the following changes:a. Enter 2 at the Choice prompt and press Enter until the Installation type

field is set to Patch.b. Type f at the Choice prompt and press Enter.c. At the Choice prompt, type the full path to <ORA_DIST_DIR>. For

example:Choice: fEnter new value for CD directory: /var/tmp/oracle10204

2. Type 3 at the Choice prompt and press Enter. The script checks theenvironment and displays a series of messages.$ ./perform_oracle_inst

3. Type y at the Choice prompt and press Enter to begin the patch installation.The script proceeds to install the patch release files, showing a series ofmessages much like the ones shown during installation of the base release.

Note: You can safely ignore any “font.properties not found” messages in theoutput.

4. Type y at the prompt to continue with the patch install.5. Watch the script's messages for success entries.

Note: If the script shows unsuccessful installation messages, check theinstallation log file named in the message. Correct the error conditionsidentified in the log file, then rerun the patch installation and double-check allmenu settings.


6. At the Choice prompt, type c and press Enter to continue. The message tellingyou to press c may have already scrolled past, because messages from severalinstallation threads are written to the same screen. If the installation haspaused, type c to continue.

Configure the Oracle Net ClientAfter the Oracle 10g Client is installed on the client machine, copy the sqlnet.oraand tnsnames.ora files.

Procedure1. Copy the sqlnet.ora and tnsnames.ora files from the Oracle 9i Net Client

directory, $ORACLE9i_HOME/network/admin.2. Place the copied files in the Oracle 10g Net Client directory,

$ORACLE10g_HOME/network/admin.

Update the oracle user's .profileModify the oracle user's .profile file.

Procedure1. Make sure that ORACLE_HOME points to $ORACLE_BASE/product/10.2.0.2. If there is not already an entry for TNS_ADMIN, add one.

TNS_ADMIN=$ORACLE_HOME/network/admin

When complete, the .profile should look similar to:

# -- Begin Oracle Settings --

ORACLE_BASE=/opt/oracleORACLE_HOME=$ORACLE_BASE/product/10.2.0ORACLE_SID=PV; export ORACLE_SIDNLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/dataLD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/adminPATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/binEXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so

export PATH ORACLE_BASE ORACLE_HOME NLS_LANGexport ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS

# -- End Oracle Settings --


About this task


Procedure1. Log in as the oracle user.2. Make sure that ORACLE_HOME points to $ORACLE_BASE/product/10.2.0.3. Change to the directory $ORACLE_HOME/install.


4. Run the script changePerm.sh.

Perform Oracle Upgrade PreparationIt is important to ensure that your database is ready for the required upgrade.

The following steps provide instructions on how to check the existing database andmake the needed changes.

Shutting down the Tivoli Netcool Performance Managercomponents

The Tivoli Netcool Performance Manager components need to be shut down forthe database upgrade procedure.

Disabling the cron JobsYou must disable the cron jobs on each DataChannel host in your environment byediting the crontab file.

About this task

To disable the cron jobs:

Procedure1. On the DataChannel host, log in as the component user, such as pvuser.2. Open the crontab file for editing by using the following command:

crontab -e

3. Comment out all jobs that start Tivoli Netcool Performance Managercomponents and any third-party tasks that work with Tivoli NetcoolPerformance Manager tools by inserting a # character at the beginning of thejob statement. For example:Before:0,5,10,15,20,25,30,35,40,45,50,55 * * * * ./opt/datachannel/dataChannel.env && /opt/datachannel/bin/cnsw > /dev/null 2>&1

After:# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * ./opt/datachannel/dataChannel.env && /opt/datachannel/bin/cnsw > /dev/null 2>&1

4. When you have made your edits, write and quit the file.

Note: While the current cron jobs must be manually commented out, these jobstatements are automatically updated when you have deployed your upgradetopology. This process is described in “Starting the cron jobs” on page 80.

Shutting down DataChannelYou must shut down the DataChannel components on each DataChannel hostrunning in your environment.

About this task

To shut down DataChannel:

Note: The DataChannel CMGR, CNS, AMGR, and LOG visual processes mustremain running until you have gathered the DataChannel parameters from yourenvironment.


Procedure1. On the DataChannel host, log in as the component user, such as pvuser.2. Change your working directory to the DataChannel bin directory

(/opt/datachannel/bin by default) using the following command:$ cd /opt/datachannel/bin

3. Shut down the DataChannel FTE.Before shutting down all DataChannel components, some DataChannel workqueues must be emptied. To shut down the DataChannel FTE and empty thework queues:$ ./dccmd stop –pattern FTE.*

4. Let all DataChannel components continue to process until the .../dodirectories for the FTE and CME components contain no files.The .../do directories are located in the subdirectories of $DCHOME (typically,/opt/datachannel) that contain the DataChannel components – for example,FTE.1.1, CME.1.1.

5. Do one of the following:a. If your environment does not run the DataLoad High Availability Manager

(HAM), use the following dccmd command to stop the DataChannelapplications:$ ./dccmd stop all

b. If your environment runs the DataLoad High Availability Manager (HAM),use the following dccmd commands to stop the DataChannel applications:$ ./dccmd stop DLDR$ ./dccmd stop LDR$ ./dccmd stop CME$ ./dccmd stop FTE$ ./dccmd stop DISC$ ./dccmd stop UBA (if required)

Note: For the DataLoad High Availability Manager, the HAM applicationmust remain running until you have gathered the DataChannel parametersfrom your environment.

Shutting down DataMartYou must shut down DataMart on each DataMart host running in yourenvironment.

About this task

To shut down DataMart:

Procedure1. On the DataChannel host, log in as the component user, such as pvuser.2. Set and export the DISPLAY variable.3. Source the DataMart environment using the following command:

$ . /opt/datamart/dataMart.env

4. Change your working directory to the DataMart bin directory(/opt/datamart/bin by default) using the following command:$ cd /opt/datamart/bin

5. Use the pismgr command to stop DataMart:$ ./pismgr stop

6. Start the DataMart Status tool using the following command:


$ pvmstat

7. Remove any DataMart locks by selecting File > Remove locks.

Verifying Tivoli Netcool Performance Manager components areshut downYou must verify that the Tivoli Netcool Performance Manager components havebeen shut down in your environment.

About this task

To verify that Tivoli Netcool Performance Manager components have been shutdown:

Procedure1. On the Database host, log in as oracle.2. Log into SqlPlus by entering the following command:

sqlplus “/as sysdba”

3. Submit the following query to the Database:SELECT username,machine,programFROM v$sessionORDER BY username,machine,program;

On a system where all the clients have been shut down, you would expect tosee output like the following:USERNAMEMACHINEPROGRAMPV_ADMINOaksqlplus@oak (TNS V1-V3)...USERNAMEMACHINEPROGRAMPV_COLLWillowpvmd@willow (TNS V1-V3)

The first item is the SQL query itself, while the second item is a DataLoadcollector. This is expected if you chose to leave the DataLoad collectors runningin order to minimize collections loss.

Backup databaseAt this point, Oracle suggests either a hot or cold backup of your database.

About this task

Oracle suggests either a hot or cold backup of your database, and recommends acold backup. See the Oracle documentation for more information.

Note: For information on Database backup and recovery, see the DatabaseAdministration Guide.


Create a system undo tablespaceThe default minimum tablespace size is 1000M, but can be larger depending onyour installation requirements.

About this task

Information on sizing the undo tablespace can be found in the Oracle DatabaseAdministrator's Guide 10g Release 2 (10.2), "Section 10: Managing the UndoTablespace".

The tablespace must be created in a directory with adequate space. The directorythat contains the rollback segment is a good candidate.

Procedure1. The directory containing the rollback segment can be found by executing the

DDL command:select file_name from dba_data_files where tablespace_name = ’RBS’;

The naming conventions used for the file path containing the tablespace areimportant. The first directories in the name's path are a mount point.In the following example, the mount point is /oradata.

Note: In the examples that follow, be sure to substitute the mount point that iscorrect for your system.The next directory is the value of ORACLE_SID. The default value for ORACLE_SID,and the one used in this example, is PV.

2. Compose the file name by concatenating the value of ORACLE_SID and_undo_data_01.dbf.Here is an example: /oradata/PV/PV_undo_data_01.dbf

3. Create a SYSTEM undo tablespaceThe following is an example of how to create a SYSTEM undo tablespace:

bash-2.05$ sqlplus "/ as sysdba"




SQL> create Undo TableSpace Undo_Data datafile ’/oradata/PV/PV_undo_data_01.dbf’ size 1000M;

Tablespace created.

4. Check the amount of free space in your system tablespace.The following query shows the maximum free space segment available in theSYSTEM tablespace.

SQL> select max(bytes) from dba_free_space where tablespace_name = ’SYSTEM’;

MAX(BYTES)----------

64880640

SQL>


5. Make sure that you have at least 150 MB of free space in your system tablespace.If there is not enough space in the system tablespace, you must either extendthe existing data file or add a new data file to the tablespace. Therecommended size is 400M, or at least 150M free, whichever is higher. Forexample:

SQL> select file_name, bytes/1048576 from dba_data_files where tablespace_name = ’SYSTEM’;

FILE_NAME--------------------------------------------------------------------------------BYTES/1048576-------------/oradata/PV/PV_sys_01.dbf

200

SQL> alter database datafile ’/oradata/PV/PV_sys_01.dbf’ resize 300M;

Database altered.

SQL> select max(bytes) from dba_free_space where tablespace_name = ’SYSTEM’;

MAX(BYTES)----------169738240

SQL>

Check all kernel parametersOracle recommends that you certify that Oracle 10g is compatible with theoperating system release you are using.

About this task

Solaris 10 is compatible with Oracle 10.2.0.4. Oracle also recommends that allnecessary operating system patches are installed. This step should already havebeen covered during the operating system upgrade.

On Solaris, Oracle recommends that you ensure that all kernel parameters are setcorrectly. See Oracle Database Installation Guide 10g Release 2 (10.2) for SolarisOperating System (SPARC 64-Bit) Part Number B15690-02 (http://download.oracle.com/docs/cd/B19306_01/install.102/b15690/pre_install.htm#sthref259), "Section 2.6: Configuring Kernel Parameters".

Procedure1. In Solaris 10, kernel parameters are replaced by resource controls. Oracle

recommends the following values, noting that they are guidelines and must betuned for production database systems:

Table 4.

Resource Control Recommended Value

project.max-sem-ids 100

process.max-sem-nsems 256

project.max-shm-memory 4294967295

project.max-shm-ids 100

2. To find the current kernel parameter settings:a. Log in as the Oracle user (for example, oracle).b. Check the project ID.


c. Check the resource control settings for that project ID:

$ id -puid=4074(oracle) gid=9999(dba) projid=3(default)

$ prctl -n project.max-shm-memory -i project 3project: 3: defaultNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

privileged 1.95GB - deny -system 16.0EB max deny -

$ prctl -n project.max-sem-ids -i project 3project: 1: user.rootNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-sem-ids

privileged 128 - deny -system 16.8M max deny -

$ prctl -n project.max-shm-ids -i project 3project: 3: defaultNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-ids

privileged 128 - deny -system 16.8M max deny -

$ prctl -n process.max-sem-nsems $$process: 12134: bashNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTprocess.max-sem-nsems

privileged 600 - deny -system 32.8K max deny -

3. To change values, check the Solaris documentation for complete information onprojects.Here is one example, which sets the value of project.max-shm-memory to 4 GB.Log in as root and add a project, attached to the dba group (assuming that theoracle user is part of the dba group), and set the value:

# projadd -p 100 -G dba -c "Oracle Project" \-K "project.max-shm-memory=(privileged,4G,deny)" group.dba

4. Log back in as oracle.5. Check with id -p that the projid is now the new project number 100 and run

the prctl again to check that the max-shm-memory value has been updated.

$ id -puid=4074(oracle) gid=9999(dba) projid=100(group.dba)

bash-3.00$ prctl -n project.max-shm-memory -i project 100project: 100: group.dbaNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

privileged 4.00GB - deny -system 16.0EB max deny -


Copy utlu102i.sql and utltzuv2.sql from ORACLE_HOMEutlu102i.sql provides information about databases to be upgraded to 10.2, andutltzuv2.sql upgrades time zones to version 2.

Procedure

Copy utlu102i.sql and utltzuv2.sql from the 10g ORACLE_HOME/rdbms/admindirectory to a directory outside of the Oracle home, such as /tmp. For example:

# cd /opt/oracle/product/10.2.0/rdbms/admin# cp utlu102i.sql utltzuv2.sql /tmp

Run and spool the utlu102i.sql fileYou must run and spool the utlu102i.sql file.

Procedure

The following is an example of how to run and spool the utlu102i.sql file:





SQL> spool /tmp/Database_Info.logSQL> @/tmp/utlu102i.sqlOracle Database 10.2 Upgrade Information Utility 02-19-2009 19:30:53. . .

PL/SQL procedure successfully completed.

SQL> spool offSQL>

Note: Should any warnings be displayed after this file has been run, these cansafely be ignored.

Make sure the database starts and ends in a similar stateThe focus of this step is to ensure that all database components are valid beforestarting the actual upgrade.


Procedurev The following example issues an SQL command that checks for invalid data:

SQL> select substr(owner, 1, 12) owner, substr(object_name, 1, 30) object,substr(object_type, 1, 30), status

from dba_objectswhere status != ’VALID’;

OWNER OBJECT SUBSTR(OBJ STATUS---------- ------------------------------ ---------- -------PV_METRIC MTRC01_NRAW_000_H0 VIEW INVALIDPV_METRIC MTRC01_NRAW_000_CURRENT VIEW INVALIDPV_METRIC MTRC01_NRAW_000_FULL VIEW INVALIDPV_METRIC MTRC01_NRAW_000_RECENT VIEW INVALIDPV_METRIC MTRC00_NRAW_000_H0 VIEW INVALIDPV_METRIC MTRC00_NRAW_000_CURRENT VIEW INVALIDPV_METRIC MTRC00_NRAW_000_FULL VIEW INVALIDPV_METRIC MTRC00_NRAW_000_RECENT VIEW INVALID

8 rows selected.

SQL>

It is common for the Tivoli Netcool Performance Manager database to havemultiple INVALID objects. The metric data loading method adds new tablepartitions to the various metric data tables. This action invalidates the views thatTivoli Netcool Performance Manager uses for reporting. However, these viewsare implicitly recompiled when needed to satisfy queries.

v If the SQL query shown in the previous example returns a number of rowsselected, you can attempt to revalidate all INVALID objects with the followingOracle provided script.While connected as the sys user, issue the following command:

SQL> @$ORACLE_HOME/rdbms/admin/utlrp


SQL>

v Rerun the original SQL command that checks for invalid objects.

SQL> select substr(owner, 1, 12) owner, substr(object_name, 1, 30) object,substr(object_type, 1, 30), status

from dba_objectswhere status != ’VALID’;

no rows selected

SQL>

This time, the query should return no rows selected. If you find objects that arecurrently invalid, do not proceed with the upgrade.


Verify that there is no database data dictionary corruptionThe following set of commands generate a script that you will subsequently run.

Procedure1. Run the following commands:

SQL> Set verify offSet space 0Set line 120Set heading offSet feedback offSet pages 1000Spool analyze.sql

Select ’Analyze cluster "’||cluster_name||’" validate structure cascade;’from dba_clusterswhere owner=’SYS’unionSelect ’Analyze table "’||table_name||’" validate structure cascade;’from dba_tableswhere owner=’SYS’ and partitioned=’NO’ and (iot_type=’IOT’ or iot_type is NULL)unionSelect ’Analyze table "’||table_name||’" validate structure cascade into invalid_rows;’from dba_tableswhere owner=’SYS’ and partitioned=’YES’;

spool offSQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> 2 3 4 5 6 7 8 9 10 11Analyze cluster "C_COBJ#" validate structure cascade;Analyze cluster "C_FILE#_BLOCK#" validate structure cascade;. . .Analyze table "VIEWCON$" validate structure cascade;Analyze table "VIEWTRCOL$" validate structure cascade;Analyze table "VTABLE$" validate structure cascade;Analyze table "_default_auditing_options_" validate structure cascade;SQL>

2. Run utlvalid.sql and the script you just generated.In the following example, the generated script is called analyze.sql.

You should not see any errors reported except for the ones listed below. Youmay or may not see a message that indicates a table was created.

SQL> @$ORACLE_HOME/rdbms/admin/utlvalid.sqlSQL> @analyze.sqlSP2-0042: unknown command "SQL>" - rest of line ignored.SP2-0734: unknown command beginning "SQL> Selec..." - rest of line ignored.SP2-0042: unknown command "SQL>" - rest of line ignored.SP2-0734: unknown command beginning "SQL> spool..." - rest of line ignored.1 Table createdSQL>

Stop the database listenerStop the database listener.

Procedure

Use the commands shown in the following example:

$ lsnrctl stop

LSNRCTL for Solaris: Version 9.2.0.8.0 - Production on 19-FEB-2009 20:06:30


Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=pmgt1k4c2)(PORT=1521)))The command completed successfully$


Verify no data files need recoveryIf you discover any data files that need recovery, do not proceed with the upgrade.

Procedure

The following query should return no rows:

SQL> select * from v$recover_file;

no rows selected

SQL>

Verify that there are no pending Distributed TransactionsTivoli Netcool Performance Manager does not use the distributed transactionsfunctionality of Oracle.

About this task

You must verify that there are no pending distributed transactions.

Procedure

The following query should return no rows:

SQL> select * from dba_2pc_pending;

no rows selected

SQL>

Verify SYS and SYSTEM users have a default SYSTEMtablespace

You must verify that SYS and SYSTEM users have a default SYSTEM tablespace.

Procedurev Run the following query to view the default tablespaces for users:

SQL> select username, default_tablespacefrom dba_userswhere username in (’SYS’,’SYSTEM’);

USERNAME DEFAULT_TABLESPACE------------------------------ ------------------------------SYS SYSTEMSYSTEM SYSTEM

SQL>

v If necessary, alter these users to have a default tablespace of SYSTEM. Run thefollowing statements:


SQL> alter user sys default tablespace SYSTEM;

User altered.

SQL> alter user system default tablespace SYSTEM;

User altered.

SQL>

Verify the AUD$ table is located in the SYSTEM tablespaceIf you have enabled database auditing, you must verify that the AUD$ table islocated in the SYSTEM tablespace.

Procedurev Run the following statement:

SQL> select tablespace_name from dba_tables where table_name = ’AUD$’;

TABLESPACE_NAME------------------------------SYSTEMSQL>

v Note the location of the control files:

SQL> select name from v$controlfile;

NAME--------------------------------------------------------------------------------/oradata/PV/PV_01.ctl/oradata/PV/PV_02.ctl

SQL>

Make note of all sysdba usersWrite down the all sysdba users.

Procedurev All sysdba users can be discovered using the following query:

SQL> select * from v$pwfile_users;

USERNAME SYSDB SYSOP------------------------------ ----- -----INTERNAL TRUE TRUESYS TRUE TRUE

SQL>

v If table XDB.MIGR9202STATUS exists in the database, drop it before upgradingthe database (to avoid the issue described in Oracle Note 356082.1).

SQL> desc XDB.MIGR9202STATUSERROR:ORA-04043: object XDB.MIGR9202STATUS does not exist

SQL>


Shut down databasePerform a shutdown immediate on the database.

About this task

Note: Do not perform a shutdown abort.

Procedure

The following example shows the commands used to perform a shutdownimmediate:





SQL> shutdown immediateDatabase closed.Database dismounted.ORACLE instance shut down.SQL>

Perform the Oracle upgradeYou are now ready to perform the Oracle upgrade.

To upgrade the Tivoli Netcool Performance Manager database from Oracle 9i toOracle 10g, perform the following tasks:

Modify the database initPV.ora fileBy default, the initPV.ora file is located in the $ORACLE_BASE/admin/<$ORACLE_SID>/pfile directory.

About this task

Open this file and perform the following tasks:

Procedure1. Add the following parameters to the file:

v _gby_hash_aggregation_enabled=FALSE

v _unnest_subquery=FALSE

v read_only_open_delayed = TRUE

v recyclebin = OFF

2. Remove the following parameters should they exist:v _system_trig_enabled

v _old_connect_by_enabled

v distributed_transactions

v job_queue_interval


v mts_servers

v log_archive_start

v optimizer_features_enable

3. Change the value of the following parameters:v shared_pool_size from 256M to at least 512Mv pga_aggregate_target parameter is set to at least 500M

4. Rename the parameter partition_view_enabled to _partition_view_enabled.Its value remains the same (TRUE).

5. After the Control Files section of the initPV.ora file, add a new section, withthe following parameters:# Undoundo_management = AUTOundo_retention = 900undo_tablespace = UNDO_DATA

6. Set the job_queue_processes parameter value to 0 (zero).7. You may need to set the CPU_COUNT parameter:

a. If the following command returns sun4v:$uname -m

Determine a value for CPU_COUNT using:$ /usr/sbin/psrinfo -p

b. And add an entry to the initPV.ora file:CPU_COUNT={value from psrinfo command above}

c. If uname -m returns anything other then sun4v, it is not necessary to setCPU_COUNT.

What to do next

The following tasks must be carried out if archiving is enabled:1. Make sure the log_archive_dest parameter only specifies a path and that the

path ends with a / (for example, /u01/oradata/pv/arch/).2. Make sure the log_archive_format parameter specifies the desired format. The

allowable parameters to define this command have changed over time. Thecustomer must refer to the appropriate Oracle documentation to determine thecorrect format for Oracle 10.2.0.

Verify the NLS_LANG parameter is set to WE8ISO8859P1You must verify that the NLS_LANG parameter is set to WE8ISO8859P1.

Procedure

Check the NLS_LANG parameter using the following query:

$ echo $NLS_LANGAMERICAN_AMERICA.WE8ISO8859P1$


Copy tnsnames.ora, sqlnet.ora, and listener.ora files to thenew ORACLE_HOME

You must copy tnsnames.ora, sqlnet.ora, and listener.ora files to the newORACLE_HOME.

Procedure

These files can be copied as demonstrated in the following example:

$ cp <920_HOME>/network/admin/* <1020_HOME>/network/admin

Copy the password file from the old home to the new homeYou must copy the password file from the old home to the new home.

Procedure

Substitute the ORACLE_SID for your environment where you see {PV}:

$ cp <920_HOME>/dbs/orapw{PV} <1020_HOME>/dbs/orapw{PV}

Replace the 32-bit library with the new 64-bit versionOn Solaris, because Oracle 10g is 64-bit, a 32-bit library used by Tivoli NetcoolPerformance Manager 4.4.1 must be replaced with the 64-bit version provided inTivoli Netcool Performance Manager 1.3.1.

About this task

As discussed in Verifying Your Tivoli Netcool Performance Manager Environmenton page 3, this document assumes that the Tivoli Netcool Performance Manager1.3.1 installation files are available in <DIST_DIR>.

Procedure

The 4.4.1 version of this library is named libpvmextc.so. The 64-bit library in 1.3.1is named libpvmextc64.so. This library should be copied from 1.3.1 to a directoryin the Oracle installation, and then a soft link made from libpvmextc64.so tolibpvmextc.so:

$ cp <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/libpvmextc64.so $ORACLE_BASE/admin/{PV}/lib$ cd $ORACLE_BASE/admin/{PV}/lib$ rm –f libpvmextc.so$ ln –s libpvmextc64.so libpvmextc.so


Create soft links in the new ORACLE_HOMEYou must create soft links in the new ORACLE_HOME

Procedure

Substitute the ORACLE_SID for your environment where you see {PV}, and therelease directory where you see {RELEASE_DIR}.

$ cd <1020_HOME>/lib$ ln –s $ORACLE_BASE/admin/{PV}/lib/libpvmextc.so$ ln –s $ORACLE_BASE/admin/{PV}/lib/libmultiTask.so$ ln –s $ORACLE_BASE/admin/{PV}/lib/libcmu.so$ cd <1020_HOME>/bin$ ln –s $ORACLE_BASE/admin/{PV}/bin/snmptrap$ ln –s $ORACLE_BASE/admin/{PV}/bin/notifyDBSpace$ ln –s $ORACLE_BASE/admin/{PV}/bin/notifyConnection$ cd <1020_HOME>/dbs$ ln –s $ORACLE_BASE/admin/{PV}/pfile/init{PV}.ora

Update the oratab entry for this databaseYou must update the oratab entry for this database.

Procedure

Edit the /var/opt/oracle/oratab file, and change the entry as follows. Be sure todisable automatic startup, by specifying N in the last field:From:{PV}:<920_HOME>:{Y|N}

To:{PV}:<1020_HOME>:{Y|N}

Update the oracle user's .profileModify the oracle user's .profile file.

Procedure1. Make sure that ORACLE_HOME points to $ORACLE_BASE/product/10.2.0.2. If there is not already an entry for TNS_ADMIN, add one.

TNS_ADMIN=$ORACLE_HOME/network/admin

When complete, the .profile should look similar to:

# -- Begin Oracle Settings --

ORACLE_BASE=/opt/oracleORACLE_HOME=$ORACLE_BASE/product/10.2.0ORACLE_SID=PV; export ORACLE_SIDNLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/dataLD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/adminPATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/binEXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so

export PATH ORACLE_BASE ORACLE_HOME NLS_LANGexport ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS

# -- End Oracle Settings --


Confirm the environment variables have been resetLog out and log back in to make sure that your environment variables are reset tothe new ORACLE_HOME.

Procedure1. Log out and log back in.2. Verify that the following list of environment variables now point to the new

home:v ORACLE_BASE (if applicable)

v ORACLE_HOME

v ORA_NLS33

v LD_LIBRARY_PATH

v PATH

v EXTPROC_DLLS

Startup upgradeBegin the database upgrade.

Procedure

As specified in the following example, change directory, enter SQL*Plus as the sysuser, and issue a startup upgrade:

$ cd $ORACLE_HOME/rdbms/admin$ sqlplus "/ as sysdba"

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Feb 20 17:14:47 2009

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to an idle instance.

SQL> startup upgradeORACLE instance started.

Total System Global Area 679477248 bytesFixed Size 2043072 bytesVariable Size 541070144 bytesDatabase Buffers 134217728 bytesRedo Buffers 2146304 bytesDatabase mounted.Database opened.SQL>

Create a SYSAUX tablespaceThe Upgrade Information tool (utlu102i.sql run earlier) provides an estimate ofthe minimum required size for the SYSAUX tablespace in the SYSAUX Tablespacesection.

About this task

The DATAFILE specification must be a full path to where the file exists. The filename follows the same naming convention as for the system UNDO data file inCreate a system undo tablespace on page 113.


Procedure

The following is an example file name, substitute the appropriate values:<mount point>/${ORACLE_SID}/${ORACLE_SID}_sysaux_01.dbf

Create the tablespace using the following statement and appropriate file name:

SQL> CREATE TABLESPACE sysaux DATAFILE ’/oradata/PV/PV_sysaux_01.dbf’SIZE 500M REUSEEXTENT MANAGEMENT LOCALSEGMENT SPACE MANAGEMENT AUTOONLINE;

2 3 4 5Tablespace created.

SQL>

Enter a spool command, and run the upgrade scriptcatupgrd.sql

The catupgrd.sql script performs the Oracle upgrade from 9.2.0 to 10.2.0.

About this task

Note: The Oracle notes state: “Before performing this action, disable anythird-party procedures that check the complexity of schema passwords.”

Procedure

Run the following statement:

SQL> spool /tmp/upgrade.logSQL> @catupgrd.sqlSQL> spool offSQL>

What to do next

Oracle recommends: “Check the spool file (/tmp/upgrade.log) and verify that thepackages and procedures compiled successfully. Correct any problems you find inthis file and rerun the appropriate upgrade script, if necessary. You can rerun anyof the scripts described in this note as many times as necessary.”

Disable statsDisable the gathering of database statistics.

Procedure

To disable stats use the following query.

SQL> EXEC DBMS_SCHEDULER.DISABLE(’GATHER_STATS_JOB’);SQL>


Run utlu102s.sqlRun the utlu102s.sql script specifying the TEXT option.

About this task

The Oracle notes state: “This is the Post-upgrade Status tool that displays thestatus of the database components in the upgraded database.”

Procedure

To run this file:

SQL> @utlu102s.sql TEXT.Oracle Database 10.2 Upgrade Status Utility 02-23-2009 15:11:29.Component Status Version HH:MM:SSOracle Database Server VALID 10.2.0.4.0 01:11:31.Total Upgrade Time: 01:15:21


SQL>


About this task


Procedure








Restart the databasePerform a startup restrict on the database.

Procedure

The following example shows the commands used to perform a startup restrict:

SQL> startup restrictORACLE instance started.Total System Global Area 679477248 bytesFixed Size 2043072 bytesVariable Size 541070144 bytesDatabase Buffers 134217728 bytesRedo Buffers 2146304 bytesDatabase mounted.Database opened.SQL>

Run the utlrp.sql scriptRun the utlrp.sql script.

Procedure

To run this file:

SQL> @utlrp.sql

TIMESTAMP-----------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_BGN 2009-02-23 15:14:52. . .


TIMESTAMP-----------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_END 2009-02-23 15:18:44


. . .

OBJECTS WITH ERRORS-------------------

0. . .

ERRORS DURING RECOMPILATION---------------------------

0


SQL>


Check for invalid objectsRun the SQL statement that checks for invalid objects.

About this taskv Check for the invalid objects:v SYS.V_$KQRPD

v SYS.V_$KQRSD

v SYS.GV_$KQRPD

v SYS.GV_$KQRSD

Other than the views shown above, the following query should return no rows.

Note: If you find objects other than views that are currently invalid, do notproceed without contacting IBM support.

Procedure

Run the query:

SQL> select substr(owner, 1, 12) owner,substr(object_name, 1, 30) object,substr(object_type, 1, 30) type, statusfrom dba_objectswhere status != ’VALID’;no rows selectedSQL>


About this task


Procedure








Modify the database initPV.ora compatible parameterYou must modify the compatible parameter of the initPV.ora file.

Procedure

Set the compatible parameter as follows:compatible=”10.2.0”


About this task


Procedure1. Log in as the oracle user.2. Change ORACLE_HOME to:

ORACLE_HOME=$ORACLE_BASE/product/10.2.0

3. Change to the directory $ORACLE_HOME/install.4. Run the script changePerm.sh.

Restart the databasePerform a normal startup on the database.

Procedure

The following example shows the commands used to perform a normal databasestartup:

SQL> startupORACLE instance started.Total System Global Area 679477248 bytesFixed Size 2043072 bytesVariable Size 541070144 bytesDatabase Buffers 134217728 bytesRedo Buffers 2146304 bytesDatabase mounted.Database opened.SQL>

Add Oracle 10g grants to the proviso admin userYou must modify the compatible parameter of the initPV.ora file.

Procedure1. Log into sqlplus as SYSTEM and run the following command:

Define DB_USER_ROOT={PV}

2. Substitute your installation's value of PV_USER_ROOT for {PV}. By default, thisvalue is PV.


$ sqlplus system/manager

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Oct 30 17:27:17 2009


Connected to:Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit ProductionWith the Partitioning, Data Mining and Real Application Testing options

SQL> Define DB_USER_ROOT=PVSQL> Grant Execute Any Program,

Execute Any Class,Create Job,Create Any Job,Create External Job,Analyze Any Dictionary,Select Any Dictionary,Select Any Transaction,Manage Scheduler,Export Full Database,Import Full Database

To &DB_USER_ROOT._ADMIN With Admin Option/

old 12: To &DB_USER_ROOT._ADMIN With Admin Optionnew 12: To PV_ADMIN With Admin Option

Grant succeeded.

SQL> Grant Scheduler_Admin,Exp_Full_Database,Imp_Full_Database

To &DB_USER_ROOT._ADMIN With Admin Option/old 4: To &DB_USER_ROOT._ADMIN With Admin Optionnew 4: To PV_ADMIN With Admin Option

Grant succeeded.

SQL> quit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bitProductionWith the Partitioning, Data Mining and Real Application Testing options$

Change listener.ora to use the new ORACLE_HOMEChange to the TNS_ADMIN directory and modify the listener.ora file to use thenew ORACLE_HOME.

Procedure1. Run the following commands to change to the TNS_ADMIN directory and modify

the listener.ora file to use the new ORACLE_HOME :$ cd $ORACLE_HOME/network/admin$ vi listener.ora

2. Within the file, modify the ORACLE_HOME as appropriate. For example:From:(ORACLE_HOME = /opt/oracle/product/9.2.0)

To(ORACLE_HOME = /opt/oracle/product/10.2.0)

3. Repeat the previous two steps for each reference you see using the ORACLE_HOMEthat is valid for your environment.


Restart the listenerRestart the listener and make sure that it is using the 10.2.0 home.

Procedure

Enter the following:

$ lsnrctl start

LSNRCTL for Solaris: Version 10.2.0.4.0 - Production on 23-FEB-2009 15:46:54

Copyright (c) 1991, 2007, Oracle. All rights reserved.

Starting /opt/oracle/product/10.2.0/bin/tnslsnr: please wait...

TNSLSNR for Solaris: Version 10.2.0.4.0 - ProductionSystem parameter file is /opt/oracle/product/10.2.0/network/admin/listener.oraLog messages written to /opt/oracle/product/10.2.0/network/log/listener.logListening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=pmgt1k4c2)(PORT=1521)))Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=pmgt1k4c2)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Solaris: Version 10.2.0.4.0 - ProductionStart Date 23-FEB-2009 15:46:54Uptime 0 days 0 hr. 0 min. 0 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File /opt/oracle/product/10.2.0/network/admin/listener.oraListener Log File /opt/oracle/product/10.2.0/network/log/listener.logListening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=pmgt1k4c2)(PORT=1521)))(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))

Services Summary...Service "PLSExtProc" has 1 instance(s).

Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...Service "PV.WORLD" has 1 instance(s).

Instance "PV", status UNKNOWN, has 1 handler(s) for this service...The command completed successfully$

Starting the Tivoli Netcool Performance Manager componentsRestart all Tivoli Netcool Performance Manager components.

Starting the cron jobsDuring the upgrade process, the deployer creates new job statements in thecrontab file. These jobs are started automatically

About this task

You can make further changes to the crontab file if needed.

To edit the crontab file:


crontab -e



Starting DataMartDuring the upgrade process, DataMart should automatically restart. However, ifDataMart has not been restarted, you must start it manually.

About this task

To start DataMart:

Procedure1. On the DataMart host, log in as the component user, such as pvuser.2. Source the DataMart environment using the following command:



4. Use the pismgr command to start DataMart:$ ./pismgr start

Starting DataViewDuring the upgrade process, DataView should automatically restart. However, ifDataView has not been restarted, you must start it manually.

About this task

To start DataView:

Procedure1. On the DataView host, log in as the component user, such as pvuser.2. Start Tivoli Integrated Portal by entering the following command:

bin/startServer.sh server1 -user <user> -password <password>

Where:v user: the Tivoli Integrated Portal administrator name.v password: the Tivoli Integrated Portal administrator password.

3. Start SilverStream by entering the following command:# cd /etc/init.d# ./SilverStream start

Starting DataChannelYou must start the DataChannel components on each DataChannel host running inyour environment.

About this task

To start DataChannel:

Procedure1. On the DataChannel host, log in as pvuser.2. Change your working directory to the DataChannel bin directory


3. Use the following commands to stop the DataChannel management processes.For example:


# kill -9 <cnsw_pid1> <cnsw_pid2># kill -9 <logw_pid1> <logw_pid2># kill -9 <amgrw_pid1> <amgrw_pid2># kill -9 <cmgrw_pid1> <cmgrw_pid2>

4. Use the following commands to restart the DataChannel managementprocesses. For example:$ ./cnsw$ ./logw$ ./amgrw$ ./cmgrw

5. Make sure the processes started correctly. Use the following commands:ps -ef | grep LOG | grep -v grep ; ps -ef | grep AMGR | grep -v grepps -ef | grep CMGR | grep -v grep ;ps -ef | grep CNS | grep -v grep

6. Use the dccmd command to start all DataChannel applications:$ ./dccmd start all

7. Use the dccmd command to verify that all of the DataChannel applicationsstarted properly by executing the following command:$ ./dccmd status all


Chapter 6. Upgrading Tivoli Netcool Performance Manager

How to prepare and upgrade an existing Tivoli Netcool Performance Manager 1.3environment to Tivoli Netcool Performance Manager 1.3.1.

Gather topology dataYou must gather your system topology data.

Procedure1. Uncompress dc.tar into a temp folder. For example, you can use the following

commands:mkdir /tmp/DC52cd /tmp/DC52tar -xvf /var/tmp/cdproviso/52/SOLARIS/DataChannel/SOL10/sparc/dc.tar

2. Make sure the file /tmp/DC52/visual exists and it is executable.3. Set the following variables in /opt/datachannel/dataChannel.env:

v ORACLE_HOME: Change this parameter so it refers to Oracle 10.2.0.v LD_LIBRARY_PATH: Change this parameter so it includes $ORACLE_HOME/lib32.v DC_HOSTNAME: Changed this value:

From:DC_HOSTNAME=`hostname | tr ’[:lower:]’ ’[:upper:]’`

To:DC_HOSTNAME=`hostname | /usr/xpg6/bin/tr ’[:lower:]’ ’[:upper:]’`

4. Set the following variables in /opt/dataload/dataLoad.env:v ORACLE_HOME: Change this parameter so it refers to Oracle 10.2.0.v LD_LIBRARY_PATH: Change this parameter so it includes $ORACLE_HOME/lib32.

DataChannel upgrade preparationProcedure1. Start the Launchpad. For instructions on how to start the launchpad, see

Starting the launchpad2. In the left pane of the Launchpad, click DataChannel Upgrade Preparation.3. Enter the following parameters:

v DC Administrative Components Host: This is the CMGR host theconfiguration is being extracted from.

Note: Please note that this parameter must be the host name as the userwants it to appear in the topology editor. Do not be set this parameter to"localhost" as that causes problems with the upgrade.

v DC Port Number: Set this parameter to the value previously obtained for theORB_NAMESERVICE_PORT property.

v DC Configuration Output File: Set this parameter to where the DataChannelmap is written.This file is loaded in to the topology editor when the user goes to load theinitial 4.4.1.4 topology.


Note: The DataChannel CMGR, CNS, AMGR, LOG, all active DataLoadcomponents and the DataLoad High Availability Manager (HAM application)must remain running in order to execute the dcConfig.sh script.

4. Click Collect DataChannel configuration A new window opens asking you tospecify the directory where the new dc.tar file has been extracted.

5. Enter the directory in which the DataChannel binary file visual exists.6. Click OK.7. To complete step 2 as specified in the Launchpad: "To drain the DataChannel,

follow the steps in the upgrade guide“, do the followinga. On the DataChannel host, log in as the component user, such as pvuser.b. Change your working directory to the DataChannel bin directory


c. Shut down the DataChannel FTE.Prior to shutting down all DataChannel components, some DataChannelwork queues must be emptied. To shut down the DataChannel FTE andempty the work queues:$ ./dccmd stop –pattern FTE.*

DataChannel will continue to process till the current data set has been emptied.This processing can take ten minutes or more. Wait a suitable period beforecontinuing with the following steps.

8. Check that DataChannel has been drained by clicking Check is theDataChannel drained. If draining has been successful, a message is displayedstating:Every component contacted appeared to be drained.

If DataChannel was not drained, the following message is displayed:One or more components did not appear to be drained.

If you see this message, continue to wait for another period and check again ifDataChannel has been drained.

9. Shut down all Tivoli Netcool Performance Manager components as specified inthe following section Shutting down the Tivoli Netcool Performance Managercomponents.

Shutting down the Tivoli Netcool Performance Managercomponents

The Tivoli Netcool Performance Manager components need to be shut down forthe database upgrade procedure.

Disabling the cron JobsYou must disable the cron jobs on each DataChannel host in your environment byediting the crontab file.

About this task

To disable the cron jobs:


crontab -e


3. Comment out all jobs that start Tivoli Netcool Performance Managercomponents and any third-party tasks that work with Tivoli NetcoolPerformance Manager tools by inserting a # character at the beginning of thejob statement. For example:Before:0,5,10,15,20,25,30,35,40,45,50,55 * * * * ./opt/datachannel/dataChannel.env && /opt/datachannel/bin/cnsw > /dev/null 2>&1

After:# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * ./opt/datachannel/dataChannel.env && /opt/datachannel/bin/cnsw > /dev/null 2>&1


Note: While the current cron jobs must be manually commented out, these jobstatements are automatically updated when you have deployed your upgradetopology. This process is described in “Starting the cron jobs” on page 56.

Shutting down DataChannelYou must shut down the DataChannel components on each DataChannel hostrunning in your environment.

About this task

To shut down DataChannel:

Note: The DataChannel CMGR, CNS, AMGR, and LOG visual processes mustremain running until you have gathered the DataChannel parameters from yourenvironment.

Procedure1. On the DataChannel host, log in as the component user, such as pvuser.2. Change your working directory to the DataChannel bin directory


3. Shut down the DataChannel FTE.Before shutting down all DataChannel components, some DataChannel workqueues must be emptied. To shut down the DataChannel FTE and empty thework queues:$ ./dccmd stop –pattern FTE.*

4. Let all DataChannel components continue to process until the .../dodirectories for the FTE and CME components contain no files.The .../do directories are located in the subdirectories of $DCHOME (typically,/opt/datachannel) that contain the DataChannel components – for example,FTE.1.1, CME.1.1.

5. Do one of the following:a. If your environment does not run the DataLoad High Availability Manager

(HAM), use the following dccmd command to stop the DataChannelapplications:$ ./dccmd stop all

b. If your environment runs the DataLoad High Availability Manager (HAM),use the following dccmd commands to stop the DataChannel applications:

Chapter 6. Upgrading Tivoli Netcool Performance Manager 61

$ ./dccmd stop DLDR$ ./dccmd stop LDR$ ./dccmd stop CME$ ./dccmd stop FTE$ ./dccmd stop DISC$ ./dccmd stop UBA (if required)

Note: For the DataLoad High Availability Manager, the HAM applicationmust remain running until you have gathered the DataChannel parametersfrom your environment.

Shutting down DataMartYou must shut down DataMart on each DataMart host running in yourenvironment.

About this task

To shut down DataMart:

Procedure1. On the DataChannel host, log in as the component user, such as pvuser.2. Set and export the DISPLAY variable.3. Source the DataMart environment using the following command:



5. Use the pismgr command to stop DataMart:$ ./pismgr stop

6. Start the DataMart Status tool using the following command:$ pvmstat

7. Remove any DataMart locks by selecting File > Remove locks.

Verifying Tivoli Netcool Performance Manager components areshut downYou must verify that the Tivoli Netcool Performance Manager components havebeen shut down in your environment.

About this task

To verify that Tivoli Netcool Performance Manager components have been shutdown:

Procedure1. On the Database host, log in as oracle.2. Log into SqlPlus by entering the following command:

sqlplus “/as sysdba”

3. Submit the following query to the Database:SELECT username,machine,programFROM v$sessionORDER BY username,machine,program;

On a system where all the clients have been shut down, you would expect tosee output like the following:


USERNAMEMACHINEPROGRAMPV_ADMINOaksqlplus@oak (TNS V1-V3)...USERNAMEMACHINEPROGRAMPV_COLLWillowpvmd@willow (TNS V1-V3)

The first item is the SQL query itself, while the second item is a DataLoadcollector. This is expected if you chose to leave the DataLoad collectors runningin order to minimize collections loss.

Confirm environment files are correctly configuredYou must confirm that the environment (.env) files are configured correctly beforeyou continue.

About this task

If your Tivoli Netcool Performance Manager components are installed on a singleserver, then follow these instructions for all components.

If your Tivoli Netcool Performance Manager components are installed on multipleservers, then follow these instructions for the components that are installed on thedatabase server.

Procedure1. Confirm that the ORACLE_HOME variables that reside in the dataMart.env,

dataLoad.env, and dataChannel.env files point to the new Oracle 10g Clientpath. For example:ORACLE_HOME=/opt/oracle/product/10.2.0

Note: These environment variables, by default, are located in /opt/datamart,/opt/dataload, and /opt/datachannel, respectively.

2. Confirm that Tivoli Netcool Performance Manager DataMart is configured touse the Oracle 10g Client Lib32 directory. To do this:a. Open the dataMart.env file.b. Confirm that $ORACLE_HOME/lib32 is added to the command that sets the

LD_LIBRARY_PATH variable.The following example shows how to do this on Solaris:## Paths# -------# Entry for $PVMHOME/LIBPATH=$PVMHOME:$PVMHOME/bin:$PATH...export LD_LIBRARY_PATH## Entry for $ORACLE_HOME/lib32if [ -z "${LD_LIBRARY_PATH:-}" ]; then

LD_LIBRARY_PATH=$PVMHOME/lib:$ORACLE_HOME/lib32


elseLD_LIBRARY_PATH=$PVMHOME/lib:$ORACLE_HOME/lib32:$LD_LIBRARY_PATH

fiexport LD_LIBRARY_PATH

3. Confirm that Tivoli Netcool Performance Manager DataChannel is configuredto use the Oracle 10g Client Lib32 directory. To do this:a. Open the dataChannel.env file.b. Add $ORACLE_HOME/lib32 to the command that sets the LD_LIBRARY_PATH

variable.The following example shows how to do this on Solaris:LD_LIBRARY_PATH=$DC_PRODUCT_HOME/lib:$DC_PRODUCT_HOME/license:\$ORACLE_HOME/lib32:$LD_LIBRARY_PATH

Upgrade Database from Tivoli Netcool Performance Manager 4.4.1 toTivoli Netcool Performance Manager 1.3.1

Before running the upgrade procedure, you must ensure that your database is atthe appropriate version level.

The database must be at version 4.4.1 with FixPack 4 or FixPack 5. To validate thatthe database is at this version, run the following query as<DB_USER_ROOT>_ADMIN:Select Str_Value From Reg$Database Where Str_Path = ’DATABASE.GENERAL.VLN’;

The value of STR_VALUE must be any of:v DB301180203

v DB4411373000

v DB4411373001

v DB4411374000

v DB4411374001

Upgrade the database portion of Tivoli Netcool PerformanceManager

To Upgrade the database portion of Tivoli Netcool Performance Manager.

Procedure1. Start the Launchpad on the database host. For instructions on how to start the

launchpad, see “Starting the launchpad” on page 65.

Note: In this chapter, it is assumed that the IBM Tivoli Netcool PerformanceManager, Version 1.3.1 files are in <DIST_DIR>.

2. Click Upgrade Preparation in the left pane of the Launchpad.3. Populate the following fields:

v Oracle home: This parameter must refer to the new 10.2.0 directory.v Oracle SID: The system identifier identifying the existing Tivoli Netcool

Performance Manager Oracle database instance. The default value is PV.v Oracle owner: The default value is oracle.v Oracle SYSTEM User: The default value is system.v Oracle SYSTEM password: The SYSTEM password was set in the 4.4.1

installation as specified in the section “Step 2.19: Change Passwords for


Database Login Names" of the 4.4.1 Installation Guide. This value should beavailable to the database administrator.

v Oracle SYS password: The SYS password was set in the 4.4.1 installation asspecified in the section “Step 2.19: Change Passwords for Database LoginNames" of the 4.4.1 Installation Guide. This value must be available to thedatabase administrator.

v DISCONNECT_CLIENTS Y/N: The default value is Y.v proviso home: Enter the home from your Tivoli Netcool Performance

Manager installation. The default is /opt/proviso

v TNPM DB user root: The default value is PV.v TNPM DB user password: The default value is pv.v Mount point for new 1.3.1 metadata tables: This parameter must be set to

an existing directory. The mount point would have been created as per theinstructions in the 4.4.1 installation, as specified in the section “Step 2.15:Create Mount Point Directories" of the 4.4.1 Installation Guide.

4. Click Upgrade Database.

Note: This step will fail if the DataChannel is not drained as per theinstructions in Chapter 6, “Upgrading Tivoli Netcool Performance Manager,” onpage 59

5. If there are errors resulting from the previous step of the form:2008-10-03 08:12 Compile_Objects W Error compiling invalid objects

a. Log in as oracle.b. Enter the following:

sqlplus "/ as sysdba"@<ORACLE_HOME>/rdbms/admin/utlrp.sql

Installing and starting the Topology EditorOnly one instance of the Topology Editor can exist in the Tivoli NetcoolPerformance Manager environment. Using the launchpad, install the TopologyEditor on the server you have chosen as the primary deployer.

You use the launchpad to install and start the Topology Editor on the primarydeployer.

Starting the launchpadTo start the launchpad:

Procedure1. Log in as root.2. Set and export the DISPLAY variable.3. Set and export the BROWSER variable to point to your web browser. For

example:On Solaris systems:# BROWSER=/opt/mozilla/mozilla# export BROWSER

Note: The BROWSER command cannot include any spaces around the equalsign.

4. Change directory to the directory where the launchpad exists.


On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS

Installing and starting the Topology EditorTo install and start the Topology Editor.

About this task

Installing a Topology Editor on top of the existing Topology Editor can causeunwanted behaviour. Therefore, it is recommended that you uninstall the existingTopology Editor before proceeding.

Note: To uninstall the Topology Editor, follow the instructions in Uninstalling theTopology Editor in the IBM Tivoli Netcool Performance Manager: InstallationGuide.

Procedure1. On the launchpad, click the Install Topology Editor option in the list of tasks.2. On the Install Topology Editor page, click the Install Topology Editor link.

The installation wizard opens in a separate window, displaying a welcomepage.

3. Click Next.4. Accept the license agreement.5. Click Next.6. Accept the default installation directory (/opt/IBM/proviso), or specify a

different one. If you have previously installed the Topology Editor on thissystem, the installer does not prompt you for an installation directory, andinstead uses the directory where you last installed the application.

7. Click Next to continue.8. Accept the default location of the base installation directory of the Oracle

JDBC driver (/opt/oracle/product/version/jdbc/lib), or click Choose to navigateto another directory.

9. Click Next to continue.10. Review the installation information, then click Install.11. When the installation is complete, click Done to close the wizard.

The installation wizard installs the Topology Editor and an instance of thedeployer in the following directories:Topology Editor:install_dir/topologyEditor

Example: /opt/IBM/proviso/topologyEditorDeployer:install_dir/deployer

Example: /opt/IBM/proviso/deployer

Note: To uninstall the Topology Editor, follow the instructions in Uninstallingthe Topology Editor in the IBM Tivoli Netcool Performance Manager:Installation Guide. Do not simply delete the /opt/IBM directory! Doing socauses problems when you try to reinstall the Topology Editor.

If the /opt/IBM directory is accidentally deleted, perform the following steps:a. Change to the /var directory.


b. Rename the hidden file .com.zerog.registry.xml (for example, rename itto .com.zerog.registry.xml.backup).

c. Reinstall the Topology Editor.d. Rename the backup file to the original name (.com.zerog.registry.xml).

12. On the Install Topology Editor page in the launchpad, click the Start TopologyEditor link.

Note: If your DISPLAY environment variable is not set, the Topology Editorwill fail with a Java assertion message (core dump).

Loading the upgrade topology into the Topology EditorThe goal of the following procedure is to save the discovered 4.4.1.4 topology inthe database and then load it into the Topology Editor.

Load the topology from the databaseYou must reload the topology from the database before you can begin the processof updating the topology for deployment.

Procedure1. In the Topology Editor, click Topology > Open existing topology. The Open

An Existing Proviso Topology window is displayed.2. For the topology source, select the From database.3. Verify that all of the fields for the database connection are filled in with the

correct values:v Database hostname — The name of the database host. The default value is

localhost.v Port — The port number used for communication with the database. The

default value is 1521.v Database user — The user name used to access the database. The default

value is PV_INSTALL.v Database Password — The password for the database user account. For

example, PV.v SID — The SID for the database. The default value is PV.If desired, click Save as defaults to save these values for future incrementalinstallations.

Note: If at any time you click cancel, memory is cleared and the topology isunchanged.

4. Click Next.5. Insert path to DC.cfg.

This file was generated as part of the steps described in “Gather topologydata” on page 59.

6. Click Next.7. Add any new hosts to your topology, by typing their names into the Add new

hosts field as a comma separated list.8. Click Next.9. Configure all added hosts.

The Configure hosts dialog allows you to enter configuration settings andapply these settings to one or more of the specified host set.


To apply configuration settings to one or more of the specified host set:a. Enter the appropriate host configuration values.b. Select the check box opposite each of the hosts to which you want to apply

the entered values.c. Click Next. The hosts for which all configuration settings have been

specified disappear from the set of selectable hosts.d. Repeat steps a, b and c till all hosts are configured.

10. Click Next.11. Configure Cross Collector distribution across the topology.

a. (Optional) Click Add Hosts to add to the set of Cross Collector hosts. Onlyhosts that have a DUS can be added.

Note: It is recommended that you have 20 Cross Collector CMEs spreadacross the set of toplolgy hosts.

b. (Optional) Click Calculate Defaults to use the wizard to calculate therecommended spread across the added hosts.

c. (Optional) To manually set the number of cross collector for each host, usethe drop-down menu opposite each host name.

12. Click Next. The wizard displays all hosts containing one or more DataViewcomponents.

13. Select the check box opposite each host to which you want to add a TivoliIntegrated Portal.

14. Click Add TIP.This step checks for existing Tivoli Integrated Portals on each selectedDataView host.If a Tivoli Integrated Portal is discovered to exist on a host. The discoveredTivoli Integrated Portal detail is added to the topology.If the discovered Tivoli Integrated Portal is an old version, it is flagged withinthe topology for upgrade.Any DataView without a Tivoli Integrated Portal is flagged within thetopology for Tivoli Integrated Portal installation on that host.The deployer will take the appropriate action when run.

15. Click Next.16. Configure Tivoli Integrated Portal properties.

a. Enter the appropriate host configuration values.v TCR_INSTALLATION_DIRECTORY: This is the directory in which Tivoli

Common Reporting is installed.v TIP_INSTALLATION_DIRECTORY: This is the directory in which Tivoli

Integrated Portal is installed.v WAS_USER_NAME: This is the WAS user name.v WAS_PASSWORD: This is the WAS password.

If you would like to configure LDAP for Tivoli Integrated Portal, selectthe LDAP check box.

b. Select the check box opposite each of the Tivoli Integrated Portal hosts towhich you want to apply the entered values.

c. Click Next. The hosts for which all configuration settings have beenspecified disappear from the set of selectable hosts.

d. Repeat steps a, b and c till all hosts are configured.17. Click Next to change the topology.


18. Click Finish. The upgrade topology is displayed in the Topology Editor.

Preparing the upgrade topology for deploymentWhen the upgrade topology is initially loaded into the Topology Editor, it willcontain several error and warning messages.

Errors are expected. This section describes how to resolve these issues and preparethe upgrade topology for deployment.

Perform the following tasks:v Upgrade of existing Tivoli Integrated Portal.v Determine which generated host definitions are valid, and decide which host

definitions are extraneous and can be removed.v Move Tivoli Netcool Performance Manager components from the extraneous

hosts to the valid host definitions so that the upgrade topology matches whatexists in your current Tivoli Netcool Performance Manager environment.

v Delete the extraneous host definitions.v Review the host and Tivoli Netcool Performance Manager component properties

so that they match the values that exist in your current Tivoli NetcoolPerformance Manager environment.

v Verify that the upgrade topology matches your current Tivoli NetcoolPerformance Manager install base before deploying the upgrade topology file.

Note: If you plan to make changes to your Tivoli Netcool Performance Managerenvironment, such as adding or removing hosts, components, or deploying anadvanced configuration, you must upgrade your existing environment first.

Technology packsIn general, you do not need to perform any special actions for technology packswhen upgrading your Tivoli Netcool Performance Manager environment. Theinstalled packs will function at the new level of Tivoli Netcool PerformanceManager without requiring any technology pack upgrade.

If you want to upgrade a technology pack after your Tivoli Netcool PerformanceManager environment has been upgraded, or your environment has theAlcatel-Lucent 5620 SAM or Cisco Netflow Technology Packs installed, see IBMTivoli Netcool Performance Manager: Technology Pack Upgrade Guide for moreinformation.

Note: If your pre-upgrade environment contains technology packs that includeXSD files, DO NOT import the XSD files into the Topology Editor until AFTER youhave finished upgrading your Tivoli Netcool Performance Manager environment.


Upgrading an existing Tivoli Integrated PortalIf you are reusing an already existing version of Tivoli Integrated Portal, but onethat requires upgrading, you must install the WebSphere® Universal Installer.

About this task

To install the WebSphere Universal Installer:

Procedure1. Open the Launchpad.

For more information about how to open the Launchpad, see Starting thelaunchpad.

2. Click the Install WebSphere Universal Installer option in the left pane.3. Click the option to install the WebSphere Universal Installer in the right pane.

Add the destination DataView ComponentsThe upgrade or your system requires that you move from SilverStream to TivoliIntegrated Portal. To prepare for the migration of SilverStream data, you must firstcreate the destination DataView and Tivoli Integrated Portal components.

Procedure1. Add the destination DataView components and Tivoli Integrated Portals to the

topology using the Topology Editor.2. Edit the destination DataView MIGRATE_FROM_HOST property to specify the source

DataView host, that is, the host containing the 4.4.1.4 DataView instance. TheSilverStream properties will be added to the destination DataView object oncethe migrate_from_host property is changed.

What to do next

The TIP and DataView records to delete will lack a host name after theirdescription within the logical view.

DataView cluster migrationAbout this task

Where there are multiple 4414 DataViews on a single source host, they must bemigrated to different target hosts as TNPM 1.3.1 only supports a single TivoliIntegrated Portal and DataView combination per host.

The user can differentiate between 4414 DataViews by the SS_HTTP_PORT property

Determining valid host definitionsIn the Physical View, there can be several host definitions that appear for the samephysical host, some of which may not be valid.

About this task

Extraneous host definitions can be generated when the upgrade topology is firstcreated. You must determine which host definitions are valid and which hostdefinitions are extraneous and can be renamed or later removed.

To determine which hosts are valid:


Procedure1. In the Topology Editor, examine each host definition that appears in the

Physical View. You must either rename delete any host definitions with thefollowing characteristics (only delete a host after its Tivoli Netcool PerformanceManager components have been removed):v Host name is blank. For example:

Host <blank>

v Host name is fully qualified:Host DOCSVR3.BBB.AAA.COM

Note: Fully-qualified host names are not supported by Tivoli NetcoolPerformance Manager .

2. If you determine that a host definition is valid and want to rename it, see“Renaming host definitions” on page 72.

3. If you determine that a host definition is extraneous and want to later delete it,you must move the Tivoli Netcool Performance Manager components from theextraneous host to a valid host definition. For more information, see “MovingTivoli Netcool Performance Manager components between host definitions.”

Moving Tivoli Netcool Performance Manager componentsbetween host definitions

Once you have determined which host definitions are valid in the Logical View,you must move Tivoli Netcool Performance Manager components from theextraneous hosts to the valid host definitions.

About this task

To move Tivoli Netcool Performance Manager components between hosts:

Procedure1. In the Topology Editor, right-click on the Tivoli Netcool Performance Manager

component in the Logical View that you want to move, then select the Changehost or Move menu option.

Note: The menu selection is “Change Host” or “Move” depending upon thecomponent that is selected.

2. In the Available hosts field, select the name of the host where you intend theTivoli Netcool Performance Manager component to reside from the scroll-downlist.

3. Click Finish.4. Repeat steps 1 - 3 until all Tivoli Netcool Performance Manager components

have been moved from the extraneous host definitions to their intended targethost definitions.


Deleting extraneous host definitionsWhen you have removed all of the Tivoli Netcool Performance Managercomponents from an extraneous host definition, you can delete the host definitionfrom the Physical View.

About this task

To delete host definitions:

Procedure1. In the Topology Editor, right-click on the name of the host definition in the

Physical View, then select the Remove menu option.2. Repeat step 1 until all of the extraneous hosts have been removed from the

Physical View.

Renaming host definitionsRenaming host definitions.

About this task

To rename a host definition:

Procedure1. In the Topology Editor, right-click on the name of the host definition in the

Physical View, then select the Rename menu option.2. In the Host Name field, specify the new name of the host definition. This name

must match the name of the physical host in your environment.

Note: Fully-qualified host names are not supported by Tivoli NetcoolPerformance Manager.

3. Click Finish.

Verifying host propertiesYou must verify the properties defined for each host in the Physical View so thatthey match the values that exist in your current Tivoli Netcool PerformanceManager environment.

About this task

If your environment uses non-default values for the Oracle data mount points,your site values can be overwritten by the Tivoli Netcool Performance Managerdefaults (/raid_2/oradata and raid_3/oradata, by default) when your upgradetopology is loaded into the Topology Editor. To remedy this issue, verify theO_MOUNTPOINT_1 and O_MOUNTPOINT_2 Database Configurations properties in yourtopology and input your site's values, if necessary.

To verify the host properties:

Procedure1. In the Topology Editor, select a host in the Physical View.2. In the Properties and Advanced Properties tabs, it is possible that some

properties are marked with a red X (missing or incorrect value) or a yellow


exclamation point (inherited value or is using a default value). You mustspecify or verify the values for any of the marked properties.

3. To specify or change the value of a property, select the Value field for thatproperty and enter the correct value. The property must match what exists inyour current Tivoli Netcool Performance Manager environment.

Note: If you use several operating systems in your environment, you mustcheck that the correct operating system is specified for each host.

4. Remove any unused custom properties. For more information, see “Removingunused custom properties.”

5. Repeat STEP 1 through STEP 4 for each host definition in the Physical View.

Verifying Tivoli Netcool Performance Manager componentproperties

You must verify the properties defined for each Tivoli Netcool PerformanceManager component in the Logical View so that they match the values that existin your current Tivoli Netcool Performance Manager environment.

About this task

To verify the Tivoli Netcool Performance Manager component properties:

Procedure1. In the Topology Editor, select a Tivoli Netcool Performance Manager

component in the Physical View.2. In the Properties and Advanced Properties tabs, it is possible that some

properties are marked with a red X (missing or incorrect value) or a yellowexclamation point (inherited value or is using a default value). You mustspecify or verify the values for any of the marked properties.

3. Review any user credentials and passwords that are specified on the AdvancedProperties tab for the current component. You must ensure that these valuesmatch those that are correct for your site.

4. To specify or change the value of a property, select its Value field and enter thecorrect value. The property must match what exists in your current TivoliNetcool Performance Manager environment.

5. Remove any unused custom properties. For more information, see Verifyinghost properties.

6. Repeat STEP 1 through STEP 5 for each Tivoli Netcool Performance Managercomponent in the Logical View.

Removing unused custom propertiesExamine each custom property and determine whether it is used in yourenvironment. If it is not used, remove the property from the upgrade topology.

About this task

Custom properties are identified by a check mark in the Is Custom column of theProperties and Advanced Properties tabs.

To remove an unused custom property:


Procedure1. In the Topology Editor, select the custom property in the Properties or

Advanced Properties tab.2. Click the Remove Custom Property button (a red X icon that appears in the

Property view).

Saving the upgrade topologyAfter you have validated your upgrade topology, you must save your upgradetopology to the database.

About this task

You will later load this saved upgrade topology from the Tivoli NetcoolPerformance Manager 1.3.1 database for deployment in your environment.

To save your upgrade topology:

Procedure1. In the Topology Editor, click Topology > Save topology as.2. If you have validated your upgrade topology and are satisfied that it is correct,

ignore the displayed warning message and click Ok.3. Use the Browse button to navigate to the location where you wish to save the

upgrade topology.4. Specify a name for the topology file, or use the default of topology.xml.5. Click Ok.

Deploying the upgrade topologyWhen the topology has been completed it can be deployed.

When the upgrade topology is ready to be deployed, deploy it using the primarydeployer, that is, the host running the Topology Editor and Deployer.

If your system contains hosts that do not support FTP or the remote execution, seeAppendix C, “Deployment Considerations,” on page 93 for more information onremote installation requirements and behavior.

To deploy the upgrade topology, you can choose to either:v Deploy the Upgrade Topology for All Components.

This upgrade strategy results in a period of no collections that lasts for theduration of the upgrade procedure. To use this deployment method, you do thefollowing:– Shut down all DataLoad collectors in your environment.– Upgrade the Tivoli Netcool Performance Manager components using the

primary deployer.v Deploy the Upgrade Topology to Minimize Collections Loss.

This upgrade strategy minimizes the period of no collections by only stoppingone DataLoad collector at a time, leaving other collectors available for datacollection. To use this deployment method, you do the following:– Deploy the upgrade topology in your environment so that only one host at a

time is upgraded.


– If a host is running a DataLoad collector, you first shut down that collector,then upgrade the 1.3.1 components on that host. Once complete, you similarlyupgrade the next host in your environment until all hosts have beenupgraded.

Deploy the upgrade topology for all componentsTo deploy the upgrade topology for all 1.3.1 components, perform the followingtasks:v Stop the DataLoad Collectorv Deploy the Topology with the primary deployer

Run the primary deployer to upgrade the 1.3.1 components.

Stop the DataLoad collectorTo stop the DataLoad collector.

Procedure1. Log in as the component user, such as pvuser, on the DataLoad host.2. Source the DataLoad environment using the following command:

$ . /opt/dataload/dataLoad.env

3. Change your working directory to the DataLoad bin directory(/opt/dataload/bin by default) using the following command:$ cd /opt/dataload/bin

4. Use the pvmdmgr command to stop the DataLoad collector:$ ./pvmdmgr stop

5. Repeat STEP 1 through STEP 4 for each DataLoad host in your environment.

Deploy the topology with the primary deployerTo deploy the upgrade topology with the primary deployer:

Procedure1. In the Topology Editor, open the upgrade topology you created in “Preparing

the upgrade topology for deployment” on page 69 from the Tivoli NetcoolPerformance Manager 1.3.1 database.

2. Click Run > Run Deployer for Installation. The deployer displays a welcomepage.

3. Click Next to continue.4. The database access window prompts for the security credentials. Enter the

host name (for example, delphi) and database administrator password (forexample, PV), and verify the other values (port number, SID, and user name).

5. Click Next to load the upgrade topology. The deployer displays a page statingthat the environment was successfully downloaded.

6. Click Next. The node selection window shows the target systems and how thefiles will be transferred (see the IBM Tivoli Netcool Performance Manager:Installation Guide for an explanation of this window). The table has one rowfor each machine where at least one Tivoli Netcool Performance Managercomponent will be installed.

7. If desired, reset the values as appropriate for your deployment.

Note: If a Run Remote step fails, you will have to complete the stepmanually on the remote machine. For more information, see Appendix C,


“Deployment Considerations,” on page 93.The deployer prompts you for the location of the setup files.

8. Click Choose the Proviso Media and browse to the location where youdownloaded the Tivoli Netcool Performance Manager distribution in“Downloading the Tivoli Netcool Performance Manager distribution to disk”on page 15. The deployer displays summary information about theinstallation.

9. Click Next to continue.10. Review the summary information, and click Run.

The deployer displays the table of installation steps.a. From the set of steps listed, select the step immediately after the Register

Database step.b. Right-click on this step and select Set Status > Held.

This will set the Status column for this step and all subsequent steps toHeld.

11. Click Run All to run all the steps in sequence.Note the following:v If an installation step fails, see the IBM Tivoli Netcool Performance

Manager: Installation Guide for debugging information. Continue theinstallation by following the instructions in Resuming a partially successfulfirst-time upgrade.

v If the Tivoli Common Reporting installation step fails, which can happenwhen there is not enough space available in /usr and /tmp or directorycleanup has not been carried out, run the tcrClean.sh script. To run thisscript:To run this script:a. On the host where the Tivoli Common Reporting installation failed,

change to the directory containing tcrClean.sh:cd /opt/IBM/proviso/deployer/proviso/bin/Util/

b. Run tcrClean.sh

c. When prompted, enter the install location of Tivoli Common Reporting.v Continue the installation by following the instructions in Resuming a

partially successful first-time upgrade.12. Once the Register Database step is complete, run the following check

a. login as the Oracle DB owner Unix user (by default this is the oracle user)b. Run the following commands to query the DB version:

$ sqlpus PV_ADMIN/[email protected]$ sqlplus PV_ADMIN/PV@PV

SQL*Plus: Release 10.2.0.4.0 - Production on Thu Dec 16 10:06:19 2010



SQL> col STR_COMPONENT_NAME format a20SQL> select str_application, str_component_name, str_major_versionfrom vers_component_version vcv,

vers_component vc,vers_version vv

where vcv.idx_component = vc.idx_ind


and vcv.idx_version = vv.idx_indand vc.str_component_name = ’Database’and vcv.dte_date = (

select MAX(vcv1.dte_date)from vers_component_version vcv1where vcv1.idx_component = vcv.idx_component);

STR_A STR_COMPONENT_NAME STR_MAJOR_VERSION----- -------------------- ------------------------------DB Database 1.3.1.0INST Database 1.3.1.0SQL>

c. Verify that the last 2 rows of the output (DB and INST) have the samevalue for STR_MAJOR_VERSION, and that the value is 1.3.1.0.

Note: If these values do not match, then there has been a problem withthe database upgrade. Do not continue with the upgrade until thisproblem has been resolved.

d. Once you have validated that the Upgrade Proviso Database step hascompleted without errors, select the step immediately after RegisterDatabase step in the step list window. Right-click on this step and selectSet Status > Ready. This will set the status of this and all subsequent stepsto Ready.

13. Click Run All to run all the steps in sequence.14. When all the steps have completed successfully, click Done to close the

wizard.

Deploy the upgrade topology to minimize collections lossTo deploy the upgrade topology to minimize collections loss, deploy the upgradetopology in your environment so that you upgrade only one host at a time.

This strategy minimizes the period of no collections by stopping only oneDataLoad collector at a time, leaving other collectors available for data collection.You will deploy the topology using the primary deployer on a host by host basis.

Do the following for each host in your topology:v Select the targeted host for deployment.v If the host is running a DataLoad collector, shut down that collector.v Run the primary deployer, de-selecting all the other hosts in the deployer so that

only the Tivoli Netcool Performance Manager components on the targeted hostare upgraded.

Deploy the topology by hostYou will deploy the upgrade topology one host at a time.

About this task

You can deploy one host at a time by de-selecting all but one of the hosts listed inthe deployer, so only the targeted host is upgraded.

To deploy the upgrade topology on one host using the primary deployer:


Procedure1. If the targeted host is running a DataLoad collector:

a. Log in as the component user, such as pvuser, on the DataLoad host.b. Source the DataLoad environment using the following command:

$ . /opt/dataload/dataLoad.env

c. Change your working directory to the DataLoad bin directory(/opt/dataload/bin by default) using the following command:$ cd /opt/dataload/bin

d. Use the pvmdmgr command to stop the DataLoad collector:$ ./pvmdmgr stop

2. In the Topology Editor, load the upgrade topology you created in Preparingthe upgrade topology for deployment from the Tivoli Netcool PerformanceManager 1.3.1 database.

3. Click Run > Run Deployer for Installation. The deployer displays a welcomepage.

4. Click Next to continue.5. The database access window prompts for the security credentials. Enter the

host name (for example, delphi) and database administrator password (forexample, PV), and verify the other values (port number, SID, and user name).

6. Click Next to load the upgrade topology. The deployer displays a page statingthat the environment was successfully downloaded.

7. Click Next. The node selection window shows the target systems and how thefiles will be transferred (see the IBM Tivoli Netcool Performance Manager:Installation Guide for an explanation of this window). The table has one rowfor each machine where at least one Tivoli Netcool Performance Managercomponent will be installed.

8. Ensure that the Enable checkbox is selected for the target host only. De-selectthe Enable checkbox for any other hosts.If desired, reset the other values as appropriate for your deployment.

9. Click Choose the Proviso Media and browse to the location where youdownloaded the Tivoli Netcool Performance Manager distribution in“Downloading the Tivoli Netcool Performance Manager distribution to disk”on page 15. The deployer displays summary information about theinstallation.

10. Click Next to continue.11. The deployer displays summary information about the installation. Review the

information, then click Run.The deployer displays the table of installation steps.a. From the set of steps listed, select the step immediately after the Register

Database step.b. Right-click on this step and select Set Status > Held.

This will set the Status column for this step and all subsequent steps toHeld.

12. Click Run All to run all the steps in sequence.Note the following:v If an installation step fails, see the IBM Tivoli Netcool Performance

Manager: Installation Guide for debugging information. Continue theinstallation by following the instructions in Resuming a partial upgrade.


v If the Tivoli Common Reporting installation step fails, which can happenwhen there is not enough space available in /usr and /tmp or directorycleanup has not been carried out, run the tcrClean.sh script. To run thisscript:a. On the host where the Tivoli Common Reporting installation failed,

change to the directory containing tcrClean.sh:cd /opt/IBM/proviso/deployer/proviso/bin/Util/

b. Run tcrClean.sh

c. When prompted, enter the install location of Tivoli Common Reporting.v Continue the installation by following the instructions in Resuming a partial

upgrade.13. Once the Register Database step is complete, run the following check

a. login as the Oracle DB owner Unix user (by default this is the oracle user)b. Run the following commands to query the DB version:

$ sqlpus PV_ADMIN/[email protected]$ sqlplus PV_ADMIN/PV@PV

SQL*Plus: Release 10.2.0.4.0 - Production on Thu Dec 16 10:06:19 2010



SQL> col STR_COMPONENT_NAME format a20SQL> select str_application, str_component_name, str_major_versionfrom vers_component_version vcv,

vers_component vc,vers_version vv

where vcv.idx_component = vc.idx_indand vcv.idx_version = vv.idx_indand vc.str_component_name = ’Database’and vcv.dte_date = (

select MAX(vcv1.dte_date)from vers_component_version vcv1where vcv1.idx_component = vcv.idx_component);

STR_A STR_COMPONENT_NAME STR_MAJOR_VERSION----- -------------------- ------------------------------DB Database 1.3.1.0INST Database 1.3.1.0SQL>

c. Verify that the last 2 rows of the output (DB and INST) have the samevalue for STR_MAJOR_VERSION, and that the value is 1.3.1.0.

Note: If these values do not match, then there has been a problem withthe database upgrade. Do not continue with the upgrade until thisproblem has been resolved.

d. Once you have validated that the Upgrade Proviso Database step hascompleted without errors, select the step immediately after RegisterDatabase step in the step list window. Right-click on this step and selectSet Status > Ready. This will set the status of this and all subsequent stepsto Ready.

14. Click Run All to run all the steps in sequence.


15. When all the steps have completed successfully, click Done to close thewizard.

What to do next

All of steps 1 to 13 listed above must be performed for each host in your topology.

Starting the Tivoli Netcool Performance Manager componentsExcept for DataChannel, all Tivoli Netcool Performance Manager componentsshould be running once the upgrade topology has been successfully deployed.

Should you find that any components are not running after deployment, thefollowing sections explain how they can be restarted.

Starting the cron jobsDuring the upgrade process, the deployer creates new job statements in thecrontab file. These jobs are started automatically

About this task

You can make further changes to the crontab file if needed.

To edit the crontab file:


crontab -e


Starting DataMartDuring the upgrade process, DataMart should automatically restart. However, ifDataMart has not been restarted, you must start it manually.

About this task

To start DataMart:

Procedure1. On the DataMart host, log in as the component user, such as pvuser.2. Source the DataMart environment using the following command:



4. Use the pismgr command to start DataMart:$ ./pismgr start


Starting DataChannelYou must start the DataChannel components on each DataChannel host running inyour environment.

About this task

To start DataChannel:

Procedure1. On the DataChannel host, log in as pvuser.2. Change your working directory to the DataChannel bin directory


3. Use the following commands to stop the DataChannel management processes.For example:# kill -9 <cnsw_pid1> <cnsw_pid2># kill -9 <logw_pid1> <logw_pid2># kill -9 <amgrw_pid1> <amgrw_pid2># kill -9 <cmgrw_pid1> <cmgrw_pid2>

4. Use the following commands to restart the DataChannel managementprocesses. For example:$ ./cnsw$ ./logw$ ./amgrw$ ./cmgrw

5. Make sure the processes started correctly. Use the following commands:ps -ef | grep LOG | grep -v grep ; ps -ef | grep AMGR | grep -v grepps -ef | grep CMGR | grep -v grep ;ps -ef | grep CNS | grep -v grep

6. Use the dccmd command to start all DataChannel applications:$ ./dccmd start all

7. Use the dccmd command to verify that all of the DataChannel applicationsstarted properly by executing the following command:$ ./dccmd status all

Migrating User Data to TIPUsers and user groups are automatically migrated from SilverStream to TIP as partof the upgrade process when upgrading using the common installer and thedeployer.

For information on how to manually migrate DataView data, see Appendix A,“Migrating DataView content and users,” on page 85.

Removing SilverStreamSilverStream should only be removed after all desired content has been migratedto the new TIP/DV server.

About this task

To remove the SilverStream installation:


Procedure1. Shut down the SilverStream server. As root, enter the command:

/etc/init.d/SilverStream stop

2. Remove the startup/shutdown scripts. As root, enter the commands:rm /etc/init.d/SilverStreamrm /etc/rc2.d/K90Silverstreamrm /etc/rc3.d/S99Silverstream

3. Remove the SilverStream deployment. As root, change directory to whereSilverStream is installed, for example, cd /opt/silverstream.

4. Remove the contents of the SilverStream directory. As root, enter the command:rm -rf *

5. Change to the parent directory and remove the now empty SilverStreamdirectory: As root, enter the commands:cd ..rmdir silverstream

Install a libcrypto.soFor full SNMPv3 support, SNMP DataLoad must have access to the libcrypto.so.

About this task

Note: As libcrypto.so is delivered as standard on Linux platforms, steps 1 and 2are not required if you are running on Linux.

For each new and existing SNMP DataLoad, you must perform the following steps.

Procedure1. Install the OpenSSL package. This package can be downloaded from

http://www.openssl.org/.2. As root, extract and install the libcrypto.so file using the following code:

# cd /usr/lib# ar -xv ./libcrypto.a# ln -s libcrypto.so.0.9.8 libcrypto.so

3. Update the dataload.env file so that the LD_LIBRARY_PATH (on Solaris & Linux)or LIBPATH (on AIX) environment variables include the path:/ProvisoAutomation/proviso/thirdparty/openssl.org/openssl-0.9.8o/{YourOS}/lib

What to do next

Check the variable has been set by doing the following:1. Open a fresh shell2. Check the dataload.env file.3. Bounce the SNMP DL

Upon startup, with a valid library, the collector will log the following logmessages:INFO:CRYPTOLIB_LOADED Library ’libcrypto.so’ (OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008, 0x90802f) has been loaded.INFO:SNMPV3_SUPPORT_OK Full SNMPv3 support Auth(None,MD5,SHA-1) x Priv(None,DES,AES) is available.


http://www.openssl.org/

Resuming a partially successful first-time upgradeIn this scenario, you try deploying a Tivoli Netcool Performance Manager topologyfor the first time. You define the topology and start the installation. Although someof the components of the Tivoli Netcool Performance Manager topology areinstalled successfully, the overall installation does not complete successfully.

It addition, it is possible to skip a section of the installation. For example, a remotenode might not be accessible for some reason. After skipping this portion of theinstallation, resume the installation to continue with the remaining steps. Thedeployer will list only those steps needed to complete the installation on themissing node.

For example, suppose that during the first installation, Oracle wasn't running, sothe database check failed. Stop the installation, start Oracle, then resume theinstallation.

Resuming a partial upgradeTo resume a partial upgrade.

Procedure1. After correcting the problem, restart the deployer from the command line using

the following command:./deployer.bin -Daction=resume

Using the resume switch enables you to resume the installation exactly whereyou left off.

Note: If you are asked to select a topology file in order to resume yourinstallation, select the topology file you saved before beginning the install.

2. The deployer displays a welcome page. Click Next to continue.3. Accept the default location of the base installation directory of the Oracle JDBC

driver (/opt/oracle/product/version/jdbc/lib), or click Choose to navigate toanother directory. Click Next to continue.

4. The steps page shows the installation steps in the very same state they were inwhen you stopped the installation (with the completed steps marked Success,the failed step marked Error, and the remaining steps marked Held).

5. Select the step that previously failed, reset it to Ready, then click Run Next.Verify that this installation step now completes successfully.

6. Run any remaining installation steps, verifying that they complete successfully.7. At the end of the installation, the deployer loads the updated topology

information into the database.



Appendix A. Migrating DataView content and users

When upgrading your system to use Tivoli Integrated Portal, existing DataViewcontent and users are automatically migrated to Tivoli Integrated Portal. Thissection also discusses how this can be done manually.

Upgrading DataView clustersThe upgrade to IBM Tivoli Netcool Performance Manager, Version 1.3.1 meansmoving from DataView and the SilverStream application server to DataView andTIP.

Before you begin

Before upgrading Netcool/Proviso DataView in a distributed environment, verifythat:v Each SilverStream server has been shut down.v Each host has TIP/TCR 2.1 installed.v Each host has 64 bit Oracle 10.2.0 with the 10.2.0.4 patchset installed.

Migrating SilverStream content to the Tivoli Integrated PortalUse the migrate command to move SilverStream content, users, or both to theTivoli Integrated Portal.

The migrate command connects remotely to a SilverStream server and migrates allthe specified data to a Tivoli Integrated Portal installation.

The migrate command requires:

Source access credentialsSilverStream administrator user name and password

Destination access credentialsTivoli Integrated Portal administrator user name and password

You can run the migrate command from Solaris, AIX®, or Linux computers. If thereare multiple SilverMasters, you can run the migrate tool and create multiple newDataView servers from a single SilverStream computer. Refer to “The migratecommand” on page 87 for more information.

SilverStream page conversionThe migrate command performs the following processing when convertingSilverStream pages to JavaServer Pages (JSPs).

Each SilverStream page is made up of three parts:v HTML (including HTML markup, inline CSS, JavaScript, and images)v Java codev SilverStream page controls


The migrate command does not modify inline CSS, JavaScript, or images. This typeof page content is extracted from the SilverStream server and imported into TivoliIntegrated Portal unchanged.

The HTML and Java code sections are read from the page, processed andcombined to generate a new JSP.

HTML

When processing HTML sections, SilverStream page controls are replaced withcustom DataView JSP tags. For example, consider the following HTML from aSilverStream page:<div><h1><AGCONTROL name="stylesheetNameLabel"></h1></div>

That HTML is converted to the following JSP. The className attribute in the newJSP tag comes from the SilverStream page control metadata section of theSilverStream page.<<div><h1><proviso:pageControl className="com.sssw.shr.page.AgpLabel"name="stylesheetNameLabel"></h1></div>

Java code

When processing Java code sections, the code is embedded into the JSP directlyusing the standard JSP statement tag. For example, consider the following Javacode from a SilverStream page:<class SomePage extends AgpPage {

private AgpLabel label;public SomePage() {this.label.setText("foo")}}

That Java code is converted to the following JSP:<%!//class SomePage extends AgpPage {private AgpLabel label;public SomePage() {this.label.setText("foo")}}%>

All JSP fragments generated from the HTML and Java code conversion arecombined into one JSP page. When executed, this JSP page generates the sameHTML as the SilverStream page.

The resulting JSP can only be run by using the SilverStream emulation layer. If youare using unsupported SilverStream page controls (AgpTabPane,AgpImageHotSpot and AgpButtonRadio) then the resulting JSP will not workcorrectly.


The migrate commandMigrates all custom DataView content, or DataView users, from the SilverStreamserver on a previous DataView installation.

The migrate command connects remotely to a SilverStream server and migrates allthe specified data to a Tivoli Integrated Portal installation. Ensure that both theSilverStream and Tivoli Integrated Portal servers are running before running thecommand.

Location

<tip_location>/products/tnpm/dataview/legacy/bin

Where <tip_location> is the Tivoli Integrated Portal installation directory, by default/opt/IBM/tivoli/tipv2.

Required privileges

Adequate privileges are required to read and write files to the file system. Youmust run this command from the UNIX command line as the Tivoli NetcoolPerformance Manager UNIX user (by default, pvuser), or a user with similar orgreater privileges.

Syntax

migrate.sh -tipuser <tip_username> -tippassword <tip_password> -ssurl<silverstream_URL> -ssuser <silverstream_username> -sspassword<silverstream_password> -target <content|users|all> [-import ] [-verbose ]

Parameters

<tip_username>A Tivoli Integrated Portal user name for the local Tivoli Integrated Portal.

<tip_password>The Tivoli Integrated Portal user password for the local Tivoli IntegratedPortal.

<silverstream_URL>The URL of the DataView SilverStream server.

<silverstream_username>The SilverStream administrator user name.

<silverstream_password>The SilverStream administrator password.

<content|users|all>Indicates the type of data to be migrated:

content

Migrates all SilverStream content. All content is copied to the contentdirectory in the Tivoli Integrated Portal installation<tip_location>/products/tnpm/dataview/legacy/content.

Depending on the type of content, it is copied to the followingdirectories:v <tip_location>/products/tnpm/dataview/legacy/content/

SilverStream/Pages

Appendix A. Migrating DataView content and users 87

v <tip_location>/products/tnpm/dataview/legacy/content/SilverStream/Objectstore/Images

v <tip_location>/products/tnpm/dataview/legacy/content/SilverStream/Objectstore/General

users

Migrates all SilverStream users. Each user in SilverStream is either anadministrator or user. In the Tivoli Integrated Portal, the administratorrole is mapped to tnpmAdministrator, and the user role is mapped totnpmUser. The migration tool creates two user groups,tnpmAdministrators and tnpmUsers, that contain all the users withthe corresponding roles.

Password information is not migrated. Under Tivoli Integrated Portal,the password is set to be the same as the user name. For example, theSilverStream user pvuser with password pv becomes user pvuser withpassword pvuser when migrated to the Tivoli Integrated Portal.

all Exports all SilverStream content and users.

Optional parameters

-importIndicates data should be imported into the Tivoli Integrated Portal.

-verboseIndicates additional migration messages should be displayed.

Example

Run the following command as user root. Assuming a default installation, thiscommand copies all SilverStream content and users in the SilverStream serversilverstreamserver to the /opt/IBM/tivoli/tipv2/products/tnpm/dataview/legacy/content directory in a Tivoli Integrated Portal installation:

migrate.sh -tipuser <tip_username> -tippassword <tip_password>http://silverstreamserver:8080/PV -ssuser <silverstream_username>-sspassword <silverstream_password> all

Moving DataView content between Tivoli Integrated Portal serversYou can use the synchronize command to move custom DataView content betweenTivoli Integrated Portal servers.

You can copy your custom DataView content, such as JSP pages, CSS and images,from a remote Tivoli Integrated Portal server to a local Tivoli Integrated Portalserver. All remote content is copied to the local content directory at<tip_location>/products/tnpm/dataview/legacy/content.


The synchronize commandCopies custom DataView content, such as JSP pages, CSS and images, from aremote Tivoli Integrated Portal to a local Tivoli Integrated Portal. All remotecontent is copied to the local content directory at <tip_location>/products/tnpm/dataview/legacy/content.

Location

<tip_location>/products/tnpm/dataview/legacy/bin

Where <tip_location> is the Tivoli Integrated Portal installation directory, by default/opt/IBM/tivoli/tipv2.

Required privileges

Adequate privileges are required to read and write files to the file system. Youmust run this command from the UNIX command line as the Tivoli NetcoolPerformance Manager UNIX user (by default, pvuser), or a user with similar orgreater privileges.

Syntax

synchronize.sh -tipuser <tip_username -tippassword <tip_password> -sourceuser<source_username> -sourcepassword <source_password> -sourceurl <source_url>[-pattern <pattern>]

Parameters

<tip_username>A Tivoli Integrated Portal user name for the local Tivoli Integrated Portal.

<tip_password>The Tivoli Integrated Portal user password for the local Tivoli IntegratedPortal.

<source_username>A Tivoli Integrated Portal user name for the remote Tivoli Integrated Portal.

<source_password>The Tivoli Integrated Portal user password for the remote Tivoli IntegratedPortal.

<source_url>The URL of the remote server, including the port and DataView context.

Optional parameter

<pattern>The name pattern that identifies the types of files to filter for thesynchronization. Wildcards * and ? are supported. To synchronize all files, omitthe pattern; do not use * on its own to synchronize all files.

Example

The following command synchronizes the DataView custom .jsp file content froma remote Tivoli Integrated Portal to a local Tivoli Integrated Portal:

Appendix A. Migrating DataView content and users 89

synchronize.sh -tipuser <tip_username> -tippassword <tip_password>-sourceuser <source_username> -sourcepassword <source_password>https://server.ibm.com:16711:PV *.jsp


Appendix B. Backup Modification

Customers that have already implemented the Tivoli Netcool PerformanceManager backup and recovery strategy must carry out the steps described in thissection.

If you have previously enabled Tivoli Netcool Performance Manager backup, youmust perform these steps in order for your backups to continue working properly.

Prior practice

Prior to this release, customers were required to modify a DataChannelconfiguration parameter (SHOULD_CHECK_DB_TO_DELETE_EOP) to enablebackups. This DataChannel parameter is no longer used. Control of the databasebackup implementation has moved to a new database registry parameter,DATABASE.BACKUP.

Upgrading the database backup procedureTo enable the new database registry parameter, you must modify the followingregistry flag:

About this task

DATABASE.BACKUP.STATE : The default value of this flag is 0. To enable backupsyou must update this flag to 1.

To edit this flag:

Procedure1. Execute the command

$ dbRegEdit pv_admin/pv DATABASE.BACKUP

Will open the default editor and show you the following:

+- BACKUP| +- READONLY_TIMEOUT : NUMBER : "129600"| +- READONLY_DELAY : NUMBER : "7200"| +- RESIZE_TIMEOUT : NUMBER : "120"| +- RESIZE_RETRIES : NUMBER : "15"| +- STATE : NUMBER : "0"

2. Modify the line:| +- STATE : NUMBER : "0"

So that it looks like:| +- STATE : NUMBER : "1"

3. Save the file. You should then see a message indicating a successful update:Configuration updated !

Note: Consult the Registry and Space Management Technote for moreinformation on using the dbRegEdit utility.

4. Log into sqlplus as PV_ADMIN and execute the following:SQL> Exec Pvm_Backup.Reinit;


This is a required step that will reinitialize the package variables used by thePVM_BACKUP procedure.

What to do next

Again, if you have previously enabled backup, you must perform these steps inorder for your backups to continue working properly.


Appendix C. Deployment Considerations

Remote installation of all Tivoli Netcool Performance Manager components issupported. However, there may arise situations where a remote host does notsupport FTP or the remote execution of files.

A remote host (a remote host is any host included in the topology that is not thehost running the Topology Editor) may not support FTP or the remote execution offiles.

It is possible your topology may include hosts one which:v FTP is possible, but REXEC/RSH are not.v Neither FTP nor REXEC/RSH are possible

This section describes how to deploy in these situations.

FTP is possible, but REXEC or RSH are notFor any remote host where FTP is possible, but REXEC or RSH are not,deployment of the required component or components must be carried out usingthe following steps.

There are two options for deployment.v Option 1:

1. Unselect the Remote Command Execution option during the installation.The deployer creates and transfers the directory with the required componentpackage in it.

2. As root, log in to the remote system and manually run the run.sh script.v Option 2:

1. Connect to the remote machine and launch the deployer again (either ingraphical or CLI mode) using the product CD.If the CD is not available, you can FTP or NFS the required componentdirectory and deployer package to the remote machine.

2. The deployer connects to the database.3. Install the required component component.

Neither FTP nor REXEC/RSH are possibleFor any remote host where neither FTP nor REXEC or RSH are possible thedeployment of the required component or components must be carried out usingthe following steps.

There are two options for deployment.v Option 1:

1. Unselect the FTP option during the installation.The deployer creates a directory with the required component package in it.

2. Copy the required component directory to the target system.3. As root, log in to the remote system and manually run the run.sh script.


v Option 2:1. Connect to the remote machine and launch the deployer again (either in

graphical or CLI mode) using the product CD.If the CD is not available, you can FTP or NFS the required componentdirectory and deployer package to the remote machine.

2. The deployer connects to the database, then installs the required componenton this machine.


Appendix D. Oracle Bug

If the database you are upgrading was originally installed as Oracle 8i, you mustapply the workaround discussing in Oracle support note 272413.1.

This is the workaround for an Oracle bug that occurred during the upgrade ofOracle 8i to Oracle 9i. This workaround must be applied before beginning theProviso upgrade.

The root of the issue is that one of the Oracle system privileges has an incorrectname. The problem is demonstrated by the following:

Run the query:SQL> Select NameFrom SYSTEM_PRIVILEGE_MAPWhere privilege=-244;NAME----------------------------------------GRANT ANY OBJECT PRIVILEGESQL>

However, on a system that was orignally upgraded from Oracle 8i to Oracle 9i youwill instead see:SQL> Select NameFrom SYSTEM_PRIVILEGE_MAPWhere privilege=-244;NAME----------------------------------------GRANT ANY OBJECT PRIVILEGESSQL>

Notice the extra "S" at the end of the privilege name. The workaround documentedin Oracle support note 272413.1 is as follows:

Workaround

To eliminate this mistake, do the following:

Logon as sysdba and execute the following 2 statements:update SYSTEM_PRIVILEGE_MAP set name=’GRANT ANY OBJECT PRIVILEGE’where privilege=-244;update STMT_AUDIT_OPTION_MAP set name=’GRANT ANY OBJECT PRIVILEGE’where option#=244;commit;



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


��

Printed in USA

Documents

IBM Tivoli Netcool Performance Manager: Upgrade Guide: 4.4.1 to 1.3 · · 2011-01-14Tivoli ® Netcool Performance Manager 1.3.1 Wireline Component ... Chapter 1. Introduction