IBM Tioli Netcool Performance Manager 1.3.2 Wireline Component Document Reision R2E2 Upgrade Guide 1.3.1 to 1.3.2
Note Before using this information and the product it supports, read the information in Notices on page 113. Copyright IBM Corporation 2006, 2013. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents About this information........ Intended audience............ Tioli Netcool Performance Manager - Wireline Component............... Serice Management Connect........ i Tioli technical training.......... ii Support information........... ii Conentions used in this publication...... ii Typeface conentions.......... ii DataView load balancing......... 26 Oracle database............ 26 Oracle serer............. 26 Tioli Common Reporting client...... 27 Jaa Runtime Enironment (JRE)...... 27 Web browsers and settings........ 27 X Emulation............. 29 WebGUI integration.......... 29 Microsoft Office Version......... 30 Chapter 1. Introduction........ 1 Summary of upgrade tasks......... 1 Verifying your Tioli Netcool Performance Manager enironment.............. 2 Supported upgrade paths for Tioli Netcool Performance Manager.......... 2 Supported platforms........... 2 Supported topology........... 3 VLN check.............. 4 Installing the pre-requisite software....... 4 Planning your upgrade........... 5 Tioli Netcool Performance Manager distribution 5 Backing up your current Tioli Netcool Performance Manager enironment...... 5 Clustering and high aailability....... 6 Report and user name duplicate pre-check.... 6 Pre-checking for report duplicates...... 7 Report user pre-check.......... 8 Chapter 2. Requirements....... 9 Minimum requirements for installation..... 9 Solaris hardware requirements....... 9 AIX hardware requirements........ 10 Linux hardware requirements....... 10 Oracle deployment space requirements.... 11 Tioli Integrated Portal deployment space requirements............. 11 Screen resolution........... 12 Minimum requirements for a proof of concept installation.............. 12 Solaris hardware requirements (POC)..... 12 AIX hardware requirements (POC)..... 12 Linux hardware requirements (POC)..... 13 Screen resolution........... 13 Supported operating systems and modules.... 13 Solaris 10 for SPARC platforms....... 13 AIX platforms............ 17 Linux platforms............ 21 Required user names........... 23 puser............... 24 oracle............... 24 Ancillary software requirements....... 24 FTP support............. 24 Open SSH and SFTP.......... 25 File compression............ 26 Chapter 3. Downloading the Tioli Netcool Performance Manager distribution to disk......... 31 Downloading the Tioli Common Reporting distribution.............. 31 Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2........... 33 Install Oracle 11.2.0.2 client (32-bit)...... 34 Download the Oracle distribution to disk... 34 Run the Oracle client configuration script... 35 Set a password for the Oracle login name... 37 Run the preinstallation script....... 37 Verify PATH and Enironment for the Oracle login name............. 38 Install the Oracle client (32-bit)....... 38 Run the root.sh script.......... 40 Update the oracle user's.profile...... 41 Configure the Oracle Net client....... 42 Install Oracle 11.2.0.2 serer (64-bit)...... 44 Download the Oracle distribution to disk... 44 Verify the required operating system packages.. 45 Run the Oracle serer configuration script... 45 Set a password for the Oracle login name... 48 Run the preinstallation script....... 48 Run the rootpre.sh script (AIX only)..... 49 Verify PATH and Enironment for the Oracle login name............. 49 Install Oracle using the menu-based script... 50 Run the root.sh script.......... 52 Set the ORACLE_SID ariable....... 53 Perform Oracle Upgrade Preparation...... 54 Shutting down the Tioli Netcool Performance Manager components.......... 54 Backup database............ 56 Run and spool the utlu112i.sql file..... 56 Make sure the database starts and ends in a similar state............. 59 Verify that there is no database data dictionary corruption.............. 60 Stop the database listener......... 61 Verify no data files need recoery...... 61 Verify no data files in backup mode..... 61 Verify that there are no pending Distributed Transactions............. 61 Copyright IBM Corp. 2006, 2013 iii
Verify SYS and SYSTEM users hae a default SYSTEM tablespace........... 62 Verify the AUD$ table is located in the SYSTEM tablespace.............. 62 Verify there are no externally authenticated SSL users............... 63 Make note of all sysdba users....... 63 Shut down database.......... 63 Perform the Oracle upgrade......... 64 Modify the database initpv.ora file..... 64 Verify the NLS_LANG parameter is set to WE8ISO8859P1............. 65 Copy tnsnames.ora, sqlnet.ora, and listener.ora files to the new ORACLE_HOME. 65 Copy the password file from the old home to the new home.............. 65 Create soft links in the new ORACLE_HOME.. 65 Update the oratab entry for this database... 66 Update the oracle user's.profile...... 66 Confirm the enironment ariables hae been reset................ 66 Startup upgrade............ 67 Enter a spool command, and run the upgrade script catupgrd.sql........... 68 Disable stats............. 68 Run utlu112s.sql........... 69 Shut down database.......... 69 Restart the database.......... 70 Run the utlrp.sql script......... 70 Check for inalid objects......... 71 Shut down database.......... 71 Modify the database initpv.ora compatible parameter.............. 72 Change listener.ora to use the new ORACLE_HOME........... 72 Restart the listener........... 72 Starting the Tioli Netcool Performance Manager components............. 73 Chapter 5. Upgrading Tioli Integrated Portal and Tioli Common Reporting.. 77 Upgrading to Tioli Integrated Portal 2.2.... 77 Upgrading to Tioli Common Reporting 2.1.1... 78 Chapter 6. Upgrading Tioli Netcool Performance Manager........ 81 Shutting down the Tioli Netcool Performance Manager components........... 81 Disabling the cron Jobs......... 82 Shutting down DataChannel........ 82 Shutting down DataMart......... 83 Verifying Netcool/Proiso components are shut down............... 84 Installing and starting the Topology Editor.... 84 Starting the Launchpad......... 85 Installing the Topology Editor....... 85 Starting the Topology Editor........ 87 Loading the upgrade topology into the Topology Editor................ 88 Preparing the upgrade topology for deployment.. 89 Technology packs........... 89 Determining alid host definitions...... 89 Moing Tioli Netcool Performance Manager components between host definitions..... 90 Deleting extraneous host definitions..... 91 Renaming host definitions........ 91 Verifying host properties......... 91 Verifying Tioli Netcool Performance Manager component properties.......... 92 Remoing unused custom properties..... 92 Saing the upgrade topology....... 93 Deploying the upgrade topology....... 93 Deploy the upgrade topology for all components 94 Deploy the upgrade topology to minimize collections loss............ 96 Update the datamart.en file....... 98 Starting the Tioli Netcool Performance Manager components.............. 98 Starting the cron jobs.......... 98 Starting DataMart........... 99 Starting DataView........... 99 Starting DataChannel.......... 99 Chapter 7. Post upgrade steps.... 101 Run the deploy_war.sh script........ 101 Install a libcrypto.so........... 102 Post upgrade HAM configuration...... 102 Upgrade Common Pack Serice....... 103 Upgrading the Base Common Pack Suite.... 103 The Base Common Pack Suite....... 104 Chapter 8. Enabling Tioli Common Reporting on Tioli Netcool Performance Manager........ 105 Chapter 9. Resuming a partially successful first-time upgrade.... 107 Resuming a partial upgrade........ 107 Appendix A. Backup Modification... 109 Upgrading the database backup procedure... 109 Appendix B. Deployment Considerations........... 111 FTP is possible, but REXEC or RSH are not... 111 Neither FTP nor REXEC/RSH are possible.... 111 Notices.............. 113 i IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
About this information Intended audience IBM Tioli Netcool Performance Manager, Version 1.3.2 is a bundled product consisting of two main components. A wireline component (formerly Tioli Netcool/Proiso), and a wireless component (formerly Tioli Netcool Performance Manager for Wireless). The IBM Tioli Netcool Performance Manager: Upgrade Guide describes how to upgrade your IBM Tioli Netcool Performance Manager enironment. This guide assumes you are a network administrator or operations specialist who has knowledge of network management and installing applications on operating systems. The audience for this manual is the network administrator or operations specialist responsible for upgrading the Tioli Netcool Performance Manager product suite on an enterprise network. To upgrade Tioli Netcool Performance Manager successfully, you should hae a thorough understanding of the following subjects: Basic principles of TCP/IP networks and network management SNMP concepts Administration of the Solaris, Linux or AIX operating enironment Administration of the Oracle database management system Tioli Netcool Performance Manager Administrators who assign permissions, create groups, and associate users with reports. Adanced users or content designers who work with style sheets and reporters to extend the capabilities of Tioli Netcool Performance Manager technology packs. Tioli Netcool Performance Manager - Wireline Component IBM Tioli Netcool Performance Manager consists of a wireline component (formerly Netcool/Proiso) and a wireless component (formerly Tioli Netcool Performance Manager for Wireless). Tioli Netcool Performance Manager - Wireline Component consists of the following subcomponents: DataMart is a set of management, configuration, and troubleshooting GUIs. The Tioli Netcool Performance Manager System Administrator uses the GUIs to define policies and configuration, and to erify and troubleshoot operations. DataLoad proides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. DataChannel aggregates the data collected through Tioli Netcool Performance Manager DataLoad for use by the Tioli Netcool Performance Manager DataView reporting functions. It also processes online calculations and detects real-time threshold iolations. DataView is a reliable application serer for on-demand, web-based network reports. Copyright IBM Corp. 2006, 2013
Technology Packs extend the Tioli Netcool Performance Manager system with serice-ready reports for network operations, business deelopment, and customer iewing. The following figure shows the different Tioli Netcool Performance Manager modules. Tioli Netcool Performance Manager documentation consists of the following: Release notes Configuration recommendations User guides Technical notes Online help The documentation is aailable for iewing and downloading on the information center at http://publib.boulder.ibm.com/infocenter/tiihelp/8r1/topic/ com.ibm.tnpm.doc/welcome_tnpm.html. Serice Management Connect Connect, learn, and share with Serice Management professionals: product support technical experts who proide their perspecties and expertise. Access Serice Management Connect at https://www.ibm.com/deeloperworks/ sericemanagement/. Use Serice Management Connect in the following ways: Become inoled with transparent deelopment, an ongoing, open engagement between other users and IBM deelopers of Tioli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. i IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Tioli technical training Support information Connect one-on-one with the experts to collaborate and network about Tioli and the (enter your community name here) community. Read blogs to benefit from the expertise and experience of others. Use wikis and forums to collaborate with the broader user community. For Tioli technical training information, see the following IBM Tioli Education website at http://www.ibm.com/software/tioli/education. If you hae a problem with your IBM software, you want to resole it quickly. IBM proides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at http://www.ibm.com/software/ support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software sericeability workbench that helps you resole questions and problems with IBM software products. The Support Assistant proides quick access to support-related information and sericeability tools for problem determination. To install the Support Assistant software, go to http://www.ibm.com/software/ support/isa. Troubleshooting Guide For more information about resoling problems, see the problem determination information for this product. Conentions used in this publication Seeral conentions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system Typeface conentions This publication uses the following typeface conentions: Bold Italic Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) Keywords and parameters in text Citations (examples: titles of publications, diskettes, and CDs Words defined in text (example: a nonswitched line is called a point-to-point line) Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictie clause."; letters as letters example: "The LUN address must start with the letter L.") About this information ii
New terms in text (except in a definition list): a iew is a frame in a workspace that contains data. Variables and alues you must proide:... where myname represents... Monospace Examples and code examples File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Bold monospace Command names, and names of macros and utilities that you can type as commands Enironment ariable names in text Keywords Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters Process names Registry ariable names in text Script names iii IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 1. Introduction Summary of upgrade tasks This chapter proides information concerning requirements and considerations that must be satisfied before you upgrade your Tioli Netcool Performance Manager enironment. A summary of the Tioli Netcool Performance Manager 1.3.1 to 1.3.2 upgrade process. Before you begin This guide assumes that you hae a fully functioning Tioli Netcool Performance Manager 1.3.1 enironment. In order to upgrade your enironment to IBM Tioli Netcool Performance Manager, Version 1.3.2, you must: 1. Verify that your enironment is running the supported ersions of both the prerequisite software and Tioli Netcool Performance Manager. For more information, see Verifying your Tioli Netcool Performance Manager enironment on page 2 2. Install the arious software packages required to facilitate and support the upgrade and the successful operation of Tioli Netcool Performance Manager. For more information, see Installing the pre-requisite software on page 4. 3. Reiew your upgrade plan and topology. For more information, see Planning your upgrade on page 5. 4. Check your existing system for duplicate report references and duplicate report user names. For more information, see Report user pre-check on page 8. 5. Download the Tioli Netcool Performance Manager and Tioli Common Reporting distribution to disk. For more information, see Chapter 3, Downloading the Tioli Netcool Performance Manager distribution to disk, on page 31. 6. Start the launchpad and Install the new Tioli Netcool Performance Manager 1.3.2 Topology Editor. 7. Update topology for deployment in your enironment. For more information, see Preparing the upgrade topology for deployment on page 89. 8. Shut down Tioli Netcool Performance Manager. For more information, see Shutting down the Tioli Netcool Performance Manager components on page 81. 9. Deploy the upgrade topology. For more information, see Deploying the upgrade topology on page 93. 10. Startup Tioli Netcool Performance Manager. For more information, see Starting the Tioli Netcool Performance Manager components on page 73. Copyright IBM Corp. 2006, 2013 1
Verifying your Tioli Netcool Performance Manager enironment To complete a Tioli Netcool Performance Manager upgrade your system must meet certain requirements. Before beginning an upgrade procedure, you must erify that your enironment meets the requirements set out in this document to ensure a smooth upgrade process. Supported upgrade paths for Tioli Netcool Performance Manager The tools and procedures described in this guide are intended to support a limited number of upgrade paths to IBM Tioli Netcool Performance Manager, Version 1.3.2. If you need to find ersion information for the Tioli Netcool Performance Manager components installed in your enironment, use the Tioli Netcool Performance Manager Info Tool as described in the Tioli Netcool Performance Manager Technical Note: Tools for Version Reporting. Consult the table below to determine what you need to do for your enironment: Table 1. Tioli Netcool Performance Manager ersion Tioli Netcool Performance Manager 1.3.1 Tioli Netcool Performance Manager Technology Packs Supported Upgrade Path You must be running Tioli Netcool Performance Manager 1.3.1 before you can upgrade directly to IBM Tioli Netcool Performance Manager, Version 1.3.2. You do not hae to upgrade your technology packs to upgrade to IBM Tioli Netcool Performance Manager, Version 1.3.2. If you are running the Tioli Netcool Performance Manager Alcatel 5620 SAM or Cisco Netflow Technology Packs, you must refer to Chapter 3, Upgrading Technology Packs for more information. Supported platforms The upgrade of Tioli Netcool Performance Manager is limited to a number of platforms. Refer to the following table for platform requirement information. 2 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Table 2. Supported Platforms Tioli Netcool Performance Manager component Required Platform Tioli Netcool Performance Manager Database Tioli Netcool Performance Manager DataView Tioli Netcool Performance Manager DataChannel Solaris 10 64-bit AIX 6.1 TL 02 SP1 ("6100-02-01), 64-bit AIX 7.1 TL 0 SP1 ("7100-00-01"), 64-bit RHEL 5.5, 64-bit Tioli Netcool Performance Manager DataLoad Tioli Netcool Performance Manager DataMart Migrating between platforms It is possible to migrate components between platforms when performing the Tioli Netcool Performance Manager upgrade. The only supported migration path is from Solaris to AIX. There is no support for any other platform migration scenario. Supported topology The upgrade procedure supports a typical deployment of Netcool/Proiso where one SNMP collector runs per physical host. If you find that your enironment does not meet this requirement, contact Professional Serices for more information. Upgrade is also supported for enironments that use the following optional adanced configurations: Remote collector or remote Complex Metric Engine (CME). No special actions are required to upgrade an enironment that contains a remote CME deployment. DataLoad High Aailability Manager (HAM). No special actions are required to upgrade an enironment that contains a DataLoad HAM deployment. Note: If you plan to make the changes to your Tioli Netcool Performance Manager enironment, such as adding or remoing hosts, components, or deploying an adanced configuration. Before you make changes, you must upgrade your existing enironment first. Chapter 1. Introduction 3
VLN check Before running the upgrade procedure, you must ensure that your database is at the appropriate ersion leel. The database must be at ersion 1.3.1. To alidate that the database is at this ersion, run the following query as <DB_USER_ROOT>_ADMIN: select str_alue from reg_database where str_path = DATABASE.GENERAL.VLN ; The return alue for 1.3.1 should be: DB131016000 Installing the pre-requisite software Before beginning to upgrade your Tioli Netcool Performance Manager enironment, you must install the prerequisite software. Before beginning to upgrade your Tioli Netcool Performance Manager enironment, you must install the prerequisite software listed in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide, including: Oracle You must upgrade Oracle before you can begin to upgrade your Tioli Netcool Performance Manager enironment. You must upgrade the Oracle Serer software and the Oracle Client software on each system that hosts a Tioli Netcool Performance Manager component. For instructions, see the Oracle documentation that accompanies the Oracle Serer and Oracle Client software. The system hosting the Tioli Netcool Performance Manager Database must hae installed the Oracle Serer: Oracle 11g. Any system hosting any of the other components, must hae installed the Oracle Client: 64 bit Oracle 11g. OpenSSH If you plan to use Remote Command Execution or transfer files using SCP/SFTP, you must install and configure OpenSSH before upgrading Tioli Netcool Performance Manager. For more information, see the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide for supported ersions and the Secure File Transfer Installation chapter of the IBM Tioli Netcool Performance 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 the launchpad. For the complete list of supported browsers, see the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. Jaa Jaa is used by DataMart, DataLoad, and technology packs. For more information, see the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide for supported ersions. 4 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Acrobat Reader Planning your upgrade Adobe Acrobat Reader is free software that enables you to read the Tioli Netcool Performance Manager documentation deliered in Portable Document Format (PDF). If you already hae Acrobat installed, you do not need to install Acrobat again. Note that on AIX systems, Acrobat Reader requires the GIMP Toolkit (GTK+) and seeral additional libraries. See the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide for more information. You can download Adobe Reader from the Adobe web site. Careful planning is required in upgrading your Tioli Netcool Performance Manager enironment to ensure that the upgrade procedure progresses without issues. Tioli Netcool Performance Manager distribution The Tioli Netcool Performance Manager distribution is aailable as a DVD/CD and as an electronic image. The instructions in this guide assume that you are installing from an electronic image. If you install the product from an electronic image, be sure to keep a copy of the distribution image in a well-known directory, because you will need this image in the future to make any changes to the enironment. The Tioli Netcool Performance Manager distribution DVD/CD contains: Tioli Netcool Performance Manager 1.3.2 Model Maker IBM Cognos Edition ersion 1.2.0. Base Common Pack suite (1.0.0.3-TIV-TNPM-BCPSUITE.tar.gz). Backing up your current Tioli Netcool Performance Manager enironment This section is included as a reminder that performing regular backups of the systems in your Tioli Netcool Performance Manager enironment is important. Backup is especially important before a major change such as an upgrade procedure is performed on a system. Backing up the database It is recommended that you perform regular backups of the Tioli Netcool Performance Manager Database, and it is recommended that you perform a cold backup of the Database before beginning an upgrade procedure. For information on Database backup and recoery, see the IBM Tioli Netcool Performance Manager: Database Administrator's Guide. Chapter 1. Introduction 5
Backing Up DataChannel It is recommended that you backup the DataChannel directories (/opt/datachannel, by default) on each host after the DataChannel components and processes hae been shut down. Backing Up DataLoad It is recommended that you back up the DataLoad directories (/opt/dataload, by default) on each host before beginning an upgrade procedure. Backing Up DataMart While the upgrade procedure automatically backs up files that you may hae changed, it is recommended that you backup the DataMart directories (/opt/datamart, by default) on each host before beginning an upgrade procedure. Backing Up DataView To back up DataView, do the following: 1. As root, use the export command to extract the DataView content from the TIP deployment. export.sh tiplocation tipuser tippassword For example: export.sh /opt/ibm/tioli/tip tipadmin tipadmin 2. Backup the <TIP>/products/tnpm/dataiew directory using the preferred backup utility. Clustering and high aailability If you are planning on Installing Tioli Netcool Performance Manager as a distributed enironment that uses clustering for high aailability, please reiew the Tioli Netcool Performance Manager HA (Hight Aailability) documentation. Tioli Netcool Performance Manager HA (Hight Aailability) documentation is aailable for download by going to http://www-01.ibm.com/software/ brandcatalog/opal/ and searching for Netcool Proiso HA Documentation. Report and user name duplicate pre-check The report and user name duplicate pre-check is a manual step to be performed before the upgrade. In the 1.3.2 upgrade there are two required pre-checks: A check for reports that are duplicated across multiple report groups. A check for duplicate report user names. Note: The upgrade process runs each pre-check to erify that you can proceed with the upgrade. 6 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Pre-checking for report duplicates A report must be referenced in one report group. About this task Locate any duplicate reports that occur on your system. Determine which report groups must contain the report, and delete the report from all other report groups by completing the following steps: 1. 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: 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_MEMBER Where Idx_App In ( Select Idx_App From APP_GRP_APP_MEMBER Group By Idx_App Haing Count(*) > 1); LEAFGRP APPGRPNAME IDX_APP APPNAME ---------- -------------------- ---------- ---------------------------------------- 998 Sample3 49000033 Metric Diagnostic Report 999 Sample4 49000033 Metric Diagnostic Report 3. Determine the full path for the report group by executing the following query for each group found in the preious query. This query generates a simple stepped' output that starts with the root node for the group. Each subsequent group is then indented two spaces. This information helps in determining the groups from which to remoe the report. SQL> Select LPAD(, 2*(Rownum-1)) Str_Name as AppGrpName From ( Select ll, agd.str_name From ( Select Leel as Ll, Idx_Group_Child From APP_GRP_GROUP Connect By Prior Idx_Group_Parent = Idx_Group_Child Start With Idx_Group_Child = 999) agg, APP_GRP_DESC agd Where agg.idx_group_child = agd.idx_ind Order By agg.ll Desc); STR_NAME ------------------------------ GST Sample4 4. Delete the appropriate report-report group linkage: SQL> Delete From APP_GRP_APP_MEMBER Where Idx_App = 49000033 And 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 remoe all duplicates. Chapter 1. Introduction 7
Report user pre-check There might be duplicate report usernames. About this task Locate any duplicate report user names that exist in your system and rename them, then use the normal interface to update the user. You can achiee this by completing the following steps: 1. Search for duplicate report user names by logging on to sqlplus as PV_ADMIN and issuing the following query SQL> Select Idx_ind, Str_Name, Str_Email_Address, Str_User_Type From RUSER_DESC Where Str_Name IN ( Select Str_Name From RUSER_DESC Group By Str_Name Haing Count(*) > 1); IDX_IND STR_NAME STR_EMAIL_ADDRESS STR_USER_TYPE ---------- ------------------------------ ------------------------------ ---------------- 100037133 John Doe johndoe@us.ibm.com EMAIL RECIPIENT 100021639 John Doe janedoe@us.ibm.com EMAIL RECIPIENT 2. Rename the User: SQL> Update RUSER_DESC Set 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 rename all of the duplicates. 8 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 2. Requirements Details of all Tioli Netcool Performance Manager requirements. Requirements are the complete set of requirements for Tioli Netcool Performance Manager 1.3.2. IBM Prerequisite Scanner IBM Prerequisite Scanner is a stand-alone prerequisite checking tool that analyzes system enironments before the installation or upgrade of a Tioli product or IBM solution. The IBM Prerequisite Scanner can be used to check for the presence of Tioli Netcool Performance Manager requirements. Instructions describing how to use and install the IBM Prerequisite Scanner are aailable at http://www-01.ibm.com/support/dociew.wss?uid=swg24029221. Minimum requirements for installation The minimum required host specifications for a Tioli Netcool Performance Manager deployment. Solaris hardware requirements Tioli Netcool Performance Manager hardware requirements for the Solaris enironment. Tioli Netcool Performance Manager has the following minimum hardware requirements for the Solaris enironment. 4 x SPARC64 VI (dual-core) 2.4GHz or 3 x SPARC64 VII (quad-core) 2.88GHz processor Note: DataLoad requires irtualization (Solaris zones). For more information, please see DataLoad SNMP on multiple CPU serers on page 10. 16 GB Memory 2 x 146GB HDD If deploying in a distributed enironment, each serer/zone requires: 1 x SPARC64 VI (dual-core) 2.4GHz or 1 x SPARC64 VII, (quad-core) 2.88GHz processor; 4 GB RAM; 146GB disk space. Note: For information about performing a minimal installation deployment, see the IBM Tioli Netcool Performance Manager: Installation Guide. Copyright IBM Corp. 2006, 2013 9
DataLoad SNMP on multiple CPU serers Serer requirements for DataLoad SNMP Tioli Netcool Performance Manager DataLoad SNMP Collector supports only single and dual CPU serers. Installing Tioli Netcool Performance Manager DataLoad SNMP Collector on serers haing more than two CPUs will cause performance problems. This is not a supported configuration, unless a Solaris 10 container (or another irtual partitioning mechanism on AIX or RedHat Enterprise Linux) isolates the collector on a irtual host that has no more than two CPUs. It is recommended that you install Tioli Netcool Performance Manager DataLoad SNMP Collectors on different systems from Tioli Netcool Performance Manager DataMart, Tioli Netcool Performance Manager Database, Tioli Netcool Performance Manager DataView, and other DataLoad SNMP or Bulk Collectors. For demonstrations, ealuations, and small amounts of data collection, you can install the preiously listed components on the same system. These restrictions do not apply to a Tioli Netcool Performance Manager DataLoad Bulk Collector. AIX hardware requirements Tioli Netcool Performance Manager hardware requirements for the AIX enironment. Tioli Netcool Performance Manager has the following minimum requirements for the AIX enironment: 4 x Power6 (Dual Core) 4.2GHz, or 3 x Power7 (Quad Core) 3.0GHz processor. Note: DataLoad requires irtualization (LPARs). For more information, please see DataLoad SNMP on multiple CPU serers. 16 GB Memory 2 x 146GB HDD If deploying in a distributed enironment, each serer/lpar requires: 1 x Power6 (Dual Core) 4.2GHz, or 1 x Power7 (Quad Core) 3.0GHz processor; 4 GB RAM; 146 GB disk space. Other deployment configurations should be sized by IBM Professional Serices. Linux hardware requirements Tioli Netcool Performance Manager has a minimal deployment space requirement on Linux Tioli Netcool Performance Manager has the following minimum requirements for the Linux enironment: 3 x Intel Xeon 5500/5600 series processors (quad-core), 2.4 GHz or greater. Note: DataLoad requires irtualization (Virtual Machine). For more information, please see DataLoad SNMP on multiple CPU serers. 16 GB memory 10 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
2 x 146 GB HDD If deploying in a distributed enironment, each serer/virtual Machine requires: 1 x Intel Xeon 5500/5600 series processor (quad-core) 2.4 GHz, 4 GB RAM, 146 GB disk space. Other deployment configurations should be sized by IBM Professional Serices. Oracle deployment space requirements Tioli Netcool Performance Manager has a minimal deployment space requirement for the Oracle serer. When you install Oracle the following host must confirm the preiously stated hardware requirements for AIX, Solaris and Linux. Howeer, Oracle may experience problems if sufficient swap space is not proided. The same amount of Swap as RAM must be present on the Oracle serer host in a distributed Tioli Netcool Performance Manager system. Twice as much Swap as RAM must be present on the Oracle serer host for a Tioli Netcool Performance Manager proof of concept install. Tioli Integrated Portal deployment space requirements Tioli Netcool Performance Manager has a minimal deployment space requirement for Tioli Integrated Portal When you install DataView, you also install Tioli Common Reporting (TCR). When performing a remote install a local /tmp folder is required on the deployer in order to contain the TCR bundle. The space requirements are: Local Tioli Integrated Portal install: /TIP install location - 2GB Remote Tioli Integrated Portal install local /tmp - 1.5GB remote /tmp - 1.5GB remote /TIP install location - 2GB Note: If you deploy many technology packs (especially Alcatel-Lucent 5620 SAM, Alcatel 5620 NM, and Nortel CS2000, which either hae multiple UBAs or require multiple DataChannel applications), you might require more hardware capacity than is specified in the minimal configuration. In these situations, before moing to a production enironment, IBM strongly recommends that you hae IBM Professional Serices size your deployment so that they can recommend additional hardware, if necessary. Chapter 2. Requirements 11
Screen resolution Recommended screen resolution details. A screen resolution of 1024 x 768 pixels or higher is recommended when running the deployer. Minimum requirements for a proof of concept installation Tioli Netcool Performance Manager has minimum required host specifications for Proof of Concept (POC) deployments. Note: The minimum requirements do not account for additional functionality such as WebGUI, Cognos and MDE, each hae additional memory and CPU impacts. Solaris hardware requirements (POC) The minimum system requirements for a proof of concept install on Solaris. 2 x SPARC64 VI (dual-core) 2.4GHz or 2 x SPARC64 VII (quad-core) 2.88GHz processor. 8GB Memory 1 x 146 GB HDD To support: SNMP data only. All Tioli Netcool Performance Manager components deployed on a single serer. Number of resources supported up to 20,000. 3 SNMP Technology Packs based on MIB II, Cisco Deice and IPSLA. 15 minute polling Number of DataView users limited to less than three. AIX hardware requirements (POC) The minimum system requirements for a proof of concept install on AIX. 2 x Power6 (Dual Core) 4.2GHz, or 2 x Power7 (Quad Core) 3.0GHz processor 8 GB Memory 1 x 146 GB HDD To support: SNMP data only. All Tioli Netcool Performance Manager components deployed on a single serer. Number of resources supported up to 20,000. 3 SNMP Technology Packs based on MIB II, Cisco Deice and IPSLA. 15 minute polling Number of DataView users limited to less than three. Note: Additional features such as WebGUI and Mass Data Extraction (MDE) are not accounted for in this spec. They will hae additional memory and CPU impacts. 12 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Linux hardware requirements (POC) The minimum system requirements for a proof of concept install on Linux. 2 x Intel Xeon 5500/5600 series processors (quad-core), 2.4 GHz or greater 8 GB memory 1 x 146 GB HDD To support: SNMP data only All Tioli Netcool Performance Manager components deployed on a single serer Number of resources supported up to 20,000 3 SNMP Technology Packs based on MIB II, Cisco Deice and IPSLA 15 minute polling Number of DataView users limited to less than three Screen resolution Recommended screen resolution details. A screen resolution of 1024 x 768 pixels or higher is recommended when running the deployer. Supported operating systems and modules The supported operating systems, modules, and third-party applications for IBM Tioli Netcool Performance Manager, Version 1.3.2. The following sections list the supported operating systems, modules, and third-party applications for IBM Tioli Netcool Performance Manager, Version 1.3.2. All subcomponents of the Tioli Netcool Performance Manager - Wireline Component can be installed on a mix of AIX, Linux, and Solaris operating systems; that is, the operating systems on which the DataChannel, DataView, DataLoad and DataMart subcomponents are installed do not hae to be of the same type. The supported ersions of AIX, Linux and Solaris operating systems are discussed in this document. For more information, see the Release notes - IBM Tioli Netcool Performance Manager, Version 1.3.2, which contains the ersion numbers for each Tioli Netcool Performance Manager module in Version 1.3.2. Solaris 10 for SPARC platforms Supported Solaris systems. Operating systems and kernel Supported operating system and kernel ersion. Solaris 10 Update 6 (released in October, 2008). Update leel can be checked from /etc/release file. Chapter 2. Requirements 13
Applying a kernel patch or a Solaris patch bundle is not the equialent to installing the specific Solaris 10 "update 6" image. Oracle 11gR2 RDBMS software is only certified for a base install image of Solaris 10 update 6 or greater. For additional detail, please see Document 971464.1, FAQ - 11gR2 requires Solaris 10 update 6 +. Kernel Parameters Solaris 10 uses the resource control facility to implement the System V IPC. Howeer, Oracle recommends that you set both resource control and /etc/system/ parameters. Operating system parameters not replaced by resource controls continue to affect performance and security on Solaris 10 systems. Parameter Replaced by Resource Control Minimum Value noexec_user_stack NA (can be set in /etc/system only) 1 semsys:seminfo_semmni project.max-sem-ids 100 semsys:seminfo_semmsl process.max-sem-nsems 256 shmsys:shminfo_shmmax project.max-shm-memory 4294967295 shmsys:shminfo_shmmni project.max-shm-ids 100 Note: "project.max-shm-memory" represent the maximum shared memory aailable for a project, so the alue for this parameter should be greater than sum of all SGA size. Refer to the following document for checking/setting kernel parameter alues using resource control :- Note 429191.1 Kernel setup for Solaris 10 using project files. The 'umask' setting for the "oracle" user has to be 022. Hostname command should return the fully qualified hostname as shown below: % hostname hostname.domainname For further information refer to the following: NOTE:429191.1 - Kernel setup for Solaris 10 using project files. NOTE:971464.1 - FAQ - 11gR2 requires Solaris 10 update 6 or greater Refer to "Verifying UDP and TCP Kernel Parameters" in the 11g Solaris Install Guide. Part Number E17163-01 for other recommended kernel parameters. http://download.oracle.com/docs/cd/e11882_01/install.112/e17163/ pre_install.htm#babejigd Solaris 10 requirements Required packages and patches for the Solaris 10 system. Tioli Netcool Performance Manager requires at a minimum the End User distribution of Solaris 10. Required packages: Required packages for the Solaris 10 system. Before installing the Oracle serer, ensure the following Solaris packages are installed on your system: SUNWarc SUNWbtool 14 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
SUNWcsl SUNWhea SUNWi15cs SUNWi1cs SUNWi1of SUNWlibC SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWxwfnt To erify that the required Solaris packages are installed: 1. Enter the following command at the shell prompt: # pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWuiu8 The following output confirms that the specified Solaris packages are installed correctly: system SUNWarc Archie Libraries system SUNWbtool CCS tools bundled with SunOS system SUNWhea SunOS Header Files system SUNWlibm Forte Deeloper Bundled libm system SUNWlibms Forte Deeloper Bundled shared libm system SUNWsprot Solaris Bundled tools system SUNWtoo Programming Tools... 2. If these packages are not on your system, see the Solaris Installation Guide for instructions on installing supplementary package software. Required patches: Required patches for the Solaris 10 system. To determine the patch leel on your system, enter the following command: uname - Note: All Tioli Netcool Performance Manager modules are tested to run on an End User distribution of Solaris 10. The following list of minimum Solaris patches is required: For all Installations : 120753-06: SunOS 5.10: Microtasking libraries (libmtsk) patch 139574-03: SunOS 5.10: file crle ldd stings elfdump patch 141444-09 141414-02 To determine whether an operating system patch is installed, enter a command similar to the following: 1. Enter the command: /usr/sbin/patchadd -p grep patch_number(without ersion number) For example, to determine if any ersion of the 120753-06 patch is installed, use the following command: Chapter 2. Requirements 15
/usr/sbin/patchadd -p grep 120753 Solaris 10 irtualized containers If you are using Solaris 10 irtualized containers, you must create containers with "whole root" partitions. If you are using Solaris 10 irtualized containers, you must create containers with "whole root" partitions. Tioli Netcool Performance Manager does not work in containers with "sparse root" partitions. Note: The Tioli Netcool Performance Manager Self Monitoring Pack and SSM packs do not report data correctly in irtualized enironments, due to compatibility issues of the underlying SSM agents in these configurations. The MIB-II pack can also hae difficulties discoering resources in irtualized serer enironments. DataMart DataMart requirements if you are using Solaris 10. Configure the default language of Solaris to English. IBM Jaa Runtime Enironment (JRE) 1.5. DataLoad DataLoad requirements if you are using Solaris 10. Configure the default language of Solaris to English. DataChannel DataChannel requirements if you are using Solaris 10. Configure the default language of Solaris to English. The DataChannel components require X libraries to be installed. The graphical tools in DataChannel also require a running X serer, which can be on a different host. Technology packs Technology pack requirements if you are using Solaris 10. Installation of technology packs on Solaris 10 requires JRE 1.6 (32-bit). The correct ersion is installed with the Topology Editor in the following default location: /opt/ibm/proiso/jm/jre/bin DataView and Tioli Integrated Portal DataView and Tioli Integrated Portal requirements if you are using Solaris 10. Jaa Runtime Enironment (JRE) 1.6 (32-bit) 16 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
AIX platforms Supported AIX systems. Tioli Netcool Performance Manager can be installed and operated in a irtualized AIX enironment. Note: Tioli Netcool Performance Manager on AIX does not support connection to a Solaris-based Oracle database. Note: The Tioli Netcool Performance Manager Self Monitoring Pack and SSM packs do not report data correctly in irtualized enironments, due to compatibility issues of the underlying SSM agents in these configurations. The MIB II pack can also hae difficulties discoering resources in irtualized serer enironments. Operating system Supported operating system and kernel ersion. IBM Tioli Netcool Performance Manager, Version 1.3.2 supports: AIX 6.1 TL 04 SP1 ("6100-04-01), 64-bit kernel AIX 7.1 TL 0 SP3 ("7100-00-03"), 64-bit kernel To erify your AIX release leel: As root, enter the following command at the shell prompt: # osleel -r This command returns a string that represents the maintenance leel for your AIX system. For AIX 6.1: If the operating system ersion is lower than AIX 6.1 Technology Leel 4 SP 1, then upgrade your operating system to this or a later leel. For AIX 7.1: If the operating system ersion is lower than AIX 7.1 Technology Leel 0 plus SP 3, then upgrade your operating system to this or a later leel. AIX maintenance packages are aailable from the following Web site: http://www-933.ibm.com/support/fixcentral/ Required files and fixes Files and fixes required by Oracle and Tioli Netcool Performance Manager for the AIX system. AIX 6.1 The following operating system filesets are required for AIX 6.1: bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat 6.1.2.1 or later bos.perf.perfstat bos.perf.proctools xlc.aix61.rte:10.1.0.0 or later gpfs.base 3.2.1.8 or later Chapter 2. Requirements 17
If you are using the minimum operating system TL leel for AIX 6L listed aboe, then install all AIX 6L 6.1 Authorized Problem Analysis Reports (APARs) for AIX 6.1 TL 02 SP1, and the following AIX fixes: IZ41855 IZ51456 IZ52319 These 6.1 fixes are already present in the following TL leels: AIX 6.1 TL-02 SP-04 and later AIX 6.1 TL-03 SP-02 and later AIX 6.1 TL-04 The following AIX fixes are required also: IZ97457 IZ89165 Note: See Oracle Metalink Note:1264074.1 and Note:1379753.1 for other AIX 6.1 patches that may be required AIX 7.1 The following operating system filesets are required for AIX 7.1: bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstat bos.perf.perfstat bos.perf.proctools xlc.aix61.rte:10.1.0.0 or later xlc.rte:10.1.0.0 or later If you are using the minimum operating system TL leel for AIX 7.1 listed aboe, then install all AIX 7L 7.1 Authorized Problem Analysis Reports (APARs) for AIX 7.1 TL 0 SP1, and the following AIX fixes: IZ87216 IZ87564 IZ89165 IZ97035 Note: See Oracle Metalink Note:1264074.1 and Note:1379753.1 for other AIX 7.1 patches that may be required. Determining installed filesets To determine if the required filesets are installed and committed, enter a command similar to the following: # lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \ bos.perf.libperfstat bos.perf.proctools To determine the supported kernel mode, enter a command similar to the following: 18 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
# getconf KERNEL_BITMODE Determining installed APAR fixes To determine if an APAR is installed, enter a command similar to the following: # /usr/sbin/instfix -i -k "IZ42940 IZ49516 IZ52331 IZ41855 IZ52319" If an APAR is not installed, then download it from the following Web site and install it: http://www-933.ibm.com/support/fixcentral/ Set resource limits The default user process limits are not adequate and must be reset. On AIX systems, the default user process limits are not adequate for Tioli Netcool Performance Manager. For detailed information on setting the correct user process limits, see Set Resource Limits in the IBM Tioli Netcool Performance Manager: Installation Guide. DataMart DataMart requirements if you are using AIX. Jaa Runtime Enironment (JRE) 1.5 or higher (for the Database Information module). DataLoad DataLoad requirements if you are using AIX. No special requirements. DataChannel DataChannel requirements if you are using AIX. The following DataChannel components require X libraries to be installed: Bulk Collector CME DLDR FTE FED (also requires that an X Serer is running) LDR The showversion utility. Technology packs Technology pack requirements if you are using AIX. Installation of technology packs on AIX 6.1 requires JRE 1.6 (32-bit). The correct ersion is installed with the Topology Editor in the following default location: /opt/ibm/proiso/jm/jre/bin Viewing the documentation on AIX systems Viewing the documentation requires that you can run Adobe Acrobat Reader. To run on AIX systems, Adobe Acrobat Reader requires GIMP Toolkit (GTK+) Version 2.2.2 or higher. You can download the toolkit from the following URL: http://www-03.ibm.com/serers/aix/products/aixos/linux/download.html Chapter 2. Requirements 19
In addition, you must install all the dependent packages for GTK+. You can install GTK+ and its dependent packages either before or after installing Acrobat Reader. At the time of publication, the latest ersion of GTK+ is gtk2-2.8.3-9, and the latest ersions of the dependent packages are as follows: libpng-1.2.8-5 libtiff-3.6.1-4 libjpeg-6b-6 gettext-0.10.40-6 glib2-2.8.1-3 atk-1.10.3-2 freetype2-2.1.7-5 xrender-0.8.4-7 expat-1.95.7-4 fontconfig-2.2.2-5 xft-2.1.6-5 cairo-1.0.2-6 pango-1.10.0-2 xcursor-1.0.2-3 gtk2-2.8.3-9 To fulfill dependency requirements, you must install these Red Hat Package Managers (RPMs) in the order specified. Installing an RPM: 1. To install an RPM use the following syntax: rpm -i rpm_filename 2. To see a list of the RPMs that hae been installed, enter the following command: rpm -qa Acrobat Reader and LDAP: By default, AIX systems do not hae LDAP installed. By default, AIX systems do not hae LDAP installed. If the AIX system does not hae LDAP installed and you run Acrobat Reader, a warning message is displayed. Click OK to hae Acrobat Reader proceed normally. To remoe the error message, delete or rename /opt/acrobat/reader/rs6000aix/ plug_ins/ppklite.api, where /opt/acrobat is the installation path. 20 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Linux platforms Supported Linux Systems IBM Tioli Netcool Performance Manager, Version 1.3.2 can be installed and operated in an enironment utilizing VMware partitions. This section details Linux enironment prerequisites for Tioli Netcool Performance Manager. Operating system Supported operating system and kernel ersions. Tioli Netcool Performance Manager supports the following Linux systems: Linux hosts running 64-bit Red Hat Enterprise Linux Version 5.5 or greater with Oracle 11g. To check the ersion of your operating system, enter: # cat /etc/redhat-release This command must return the output similar to: Red Hat Enterprise Linux Serer release 5.5 (Tikanga) To erify the processor type, run the following command: uname -p To erify the machine type, run the following command: uname -m To erify the hardware platform, run the following command: uname -i All results should contain the output: x86_64 Note: See Note 225710.1 for supported kernels and Note 265262.1 for "Things to know about Linux." https://support.oracle.com/csp/main/article?cmd=show &type=not&id=265262.1 Database Database requirements if you are using Linux. It is recommended that the user consult Metalink Note 880989.1, Requirements For Installing Oracle11g On RHEL5, which has a full list of Oracle requirements for RHEL5. Oracle keeps this list up to date. Required packages Required packages if you are using Linux. The following is a list of packages for Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0: binutils-2.17.50.0.6-6.el5 (x86_64) compat-libstdc++-33-3.2.3-61 (x86_64) - both architectures are required. See next line. compat-libstdc++-33-3.2.3-61 (i386) - both architectures are required. See preious line. Chapter 2. Requirements 21
elfutils-libelf-0.125-3.el5 (x86_64) glibc-2.5-24 (x86_64) - both architectures are required. See next line. glibc-2.5-24 (i686) - both architectures are required. See preious line. glibc-common-2.5-24 (x86_64) ksh-20060214-1.7 (x86_64) libaio-0.3.106-3.2 (x86_64) - both architectures are required. See next line. libaio-0.3.106-3.2 (i386) - both architectures are required. See preious line. libgcc-4.1.2-42.el5 (i386) - both architectures are required. See next line. libgcc-4.1.2-42.el5 (x86_64) - both architectures are required. See preious line. libstdc++-4.1.2-42.el5 (x86_64) - both architectures are required. See next line. libstdc++-4.1.2-42.el5 (i386) - both architectures are required. See preious line. make-3.81-3.el5 (x86_64) Note: These are minimum required ersions. Also, for some architectures both of the i386 and x86_64 package ersions must be erified. For example, both the i386 and the x86_64 architectures for glibc-2.5-24 must be installed. Also required are: elfutils-libelf-deel-0.125-3.el5.x86_64.rpm which in turn requires the following: elfutils-libelf-deel and elfutils-libelf-deel-static One depends upon the other. Therefore, they must be installed together, in one (1) "rpm -ih" command as follows: rpm -ih elfutils-libelf-deel-0.125-3.el5.x86_64.rpm elfutils-libelf-deel-static-0.125-3.el5.x86_64.rpm glibc-headers-2.5-24.x86_64.rpm which in turn requires the following: kernel-headers-2.6.18-92.el5.x86_64.rpm glibc-deel-2.5-24.x86_64.rpm - both architectures are required. See next item. glibc-deel-2.5-24.i386.rpm - both architectures are required. See preious item. gcc-4.1.2-42.el5.x86_64.rpm which in turn requires the following: libgomp-4.1.2-42.el5.x86_64.rpm libstdc++-deel-4.1.2-42.el5.x86_64.rpm gcc-c++-4.1.2-42.el5.x86_64.rpm libaio-deel-0.3.106-3.2.x86_64.rpm - both architectures are required. See next item libaio-deel-0.3.106-3.2.i386.rpm - both architectures are required. See preious item. sysstat-7.0.2-1.el5.x86_64.rpm unixodbc-2.2.11-7.1.x86_64.rpm - both architectures are required. See next item 22 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Required user names unixodbc-2.2.11-7.1.i386.rpm - both architectures are required. See preious item. unixodbc-deel-2.2.11-7.1.x86_64.rpm - both architectures are required. See next item unix ODBC-deel-2.2.11-7.1.i386.rpm - both architectures are required. See preious item. The following packages are required and checked for by the check_os.ini application: libxp-1.0.0-i386 libxp-1.0.0-x86_64 libxpm-3.5.5-x86_64 libstdc++-deel-4.1.1-x86_64 glibc-deel-2.5-i386 glibc-deel-2.5-x86_64 gcc-c++-4.1.2-x86_64 openmotif-2.3.1-i386 openmotif-2.3.1-x86_64 DataMart DataMart requirements if you are using Linux. Jaa Runtime Enironment (JRE) 1.5 or higher (for the Database Information module). DataLoad DataLoad requirements if you are using Linux. No special requirements. DataChannel DataChannel requirements if you are using Linux. No special requirements. There are two user names that must created when installing Tioli Netcool Performance Manager. Two specific user names are required on any serer hosting Tioli Netcool Performance Manager components, they are: puser: A dedicated Tioli Netcool Performance Manager Unix user. oracle: A dedicated Oracle user. Chapter 2. Requirements 23
puser The puser user name. oracle The Tioli Netcool Performance Manager UNIX user puser must be added to each serer hosting a Tioli Netcool Performance Manager component. The Tioli Netcool Performance Manager UNIX user, which is referred to as puser throughout the documentation, can be named by using any string as required by your organizations naming standards. For more information on how to add the Tioli Netcool Performance Manager UNIX user puser, see the Pre-Installation Setup Tasks > Adding the puser Login Name section of the IBM Tioli Netcool Performance Manager: Installation Guide. The oracle user name. The Oracle user oracle is added to each serer hosting a Tioli Netcool Performance Manager component. This user is added when installing either Oracle client or serer. The default username used is oracle; howeer, this Oracle username can be named using any string as required by your organizations naming standards. Note: Should you choose a non-default Oracle username, you must use the same name across all instances of Oracle Client and Serer throughout your Tioli Netcool Performance Manager system. For more information on creating the oracle user for the Oracle serer, see the "Installing the Oracle Serer > Run the Oracle Serer Configuration Script" section of the IBM Tioli Netcool Performance Manager: Installation Guide. For more information on creating the oracle user for the Oracle client, see the Installing the Oracle Client >Run the Oracle Client Configuration Script section of the IBM Tioli Netcool Performance Manager: Installation Guide. Ancillary software requirements Extra and third-party software requirements. The following sections outline the extra software packages required by Tioli Netcool Performance Manager. FTP support Tioli Netcool Performance Manager requires FTP support. The FTP (File Transfer Protocol) ersion used to transfer files between Tioli Netcool Performance Manager components is deliered with Solaris 10. AIX also uses FTP to transfer files between Tioli Netcool Performance Manager components. Tioli Netcool Performance Manager supports the following file transport protocols between Tioli Netcool Performance Manager components and third-party equipment (for example, EMS): FTP Solaris 10 24 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Microsoft Internet Information Serices (IIS) FTP serer Open SSH and SFTP Tioli Netcool Performance Manager requires OpenSSH and SFTP support. Tioli Netcool Performance Manager supports encrypted Secure File Transfer (SFTP) and FTP to moe data files from DataLoad to DataChannel, or from DataChannel Remote to the DataChannel Loader. Tioli Netcool Performance Manager SFTP is compatible only with OpenSSH serer and client ersion 3.1p1 and aboe. OpenSSH is freely downloadable and distributable (http://www.openssh.org). OpenSSH is supported on Solaris, AIX, and Linux. Other SSH ersions such as F-Secure, the SSH bundled in Solaris 10 and the SSH bundled with AIX is not compatible. If you use the SFTP capability, you must obtain, install, generate keys for, maintain, and support OpenSSH and any packages required by OpenSSH. See Tioli Netcool Performance Manager Technical Note: DataChannel Secure File Transfer Installation for more information about installing and configuring OpenSSH. AIX requirements AIX requirements in order to use OpenSSH and SFTP. The following table lists additional prerequisites that must be installed on an AIX system, and where these packages can be found: Table 2: Additional Prerequisites Package openssl-0.9.7g-1.aix5.1.ppc.rpm openssh-4.1p1_53.tar.z bos.adt.libm Location https://www14.software.ibm.com/webapp/ iwm/web/prelogin.do?source=aixtbx https://sourceforge.net/projects/opensshaix/ AIX installation CD. Solaris requirements Solaris requirements in order to use OpenSSH and SFTP. The following are additional prerequisites that must be installed on an Solaris systems: openssh - SSH client (openssh-4.5p1-sol-sparc-local.gz or higher). zlib - zlib compression and decompression library (zlib-1.2.3-sol9-sparc-local.gz or higher). Linux requirements Linux requirements in order to use OpenSSH and SFTP. OpenSSH is required for VSFTP to work with Tioli Netcool Performance Manager.OpenSSH is installed by default on any RHEL system. By default, FTP is not enabled on Linux systems. You must enable FTP on your Linux host to carry out the installation of Tioli Netcool Performance Manager. Chapter 2. Requirements 25
To enable FTP on your Linux host, run the following command as root: /etc/init.d/sftpd start File compression File compression support. Archies deliered as part of the IBM Tioli Netcool Performance Manager distribution are created by using GNU Tar. This program must be used for the decompression of archies. DataView load balancing Load balancing support. IBM Tioli Netcool Performance Manager supports the use of an external load balancer to optimize the use of aailable DataView instances. The load balancer must support the following basic features: Basic IP-based load balancing Sticky sessions based on incoming IP Up/down status based on checking for a listening port The following is the link to the CSS Basic Configuration Guide:http:// www.cisco.com/uniercd/cc/td/doc/product/webscale/css/css_401/bsccfgg d/index.htm Oracle database Oracle database license recommendations. License recommendations When purchasing a license from Oracle, IBM recommends a Processor license rather than a Named User Plus license. Oracle defines a Named User in such a way that it includes not only actual human users, but also non-human-operated deices. In other words, you would require a Named User Plus license for eery resource that Tioli Netcool Performance Manager polls, which would be ery expensie. http://www.oracle.com. Oracle serer Oracle serer support. Oracle 11g Enterprise Edition for Solaris (SPARC) and Linux AIX are 64-bit only. Oracle 11g Enterprise Edition must include the partitioning option. The database no longer proides 32-bit libraries, therefore you must install the Oracle client on eery host of the Tioli Netcool Performance Manager. Note: Tioli Netcool Performance Manager must be installed and run as a standalone database. It must not be placed on a serer that already has a database as the installation program will likely to interfere. The co-hosting of Tioli Netcool 26 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Performance Manager also affects performance in unknown ways. If a co-host is required then the Customer should seek out Professional Serices for support. Hidden Oracle parameters Hidden parameters that must be set for Oracle. This section lists all of the Oracle '_', or hidden parameters, used by Tioli Netcool Performance Manager: _partition_iew_enabled=true _unnest_subquery=false _gby_hash_aggregation_enabled=false Tioli Common Reporting client Tioli Common Reporting and Cognos client-side requirements. Tioli Netcool Performance Manager supports the use of: Tioli Integrated Portal 2.1 and Tioli Integrated Portal 2.2 You should install Tioli Integrated Portal 2.1 if your system hosts software that is incompatible with Tioli Integrated Portal 2.2 To use Cognos, you must download and install a windows ersion of Tioli Common Reporting 2.1 from xtreme Leerage. There are two prerequisites that must be in place to use TCR/Cognos on a Microsoft Windows enironment: Framework Manager Oracle Client Jaa Runtime Enironment (JRE) Required Jaa support. Jaa Runtime Enironment (JRE) 1.6 (32-bit) is required for all serers hosting Tioli Netcool Performance Manager components. The exception to this is DataMart which requires is IBM Jaa 1.5 R6. The IBM JDK is not supplied and installed automatically with the DataMart, DataChannel and DataLoad components. When installing those components on serers that are remote from the serer hosting the primary deployer (Topology Editor and Deployer) or TIP, then the required JRE, as stated aboe, will need to be deployed to those serers separately. Web browsers and settings Supported browsers. The following browsers are required to support the Web client and proide access to DataView reports: Important: If you are using Tioli Netcool Performance Manager with WebGUI, see WebGUI integration on page 29 for the browsers supported with both. Important: No other browser types are supported. Chapter 2. Requirements 27
Table 3. Windows Clients Windows Vista Microsoft Internet Explorer 7.0, 8.0 Mozilla Firefox 3.6. Windows XP Microsoft Internet Explorer 7.0, 8.0 Mozilla Firefox 3.6. Note: When using Windows Internet Explorer, IBM recommends that you hae aailable at least 1GB of memory Table 4. UNIX Clients AIX Red Hat 5 Solaris 10 Firefox 3.6 Firefox 3.6 Firefox 3.6 The following are required browser settings: Enable JaaScript Enable cookies Browser requirements for the Launchpad Web browser requirements for the Launchpad. The new Launchpad has been tested on the following browsers: On Solaris: Firefox 3.6 On AIX: Firefox 3.6 On Linux: Firefox 3.6 For information about downloading and installing these browsers, see the following web sites: http://www.mozilla.org/ http://www-03.ibm.com/systems/p/os/aix/browsers/index.html Note: You must be a registered user to use this site. Screen resolution Recommended screen resolution details. A screen resolution of 1152 x 864 pixels or higher is recommended for the display of DataView reports. Some reports may experience rendering issues at lower resolutions. Report Studio - Cognos Report Studio support. Report Studio is only supported by Microsoft Internet Explorer. 28 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
X Emulation Remote desktop support. For DataMart GUI access, Tioli Netcool Performance Manager supports the following: Natie X Terminals Exceed V 6.2 The following libraries are required in order for Exceed to work with Eclipse: libgtk 2.10.1 libgib 2.12.1 libfreetype 2.1.10 libatk 1.12.1 libcairo 1.2.6 libxft 2.1.6 libpango 1.14.0 Real VNC serer 4.0 WebGUI integration WebGUI ersion support. The IBM Tioli Netcool/OMNIbus Web GUI Integration Guide for Wireline describes how to integrate IBM Tioli Netcool /OMNIbus Web GUI with the wireline component of Tioli Netcool Performance Manager. Tioli Netcool Performance Manager 1.3.2 will hae support for: Tioli Integrated Portal 2.1 and WebGui 7.3.1 + Fix pack x (as per Tioli Netcool Performance Manager 1.3.1 support) - example scenario where customer has multiple Tioli products in TIP Tioli Integrated Portal 2.2 and WebGui 7.3.1 +FP1+FP2 (new support to 1.3.2). The web browsers supported by WebGUI and Tioli Netcool Performance Manager are listed in the following table. Table 5. Web clients browsers supported by WebGUI Browser Version Operating system Internet Explorer 7.0, 8.0 Windows 2003, Windows XP, Windows Vista, Windows 2008, and Windows 7 Mozilla Firefox 3.5, 3.6 Windows 2003, Windows XP, Windows Vista, Windows 2008, and Windows 7 SuSE Linux Enterprise Serer (SLES) 10, and 11 Red Hat Enterprise Linux (RHEL) 4, 5 and 6 Solaris 9 and 10 Chapter 2. Requirements 29
Note: When using Windows Internet Explorer, IBM recommends that you hae at least 1GB of memory aailable. Microsoft Office Version Microsoft Office support. The Tioli Netcool Performance Manager DataView Scheduled Report option generates files compatible with Microsoft Office Word 2002 or higher. 30 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 3. Downloading the Tioli Netcool Performance Manager distribution to disk How to set up the Tioli Netcool Performance Manager distribution for the upgrade 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 filesystem before beginning the installation. To download the Tioli Netcool Performance Manager distribution to a directory on the host from which you intend to run the Topology Editor: 1. On the target host, log in as the Tioli Netcool Performance Manager user, such as puser. 2. Create a directory to hold the contents of your Tioli Netcool Performance Manager distribution. For example: $ mkdir /ar/tmp/cdproiso/132 Note: Any further references to this directory will be made using <DIST_DIR>. The addition of the 132 directory is to ensure that the download of the new distribution does not oerwrite existing files, and to ensure that it does not sit in the same directory as the preious distribution. 3. Download the Tioli Netcool Performance Manager distribution to the host directory created in the preious step and expand the contents of the distribution package. Downloading the Tioli Common Reporting distribution You must download the Tioli Common Reporting distribution to the target serer and place the file in a specific directory. About this task Note: If you extract the tar directly into the same root location as the Tioli Netcool Performance Manager components then the Tioli Common Reporting launchpad.sh oerwrites the Tioli Netcool Performance Manager Installer launchpad.sh, meaning that the launchpad cannot be started for the installer. The Tioli Common Reporting drier must be extracted so it can be used by the Tioli Netcool Performance Manager Common Installer. If you decide not to extract the tar as a peer to the other components, a Tioli Common Reporting folder must still be created haing a path to the Tioli Common Reportinginstall.sh the same as: /TCR/TCRInstaller/install.sh. The following process ensures that you specify the Tioli Common Reporting media location only once: Copyright IBM Corp. 2006, 2013 31
1. Create a directory named TCR as a peer to the other Tioli Netcool Performance Manager components, that is, DataView, DataChannel, and so on. For example: <DIST_DIR>/proiso/SOLARIS/TCR 2. Extract the Tioli Common Reporting 2.1.1 inside this folder. 32 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 The following tasks assume that you hae a fully functioning Netcool/Proiso 4.4.3.3 or later enironment with Oracle 10.2.0.4 database running on a Solaris 10 (update 6 and later), AIX 6.1 or AIX 7.1, or Red Hat Enterprise Linux 5.5 platform. Do not use DBUA to upgrade the database from Oracle 10.2.0.4 to Oracle 11.2.0.2. The DBUA upgrade will not complete the upgrade procedure. The manual upgrade procedure to Oracle 11.2.0.2 should be used. This upgrade document assumes an Oracle 10.2.0.4 database containing only a Tioli Netcool Performance Manager 1.3.1 release and aboe with no third party software or objects installed. If you hae any third party applications installed, do not continue with this upgrade without consulting the Oracle documentation. Oracle topology Oracle client must be 32-bit and installed on all machines except for the serer that hosts the Tioli Netcool Performance Manager database serer, but should there be another Tioli Netcool Performance Manager component on the serer hosting the Tioli Netcool Performance Manager database serer, the client must also be installed on that serer, haing a separate ORACLE_HOME for both Oracle client and serer. Oracle home for the serer and client: ORACLE_HOME for 11g 32 bit client should be /opt/oracle/product/11.2.0.2- client32/ ORACLE_HOME for 11g 64 bit serer should be /opt/oracle/product/ 11.2.0.2/ The reason for this is that Oracle 10g included 32-bit libraries with the 64-bit install. Howeer, Oracle 11g does not, the 32-bit and 64-bit libraries are now separate installs. Summary of Oracle upgrade tasks In order to upgrade your database, you must perform the following steps: 1. Download the Oracle distribution to disk. 2. Install Oracle 11.2.0.2 Client (32-bit). The Oracle client should be installed to all serers hosting Tioli Netcool Performance Manager components, except for the serer hosting the Tioli Netcool Performance Manager database. Howeer, should there be another TNPM component on the serer hosting the Oracle database serer, the client must also be installed on that serer, haing a separate ORACLE_HOME for both Oracle client and serer. 3. Install Oracle 11.2.0.2 Serer (64-bit). 4. Back up all serers hosting Tioli Netcool Performance Manager components and the Oracle 10.2.0.4 database. 5. Back up the Oracle 10.2.0.4 database. 6. Shut down Tioli Netcool Performance Manager components. Copyright IBM Corp. 2006, 2013 33
7. Upgrade the Tioli Netcool Performance Manager database from Oracle 10.2.0.4 to Oracle 11.2.0.2. 8. Back up the upgrade. Install Oracle 11.2.0.2 client (32-bit) Instructions on how to install the Oracle 11.2.0.2 client (32-bit). The deployer and Topology Editor use Oracle 11.2.0.2 client (32-bit) The deployer must run on the Host DB serer. Therefore, in the Tioli Netcool Performance Manager, Oracle 11.2.0.2 client (32-bit) must be installed. You must specify a different directory path for the Oracle 11.2.0.2 client (32-bit) from the directory specified when installing the Oracle 10.2.0.4 client (32-bit). For example, assuming that Oracle 10.2.0.4 is installed in /opt/oracle/product/10.2.0/ then you must install the Oracle 11.2.0.2 client (32-bit) in /opt/oracle/product/ 11.2.0.2-client32/. Download the Oracle distribution to disk The Oracle installation files must be in place before you can begin the installation of Oracle. About this task Note: Oracle 11.2.0.2 must be installed into a new ORACLE_HOME. Make sure that you install Oracle into a different ORACLE_HOME than the one used for Oracle 10.2.0.4. 1. Log in as root. 2. Set the DISPLAY enironment ariable. 3. Create a directory to hold the contents of the Oracle distribution. For example: # mkdir /ar/tmp/oracle11202 4. Download the Oracle files to the /ar/tmp/oracle11202 directory. 5. Extract the Oracle distribution files that now exist in the /ar/tmp/oracle11202 directory. Results The directory created and to which the Oracle 11.2.0.2 distribution was downloaded will from now on be referred to using <ORA_DIST_DIR>. Before beginning this task, make sure that you hae: downloaded the Tioli Netcool Performance Manager distribution to disk.. The directory created and to which the Tioli Netcool Performance Manager distribution was downloaded will from now on be referred to using <DIST_DIR>. What to do next Before you proceed to the next step, make sure that you obtain the upgrade instructions proided by Oracle. The instructions contain information on performing steps required for the upgrade that are not documented in this guide. 34 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
See your database administrator to determine whether there are any company-specific requirements for installing Oracle in your enironment. Run the Oracle client configuration script The Oracle client configuration shell script creates the enironment for the client software installation on the local system. About this task This script is named configure_client and is located with the Tioli Netcool Performance Manager files downloaded as part of the Tioli Netcool Performance Manager distribution. If you are performing this step as part of an upgrade procedure, make sure that you run the configuration script proided with the target ersion of Tioli Netcool Performance Manager. The client configuration script makes the following changes to the local system: Adds the dba and oinstall groups to /etc/group. Adds the Solaris login name oracle, whose primary group membership is dba, and secondary group membership is oinstall. Note: You must use the same Oracle username across all instances of Oracle Client and Serer throughout your Tioli Netcool Performance Manager system. Creates the Oracle client directory structure. When you create the enironment for Oracle 11.2.0.2, the default location for this directory structure is /opt/oracle/product/11.2.0.2-client32/. You specify this directory as the target location when you install the Oracle client. Note: None of the aboe changes will be made if the changes are already in place. To configure the Oracle installation enironment: 1. Log in as root. 2. Set the ORACLE_BASE enironment ariable to point to the top-leel directory where you want the Oracle client files installed. The default installation directory is /opt/oracle. For example: # ORACLE_BASE=/opt/oracle # export ORACLE_BASE Note: The configure_client script places this ariable into the oracle login name's.profile file. To check that the ariable is set correctly, enter the following command: # en grep ORA 3. Set the ORACLE_HOME enironment ariable. For example: # ORACLE_HOME=/opt/oracle/product/11.2.0.2-client32/ # export ORACLE_HOME Note: The alue defined in the configure_client script for ORACLE_HOME is the alue needed in the Topology Editor for Oracle Home on the host leel. 4. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/oracle/instance Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 35
AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX<ersion_num>/oracle/instance Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/oracle/instance where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Download the Oracle distribution to disk on page 34. 5. Run the Oracle configuration script using the following command: #./configure_client The following screen is displayed: -------------------------------------------------- configure_client Setting the Oracle client enironment Tue Dec 6 14:51:23 CST 2011 -------------------------------------------------- OS... : [ SunOS 5.10 Generic_141444-09 ] Host... : [ l3prosol1z3 ] Logname... : [ root ] ORACLE_BASE.. : [ /opt/oracle ] ORACLE_HOME.. : [ /opt/oracle/product/11.2.0.2-client32/ ] DBA group... : [ dba ] OUI Inentory group... : [ oinstall ] Oracle Software owner... : [ oracle ] Configure Oracle release.. : [ 11.2.0 ] Menu : 1. Modify Oracle software owner. 2. Next supported release. 3. Check enironment. 0. Exit Choice : 6. 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 enironment... 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: 36 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
--> Created. Checking for oracle directory tree : [ /opt/oracle/product ] --> Created. [ /opt/oracle/product ] --> Created. [ /opt/oracle/product/11.2.0 ] --> Created. Checking for oracle.profile file --> Created. Press Enter to continue... 7. Press Enter to continue. The configure_client main screen is displayed. 8. Type 0 and press Enter to exit the script. Set a password for the Oracle login name You must assign a password for the oracle login name to maintain system security. About this task The configure_ora script you ran in the preious section creates the oracle login name. You must assign a password for the oracle login name to maintain system security, and because subsequent installation steps expect the password to be already set. To set a password: 1. Log in as root. 2. Enter the following command: # passwd oracle 3. Enter and re-enter the password (oracle, by default) as prompted. The password is set. Run the preinstallation script Run the preinstallation script to erify your readiness to install Oracle. 1. As root, change directory using the following command: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/oracle/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX<ersion_num>/oracle/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/oracle/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Download the Oracle distribution to disk on page 34. 2. Set the ORACLE_BASE enironment ariable. 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 serer configuration script. Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 37
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 before proceeding to the next step. Verify PATH and Enironment for the Oracle login name Before proceeding to install Oracle files, make sure the /usr/ccs/bin directory is in the PATH enironment ariable for the oracle login name. About this task To erify the PATH and enironment: 1. Log in as oracle. Set and export the DISPLAY enironment ariable. If you are using the su command to become oracle, use a hyphen as the second argument so the oracle user login enironment is loaded: # su - oracle 2. Verify that the enironment ariable ORACLE_BASE has been set by entering the following command: $ en grep ORA If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the.profile file was set for the oracle user, as described in Run the Oracle serer configuration script on page 45. 3. To erify the path, enter the following command: $ echo $PATH The output must show that /usr/ccs/bin is part of the search path. For example: /usr/bin:/opt/oracle/product/11.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 client (32-bit) The Oracle installation script is a shell script that you can use to install the Oracle serer, Oracle client software, or patches to existing installations of the Oracle serer and client. About this task This script is named perform_oracle_inst and is located with the Tioli Netcool Performance Manager files that you obtained in Download the Oracle distribution to disk on page 34. This script is proided by IBM as part of the Tioli Netcool Performance Manager installation package. 38 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
An Oracle client installation is not usable until the following Net configuration files are configured and installed: tnsnames.ora sqlnet.ora These files are configured in later steps. To install the Oracle client: 1. Log in as oracle. 2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/oracle/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX<ersion_num>/oracle/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/oracle/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Download the Oracle distribution to disk on page 34. 3. Enter the following command to start the installer: $./perform_oracle_inst 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... : [ 11.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/11.2.0.2-client32/ ] c) DBA group... : [ dba ] d) OUI Inentory group... : [ oinstall ] e) Oracle Software owner... : [ oracle ] f) Directory where CDs were copied: [ ] Menu : 1. Next supported release 2. Set install type to: Client 3. Perform install 0. Exit Choice : Note: The ORACLE_HOME should match the ORACLE_HOME set in the deployer for the serer on which the client is being installed. 4. Enter f at the Choice prompt and press Enter. Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 39
5. Enter the full path to the <ORA_DIST_DIR>, as created in Download the Oracle distribution to disk on page 34. For example: Choice: f Enter new alue for CD directory: /ar/tmp/oracle11202 6. Edit any other menu settings as necessary. Make sure that the alues for ORACLE_BASE and ORACLE_HOME correspond to the locations you specified when you 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 enironment, then asks whether you want to perform the installation. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series of status messages. Note: You can safely ignore any font.properties not found messages in the output. When the installation reaches the In Summary Page stage, the installation slows down significantly while Oracle files are copied and linked. 9. On AIX, you may be asked if the script named rootpre.sh has been run. To run this script: a. Open another window. b. Login as root. c. cd to /ar/tmp/oracle11202/database/rootpre d. run rootpre.sh e. Then answer Y to the installation script. 10. When the installation process is finished, the installation displays a success message. Write down the log file location to aid in troubleshooting if there is an installation error. 11. Type C and press Enter to return to the installation menu. 12. Type 0 and press Enter to exit the installation menu. 13. Perform the steps in Run the root.sh script on page 104. Run the root.sh script After successfully running an Oracle client or serer installation, you must run the root.sh script. About this task This step is also required after an Oracle patch installation. See Verify the required operating system packages on page 45. To run the root.sh script: 1. Log in as root or become superuser. Set the DISPLAY enironment ariable. 2. Change to the directory where Oracle serer files were installed. (This is the directory as set in the ORACLE_HOME enironment ariable.) For example: # cd /opt/oracle/product/11.2.0.2-client32/ 3. Run the following command:./root.sh 40 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Messages like the following are displayed: Running Oracle11 root.sh script... The following enironment ariables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /opt/oracle/product/11.2.0.2-client32/ Enter 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 accept the default alue. The default entry might be NFS-mounted at your site so it can be shared among seeral workstations and therefore might be write-protected. If so, enter the location of a machine-specific alternatie bin directory. (You might need to create this alternatie directory at a shell prompt first.) For example, enter /usr/delphi/bin. 5. The script continues as follows:... Adding entry to /ar/opt/oracle/oratab file... Entries will be added to the /ar/opt/oracle/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. # The script runs to completion with no further prompts. Update the oracle user's.profile Modify the oracle user's.profile file. 1. Make sure that ORACLE_HOME points to $ORACLE_BASE/product/11.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 -- umask 022 ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_BASE/product/11.2.0 NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib TNS_ADMIN=$ORACLE_HOME/network/admin PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/local/bin EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpmextc.so export PATH ORACLE_BASE ORACLE_HOME NLS_LANG export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN EXTPROC_DLLS ORACLE_SID=PV Export ORACLE_SID # -- End Oracle Settings -- Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 41
Configure the Oracle Net client You must configure the Oracle Net client by setting up the TNS (Transport Network Substrate) serice names for your Tioli Netcool Performance Manager database instance. About this task Next, you configure the Oracle Net client by setting up the TNS (Transport Network Substrate) serice names for your Tioli Netcool Performance Manager database instance. You must perform this step for each instance of the Oracle client software that you installed on the system. You must configure sqlnet.ora and tnsnames.ora files for both Oracle serer and Oracle client installations. Howeer, the tnsnames.ora file for client installations should not hae the EXTPROC_CONNECTION_DATA section. If you are installing DataView and one or more other Tioli Netcool Performance Manager components on the same system, you must make sure that the tnsnames.ora and sqlnet.ora files for each set of client software are identical. The easiest way to do this is to create these files when you are configuring the first client instance for Net and then to copy it to the corresponding directory when you configure the second instance. Create the sqlnet.ora file The sqlnet.ora file manages Oracle network operations. You can create a new sqlnet.ora file, or FTP the file from your Oracle serer. About this task To set up the TNS serice names: 1. Log in as oracle. 2. Change to the following directory: $ cd $ORACLE_HOME/network/admin 3. To create the sqlnet.ora file, FTP the following file from your Oracle serer: /opt/oracle/admin/skeleton/bin/template.example_tnpm.sqlnet.ora 4. Add the following lines to it: NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD For example: # sqlnet.ora network configuration file in # /opt/oracle/product/11.2.0.2/network/admin NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD Note: If you do not use WORLD as the DEFAULT_DOMAIN alue, make sure you enter the same alue for DEFAULT_DOMAIN in both sqlnet.ora and tnsnames.ora. 5. Write and quit the sqlnet.ora file. Create the tnsnames.ora file The tnsnames.ora file maintains the relationships between logical node names and physical locations of Oracle serers in the network. 42 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
About this task You can create a new tnsnames.ora file, or FTP the file from your Oracle serer. To create the tnsnames.ora file: 1. FTP the following file from your Oracle serer: /opt/oracle/admin/skeleton/bin/template.example_tnpm.tnsnames.ora 2. Add the following lines: # tnsnames.ora network configuration file in # /opt/oracle/product/11.2.0.2/network/admin # # For Oracle client installations, tnsnames.ora # only needs the PV.WORLD entry. PV.WORLD = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = yourhost) (PORT = 1521) ) ) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME = PV) ) ) Note: Indents in this file must be presered. 3. Replace the string yourhost in the line (HOST = yourhost) with the name of your Oracle serer. Note the following: You will use the alue in the INSTANCE_NAME field as the TNS entry when installing DataMart. If you reconfigure the Oracle client to connect to a different Oracle database in another Tioli Netcool Performance Manager installation, be sure you update the HOST entry in the tnsnames.ora file, then restart the Oracle client. Specify the host using the hostname only, do not use the IP address. 4. (optional) Replace the default port number 1521 in the line (PORT = 1521) with your required port number. 5. Write and quit the file. Test the Oracle net configuration The steps required to test the Oracle Net configuration. About this task To test the Oracle Net configuration: 1. Log in as oracle. 2. Enter a command with the following syntax: tnsping Net_serice_name 10 Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 43
For example: tnsping PV.WORLD 10 3. Test again, using the same Net instance name without the domain suffix: tnsping PV 10 Look for successful completion messages (OK). Install Oracle 11.2.0.2 serer (64-bit) Instructions on how to install the Oracle 11.2.0.2 serer (64-bit). To install Oracle 11.2.0.2 serer (64-bit), you can use the scripts proided as part of Tioli Netcool Performance Manager. Download the Oracle distribution to disk The Oracle installation files must be in place before you can begin the installation of Oracle. About this task Note: Oracle 11.2.0.2 must be installed into a new ORACLE_HOME. Make sure that you install Oracle into a different ORACLE_HOME than the one used for Oracle 10.2.0.4. 1. Log in as root. 2. Set the DISPLAY enironment ariable. 3. Create a directory to hold the contents of the Oracle distribution. For example: # mkdir /ar/tmp/oracle11202 4. Download the Oracle files to the /ar/tmp/oracle11202 directory. 5. Extract the Oracle distribution files that now exist in the /ar/tmp/oracle11202 directory. Results The directory created and to which the Oracle 11.2.0.2 distribution was downloaded will from now on be referred to using <ORA_DIST_DIR>. Before beginning this task, make sure that you hae: downloaded the Tioli Netcool Performance Manager distribution to disk.. The directory created and to which the Tioli Netcool Performance Manager distribution was downloaded will from now on be referred to using <DIST_DIR>. What to do next Before you proceed to the next step, make sure that you obtain the upgrade instructions proided by Oracle. The instructions contain information on performing steps required for the upgrade that are not documented in this guide. See your database administrator to determine whether there are any company-specific requirements for installing Oracle in your enironment. 44 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Verify the required operating system packages Before installing the Oracle serer, make sure the all required packages are installed on your system. 1. Make sure all the required Solaris packages and patches are installed on your system. All required packages and patches are specified in the IBM Tioli Netcool Performance Manager: Configuration Recommendations Guide. 2. If these packages are not on your system, see the releant operating system Installation Guide for instructions on installing supplementary package software. Run the Oracle serer configuration script In this step, you set up the Oracle enironment using the script proided with the Tioli Netcool Performance Manager DataMart files on the Tioli Netcool Performance Manager distribution. About this task This script automatically creates the following configuration: Adds the dba and oinstall groups to /etc/group Adds the login name oracle, whose primary group membership is dba and secondary group membership is oinstall. Note: You must use the same Oracle username across all instances of Oracle Client and Serer throughout your Tioli Netcool Performance Manager system. Creates the Oracle directory structure Creates startup and shutdown scripts for Oracle serer processes Note: If you hae 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 a different home directory for the oracle user, create the oracle user before running the script. The script does not create an oracle user if one already exists. Note: It is likely you hae already created the dba and oinstall groups and the oracle user. Howeer, this script must still be run to create the required Oracle directory structure. To configure the Oracle installation enironment using the script: 1. As root, set the ORACLE_BASE enironment ariable to point to the top-leel directory where you want the Oracle serer files installed. The default installation directory is /opt/oracle. For example: # ORACLE_BASE=/opt/oracle # export ORACLE_BASE Note: The script places this ariable into the oracle login account's.profile file. To check that the ariable is set correctly, enter the following command: # en grep ORA Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 45
2. Change to the following directory: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/oracle/instance AIX systems: # cd <DIST_DIR>/proiso/DataBase/AIX<ersion_num>/oracle/instance Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/oracle/instance where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Download the Oracle distribution to disk on page 34. 3. Run the Oracle configuration script by entering the following command: #./configure_ora The following screen is displayed: -------------------------------------------------- Setting the Oracle enironment <Current Date> -------------------------------------------------- OS... : [ SunOS 5.10 Generic ] Host... : [ delphi ] Logname... : [ root ] ORACLE_BASE.. : [ /opt/oracle ] DBA group... : [ dba ] OUI Inentory group... : [ oinstall ] Oracle Software owner... : [ oracle ] Configure Oracle release.. : [ 11.2.0 ] Menu : 1. Modify Oracle software owner. 2. Next supported release 3. Check enironment. 0. Exit Choice: 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: Checking enironment... 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: 46 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
--> Created. Checking for oracle directory tree : [ /opt/oracle/product ] --> Created. [ /opt/oracle/product/11.2.0 ] --> Created. [ /opt/oracle/product/11.2.0/dbs ] --> Created. [ /opt/oracle/admin ] --> Created. [ /opt/oracle/admin/skeleton ] --> Created. [ /opt/oracle/admin/skeleton/lib ] --> Ok. [ /opt/oracle/admin/skeleton/lib/libpmextc.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 : /ar/opt/oracle/oratab --> Created. /ar/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 script The script creates the Oracle directory structure. The following example shows the directory structure created for Oracle, where ORACLE_BASE was set to /opt/oracle: /opt/oracle/product /opt/oracle/product/11.2.0 /opt/oracle/product/11.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: /etc/init.d/dbora, which starts the Oracle Listener and database serer automatically on each system boot Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.d Oracle configuration files /ar/opt/oracle/oratab and lsnrtab A.profile file for the oracle user containing the following lines: # -- Begin Oracle Settings -- umask 022 ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_BASE/product/11.2.0 NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib TNS_ADMIN=$ORACLE_HOME/network/admin PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpmextc.so export PATH ORACLE_BASE ORACLE_HOME NLS_LANG export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN export EXTPROC_DLLS # -- End Oracle Settings -- Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 47
Note the following points: The alue of ORACLE_HOME must not contain soft links to other directories or file systems. Be sure to specify the entire absolute path to Oracle. The ORACLE_SID ariable is added to this file at a later stage. Set a password for the Oracle login name You must assign a password for the oracle login name to maintain system security. About this task The configure_ora script you ran in the preious section creates the oracle login name. You must assign a password for the oracle login name to maintain system security, and because subsequent installation steps expect the password to be already set. To set a password: 1. Log in as root. 2. Enter the following command: # passwd oracle 3. Enter and re-enter the password (oracle, by default) as prompted. The password is set. Run the preinstallation script Run the preinstallation script to erify your readiness to install Oracle. 1. As root, change directory using the following command: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/oracle/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX<ersion_num>/oracle/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/oracle/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Download the Oracle distribution to disk on page 34. 2. Set the ORACLE_BASE enironment ariable. 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 serer configuration script. 3. Enter the following command: #./pre_install_as_root The following messages indicate success: 48 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
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 before proceeding to the next step. Run the rootpre.sh script (AIX only) To run the rootpre.sh script. 1. Log in as root or become superuser. 2. Set the DISPLAY enironment ariable. 3. Change to the directory <ORA_DIST_DIR>/database. Note: The Oracle serer (64-bit) distribution is downloaded to <ORA_DIST_DIR> as per the instructions in the section Download the Oracle distribution to disk on page 34. 4. Run the following command:./rootpre.sh rootpre.sh may return an error like the following: Configuring Asynchronous I/O... Asynchronous I/O is not installed on this system. This error can safely be ignored. Note: For more information on this Oracle error, see Oracle Metalink Article 282036.1. Verify PATH and Enironment for the Oracle login name Before proceeding to install Oracle files, make sure the /usr/ccs/bin directory is in the PATH enironment ariable for the oracle login name. About this task To erify the PATH and enironment: 1. Log in as oracle. Set and export the DISPLAY enironment ariable. If you are using the su command to become oracle, use a hyphen as the second argument so the oracle user login enironment is loaded: # su - oracle 2. Verify that the enironment ariable ORACLE_BASE has been set by entering the following command: $ en grep ORA If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the.profile file was set for the oracle user, as described in Run the Oracle serer configuration script on page 45. 3. To erify the path, enter the following command: $ echo $PATH Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 49
The output must show that /usr/ccs/bin is part of the search path. For example: /usr/bin:/opt/oracle/product/11.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 script To 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 proided by IBM is used to install Oracle serer, Oracle client, and upgrade patches to an existing Oracle serer or Client installation. To install the Oracle serer (64-bit) using the menu-based script: 1. As Oracle, change directory using the following command: Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/DataBase/SOL10/oracle/instance/ora_installer AIX systems: # cd <DIST_DIR>/proiso/AIX/DataBase/AIX<ersion_num>/oracle/instance/ora_installer Linux systems: # cd <DIST_DIR>/proiso/RHEL/DataBase/RHEL5/oracle/instance/ora_installer where: <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution in Download the Oracle distribution to disk on page 34. 2. Enter the following command to start the installer: $./perform_oracle_inst The installation menu is displayed: 50 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
-------------------------------------------------- perform_oracle_inst Installation of oracle binaries <Current Date> -------------------------------------------------- OS... : [ SunOS 5.10 Generic ] Host... : [ delphi ] Logname... : [ oracle ] Install Oracle release... : [ 11.2.0 ] Installation type... : [ Serer ] Enter the appropriate letter to modify the entries below: a) ORACLE_BASE.. : [ /opt/oracle/ ] b) ORACLE_HOME.. : [ /opt/oracle/product/11.2.0.2/ ] c) DBA group... : [ dba ] d) OUI Inentory group... : [ oinstall ] e) Oracle Software owner... : [ oracle ] f) Directory where CDs were copied: [] Menu : 1. Next supported release 2. Set install type to: Client 3. Perform install 0. Exit Choice : 3. Verify the following settings: The Oracle release number is 11.2.0. The Installation type field is Serer. This field cycles between three settings: Serer, Client, and Patch. Type 2 at the Choice prompt and press Enter until Serer 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: f Enter new alue for CD directory: /ar/tmp/oracle11202 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 11.2.0.2, 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 11.2.0.2, the default is /opt/oracle/product/11.2.0.2/. 10. Edit other menu settings as required. For example, if you used non-default alues for ORACLE_BASE or ORACLE_HOME, enter your settings until the menu shows they correctly point to the directories created for Oracle 11.2.0.2. 11. To begin the Oracle installation, type 3 at the Choice prompt and press Enter. The installation script checks the enironment, then asks if you want to perform the installation. 12. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series of status messages. Note: You can safely ignore any font.properties not found messages in the output. When the installation reaches the In Summary Page stage, the installation slows down significantly while Oracle files are copied and linked. 13. When the installation is complete, messages like the following are displayed: Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 51
In End of Installation Page The installation of Oracle11 Database was successful. Please check /opt/oracle/orainentory/logs/silentinstall2011-09-28_04-23-53pm.log for more details. The Oracle installation has completed. Please check the messages aboe to determine if the install completed successfully. If you do not see successful completion messages, consult the install log at: /opt/oracle/orainentory/logs Press C to continue... Note: Write down the log file location to aid in troubleshooting if there is an installation error. 14. Type C and press Enter to return to the installation menu. 15. Type 0 and press Enter to exit the installation menu. What to do next Note: Reiew the Oracle installation logs at $ORACLE_BASE/oraInentory/logs for errors as some fatal errors may be reported in the log, but the natie Oracle installer will report success in standard output. Run the root.sh script After successfully running an Oracle client or serer installation, you must run the root.sh script. About this task This step is also required after an Oracle patch installation. See Verify the required operating system packages on page 45. To run the root.sh script: 1. Log in as root or become superuser. Set the DISPLAY enironment ariable. 2. Change to the directory where Oracle serer files were installed. (This is the directory as set in the ORACLE_HOME enironment ariable.) For example: # cd /opt/oracle/product/11.2.0.2-client32/ 3. Run the following command:./root.sh Messages like the following are displayed: Running Oracle11 root.sh script... The following enironment ariables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /opt/oracle/product/11.2.0.2-client32/ Enter 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 accept the default alue. The default entry might be NFS-mounted at your site so it can be shared among seeral workstations and therefore might be write-protected. If so, enter the location of a machine-specific alternatie bin directory. (You might need to create this alternatie directory at a shell prompt first.) For example, enter /usr/delphi/bin. 5. The script continues as follows: 52 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
... Adding entry to /ar/opt/oracle/oratab file... Entries will be added to the /ar/opt/oracle/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. # The script runs to completion with no further prompts. Set the ORACLE_SID ariable A system identifier (SID) identifies each Oracle database instance for internal connectiity on the Oracle serer itself. (Connectiity from Oracle Clients to the serer is controlled by the TNS names system configured later.) The enironment ariable for the system identifier is ORACLE_SID. About this task Decide on an SID to use for your Tioli Netcool Performance Manager database instance. The assumed default for the Tioli Netcool Performance Manager installation is PV. IBM recommends using this default SID unless your site has established Oracle SID naming conentions. To set the ORACLE_SID enironment ariable: 1. Log in as oracle. 2. Open the.profile file with a text editor. 3. Add the following line anywhere between the Begin and End Oracle Settings comment lines: ORACLE_SID=PV; export ORACLE_SID For example: # -- Begin Oracle Settings -- umask 022 ORACLE_BASE=/opt/oracle/ ORACLE_HOME=/opt/oracle/product/11.2.0.2/ ORACLE_SID=PV; export ORACLE_SID NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib TNS_ADMIN=$ORACLE_HOME/network/admin PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/delphi/bin EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpmextc.so export PATH ORACLE_BASE ORACLE_HOME NLS_LANG export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN export EXTPROC_DLLS # -- End Oracle Settings -- 4. Sae and exit the.profile file. 5. Enter the following shell command to actiate the change to your profile: $../.profile 6. Make sure the ariable was set by entering the following command: $ en grep ORACLE_SID Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 53
Perform Oracle Upgrade Preparation It is important to ensure that your database is ready for the required upgrade. The following steps proide instructions on how to check the existing database and make the needed changes. Note: When you complete the installation of Oracle 11.2.0, make sure you change your ORACLE_HOME enironment ariable back to the Oracle 10.2.0 home. You will be directed to change to the 11.2.0 ORACLE_HOME later in the upgrade process. Shutting down the Tioli Netcool Performance Manager components The Tioli Netcool Performance Manager components DataChannel and DataMart need to be shut down for the Oracle upgrade procedure. An oeriew of the strategy is as follows: 1. Shut down the DataChannel and DataMart components on all hosts now. 2. Follow all the instructions on preparing for Oracle upgrade. Instructions for these steps are contained the following sections. Note: DataLoad and Tioli Integrated Portal can remain running. Shutting down DataChannel You must shut down the DataChannel components on each DataChannel host running in your enironment. About this task To shut down DataChannel: Note: The DataChannel CMGR, CNS, AMGR, and LOG isual processes must remain running until you hae gathered the DataChannel parameters from your enironment. 1. On the DataChannel host, log in as the component user, such as puser. 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 work queues must be emptied. To shut down the DataChannel FTE and empty the work queues: $./dccmd stop pattern FTE.* 4. Let all DataChannel components continue to process until the.../do directories 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: 54 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
a. If your enironment does not run the DataLoad High Aailability Manager (HAM), use the following dccmd command to stop the DataChannel applications: $./dccmd stop all b. If your enironment runs the DataLoad High Aailability 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 Aailability Manager, the HAM application must remain running until you hae gathered the DataChannel parameters from your enironment. Shutting down DataMart You must shut down DataMart on each DataMart host running in your enironment. About this task To shut down DataMart: 1. On the DataChannel host, log in as the component user, such as puser. 2. Set and export the DISPLAY ariable. 3. Source the DataMart enironment using the following command: $. /opt/datamart/datamart.en 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: $ pmstat 7. Remoe any DataMart locks by selecting File > Remoe locks. Verifying Netcool/Proiso components are shut down You must erify that the Netcool/Proiso components hae been shut down in your enironment. About this task To erify that Netcool/Proiso components hae been shut down: 1. 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: Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 55
SELECT username,machine,program FROM $session ORDER BY username,machine,program; On a system where all the clients hae been shut down, you would expect to see output like the following: USERNAME MACHINE PROGRAM PV_ADMIN Oak sqlplus@oak (TNS V1-V3)... USERNAME MACHINE PROGRAM PV_COLL Willow pmd@willow (TNS V1-V3) The first item is the SQL query itself, while the second item is a DataLoad collector. This is expected if you chose to leae the DataLoad collectors running in order to minimize collections loss. Backup database At 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 a cold backup. See the Oracle documentation for more information. Note: For information on Database backup and recoery, see the Database Administration Guide. Run and spool the utlu112i.sql file The utlu112i.sql is an Oracle Pre-Upgrade Information Tool. You must run and spool the utlu112i.sql file. Before you begin Note: Ensure the current working directory has write permissions for the user running sqlplus. The output file will be spooled to the current working directory unless another directory is specified. The following is an example of how to run and spool the utlu112i.sql file: bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.4.0 - Production on Fri Oct 7 15:15:36 2011 Copyright (c) 1982, 2007, Oracle. All Rights Resered. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bit Production With the Partitioning, Data Mining and Real Application Testing options 56 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
SQL> spool upgrade.log SQL> @/opt/oracle/product/11.2.0/rdbms/admin/utlu112i.sql Oracle Database 11.2 Pre-Upgrade Information Tool 10-07-2011 15:38:34 Script Version: 11.2.0.2.0 Build: 001. ********************************************************************** Database: ********************************************************************** --> name: PV --> ersion: 11.2.0.2.0 --> compatible: 11.2.0 --> blocksize: 16384 --> platform: Linux x86 64-bit --> timezone file: V4. ********************************************************************** Tablespaces: [make adjustments in the current enironment] ********************************************************************** --> SYSTEM tablespace is adequate for the upgrade.... minimum required size: 350 MB --> UNDO_DATA tablespace is adequate for the upgrade.... minimum required size: 144 MB --> SYSAUX tablespace is adequate for the upgrade.... minimum required size: 110 MB. ********************************************************************** Flashback: OFF ********************************************************************** ********************************************************************** Update Parameters: [Update Oracle Database 11.2 init.ora or spfile] Note: Pre-upgrade tool was run on a lower ersion 64-bit database. ********************************************************************** --> If Target Oracle is 32-Bit, refer here for Update Parameters: -- No update parameter changes are required.. --> If Target Oracle is 64-Bit, refer here for Update Parameters: -- No update parameter changes are required.. ********************************************************************** Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile] ********************************************************************** -- No renamed parameters found. No changes are required.. ********************************************************************** Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile] ********************************************************************** --> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" --> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest". ********************************************************************** Components: [The following database components will be upgraded or installed] ********************************************************************** --> Oracle Catalog Views [upgrade] VALID --> Oracle Packages and Types [upgrade] VALID. ********************************************************************** Miscellaneous Warnings ********************************************************************** WARNING: --> Database is using a timezone file older than ersion 14.... After the release migration, it is recommended that DBMS_DST package... be used to upgrade the 10.2.0.4.0 database timezone ersion... to the latest ersion which comes with the new release. WARNING: --> Database contains INVALID objects prior to upgrade.... The list of inalid SYS/SYSTEM objects was written to... registry$sys_in_objs. Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 57
... The list of non-sys/system objects was written to... registry$nonsys_in_objs.... Use utluiobj.sql after the upgrade to identify any new inalid... objects due to the upgrade.... USER PUBLIC has 1 INVALID objects.... USER PV_COLL has 2 INVALID objects.... USER PV_GUI has 1 INVALID objects.... USER PV_INVENTORY has 1 INVALID objects.... USER PV_LOIS has 1 INVALID objects.... USER PV_OPERATOR has 2 INVALID objects.... USER PV_RESMGR has 1 INVALID objects.... USER PV_UBA has 1 INVALID objects.... USER SYS has 1 INVALID objects.. ********************************************************************** Recommendations ********************************************************************** Oracle recommends gathering dictionary statistics prior to upgrading the database. To gather dictionary statistics execute the following command while connected as SYSDBA: EXECUTE dbms_stats.gather_dictionary_stats; ********************************************************************** Oracle recommends remoing all hidden parameters prior to upgrading. To iew existing hidden parameters execute the following command while connected AS SYSDBA: SELECT name,description from SYS.V$PARAMETER WHERE name LIKE \_% ESCAPE \ Changes will need to be made in the init.ora or spfile. ********************************************************************** Oracle recommends reiewing any defined eents prior to upgrading. To iew existing non-default eents execute the following commands while connected AS SYSDBA: Eents: SELECT (translate(alue,chr(13) chr(10), )) FROM sys.$parameter2 WHERE UPPER(name) = EVENT AND isdefault= FALSE Trace Eents: SELECT (translate(alue,chr(13) chr(10), )) from sys.$parameter2 WHERE UPPER(name) = _TRACE_EVENTS AND isdefault= FALSE Changes will need to be made in the init.ora or spfile. ********************************************************************** SQL>spool off Note: The warning "Database is using a timezone file older than ersion 14." is normal, and can be ignored as it will be handled in later in the upgrade. Note: The warning "Database contains INVALID objects prior to upgrade." is normal, and can be ignored as it will be handled in later in the upgrade. Follow all recommendations that the Pre-Upgrade Information Tool generates. The two common issues listed below are handled in the proceeding steps. What to do next The most common issues are handled in the following steps. 58 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Make sure the database starts and ends in a similar state The focus of this step is to ensure that all database components are alid before starting the actual upgrade. The following example issues an SQL command that checks for inalid data: SQL> select substr(owner, 1, 12) owner, substr(object_name, 1, 30) object, substr(object_type, 1, 30), status from dba_objects where status!= VALID ; OWNER OBJECT SUBSTR(OBJ STATUS ---------- ------------------------------ ---------- ------- PV_METRIC MTRC01_NRAW_000_H0 VIEW INVALID PV_METRIC MTRC01_NRAW_000_CURRENT VIEW INVALID PV_METRIC MTRC01_NRAW_000_FULL VIEW INVALID PV_METRIC MTRC01_NRAW_000_RECENT VIEW INVALID PV_METRIC MTRC00_NRAW_000_H0 VIEW INVALID PV_METRIC MTRC00_NRAW_000_CURRENT VIEW INVALID PV_METRIC MTRC00_NRAW_000_FULL VIEW INVALID PV_METRIC MTRC00_NRAW_000_RECENT VIEW INVALID 8 rows selected. SQL> It is common for the Tioli Netcool Performance Manager database to hae multiple INVALID objects. The metric data loading method adds new table partitions to the arious metric data tables. This action inalidates the iews that Tioli Netcool Performance Manager uses for reporting. Howeer, these iews are implicitly recompiled when needed to satisfy queries. If the SQL query shown in the preious example returns a number of rows selected, you can attempt to realidate all INVALID objects with the following Oracle proided script. While connected as the sys user, issue the following command: SQL> @$ORACLE_HOME/rdbms/admin/utlrp PL/SQL procedure successfully completed. SQL> Rerun the original SQL command that checks for inalid objects. SQL> select substr(owner, 1, 12) owner, substr(object_name, 1, 30) object, substr(object_type, 1, 30), status from dba_objects where status!= VALID ; no rows selected SQL> This time, the query should return no rows selected. If you find objects that are currently inalid, do not proceed with the upgrade. Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 59
Verify that there is no database data dictionary corruption The following set of commands generate a script that you will subsequently run. Before you begin Note: Ensure the current working directory has write permissions for the user running sqlplus. The output file will be spooled to the current working directory unless another directory is specified. 1. Run the following commands: SQL> Set erify off Set space 0 Set line 120 Set heading off Set feedback off Set pages 1000 Spool analyze.sql Select Analyze cluster " cluster_name " alidate structure cascade; from dba_clusters where owner= SYS union Select Analyze table " table_name " alidate structure cascade; from dba_tables where owner= SYS and partitioned= NO and (iot_type= IOT or iot_type is NULL) union Select Analyze table " table_name " alidate structure cascade into inalid_rows; from dba_tables where owner= SYS and partitioned= YES ; spool off SQL> SQL> SQL> SQL> SQL> SQL> SQL> SQL> 2 3 4 5 6 7 8 9 10 11 Analyze cluster "C_COBJ#" alidate structure cascade; Analyze cluster "C_FILE#_BLOCK#" alidate structure cascade;... Analyze table "VIEWCON$" alidate structure cascade; Analyze table "VIEWTRCOL$" alidate structure cascade; Analyze table "VTABLE$" alidate structure cascade; Analyze table "_default_auditing_options_" alidate structure cascade; SQL> 2. Run utlalid.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. You may or may not see a message that indicates a table was created. SQL> @$ORACLE_HOME/rdbms/admin/utlalid.sql SQL> @analyze.sql SP2-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 created SQL> Results Oracle now has us check that all snapshot refreshes hae completed and replication is stopped. Netcool/Proiso 4.4.3.3 does not use these features. If you hae added any of these features then please refer to Oracle Note: 837570.1. 60 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Stop the database listener Stop the database listener. Use the commands shown in the following example: -bash-3.2$ lsnrctl stop LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 07-OCT-2011 21:05:50 Copyright (c) 1991, 2007, Oracle. All rights resered. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=pmgxs23.tilab.raleigh.ibm.com)(PORT=1521))) The command completed successfully -bash-3.2$ Verify no data files need recoery If you discoer any data files that need recoery, do not proceed with the upgrade. The following query should return no rows: SQL> select * from $recoer_file; no rows selected SQL> Verify no data files in backup mode If you discoer any data files are in backup mode, do not proceed with the upgrade. The following query should return no rows: SQL> select * from $backup where status!= NOT ACTIVE ; no rows selected SQL> Verify that there are no pending Distributed Transactions Tioli Netcool Performance Manager does not use the distributed transactions functionality of Oracle. About this task You must erify that there are no pending distributed transactions. Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 61
The following query should return no rows: SQL> select * from dba_2pc_pending; no rows selected SQL> Verify SYS and SYSTEM users hae a default SYSTEM tablespace You must erify that SYS and SYSTEM users hae a default SYSTEM tablespace. Run the following query to iew the default tablespaces for users: SQL> select username, default_tablespace from dba_users where username in ( SYS, SYSTEM ); USERNAME DEFAULT_TABLESPACE ------------------------------ ------------------------------ SYS SYSTEM SYSTEM SYSTEM SQL> If necessary, alter these users to hae a default tablespace of SYSTEM. Run the following 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 tablespace If you hae enabled database auditing, you must erify that the AUD$ table is located in the SYSTEM tablespace. Run the following statement: SQL> select tablespace_name from dba_tables where table_name = AUD$ ; TABLESPACE_NAME ------------------------------ SYSTEM SQL> Note the location of the control files: 62 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
SQL> select name from $controlfile; NAME -------------------------------------------------------------------------------- /oradata/pv/pv_01.ctl /oradata/pv/pv_02.ctl SQL> Verify there are no externally authenticated SSL users The database should hae no externally authenticated SSL users. Run the following statement: SQL> select tablespace_name from dba_tables where table_name = AUD$ ; SQL> SELECT name from sys.user$ WHERE ext_username IS NOT NULL AND password = 'GLOBAL'; no rows selected SQL> If there are externally authenticated SSL users, please refer to the official Oracle 11g upgrade guide on how to remedy this. Make note of all sysdba users Write down the all sysdba users. All sysdba users can be discoered using the following query: SQL> select * from $pwfile_users; USERNAME SYSDB SYSOP ------------------------------ ----- ----- INTERNAL TRUE TRUE SYS TRUE TRUE SQL> Shut down database Perform a shutdown immediate on the database. About this task Note: Do not perform a shutdown abort. The following example shows the commands used to perform a shutdown immediate: Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 63
-bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.4.0 Production on Sat Oct 8 18:42:52 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to: Oracle Database 11g Enterprise Edition Release 10.2.0.4.0-64bit Production With the Partitioning option SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> Perform the Oracle upgrade You are now ready to perform the Oracle upgrade. To upgrade the Tioli Netcool Performance Manager database from Oracle 10g to Oracle 11g, perform the following tasks: Modify the database initpv.ora file By default, the initpv.ora file is located in the $ORACLE_BASE/admin/PV/pfile directory. About this task Open this file and perform the following tasks: 1. Change to the directory: $ORACLE_BASE/admin/PV/pfile. 2. Make a backup of the initpv.ora file 3. Remoe the following parameters should they exist: background_dump_dest core_dump_dest user_dump_dest 4. Set the compatible parameter as follows: compatible="11.2.0" What to do next The following tasks must be carried out if archiing is enabled: 1. Make sure the log_archie_dest parameter only specifies a path and that the path ends with a / (for example, /u01/oradata/p/arch/). 2. Make sure the log_archie_format parameter specifies the desired format. The allowable parameters to define this command hae changed oer time. The customer must refer to the appropriate Oracle documentation to determine the correct format for Oracle 11.2.0.2. 64 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Verify the NLS_LANG parameter is set to WE8ISO8859P1 You must erify that the NLS_LANG parameter is set to WE8ISO8859P1. Check the NLS_LANG parameter using the following query: $ echo $NLS_LANG AMERICAN_AMERICA.WE8ISO8859P1 $ Copy tnsnames.ora, sqlnet.ora, and listener.ora files to the new ORACLE_HOME You must copy tnsnames.ora, sqlnet.ora, and listener.ora files to the new ORACLE_HOME. These files can be copied as demonstrated in the following example: $ cp <1020_HOME>/network/admin/* <1120_HOME>/network/admin Copy the password file from the old home to the new home You must copy the password file from the old home to the new home. Substitute the ORACLE_SID for your enironment where you see {PV}: $ cp <1020_HOME>/dbs/orapw{PV} <1120_HOME>/dbs/orapw{PV} Create soft links in the new ORACLE_HOME You must create soft links in the new ORACLE_HOME The example below assumes ORACLE_HOME is /opt/oracle/product/11.2.0 and the instance name is PV. Replace these alues if the system is different. # make soft links $ cd /opt/oracle/product/11.2.0/lib # on Solaris: $ ln s $ORACLE_BASE/admin/PV/lib/libpmextc64.so libpmextc.so #onaix $ ln s $ORACLE_BASE/admin/PV/lib/libpmextc.so libpmextc.so # on all systems $ ln s $ORACLE_BASE/admin/PV/lib/libmultiTask.so $ ln s $ORACLE_BASE/admin/PV/lib/libcmu.so $ cd /opt/oracle/product/11.2.0/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 /opt/oracle/product/11.2.0/dbs $ ln s $ORACLE_BASE/admin/PV/pfile/initPV.ora Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 65
Update the oratab entry for this database You must update the oratab entry for this database. Edit the /ar/opt/oracle/oratab file (on Solaris) or /etc/oratab (on AIX, RHEL), and change the entry as follows. Be sure to disable automatic startup, by specifying N in the last field: From: PV:/opt/oracle/product/10.2.0:{Y N} To: PV:/opt/oracle/product/11.2.0:N Update the oracle user's.profile Modify the oracle user's.profile file. 1. Make sure that ORACLE_HOME points to $ORACLE_BASE/product/11.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 -- umask 022 ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_BASE/product/11.2.0 NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib TNS_ADMIN=$ORACLE_HOME/network/admin PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/local/bin EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpmextc.so export PATH ORACLE_BASE ORACLE_HOME NLS_LANG export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN EXTPROC_DLLS ORACLE_SID=PV Export ORACLE_SID # -- End Oracle Settings -- Confirm the enironment ariables hae been reset Log out and log back in to make sure that your enironment ariables are reset to the new ORACLE_HOME. About this task On AIX, LIBPATH is the same as LD_LIBRARY_PATH on Solaris and RHEL. 1. Log out and log back in. 2. Verify that the following list of enironment ariables now point to the new home: ORACLE_BASE (if applicable) 66 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
ORACLE_HOME ORA_NLS33 LD_LIBRARY_PATH PATH EXTPROC_DLLS What to do next Also make sure that the PATH does not contain any directories from the old 10.2.0 installation. Startup upgrade Begin the database upgrade. As specified in the following example, change directory cd $ORACLE_HOME/rdbms/ admin, enter SQL*Plus as the sys user, and issue a startup upgrade: -bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 11.2.0.2.0 Production on Fri Oct 7 21:28:42 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to an idle instance. SQL> startup upgrade; ORACLE instance started. Total System Global Area Fixed Size Variable Size Database Buffers Redo Buffers Database mounted. Database opened. SQL> 680644608 bytes 2229520 bytes 541068016 bytes 134217728 bytes 3129344 bytes Results If you encounter the following error on AIX: -bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 11.2.0.2.0 Production on Thu Oct 6 09:22:12 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to an idle instance. SQL> startup upgrade; ORA-09925: Unable to create audit trail file IBM AIX RISC System/6000 Error: 2: No such file or directory Additional information: 9925 Create an empty audit trail directory by running: mkdir /opt/oracle/admin/pv/adump Then rerun the startup upgrade. Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 67
Enter a spool command, and run the upgrade script catupgrd.sql The catupgrd.sql script performs the upgrade from Oracle 10.2.0.4 to Oracle 11.2.0.2. Before you begin Note: Ensure the current working directory has write permissions for the user running sqlplus. The output file will be spooled to the current working directory unless another directory is specified. Note: The Oracle notes state: Before performing this action, disable any third-party procedures that check the complexity of schema passwords. 1. Run the following statement: -bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 11.2.0.2.0 Production on Fri Oct 7 21:28:42 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to an idle instance. SQL> startup upgrade; SQL> spool /tmp/upgrade.log SQL> @/opt/oracle/product/11.2.0/rdbms/admin/catupgrd.sql SQL> spool off SQL> 2. Oracle recommends: Check the spool file (/tmp/upgrade.log) and erify that the packages and procedures compiled successfully. Correct any problems you find in this file and rerun the appropriate upgrade script, if necessary. You can rerun any of the scripts described in this note as many times as necessary. 3. Restart the Oracle serer. Run the following statement: bash-3.2$ sqlplus "/as sysdba" SQL*Plus: Release 11.2.0.2.0 Production on Tue Dec 6 20:18:03 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to an idle instance. SQL> startup ORACLE instance started. Disable stats Disable the gathering of database statistics. To disable stats use the following query. SQL> EXEC DBMS_SCHEDULER.DISABLE( GATHER_STATS_JOB ); SQL> 68 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Run utlu112s.sql Run the utlu112s.sql script specifying the TEXT option. About this task The Oracle notes state: This is the Post-upgrade Status tool that displays the status of the database components in the upgraded database. To run this file: sqlplus "/ as sysdba" SQL> startup; SQL> exec p_admin.pm_client.use_session_parameter( PV_ADMIN ) ; PL/SQL procedure successfully completed. SQL> @$ORACLE_HOME/rdbms/admin/utlu112s.sql. Oracle Database 11.2 Post-Upgrade Status Tool 10-07-2011 22:13:52. Component Status Version HH:MM:SS. Oracle Serer. VALID 11.2.0.2.0 00:16:01 Gathering Statistics. 00:00:34 Total Upgrade Time: 00:16:37 PL/SQL procedure successfully completed. SQL> Shut down database Perform a shutdown immediate on the database. About this task Note: Do not perform a shutdown abort. The following example shows the commands used to perform a shutdown immediate: -bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.4.0 Production on Sat Oct 8 18:42:52 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to: Oracle Database 11g Enterprise Edition Release 10.2.0.4.0-64bit Production With the Partitioning option SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 69
Restart the database Perform a startup restrict on the database. The following example shows the commands used to perform a startup restrict: SQL> startup restrict ORACLE instance started. Total System Global Area 679477248 bytes Fixed Size 2043072 bytes Variable Size 541070144 bytes Database Buffers 134217728 bytes Redo Buffers 2146304 bytes Database mounted. Database opened. SQL> Run the utlrp.sql script Run the utlrp.sql script. To run this file: SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql TIMESTAMP ----------------------------------------------------------------------------- COMP_TIMESTAMP UTLRP_BGN 2011-09-23 15:14:52... PL/SQL procedure successfully completed. TIMESTAMP ----------------------------------------------------------------------------- COMP_TIMESTAMP UTLRP_END 2011-09-23 15:18:44 PL/SQL procedure successfully completed.... OBJECTS WITH ERRORS ------------------- 0... ERRORS DURING RECOMPILATION --------------------------- 0 PL/SQL procedure successfully completed. SQL> 70 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Check for inalid objects Run the SQL statement that checks for inalid objects. About this task The query should return no rows. Note: If you find objects that are currently inalid, do not proceed without contacting IBM support. Run the query: SQL> select substr(owner, 1, 12) owner, substr(object_name, 1, 30) object, substr(object_type, 1, 30) type, status from dba_objects where status!= VALID ; no rows selected SQL> Shut down database Perform a shutdown immediate on the database. About this task Note: Do not perform a shutdown abort. The following example shows the commands used to perform a shutdown immediate: -bash-3.2$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.4.0 Production on Sat Oct 8 18:42:52 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to: Oracle Database 11g Enterprise Edition Release 10.2.0.4.0-64bit Production With the Partitioning option SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 71
Modify the database initpv.ora compatible parameter You must modify the compatible parameter of the initpv.ora file. 1. Change to the directory: $ORACLE_BASE/admin/PV/pfile. 2. Open the initpv.ora file. 3. Set the compatible parameter as follows: compatible= 11.2.0 Change listener.ora to use the new ORACLE_HOME Change to the TNS_ADMIN directory and modify the listener.ora file to use the new ORACLE_HOME. 1. 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 $ i listener.ora 2. Within the file, modify the ORACLE_HOME as appropriate. For example: From: (ORACLE_HOME = /opt/oracle/product/10.2.0/) To (ORACLE_HOME = /opt/oracle/product/11.2.0.2/) 3. Repeat the preious two steps for each reference you see using the ORACLE_HOME that is alid for your enironment. Restart the listener Restart the listener and make sure that it is using the 11.2.0 home. 72 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Enter the following: -bash-3.2$ lsnrctl start LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 08-OCT-2011 18:39:48 Copyright (c) 1991, 2010, Oracle. All rights resered. Starting /opt/oracle/product/11.2.0/bin/tnslsnr: please wait... TNSLSNR for Linux: Version 11.2.0.2.0 - Production System parameter file is /opt/oracle/product/11.2.0/network/admin/listener.ora Log messages written to /opt/oracle/diag/tnslsnr/pmgxs23/listener/alert/log.xml Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521))) Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC))) Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=pmgxs23.tilab.raleigh.ibm.com)(PORT=1521))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production Start Date 08-OCT-2011 18:39:48 Uptime 0 days 0 hr. 0 min. 0 sec Trace Leel off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /opt/oracle/product/11.2.0/network/admin/listener.ora Listener Log File /opt/oracle/diag/tnslsnr/pmgxs23/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC))) Serices Summary... Serice "PLSExtProc" has 1 instance(s). Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this serice... Serice "PV.WORLD" has 1 instance(s). Instance "PV", status UNKNOWN, has 1 handler(s) for this serice... The command completed successfully -bash-3.2$ What to do next The following steps relate to the restarting Tioli Netcool Performance Manager. Before restarting the system, ensure you hae completed on Post Upgrade Instructions in the Oracle 11 Upgrade Guide and applied these to each releant system. Starting the Tioli Netcool Performance Manager components Except for DataChannel, all Tioli Netcool Performance Manager components should be running once the upgrade topology has been successfully deployed. Should you find that any components are not running after deployment, the following sections explain how they can be restarted. Starting the cron jobs During the upgrade process, the deployer creates new job statements in the crontab 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: Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 73
1. On the DataChannel host, log in as the component user, such as puser. 2. Open the crontab file for editing by using the following command: crontab -e 3. When you hae made your edits, write and quit the file. Starting DataMart During the upgrade process, DataMart should automatically restart. Howeer, if DataMart has not been restarted, you must start it manually. About this task To start DataMart: 1. On the DataMart host, log in as the component user, such as puser. 2. Source the DataMart enironment using the following command: $. /opt/datamart/datamart.en 3. Change your working directory to the DataMart bin directory (/opt/datamart/bin by default) using the following command: $ cd /opt/datamart/bin 4. Use the pismgr command to start DataMart: $./pismgr start Starting DataView During the upgrade process, DataView should automatically restart. Howeer, if DataView has not been restarted, you must start it manually. About this task To start DataView: 1. On the DataView host, log in as the component user, such as puser. 2. Start Tioli Integrated Portal and Tioli Common Reporting: To start these components enter the following command: <tipcomponents>/tcrcomponent/bin/starttcrserer.sh <username> <password> Where: user: the Tioli Integrated Portal administrator name. password: the Tioli Integrated Portal administrator password. For example: /opt/ibm/tioli/tip21components/tcrcomponent/bin/starttcrserer.sh tipadmin tipadmin Starting DataChannel You must start the DataChannel components on each DataChannel host running in your enironment. About this task To start DataChannel: 74 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
1. On the DataChannel host, log in as puser. 2. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default) using the following command: $ cd /opt/datachannel/bin 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 management processes. For example: $./cnsw $./logw $./amgrw $./cmgrw 5. Make sure the processes started correctly. Use the following commands: ps -ef grep LOG grep - grep ; ps -ef grep AMGR grep - grep ps -ef grep CMGR grep - grep ;ps -ef grep CNS grep - grep 6. Use the dccmd command to start all DataChannel applications: $./dccmd start all 7. Use the dccmd command to erify that all of the DataChannel applications started properly by executing the following command: $./dccmd status all Chapter 4. Upgrading Oracle 10.2.0.4 to Oracle 11.2.0.2 75
76 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 5. Upgrading Tioli Integrated Portal and Tioli Common Reporting The upgrade of Tioli Integrated Portal to ersion 2.2 and Tioli Common Reporting to ersion 2.1.1. Some software is not compatible with Tioli Integrated Portal 2.2. Should your system contain software that is incompatible with Tioli Integrated Portal 2.2, you should remain with Tioli Integrated Portal 2.1 and skip the section describing how to upgrade to Tioli Integrated Portal 2.2. Upgrading to Tioli Integrated Portal 2.2 This is an optional step. Should you be running software that is incompatible with Tioli Integrated Portal 2.2, you should remain with Tioli Integrated Portal 2.1 and skip this step. 1. Login as root or the user with which you hae installed Tioli Integrated Portal. 2. Obtain the software: Download the ersion of Tioli Integrated Portal Feature Pack for your OS located at: http://www.ibm.com/support/fixcentral/swg/ selectfixes?parent=ibm~tioli&product=ibm/tioli/tioli+integrated+portal &release=all&platform=all&function=all 3. Unzip the downloaded Feature Pack, for example, 2.2.0.1-TIV-TIP-AIXPPC32- RP0001.zip, in a temporary directory. Note: Ensure the JRE in use is IBM Jaa 6, using 'jaa -ersion' and/or 'which jaa'. If not, then set the PATH enironment ariable to include the TIP jaa in the path, for example, export PATH=/opt/IBM/jaa/bin:$PATH There cannot be any JAVA processes running from the TIP directory or the upgrade will fail. The -jre option in the upgrade command below also cannot contain any reference to the jre from the TIP directory 4. Copy the following files into the directory where the downloaded feature pack: upgrade_tip.sh upgrade_tcr.sh tip_response.template tcr_response.template The location form which these files are copied can be, for example, /Builds/1.3.2-I5-B11/proiso/AIX/contribs/TIP-TCR. 5. Stop Tioli Integrated Portal and Tioli Common Reporting: To stop these components, enter the following command: <tipcomponents>/tcrcomponent/bin/stoptcrserer.sh <username> <password> For example: /opt/ibm/tioli/tip21components/tcrcomponent/bin/stoptcrserer.sh tipadmin tipadmin Copyright IBM Corp. 2006, 2013 77
6. Download 2.2.0.1-TIV-TIP-FITSuit-RP0001.zip from: http://www.ibm.com/ support/fixcentral/swg/selectfixes?parent=ibm~tioli&product=ibm/tioli/ Tioli+Integrated+Portal&release=All&platform=All&function=all 7. Unzip 2.2.0.1-TIV-TIP-FITSuit-RP0001.zip into this directory /opt/ibm/tioli/tip21/profiles/tipprofile/etc 8. Run the upgrade script./upgrade_tip.sh -jre {path-to-a-jre} -tipmedia {TIP_FP-directory} -tipinstall {TIP-install-dir} Where: tipmedia is the folder into which you unzipped the two prerequisite downloads. tipinstall is the Tioli Integrated Portal install folder. For example:./upgrade_tip.sh -jre /export/home/jaa/jre -tipmedia /export/home/proiso/solaris/tcr/tcrinstaller/tip_fp -tipinstall /opt/proiso/tip Other options supported: tipusername U specify TIP admin username. tippassword P specify TIP admin password. locale L Locale for installation (default: en). Upgrading to Tioli Common Reporting 2.1.1 Instructions on how to upgrade to Tioli Common Reporting 2.1.1. Before you begin You should already hae downloaded the Tioli Common Reporting at this point. About this task Note: there cannot be any JAVA processes running from the TIP directory or the upgrade will fail. To upgrade Tioli Common Reporting: 1. Login as root or the user with which you installed Tioli Integrated Portal. 2. Stop Tioli Integrated Portal and Tioli Common Reporting: To stop these components enter the following command: <tipcomponents>/tcrcomponent/bin/stoptcrserer.sh <username> <password> For example: /opt/ibm/tioli/tip21components/tcrcomponent/bin/stoptcrserer.sh tipadmin tipadmin 3. Change to the directory containing the scripts on CDROM, for example contribs/tip-tcr. cd <CDROM>/contribs/TIP-TCR 4. Run the upgrade script 78 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
./upgrade_tcr.sh -tcrmedia {TCR-media-directory} -tipinstall {TIP-install-dir} For example:./upgrade_tcr.sh -tcrmedia /export/home/proiso/solaris/tcr/tcrinstaller -tipinstall /opt/ibm/tioli/tip21 Other options supported: tipusername U specify TIP admin username tippassword P specify TIP admin password tipport N specify TIP port (default is 16711) cognosport N Port number for IBM Cognos content database (default: 1527) locale L Locale for installation (default: en) 5. Start Tioli Integrated Portal and Tioli Common Reporting: To start these components enter the following command: <tipcomponents>/tcrcomponent/bin/starttcrserer.sh <username> <password> For example: /opt/ibm/tioli/tip21components/tcrcomponent/bin/starttcrserer.sh tipadmin tipadmin Chapter 5. Upgrading Tioli Integrated Portal and Tioli Common Reporting 79
80 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 6. Upgrading Tioli Netcool Performance Manager How to prepare and upgrade an existing Tioli Netcool Performance Manager 1.3.1 enironment to Tioli Netcool Performance Manager 1.3.2. Shutting down the Tioli Netcool Performance Manager components The Tioli Netcool Performance Manager components, except for the Database and Tioli Integrated Portal, need to be shut down for the upgrade procedure. There are a number of shutdown scenarios aailable: Shut down the DataChannel and DataMart components on all hosts now, leaing the DataLoad collectors running. An oeriew of the strategy is as follows: 1. Shut down the DataChannel and DataMart components on all hosts now. 2. Follow all the instructions in this chapter up to the section, Deploying the upgrade topology on page 93 3. When deploying, deploy all components but DataLoad. 4. When this deployment is complete, shut down DataLoad, deploy the DataLoad component, and then restart all components. This upgrade strategy reduces the period of no collections as the DataLoad collectors are only stopped while the installer deploys the upgraded DataLoad topology. To use this strategy, perform all steps in this chapter, choosing Deploy the upgrade topology for all components on page 94 when you deploy your upgrade topology. Shut down the DataChannel and DataMart components on all hosts now, and deploy the upgrade topology in your enironment to upgrade only one host at a time. An oeriew of the strategy is as follows: 1. Shut down the DataChannel and DataMart components on all hosts now. 2. Follow all the instructions in this chapter up to the section, Deploying the upgrade topology on page 93 3. If a host is running a DataLoad collector, you only shut down that collector, then upgrade the Tioli Netcool Performance Manager components on that host. This upgrade strategy minimizes the period of no collections by only stopping one DataLoad collector at a time, leaing other collectors aailable for data collection. To use this strategy, perform all steps in this chapter, choosing Deploy the upgrade topology to minimize collections loss on page 96 when you deploy your upgrade topology. Note: Tioli Integrated Portal must remain running. If Tioli Integrated Portal is not running, the Tioli Common Reporting upgrade and DataView upgrade will be successful, but the DataView migration step will fail. Copyright IBM Corp. 2006, 2013 81
Disabling the cron Jobs You must disable the cron jobs on each DataChannel host in your enironment by editing the crontab file. About this task To disable the cron jobs: 1. On the DataChannel host, log in as the component user, such as puser. 2. Open the crontab file for editing by using the following command: crontab -e 3. Comment out all jobs that start Tioli Netcool Performance Manager components and any third-party tasks that work with Tioli Netcool Performance Manager tools by inserting a # character at the beginning of the job statement. For example: Before: 0,5,10,15,20,25,30,35,40,45,50,55 ****. /opt/datachannel/datachannel.en && /opt/datachannel/bin/cnsw > /de/null 2>&1 After: # 0,5,10,15,20,25,30,35,40,45,50,55 ****. /opt/datachannel/datachannel.en && /opt/datachannel/bin/cnsw > /de/null 2>&1 4. When you hae made your edits, write and quit the file. Note: While the current cron jobs must be manually commented out, these job statements are automatically updated when you hae deployed your upgrade topology. This process is described in Starting the cron jobs on page 73. Shutting down DataChannel You must shut down the DataChannel components on each DataChannel host running in your enironment. About this task To shut down DataChannel: Note: The DataChannel CMGR, CNS, AMGR, and LOG isual processes must remain running until you hae gathered the DataChannel parameters from your enironment. 1. On the DataChannel host, log in as the component user, such as puser. 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 work queues must be emptied. To shut down the DataChannel FTE and empty the work queues: $./dccmd stop pattern FTE.* 4. Let all DataChannel components continue to process until the.../do directories for the FTE and CME components contain no files. 82 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
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 enironment does not run the DataLoad High Aailability Manager (HAM), use the following dccmd command to stop the DataChannel applications: $./dccmd stop all b. If your enironment runs the DataLoad High Aailability 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 Aailability Manager, the HAM application must remain running until you hae gathered the DataChannel parameters from your enironment. Shutting down DataMart You must shut down DataMart on each DataMart host running in your enironment. About this task To shut down DataMart: 1. On the DataChannel host, log in as the component user, such as puser. 2. Set and export the DISPLAY ariable. 3. Source the DataMart enironment using the following command: $. /opt/datamart/datamart.en 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: $ pmstat 7. Remoe any DataMart locks by selecting File > Remoe locks. Chapter 6. Upgrading Tioli Netcool Performance Manager 83
Verifying Netcool/Proiso components are shut down You must erify that the Netcool/Proiso components hae been shut down in your enironment. About this task To erify that Netcool/Proiso components hae been shut down: 1. 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,program FROM $session ORDER BY username,machine,program; On a system where all the clients hae been shut down, you would expect to see output like the following: USERNAME MACHINE PROGRAM PV_ADMIN Oak sqlplus@oak (TNS V1-V3)... USERNAME MACHINE PROGRAM PV_COLL Willow pmd@willow (TNS V1-V3) The first item is the SQL query itself, while the second item is a DataLoad collector. This is expected if you chose to leae the DataLoad collectors running in order to minimize collections loss. Installing and starting the Topology Editor Only one instance of the Topology Editor can exist in the Tioli Netcool Performance Manager enironment. Using the launchpad, install the Topology Editor on the serer you hae chosen as the primary deployer. You use the launchpad to install and start the topology editor on the primary deployer. Note: Best practice on an upgrade scenario is to uninstall the older ersion of topology editor and install the newer ersion of topology editor. 84 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Starting the Launchpad The steps required to start the launchpad. About this task To start the launchpad: 1. Log in as root. 2. Set and export the DISPLAY ariable. 3. Set and export the BROWSER ariable to point to your Web browser. For example: On Solaris systems: # BROWSER=/opt/mozilla/mozilla # export BROWSER On AIX systems: # BROWSER=/usr/mozilla/firefox/firefox # export BROWSER On Linux systems: # BROWSER=/usr/bin/firefox # export BROWSER Note: The BROWSER command cannot include any spaces around the equal sign. 4. Change directory to the directory where the launchpad resides. On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS On AIX systems: # cd <DIST_DIR>/proiso/AIX On Linux systems: # cd <DIST_DIR>/proiso/RHEL <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution. 5. Enter the following command to start the launchpad: #./launchpad.sh Installing the Topology Editor The steps required to install the Topology Editor. About this task Only one instance of the Topology Editor can exist in the Tioli Netcool Performance Manager enironment. Install the Topology Editor on the same system that will host database serer. You can install the Topology Editor from the launchpad or from the command line. To install the Topology Editor: Chapter 6. Upgrading Tioli Netcool Performance Manager 85
1. You can begin the Topology Editor installation procedure from the command line or from the launchpad. From the launchpad: a. On the launchpad, click the Install Topology Editor option in the list of tasks. b. On the Install Topology Editor page, click the Install Topology Editor link. From the command line: a. Log in as root. b. Change directory to the directory that contains the Topology Editor installation script: On Solaris systems: # cd <DIST_DIR>/proiso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM On AIX systems: # cd <DIST_DIR>/proiso/AIX/Install/topologyEditor/Disk1/InstData/VM On Linux systems: # cd <DIST_DIR>/proiso/RHEL/Install/topologyEditor/Disk1/InstData/VM <DIST_DIR> is the directory on the hard drie where you copied the contents of the Tioli Netcool Performance Manager distribution. c. Enter the following command: #./installer.bin The installation wizard opens in a separate window, displaying a welcome page. 2. Click Next. 3. Reiew and accept the license agreement, then click Next. 4. Confirm the wizard is pointing to the correct directory. The default is /opt/ibm/proiso. If you hae preiously installed the Topology Editor on this system, the installer does not prompt you for an installation directory and instead uses the directory where you last installed the application. 5. Click Next to continue. 6. Confirm the wizard is pointing to the correct base installation directory of the Oracle JDBC drier (/opt/oracle/product/11.0.2-client32/jdbc/libersion/ jdbc/lib), or click Choose to naigate to another directory. 7. Click Next to continue. 8. Reiew the installation information, then click Run. 9. When the installation is complete, click Done to close the wizard. The installation wizard installs the Topology Editor and an instance of the deployer in the following directories: Interface Directory Topology Editor install_dir/topologyeditor For example: /opt/ibm/proiso/topologyeditor Deployer install_dir/deployer For example: /opt/ibm/proiso/deployer 86 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Results The combination of the Topology Editor and the deployer is referred to as the primary deployer. For more information, see the "Resuming a partially successful first-time installation" section of the Tioli Netcool Performance Manager wireless Installation Guide. Note: To uninstall the Topology Editor, follow the instructions in the "Uninstalling the Topology Editor" section of the Tioli Netcool Performance Manager wireless Installation Guide. Do not delete the /opt/ibm directory. Doing so will cause problems when you try to reinstall the Topology Editor. If the /opt/ibm directory is accidentally deleted, perform the following steps: 1. Change to the /ar directory. 2. Rename the hidden file.com.zerog.registry.xml (for example, rename it to.com.zerog.registry.xml.backup). 3. Reinstall the Topology Editor. 4. Rename the backup file to the original name (.com.zerog.registry.xml). Starting the Topology Editor After you hae installed the Topology Editor, you can inoke it from either the launchpad or from the command line. To start the Topology Editor from the launchpad: 1. If the Install Topology Editor page is not already open, click the Install Topology Editor option in the list of tasks to open it. 2. On the Install Topology Editor page, click the Start Topology Editor link. To start the Topology Editor from the command line: 1. Log in as root. 2. Change directory to the directory in which you installed the Topology Editor. For example: # cd /opt/ibm/proiso/topologyeditor 3. Enter the following command: #./topologyeditor Note: If your DISPLAY enironment ariable is not set, the Topology Editor will fail with a Jaa assertion message (core dump). If you are running the Topology Editor for an AIX 6.1 or AIX 7.1 enironment, use the command: #./topologyeditor -m /opt/ibm/proiso/topologyeditor/jre/bin/jaa Chapter 6. Upgrading Tioli Netcool Performance Manager 87
Loading the upgrade topology into the Topology Editor To load the upgrade topology. 1. In the Topology Editor, select Topology > Open existing topology. The Open Topology window is displayed. 2. For the topology source, select where it is being loaded from: local If you select local, you will be required to click the Browse button and naigate to the desired topology file. From database If you select From database, you will be required to erify that all of the fields for the database connection are filled in with the correct alues: Database hostname The name of the database host. The default alue is localhost. Port The port number used for communication with the database. The default alue is 1521. Database user The user name used to access the database. The default alue is PV_INSTALL. Database Password The password for the database user account. For example, PV. SID The SID for the database. The default alue is PV. If desired, click Sae as defaults to sae these alues for future incremental installations. Note: If at any time you click cancel, memory is cleared and the topology is unchanged. 3. Click Next to change the topology. 4. Click Finish. The upgrade topology is displayed in the Topology Editor. 5. Sae the topology and close the topology. 6. Reopen the saed topology to edit it. 7. In the Topology Editor, make sure the MIGRATE_FROM_HOST property specifies the source DataView host, that is, the host containing the 1.3.1 DataView instance. Note: For some enironments, loading the upgrade topology into the Topology Editor can take seeral minutes. 8. Update the following properties: TIP_ADMIN_USER = tipadmin Port = 16710 TIP_ADMIN_PASSWORD = tipadmin 88 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Preparing the upgrade topology for deployment When the upgrade topology is initially loaded into the Topology Editor, it will contain seeral error and warning messages. Errors are expected. This section describes how to resole these issues and prepare the upgrade topology for deployment. Perform the following tasks: Upgrade of existing Tioli Integrated Portal. Determine which generated host definitions are alid, and decide which host definitions are extraneous and can be remoed. Moe Tioli Netcool Performance Manager components from the extraneous hosts to the alid host definitions so that the upgrade topology matches what exists in your current Tioli Netcool Performance Manager enironment. Delete the extraneous host definitions. Reiew the host and Tioli Netcool Performance Manager component properties so that they match the alues that exist in your current Tioli Netcool Performance Manager enironment. Verify that the upgrade topology matches your current Tioli Netcool Performance Manager install base before deploying the upgrade topology file. Note: If you plan to make changes to your Tioli Netcool Performance Manager enironment, such as adding or remoing hosts, components, or deploying an adanced configuration, you must upgrade your existing enironment first. Technology packs In general, you do not need to perform any special actions for technology packs when upgrading your Tioli Netcool Performance Manager enironment. The installed packs will function at the new leel of Tioli Netcool Performance Manager without requiring any technology pack upgrade. If you want to upgrade a technology pack after your Tioli Netcool Performance Manager enironment has been upgraded, or your enironment has the Alcatel-Lucent 5620 SAM or Cisco Netflow Technology Packs installed, see IBM Tioli Netcool Performance Manager: Technology Pack Upgrade Guide for more information. Note: If your pre-upgrade enironment contains technology packs that include XSD files, DO NOT import the XSD files into the Topology Editor until AFTER you hae finished upgrading your Tioli Netcool Performance Manager enironment. Determining alid host definitions In the Physical View, there can be seeral host definitions that appear for the same physical host, some of which may not be alid. About this task Extraneous host definitions can be generated when the upgrade topology is first created. You must determine which host definitions are alid and which host definitions are extraneous and can be renamed or later remoed. To determine which hosts are alid: Chapter 6. Upgrading Tioli Netcool Performance Manager 89
1. In the Topology Editor, examine each host definition that appears in the Physical View. You must either rename delete any host definitions with the following characteristics (only delete a host after its Tioli Netcool Performance Manager components hae been remoed): Host name is blank. For example: Host <blank> Host name is fully qualified: Host DOCSVR3.BBB.AAA.COM Note: Fully-qualified host names are not supported by Tioli Netcool Performance Manager. 2. If you determine that a host definition is alid and want to rename it, see Renaming host definitions on page 91. 3. If you determine that a host definition is extraneous and want to later delete it, you must moe the Tioli Netcool Performance Manager components from the extraneous host to a alid host definition. For more information, see Moing Tioli Netcool Performance Manager components between host definitions. Moing Tioli Netcool Performance Manager components between host definitions Once you hae determined which host definitions are alid in the Logical View, you must moe Tioli Netcool Performance Manager components from the extraneous hosts to the alid host definitions. About this task To moe Tioli Netcool Performance Manager components between hosts: 1. In the Topology Editor, right-click on the Tioli Netcool Performance Manager component in the Logical View that you want to moe, then select the Change host or Moe menu option. Note: The menu selection is Change Host or Moe depending upon the component that is selected. 2. In the Aailable hosts field, select the name of the host where you intend the Tioli Netcool Performance Manager component to reside from the scroll-down list. 3. Click Finish. 4. Repeat steps 1-3until all Tioli Netcool Performance Manager components hae been moed from the extraneous host definitions to their intended target host definitions. 90 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Deleting extraneous host definitions When you hae remoed all of the Tioli Netcool Performance Manager components from an extraneous host definition, you can delete the host definition from the Physical View. About this task To delete host definitions: 1. In the Topology Editor, right-click on the name of the host definition in the Physical View, then select the Remoe menu option. 2. Repeat step 1 until all of the extraneous hosts hae been remoed from the Physical View. Renaming host definitions Renaming host definitions. About this task To rename a host definition: 1. 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 enironment. Note: Fully-qualified host names are not supported by Tioli Netcool Performance Manager. 3. Click Finish. Verifying host properties You must erify the properties defined for each host in the Physical View so that they match the alues that exist in your current Tioli Netcool Performance Manager enironment. About this task If your enironment uses non-default alues for the Oracle data mount points, your site alues can be oerwritten by the Tioli Netcool Performance Manager defaults (/raid_2/oradata and raid_3/oradata, by default) when your upgrade topology is loaded into the Topology Editor. To remedy this issue, erify the O_MOUNTPOINT_1 and O_MOUNTPOINT_2 Database Configurations properties in your topology and input your site's alues, if necessary. To erify the host properties: 1. In the Topology Editor, select a host in the Physical View. 2. In the Properties and Adanced Properties tabs, it is possible that some properties are marked with a red X (missing or incorrect alue) or a yellow Chapter 6. Upgrading Tioli Netcool Performance Manager 91
exclamation point (inherited alue or is using a default alue). You must specify or erify the alues for any of the marked properties. 3. To specify or change the alue of a property, select the Value field for that property and enter the correct alue. The property must match what exists in your current Tioli Netcool Performance Manager enironment. Note: If you use seeral operating systems in your enironment, you must check that the correct operating system is specified for each host. 4. Remoe any unused custom properties. For more information, see Remoing unused custom properties. 5. Repeat STEP 1 through STEP 4 for each host definition in the Physical View. Verifying Tioli Netcool Performance Manager component properties You must erify the properties defined for each Tioli Netcool Performance Manager component in the Logical View so that they match the alues that exist in your current Tioli Netcool Performance Manager enironment. About this task To erify the Tioli Netcool Performance Manager component properties: 1. In the Topology Editor, select a Tioli Netcool Performance Manager component in the Physical View. 2. In the Properties and Adanced Properties tabs, it is possible that some properties are marked with a red X (missing or incorrect alue) or a yellow exclamation point (inherited alue or is using a default alue). You must specify or erify the alues for any of the marked properties. 3. Reiew any user credentials and passwords that are specified on the Adanced Properties tab for the current component. You must ensure that these alues match those that are correct for your site. 4. To specify or change the alue of a property, select its Value field and enter the correct alue. The property must match what exists in your current Tioli Netcool Performance Manager enironment. 5. Remoe any unused custom properties. For more information, see Verifying host properties on page 91. 6. Repeat STEP 1 through STEP 5 for each Tioli Netcool Performance Manager component in the Logical View. Remoing unused custom properties Examine each custom property and determine whether it is used in your enironment. If it is not used, remoe the property from the upgrade topology. About this task Custom properties are identified by a check mark in the Is Custom column of the Properties and Adanced Properties tabs. To remoe an unused custom property: 92 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
1. In the Topology Editor, select the custom property in the Properties or Adanced Properties tab. 2. Click the Remoe Custom Property button (a red X icon that appears in the Property iew). Saing the upgrade topology After you hae alidated your upgrade topology, you must sae your upgrade topology to the database. About this task You will later load this saed upgrade topology from the Tioli Netcool Performance Manager 1.3.2 database for deployment in your enironment. To sae your upgrade topology: 1. In the Topology Editor, click Topology > Sae topology as. 2. If you hae alidated your upgrade topology and are satisfied that it is correct, ignore the displayed warning message and click Ok. 3. Use the Browse button to naigate to the location where you wish to sae the upgrade topology. 4. Specify a name for the topology file, or use the default of topology.xml. 5. Click Ok. Deploying the upgrade topology When the topology has been completed it can be deployed. When the upgrade topology is ready to be deployed, deploy it using the primary deployer, that is, the host running the Topology Editor and Deployer. To deploy the upgrade topology, you can choose to either: Deploy the Upgrade Topology for All Components. This upgrade strategy results in a period of no collections that lasts for the duration of the upgrade procedure. To use this deployment method, you do the following: Shut down all DataLoad collectors in your enironment. Upgrade the Tioli Netcool Performance Manager components using the primary deployer. Deploy the Upgrade Topology to Minimize Collections Loss. This upgrade strategy minimizes the period of no collections by only stopping one DataLoad collector at a time, leaing other collectors aailable for data collection. To use this deployment method, you do the following: Deploy the upgrade topology in your enironment 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.2 components on that host. Once complete, you similarly upgrade the next host in your enironment until all hosts hae been upgraded. Chapter 6. Upgrading Tioli Netcool Performance Manager 93
Deploy the upgrade topology for all components To deploy the upgrade topology for all 1.3.2 components, perform the following tasks: Stop the DataLoad Collector. Deploy the Topology with the primary deployer. Run the primary deployer to upgrade the 1.3.2 components. Stop the DataLoad collector To stop the DataLoad collector: 1. Log in as the component user, such as puser, on the DataLoad host. 2. Source the DataLoad enironment using the following command: $. /opt/dataload/dataload.en 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 pmdmgr command to stop the DataLoad collector: $./pmdmgr stop 5. Repeat STEP 1 through STEP 4 for each DataLoad host in your enironment. Deploy the topology with the primary deployer To deploy the upgrade topology with the primary deployer: 1. In the Topology Editor, open the upgrade topology you created in Preparing the upgrade topology for deployment on page 89 from the Tioli Netcool Performance Manager database. 2. Click Run > Run Deployer for Installation. The deployer displays a welcome page. 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 (for example, PV), and erify the other alues (port number, SID, and user name). 5. Click Next to load the upgrade topology. The deployer displays a page stating that the enironment was successfully downloaded. 6. Click Next. The node selection window shows the target systems and how the files will be transferred (see the IBM Tioli Netcool Performance Manager: Installation Guide for an explanation of this window). The table has one row for each machine where at least one Tioli Netcool Performance Manager component will be installed. 7. If desired, reset the alues as appropriate for your deployment. Note: If a Run Remote step fails, you will hae to complete the step manually on the remote machine. For more information, see Appendix B, Deployment Considerations, on page 111. The deployer prompts you for the location of the setup files. 8. Click Choose the Proiso Media and browse to the location where you downloaded the Tioli Netcool Performance Manager distribution in 94 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 3, Downloading the Tioli Netcool Performance Manager distribution to disk, on page 31. The deployer displays summary information about the installation. 9. Click Next to continue. 10. Reiew 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 to Held. 11. Click Run All to run all the steps in sequence. Note the following: If an installation step fails, see the IBM Tioli Netcool Performance Manager: Installation Guide for debugging information. Continue the installation by following the instructions in Chapter 9, Resuming a partially successful first-time upgrade, on page 107. If the Tioli Common Reporting installation step fails, which can happen when there is not enough space aailable in /usr and /tmp or directory cleanup has not been carried out, run the tcrclean.sh script. To run this script: To run this script: a. On the host where the Tioli Common Reporting installation failed, change to the directory containing tcrclean.sh: cd /opt/ibm/proiso/deployer/proiso/bin/util/ b. Run tcrclean.sh c. When prompted, enter the install location of Tioli Common Reporting. Continue the installation by following the instructions in Chapter 9, Resuming a partially successful first-time upgrade, on page 107. 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 ersion: $ sqlpus PV_ADMIN/PV@PV bash-3.2$ sqlplus PV_ADMIN/PV@PV SQL*Plus: Release 11.2.0.2.0 Production on Sat Oct 8 18:42:52 2011 Copyright (c) 1982, 2010, Oracle. All rights resered. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0-64bit Production With the Partitioning option SQL> col STR_COMPONENT_NAME format a20 SQL> select str_application, str_component_name, str_major_ersion from ers_component_ersion c, ers_component c, ers_ersion where c.idx_component = c.idx_ind and c.idx_ersion =.idx_ind and c.str_component_name = Database and c.dte_date = ( select MAX(c1.dte_date) from ers_component_ersion c1 where c1.idx_component = c.idx_component Chapter 6. Upgrading Tioli Netcool Performance Manager 95
); 23456789101112 STR_A STR_COMPONENT_NAME STR_MAJOR_VERSION ----- -------------------- ------------------------------ INST Database 1.3.2.0 DB Database 1.3.2.0 c. Verify that the last 2 rows of the output (DB and INST) hae the same alue for STR_MAJOR_VERSION, and that the alue is 1.3.2. Note: If these alues do not match, then there has been a problem with the database upgrade. Do not continue with the upgrade until this problem has been resoled. d. Once you hae alidated that the Upgrade Proiso Database step has completed without errors, select the step immediately after Register Database step in the step list window. Right-click on this step and select Set Status > Ready. This will set the status of this and all subsequent steps to Ready. 13. Click Run All to run all the steps in sequence. 14. When all the steps hae completed successfully, click Done to close the wizard. Deploy the upgrade topology to minimize collections loss To deploy the upgrade topology to minimize collections loss, deploy the upgrade topology in your enironment so that you upgrade only one host at a time. This strategy minimizes the period of no collections by stopping only one DataLoad collector at a time, leaing other collectors aailable 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: Select the targeted host for deployment. If the host is running a DataLoad collector, shut down that collector. Run the primary deployer, de-selecting all the other hosts in the deployer so that only the Tioli Netcool Performance Manager components on the targeted host are upgraded. Deploy the topology by host You 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 in the deployer, so only the targeted host is upgraded. To deploy the upgrade topology on one host using the primary deployer: 1. If the targeted host is running a DataLoad collector: a. Log in as the component user, such as puser, on the DataLoad host. b. Source the DataLoad enironment using the following command: $. /opt/dataload/dataload.en c. Change your working directory to the DataLoad bin directory (/opt/dataload/bin by default) using the following command: 96 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
$ cd /opt/dataload/bin d. Use the pmdmgr command to stop the DataLoad collector: $./pmdmgr stop 2. In the Topology Editor, load the upgrade topology you created in Preparing the upgrade topology for deployment on page 89 from the Tioli Netcool Performance Manager database. 3. Click Run > Run Deployer for Installation. The deployer displays a welcome page. 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 (for example, PV), and erify the other alues (port number, SID, and user name). 6. Click Next to load the upgrade topology. The deployer displays a page stating that the enironment was successfully downloaded. 7. Click Next. The node selection window shows the target systems and how the files will be transferred (see the IBM Tioli Netcool Performance Manager: Installation Guide for an explanation of this window). The table has one row for each machine where at least one Tioli Netcool Performance Manager component will be installed. 8. Ensure that the Enable checkbox is selected for the target host only. De-select the Enable checkbox for any other hosts. If desired, reset the other alues as appropriate for your deployment. 9. Click Choose the Proiso Media and browse to the location where you downloaded the Tioli Netcool Performance Manager distribution in Chapter 3, Downloading the Tioli Netcool Performance Manager distribution to disk, on page 31. The deployer displays summary information about the installation. 10. Click Next to continue. 11. The deployer displays summary information about the installation. Reiew 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 to Held. 12. Click Run All to run all the steps in sequence. Note the following: If an installation step fails, see the IBM Tioli Netcool Performance Manager: Installation Guide for debugging information. Continue the installation by following the instructions in Resuming a partial upgrade on page 107. If the Tioli Common Reporting installation step fails, which can happen when there is not enough space aailable in /usr and /tmp or directory cleanup has not been carried out, run the tcrclean.sh script. To run this script: a. On the host where the Tioli Common Reporting installation failed, change to the directory containing tcrclean.sh: cd /opt/ibm/proiso/deployer/proiso/bin/util/ b. Run tcrclean.sh Chapter 6. Upgrading Tioli Netcool Performance Manager 97
c. When prompted, enter the install location of Tioli Common Reporting. Continue the installation by following the instructions in Resuming a partial upgrade on page 107. 13. When all the steps hae completed successfully, click Done to close the wizard. What to do next All of steps 1 to 13 listed aboe must be performed for each host in your topology. Update the datamart.en file You must edit the datamart.en to hold the correct Jaa and Oracle settings. About this task To change : 1. On the DataMart host, log in as the component user, such as puser. 2. Source the DataMart enironment using the following command: $. /opt/datamart/datamart.en 3. Update the alue for ORACLE_HOME to be that of your new Oracle 11g-Client32 directory. ORACLE_HOME for 11g 32 bit client should be /opt/oracle/product/ 11.2.0.2-client32/ 4. Add the following lines: ## Jaa # ------- DM_JAVA_HOME=$PVMHOME/jaa/jre DM_JAVA_EXEC=$DM_JAVA_HOME/bin/jaa export DM_JAVA_HOME DM_JAVA_EXEC Starting the Tioli Netcool Performance Manager components Except for DataChannel, all Tioli Netcool Performance Manager components should be running once the upgrade topology has been successfully deployed. Should you find that any components are not running after deployment, the following sections explain how they can be restarted. Starting the cron jobs During the upgrade process, the deployer creates new job statements in the crontab 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: 1. On the DataChannel host, log in as the component user, such as puser. 2. Open the crontab file for editing by using the following command: 98 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
crontab -e 3. When you hae made your edits, write and quit the file. Starting DataMart During the upgrade process, DataMart should automatically restart. Howeer, if DataMart has not been restarted, you must start it manually. About this task To start DataMart: 1. On the DataMart host, log in as the component user, such as puser. 2. Source the DataMart enironment using the following command: $. /opt/datamart/datamart.en 3. Change your working directory to the DataMart bin directory (/opt/datamart/bin by default) using the following command: $ cd /opt/datamart/bin 4. Use the pismgr command to start DataMart: $./pismgr start Starting DataView During the upgrade process, DataView should automatically restart. Howeer, if DataView has not been restarted, you must start it manually. About this task To start DataView: 1. On the DataView host, log in as the component user, such as puser. 2. Start Tioli Integrated Portal and Tioli Common Reporting: To start these components enter the following command: <tipcomponents>/tcrcomponent/bin/starttcrserer.sh <username> <password> Where: user: the Tioli Integrated Portal administrator name. password: the Tioli Integrated Portal administrator password. For example: /opt/ibm/tioli/tip21components/tcrcomponent/bin/starttcrserer.sh tipadmin tipadmin Starting DataChannel You must start the DataChannel components on each DataChannel host running in your enironment. About this task To start DataChannel: 1. On the DataChannel host, log in as puser. Chapter 6. Upgrading Tioli Netcool Performance Manager 99
2. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default) using the following command: $ cd /opt/datachannel/bin 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 management processes. For example: $./cnsw $./logw $./amgrw $./cmgrw 5. Make sure the processes started correctly. Use the following commands: ps -ef grep LOG grep - grep ; ps -ef grep AMGR grep - grep ps -ef grep CMGR grep - grep ;ps -ef grep CNS grep - grep 6. Use the dccmd command to start all DataChannel applications: $./dccmd start all 7. Use the dccmd command to erify that all of the DataChannel applications started properly by executing the following command: $./dccmd status all 100 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 7. Post upgrade steps Run the deploy_war.sh script A number of steps that may be required when you complete the upgrade of Tioli Netcool Performance Manager 1.3.1 to Tioli Netcool Performance Manager 1.3.2. After upgrade you must run the deploy_war.sh script, if cognos enablement or common pack serice was installed on the preious ersion of Tioli Netcool Performance Manager, that is, Tioli Netcool Performance Manager 1.3.1; otherwise, user can skip this task. About this task Carry out the steps documented in this topic only if cognos enablement or common pack serice was installed on the preious ersion of Tioli Netcool Performance Manager, that is, Tioli Netcool Performance Manager 1.3.1. 1. Change to the directory containing the scripts, contribs/tip-tcr. For example: cd <CDROM>/contribs/TIP-TCR 2. As the user which installed Tioli Common Reporting,, run the./deploy_war.sh script 3. Enter TIP location, or press Return to use the default, at the following prompt: TIP Installation Directory [ /opt/ibm/tioli/tip2 ]: 4. Enter the Tioli Integrated Portal Components location, or press Return to use the default, at the following prompt: TIP Components Installation Directory [ /opt/ibm/tioli/tip2components ]: 5. Enter the Oracle DB serer hostname at the following prompt, input is mandatory for this item: ORACLE_HOSTNAME: 6. Enter ORACLE_HOME, or press Return to use the default, at the following prompt: ORACLE_HOME [ /opt/oracle/product/11.2.0-client32 ]: 7. Enter the appropriate ORACLE_SID at the following prompt: Oracle SID (wireline DEFAULT: p; wireless DEFAULT: tdb): tdb 8. Enter the Oracle port, or press Return to accept the default, at the following prompt: ORACLE_PORT [ 1521 ]: 9. Enter Tioli Integrated Portal admin username, or press Return to accept the default, at the following prompt: TIPADMIN_USER [ tipadmin ]: 10. Enter the password for tipadmin user at the following prompt: tipadmin user password: 11. Enter the password for bicontrol user at the following prompt: bicontrol user password: 12. Restart Tioli Integrated Portal. Copyright IBM Corp. 2006, 2013 101
Install a libcrypto.so For full SNMP3 support, SNMP DataLoad must hae access to the libcrypto.so. About this task Note: As libcrypto.so is deliered as standard on Linux platforms, steps 1 and 2 are not required if you are running on Linux. For each new and existing SNMP DataLoad, you must perform the following steps. 1. 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 -x./libcrypto.a # ln -s libcrypto.so.0.9.8 libcrypto.so 3. Update the dataload.en file so that the LD_LIBRARY_PATH (on Solaris & Linux) or LIBPATH (on AIX) enironment ariables include the path: /usr/lib What to do next Check the ariable has been set by doing the following: 1. Open a fresh shell 2. Check the dataload.en file. 3. Bounce the SNMP DL Upon startup, with a alid library, the collector will log the following log messages: INFO:CRYPTOLIB_LOADED Library libcrypto.so (OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008, 0x90802f) has been loaded. INFO:SNMPV3_SUPPORT_OK Full SNMP3 support Auth(None,MD5,SHA-1) x Pri(None,DES,AES) is aailable. Post upgrade HAM configuration Steps that must be taken if you hae upgraded from a Tioli Netcool Performance Manager 1.3.1 system with HAM 1+1 to Tioli Netcool Performance Manager 1.3.2. About this task Once the spare has taken oer the SNMP.1.1 collection, check the output folder of the SNMP.1.1 folder. You will notice that the data files are stacking up in tnpmaix1. The FTE.1.1 fails to transfer the data from tnpmaix1. If you hae setup HAM enironment prior to the upgrade, the Topology Editor needs to be updated after successfully upgrading it to Tioli Netcool Performance Manager 1.3.2. 1. Using the topology editor, in the Logical View naigate to the Datachannel that hosts the primary collector. For example, Datachannel 1 Collector 1.1 102 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
2. From the Collector 1.1, naigate to FTE.1.1 and select the source property (of the spare collector) from the property table. 3. Reset the alue of that source property to the default. 4. Run the deployer. Note: Ensure the action to update the DC configuration runs. 5. Verify the configuration was updated by using the following command: dccmd debug CMGR "self dbcfgprint" grep SOURCE 6. Bounce the FTE For example: dccmd bounce FTE.*.* Upgrade Common Pack Serice Steps that must be taken if you hae upgraded from a Tioli Netcool Performance Manager 1.3.1 system which uses the Common Pack Serice. About this task If your preious installation of Tioli Netcool Performance Manager employed the Common Pack Serice, you must upgrade the common pack serice ersion to the ersion supported by Tioli Netcool Performance Manager 1.3.1. For information on how to carry out this upgrade, please see the chapter "Installing and configuring the Common Pack Serice" in the Model Maker Install and User Guide. Upgrading the Base Common Pack Suite Tioli Netcool Performance Manager 1.3.2 distribution CD also contains the BCP Suite (1.0.0.3-TIV-TNPM-BCPSUITE.tar.gz). About this task Upgrade a number of Base Common Packs (BCPs) from the Base Common Pack Suite that is now aailable on Tioli Netcool Performance Manager 1.3.2 distribution DVD/CD. Base Common Packs (BCPs) are themseles common packs and you upgrade them exactly as you upgrade any other common pack. For more information about BCPs, see The Base Common Pack Suite on page 104. Note: IBM is not mandating the upgrade to the latest BCP Suite immediately. Upgrade can be performed as per your conenience. 1. Download and extract the latest Base Common Pack Suite from 1.0.0.3-TIV-TNPM-BCPSUITE.tar.gz file to a location of your choice. 2. Uninstall the existing common packs. For instructions on uninstalling common packs, see Uninstalling common packs in IBM Tioli Netcool Performance Manager: Model Maker 1.2.0 Installation and User Guide. 3. Install the latest Base Common Pack Suite and the common packs that you uninstalled in step 2. For instructions on installing Base Common Packs, see Installing common packs in IBM Tioli Netcool Performance Manager: Model Maker 1.2.0 Installation and User Guide. Chapter 7. Post upgrade steps 103
The Base Common Pack Suite The Base Common Pack Suite is a set of generic Base Common Packs (BCPs), some of which are mandatory requirements for working with common packs. All common packs hae a dependency on at least one BCP, the TCR Time BCP. For Wireless users, BCPs proide the cross-endor technology support proided by GOMs and GOMlets for technology packs. The Base Common Pack Suite is updated periodically with the latest ersions of the BCPs. Before you install or create common packs, you must download the latest ersion of the Base Common Pack Suite, and install the BCPs you require. The Base Common Pack Suite consists of an archie file containing a set of common pack JAR files, which you must download and extract before installing. The TCR Time BCP is a mandatory dependent pack for all wireless and wireline common packs, and proides a common time dimension for reporting. It must be installed before you can work with any common packs. The Wireline Common BCP is a mandatory dependent pack for all wireline common packs. It must be installed before you can work with wireline common packs. Typically, a number of Wireless BCPs are dependent packs for a wireless common pack. Wireless BCPs support a number of Global Object Model (GOM) and GOMlet technology packs. Refer to indiidual wireless common pack release notes to see the list of dependent packs for a particular pack. For current ersion information about the Base Common Pack Suite, see the Known issues with Tioli Netcool Performance Manager 1.3.2 technote in the Support knowledge base. 104 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 8. Enabling Tioli Common Reporting on Tioli Netcool Performance Manager Once you hae upgraded the core system, install the latest ersion of Model Maker IBM Cognos Edition tooling to enable Common Reporting on Tioli Netcool Performance Manager. If you hae preiously used the Model Maker IBM Cognos Edition tooling with your Tioli Netcool Performance Manager 1.3.1 system, you must upgrade to the latest ersion. For more information about installing or upgrading Model Maker IBM Cognos Edition, see the latest ersions of the following guides: IBM Tioli Netcool Performance Manager: Model Maker IBM Cognos Edition Installation and User Guide IBM Tioli Netcool Performance Manager Installation Guide, and the chapter entitled "Enabling Common Reporting on Tioli Netcool Performance Manager". Copyright IBM Corp. 2006, 2013 105
106 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Chapter 9. Resuming a partially successful first-time upgrade Resuming a partial upgrade In this scenario, you try deploying a Tioli Netcool Performance Manager topology for the first time. You define the topology and start the installation. Although some of the components of the Tioli Netcool Performance Manager topology are installed successfully, the oerall installation does not complete successfully. It addition, it is possible to skip a section of the installation. For example, a remote node might not be accessible for some reason. After skipping this portion of the installation, resume the installation to continue with the remaining steps. The deployer will list only those steps needed to complete the installation on the missing node. For example, suppose that during the first installation, Oracle wasn't running, so the database check failed. Stop the installation, start Oracle, then resume the installation. To resume a partial upgrade. 1. 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 where you left off. Note: If you are asked to select a topology file in order to resume your installation, select the topology file you saed 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 drier (/opt/oracle/product/ersion/jdbc/lib), or click Choose to naigate to another directory. Click Next to continue. 4. The steps page shows the installation steps in the ery same state they were in when 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 preiously failed, reset it to Ready, then click Run Next. Verify that this installation step now completes successfully. 6. Run any remaining installation steps, erifying that they complete successfully. 7. At the end of the installation, the deployer loads the updated topology information into the database. Copyright IBM Corp. 2006, 2013 107
108 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Appendix A. Backup Modification Customers that hae already implemented the Tioli Netcool Performance Manager backup and recoery strategy must carry out the steps described in this section. If you hae preiously enabled Tioli Netcool Performance Manager backup, you must perform these steps in order for your backups to continue working properly. Prior practice Prior to this release, customers were required to modify a DataChannel configuration parameter (SHOULD_CHECK_DB_TO_DELETE_EOP) to enable backups. This DataChannel parameter is no longer used. Control of the database backup implementation has moed to a new database registry parameter, DATABASE.BACKUP. Upgrading the database backup procedure To enable the new database registry parameter, you must modify the following registry flag: About this task DATABASE.BACKUP.STATE : The default alue of this flag is 0. To enable backups you must update this flag to 1. To edit this flag: 1. Execute the command $ dbregedit p_admin/p 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. Sae the file. You should then see a message indicating a successful update: Configuration updated! Note: Consult the Registry and Space Management Technote for more information on using the dbregedit utility. 4. Log into sqlplus as PV_ADMIN and execute the following: SQL> Exec Pm_Backup.Reinit; Copyright IBM Corp. 2006, 2013 109
This is a required step that will reinitialize the package ariables used by the PVM_BACKUP procedure. What to do next Again, if you hae preiously enabled backup, you must perform these steps in order for your backups to continue working properly. 110 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Appendix B. Deployment Considerations Remote installation of all Tioli Netcool Performance Manager components is supported. Howeer, there may arise situations where a remote host does not support FTP or the remote execution of files. A remote host (a remote host is any host included in the topology that is not the host running the Topology Editor) may not support FTP or the remote execution of files. It is possible your topology may include hosts one which: FTP is possible, but REXEC/RSH are not. Neither FTP nor REXEC/RSH are possible This section describes how to deploy in these situations. FTP is possible, but REXEC or RSH are not For any remote host where FTP is possible, but REXEC or RSH are not, deployment of the required component or components must be carried out using the following steps. There are two options for deployment. Option 1: 1. Unselect the Remote Command Execution option during the installation. The deployer creates and transfers the directory with the required component package in it. 2. As root, log in to the remote system and manually run the run.sh script. 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 aailable, you can FTP or NFS the required component directory and deployer package to the remote machine. 2. The deployer connects to the database. 3. Install the required component. Neither FTP nor REXEC/RSH are possible For any remote host where neither FTP nor REXEC or RSH are possible the deployment of the required component or components must be carried out using the following steps. There are two options for deployment. 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. Copyright IBM Corp. 2006, 2013 111
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 aailable, you can FTP or NFS the required component directory and deployer package to the remote machine. 2. The deployer connects to the database, then installs the required component on this machine. 112 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user's responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law : INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, 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 be incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Copyright IBM Corp. 2006, 2013 113
IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objecties only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may ary. This information is for planning purposes only. The information herein is subject to change before the products described become aailable. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to 114 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of deeloping, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Each copy or any portion of these sample programs or any deriatie work, must include a copyright notice as follows: (your company name) (year). Portions of this code are deried from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights resered. If you are iewing this information in softcopy form, the photographs and color illustrations might not be displayed. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and serice names might be trademarks of IBM or other companies. A current list of IBM trademarks is aailable on the web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Goernment Commerce. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a trademark of Linus Toralds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. UNIX is a registered trademark of The Open Group in the United States and other countries. Notices 115
Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. 116 IBM Tioli Netcool Performance Manager: Upgrade Guide: 1.3.1 to 1.3.2
Printed in USA