IBM Rational Portfolio Manager 7.1.1.2 Interim Fix 005 Readme for UNIX

Contents

• Description
• New Features
• Problems Solved
• Known Problems
• Platforms NOT supported in Rational Portfolio Manager, version 7.1.1.2 interim fix 005
• Prerequisites for installing Rational Portfolio Manager, version 7.1.1.2 interim fix
• Installing Rational Portfolio Manager, version 7.1.1.2 interim fix for UNIX
• Contacting IBM Rational Software Support
• Notices and trademarks

Description

This is the fifth interim fix for Rational Portfolio Manager. This interim fix contains defect fixes to Rational Portfolio Manager, version 7.1.1.2. Interim fixes are cumulative, and contain all fixes delivered in previous interim fixes for the release. When you install interim fix 005, you will also get all the fixes delivered in the previous interim fixes.

To install this interim fix, in addition to the installation instructions contained in this Readme file, you also need to refer to the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade Guide. This guide is available at http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss?CTY=US&FNC=SRX&PBL=SC23-6197-02.

You can also find the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade information in the Rational Portfolio Manager 7.1.1.2 Information Center. The Information Center is available at http://publib.boulder.ibm.com/infocenter/ratportm/v7r1m1/index.jsp.

New Features

The new feature delivered in Rational Portfolio Manager, version 7.1.1.2 interim fix 005 is documented as an individual technote and is available at http://www.ibm.com/support/search.wss?rs=2178&tc=SSRR2G&q=RN7.1.1.2iFix005new&rankprofile=8

Problems Solved

Known Problems

The known problems are documented as individual technotes and are available at http://www.ibm.com/support/search.wss?rs=2178&tc=SSRR2G&q=RN7.1.1.2&rankprofile=8. As problems are discovered and resolved, the knowledge base is updated and maintained with new information. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

Platforms NOT supported in Rational Portfolio Manager, version 7.1.1.2 interim fix 005

• DB2® 8.2 32-bit is not available for Linux 3.0
• DB2 8.2 32-bit is not available for Solaris

Prerequisites for installing Rational Portfolio Manager, version 7.1.1.2 interim fix

Before you begin

1. Back up your existing database before applying the interim fix, to ensure a full recovery in case of crashes or failures.
2. Ensure you have a copy of the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade Guide for reference during the installation.
3. Ensure you have the following database connection information for updating the database component:

   For DB2 database

   • Database name
   • Instance owner
   • Instance owner password
   • Connected user and password, if applicable

   For Oracle database

   • ORACLE_HOME
   • ORACLE_SID or TNS string
   • Rational Portfolio Manager schema owner
   • Rational Portfolio Manager schema owner password
   • Rational Portfolio Manager database SYS user password
   • Connected user and password, if applicable

Installing Rational Portfolio Manager, version 7.1.1.2 interim fix for UNIX

1. Downloading the interim fix package

1. Download the interim fix package from here to your server.
2. Extract the interim fix package using the command:

   gunzip <IFix-package-name>.tar.gz

3. Untar the interim fix package by using the command:

   tar -xvf <IFix-package-name>.tar

   Note: In this Readme, the path where you extract the package, for example, /home/db2inst1/rpm/7.1.1.2-RATIONAL-RPM-Aix-iFix-005 is referred to as ${IFIX_PACKAGE}.
4. Stop the Rational Portfolio Manager Web application and the associated alert server.

2a. For DB2 users: Updating the database component

1. Open a terminal shell.
2. In the shell, navigate to the code subdirectory ${IFIX_PACKAGE}/Database/DB2
3. From the shell window, restart DB2 by running the following commands in sequence:

   db2 force applications all
   db2stop force
   db2start

4. From the shell window, update the DB2 package:
   1. Connect to the database (substitute the actual values for database name, instance owner, and instance owner password):

      db2 connect to <database_name> user <instance_owner> using <instance_owner_pwd>

   2. Retrieve the Rational Portfolio Manager shared object (SO) library file name stored in DB2, by running the following query:

      db2 "select procname, implementation from syscat.procedures where procname = 'SP_GET_VERSION'"

      The following table shows a sample result of a query, where the returned library file is 'myrpm'.

      PROCNAME	IMPLEMENTATION
      SP_GET_VERSION	/home/db2inst1/sqllib/function/myrpm!SP_GET_VERSION

      If the above query returns a library file name other than ibmrpm.so, rename the ibmrpm.so file found in the directory path in Step 2 to the name returned in the query. For example as per the above sample query, the returned library name is 'myrpm' and you need to rename ibmrpm.so to myrpm.so.

      To rename ibmrpm.so to myrpm.so, use the command mv ibmrpm.so myrpm.so.

5. To grant script execution rights, run the following command:

   chmod 777 applyIFix.sh

6. Run the following command:

   ./applyIFix.sh <database_name> <instance_owner> <instance_owner_pwd>
   <<connected_user>> <<connected_user_pwd>>

   Note: Parameters <<connected_user>> and <<connected_user_pwd>> are required only if the Rational Portfolio Manager database was setup using scenario #2 - connected user. For more information on scenario #2, refer to Rational Portfolio Manager 7.1.1.2 Installation and Upgrade guide.
7. Verify that the applyIFix.sh script copied the .so file identified in Step 4b into $DB2DIR/function directory. If not, copy the file manually.
8. To verify if the application of the interim fix was successful, in the shell window, perform the following steps:
   1. If instance owner credentials were provided in step 6, then connect to the database using the following command (supply the actual values for database name, instance owner, and instance owner password):

      db2 connect to <database_name> user <instance_owner> using <instance_owner_pwd>

   2. If connected user credentials were provided in step 6, then connect to the database using the following command (supply the actual values for database name, connected user, and connected user password):

      db2 connect to <database_name> user <connected_user> using <connected_user_pwd> 

   3. Enter the following stored procedure call that should return the value as 7.1.1.2:

      db2 "call sp_get_version()"

      Important: If the stored procedure call does not return the value as 7.1.1.2, then contact IBM Rational Software Support.
   4. Enter the following command, which should return a 32-digit alphanumeric character string, to indicate successful application of the interim fix:

      db2 "values(get_unique_id())"

      Note: If the command does not return such a value, then contact IBM Rational Software Support.

2b. For Oracle users: Updating the database component

1. Open a terminal shell.
2. In the shell window, change the path to ${IFIX_PACKAGE}/Database/Oracle
3. Grant script execution rights by running the following commands:

   chmod 777 applyIFix.sh
   chmod 777 verify_con_user.sh

4. Apply the interim fix according to the database scenario applicable.
   1. In an Instance owner scenario, run the script:

       ./applyIFix.sh

      Enter the following information when you are prompted:

      • ORACLE_HOME
      • ORACLE_SID or TNS string
      • Rational Portfolio Manager schema owner
      • Rational Portfolio Manager schema owner password
   2. In a Connected user scenario, run the following scripts:

      ./applyIFix.sh
      ./verify_con_user.sh

      Enter the following information when you are prompted:

      • ORACLE_HOME
      • ORACLE_SID or TNS string
      • Rational Portfolio Manager schema owner
      • Rational Portfolio Manager schema owner password
      • Rational Portfolio Manager connected user name
      • Rational Portfolio Manager connected user password
      • Rational Portfolio Manager database SYS user password
5. Check log files produced in ${IFIX_PACKAGE}/Database/Oracle/logs for errors.
   Note: If the log file lists invalid objects or other errors, then contact IBM Rational Software Support.
6. Update the Oracle leveling library with the appropriate one from the directory, ${IFIX_PACKAGE}/Database/Oracle/Leveling
   Note: For more information on shared library configuration, refer to Rational Portfolio Manager 7.1.1.2 Installation and Upgrade guide, Chapter 3. Installing IBM Rational Portfolio Manager database.

3. Updating the middleware component

Update the middleware component as specified in the Rational Portfolio Manager 7.1.1.2 Installation and Upgrade guide, Chapter 4. Installing IBM Rational Portfolio Manager middleware.

4. OPTIONAL - Installation of IBM Rational Portfolio Manager Open Data Access solution

The open data access solution facilitates access to data stored in Rational Portfolio Manager databases, through the creation of an external database that has a publicly documented schema. For more information about the feature and installation instructions, click here.

5. Restarting Rational Portfolio Manager

Restart the Rational Portfolio Manager Web application and the associated alert server.

Contacting IBM Rational Software Support

IBM Rational Software Support provides you with technical assistance.

For contact information and guidelines or reference materials that you need when you require support, read the IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

For product news, events, and other information, visit the product home page for Rational Portfolio Manager Software at http://www.ibm.com/software/awdtools/portfolio/index.html.

Before you contact IBM Rational Software Support, gather the background information that you need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

• What software versions were you running when the problem occurred?
• Do you have logs, traces, or messages that are related to the problem?
• Can you reproduce the problem? If so, what steps do you take to reproduce it?
• Is there a workaround for the problem? If so, be prepared to describe the workaround.

Notices and trademarks

© Copyright IBM Corporation 2000, 2009. All Rights Reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

The following paragraph does not apply to the United Kingdom or any other country where such provisions 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 OR CONDITIONS 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 may 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 improvements 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 provided for convenience only and do not in any manner serve 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.

Licensees of this program who wish to have 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:

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Trademarks and service marks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

• IBM
• Rational
• DB2
• WebSphere

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

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

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