Prospect® Web 2.2.7 Interim Fix 10 (2.2.7.10)
Prospect® Web 2.2.7.10 is an Interim Fix for Prospect® Web 2.2.7. It is a cumulative interim fix and includes all of the content from previous Prospect® Web 2.2.7 interim fixes.
Check you have installed on your system one of the versions required as
prerequisite, by running the show_installed command.
Note that 2.2.7 release is displayed as 2.2.7.0.
This Interim Fix introduces the solutions for IZ92549, IZ96486, IZ96101, IZ91934, IZ96488 and IZ92465.
This is documented in the Prospect® Web Administration Guide available on the IBM Tivoli Netcool Information Center.
Readme
file for: Prospect®
Web 2.2.7 Interim Fix 10 [Server: Build 1]
Product/Component Release: 2.2.7
Update Name: 2.2.7 Interim Fix 10 (2.2.7.10)
Fix ID: 2.2.7-PROSPECTWEB-IF00010
Publication Date: 9 July 2013
Last modified date: 5 July 2013
Table of Contents
Installation Privileges Required
Pre Upgrade installation Steps
Post-Upgrade Installation Instructions
Installing the Prospect® Web Administration Client
4 Release Details and Overview
Add User to LDAP Synchronisation Support
Disable/Enable 2.2.6 Report Header Compatibility Mode for CSV and Excel Downloads.
Stopping Database Activity to Enable Upgrade
Dataloading on Multi Instance Installation
Upgrading Oracle 10.2.0.4 Patch set to 10.2.0.5 Patch set
Install Oracle 10.2.0.5 Software
Copyright and Trademark Information
Download Prospect® Web 2.2.7
Interim Fix 10 from the following location:
ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_2.2.7/2.2.7-PROSPECTWEB-IF00010/
or access the fix from the table below.
Below is a list of components, platforms, and file names that apply to this readme file.
|
Product/Component Name: |
Platform: |
File: |
|
Prospect® Web Server Software |
Solaris |
|
|
Prospect® Web Administration Client |
Windows |
If your system has a security policy in place such that a session is
disconnected after a lengthy period of inactivity, you should disable this
setting before the upgrade starts.
There is a possibility that the upgrade can take a while to run. Since there is no user input required during the upgrade, this can make the session appears idle. If timeouts are not disabled, the upgrade terminal could be disconnected during the upgrade.
Please find the latest supported platforms in below:
· Oracle 10g 10.2.0.4 or Oracle 11g 11.2.0.1
Note: Ensure that you have sufficient file system free space to download, extract and install the patch.
Prospect® Web 2.2.7.10 Interim Fix cannot be uninstalled. Back up the Prospect® Web system, including the Oracle schema before you proceed with the upgrade.
|
Privilege |
Required |
|
Oracle flexpm user DBA role |
No |
|
Root privilege required |
No |
|
Oracle sys user password set to default (change_on_install) |
No |
|
UNIX flexpm account is part of dba group |
Yes |
This interim fix is installed via the wminstall command.
Note: By default, during a product upgrade, wminstall performs the ps-mgr stop all command, which allows all currently running reports, maintenance jobs, loader jobs to complete before shutting down. To shorten the amount of time that the Prospect® Web server is down for an upgrade, you can specify for wminstall to perform the ps-mgr halt command instead, which forces the middleware to shut down immediately, and causes any currently-running reports, maintenance jobs, and loader jobs to fail. In this case, the user is responsible for ensuring the correct termination of processes and the release of shared resources.
To request that only a “halt” is performed, move the spec.xml file to a local directory and change the following statement in the spec.xml file, which is currently set to “stop all”:
<PRE_INSTALL language="java">middleware_down_up -e</PRE_INSTALL>
to the following:
<PRE_INSTALL language="java">middleware_down_up -h</PRE_INSTALL>
In either case, the upgrade process automatically restarts the product.
Version 4.0.5-GA of JBoss is a prerequisite for this upgrade. Download the JBoss installation zip file from the following location: http://www.jboss.org/jbossas/downloads[2] (but do not extract the files). You need to know the directory name where the JBoss zip file is located, as this is used as the JBOSS_ZIP_DIR when running the upgrade.
The upgrade may abort due to database activity, i.e., open Oracle sessions other than the upgrade session. This is normal intended behaviour and will leave the system in a consistent pre-upgrade state. Partition Maintenance jobs will give rise to this. Stopping Database Activity to Enable Upgrade describes how to deal with Database Activity prior to an upgrade.
Install Oracle 10g (Version 10.2.0, 32-bit) Client software. When installing Oracle Client, use the following directories:
ORACLE_BASE -> /u01/apps/oracle_client
ORACLE_HOME -> /u01/apps/oracle_client/product/10.2.0
Download the Oracle 10g client installation file from My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com/
10gr2_client_sol.cpio
Note: Perform the installation using oracle user permissions. Do not run the Oracle Universal Installer (OUI) as root.
To install Oracle 10g Client, perform the following procedures:
1. Install Oracle 10g Client
2. Install Oracle 10g Client Patches
3. Post Installation Oracle 10g Client
Before
You Begin
This installation procedure assumes that you have already prepared the server as described in the preceding sections:
Install Oracle 10g Client
The Installer is a Java-based interface that uses the X Window system. Use a workstation with an X Window display, not a console. Start the Installer according to the following procedure.
To start the Oracle Installer
1. Use the following commands on the X session host to enable access to the X Window server.
$ xhost +
Note: Please make sure that the xhost command is available in your PATH environment variable. For Solaris, include /usr/openwin/bin in the PATH.
2. Use telnet or rlogin to log on to the database server host. Use the IBM Prospect Oracle logon account:
$ rlogin 'hostname' -l oracle
Substitute the appropriate server name for hostname.
3. Set the DISPLAY variable so that the Installer can access the X Window server:
$ export DISPLAY ; DISPLAY='hostname':0.0
Substitute the appropriate display hostname.
4. Copy the install package 10gr2_client_sol.cpio into a temporary directory, not the one that oracle is going to be installed in. For example, /u01/oinstall
5. Unpack the installation package:
cpio -icvdu < 10gr2_client_sol.cpio
6. Export ORACLE environment variable
export ORACLE_BASE=/u01/apps/oracle_client
export ORACLE_HOME=/u01/apps/oracle_client/product/10.2.0
7. Run the Installer in the background by using the ampersand (&).
./runInstaller &
This allows the command shell to accept additional commands. After running some initial checks, the Java client launches which configures and begins the installation.
8. On the WELCOME screen, click NEXT.
9. On the SELECT INSTALLATION TYPE window, select the ADMINISTRATOR option and click NEXT.
10. The SPECIFY HOME DETAILS window appears. Enter the following details:
Name: client_10g
Path: /u01/apps/oracle_client/product/10.2.0
Click NEXT.
11. Correct any reported errors on the PRODUCT-SPECIFIC PREREQUISITE CHECKS window, and click NEXT.
12. On the SUMMARY window, click INSTALL.
13. On the next ORACLE NET CONFIGURATION ASSISTANT window, select PERFORM TYPICAL CONFIGURATION check box and click NEXT.
14. Click NEXT on the WELCOME window.
15. Click FINISH after the ORACLE NET CONFIGURATION ASSISTANT: DONE window is displayed.
16. Log in as root and verify that the following environment variables are set:
ORACLE_OWNER = oracle
ORACLE_HOME = /u01/apps/oracle_client/product/10.2.0
Then, execute the following script:
/u01/apps/oracle_client/product/10.2.0/root.sh
Choose Y if the prompt displays “dbhome”, “oraenv” or “coraenv” already exist.
17. Click OK, after running the above script.
18. Click EXIT when the installation is complete.
Install Oracle 10g Client Patches
This section details changes that must be made at the client level to apply the Oracle supplied 10g patch for 10.2.0.4.
Download below 10g patch file for Solaris from My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com/
p6810189_10204_Solaris-64.zip
To start the Oracle Installer
1. Use the following commands on the X session host to enable access to the X Window server.
$ xhost +
Note: Please make sure that the xhost command is available in your PATH environment variable. For Solaris, include /usr/openwin/bin in the PATH.
2. Use telnet or rlogin to log on to the database server host. Use the IBM Prospect Oracle logon account:
$ rlogin 'hostname' -l oracle
Substitute the appropriate server name for hostname.
3. Set the DISPLAY variable so that the Installer can access the X Window server:
$ export DISPLAY ; DISPLAY='hostname':0.0
Substitute the appropriate display hostname.
4. Copy the install package p6810189_10204_Solaris-64.zip into a temporary directory, not the one that oracle is going to be installed in. For example, /u01/oinstall
5. Unpack the installation package:
$ unzip p6810189_10204_Solaris-64.zip
6. Export ORACLE environment variable
export ORACLE_BASE=/u01/apps/oracle_client
export ORACLE_HOME=/u01/apps/oracle_client/product/10.2.0
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
7. Run the Installer
$ cd Disk1
$ ./runInstaller
8. On the WELCOME screen, click NEXT.
9. On the SPECIFY HOME DETAILS screen, select the name of the Oracle home that you want to update, or select the Path that you want to update, and then click NEXT.
10. Correct any reported errors on the PRODUCT-SPECIFIC PREREQUISITE CHECKS screen, and click NEXT.
11. On the REGISTRATION screen, click NEXT.
12. On the SUMMARY screen, click INSTALL.
13. Click EXIT when finished.
Post Installation Oracle 10g Client
Create symbolic link between Oracle Database and Oracle 10g Client
If Oracle database installed is 10g,
$ln -s /u01/apps/oracle/product/10.2.0/network /u01/apps/oracle_client/network
$ln -s /u01/apps/oracle/product/10.2.0/dbs /u01/apps/oracle_client/product/10.2.0/dbs
$ln -s /u01/apps/oracle/admin /u01/apps/oracle_client/admin
$cp /u01/apps/oracle/product/10.2.0/bin/lsnrctl /u01/apps/oracle_client/product/10.2.0/bin
If Oracle database installed is 11g,
$ln -s /u01/apps/oracle/product/11.2.0/network /u01/apps/oracle_client/network
$ln -s /u01/apps/oracle/product/11.2.0/dbs /u01/apps/oracle_client/product/10.2.0/dbs
$ln -s /u01/apps/oracle/admin /u01/apps/oracle_client/admin
$cp /u01/apps/oracle/product/11.2.0/bin/lsnrctl /u01/apps/oracle_client/product/10.2.0/bin
Copy Database network configuration file to Oracle 10g Client
If the installed database is Oracle 11g, run the following command:
$ cp /u01/apps/oracle/product/11.2.0/network/admin/*ora /u01/apps/oracle_client/product/10.2.0/network/admin
If the installed database is Oracle 10g, run the following command:
$ cp /u01/apps/oracle/product/10.2.0/network/admin/*ora /u01/apps/oracle_client/product/10.2.0/network/admin
Note: This is important as wminstall needs this initial connection, else wminstall will fail.
Change
Oracle 10g Client home directory permission
Run the following command to change directory permission for the Oracle 10g client:
$ chmod -R 775 /u01/apps/oracle_client
Note: Failing to do this will make preset_oracle_paths fail.
1. Log on as user flexpm
2. Source the Prospect® Web Environment to be upgraded.
If the server is running multiple Prospect schemas or the profile for the Prospect® Web instance to be upgraded is not configured to be executed on log in as the flexpm user, then the profile must be sourced before applying this upgrade. Go to the correct directory where the Prospect® Web instance to be upgraded is installed and source the environment.
For example, if Prospect® Web is installed in /u01/apps/WatchMark/FlexPM/pweb
[flexpm] $ cd /u01/apps/WatchMark/FlexPM/pweb
[flexpm] $ . ./.profile
Alternately, if a menu system is in place to allow selection of the Prospect® Web system to be upgraded from a list of installed Prospect applications, then select the appropriate option to source the environment.
3. Create a temporary directory under $FLEXPM_HOME and copy the server tarball to this location
[flexpm] $ mkdir $FLEXPM_HOME/tmp
[flexpm] $ cp 2.2.7-PROSPECTWEB-IF00010-server.tar.gz $FLEXPM_HOME/tmp
[flexpm] $ cd $FLEXPM_HOME/tmp
4. Untar the server tarball
[flexpm] $ gunzip 2.2.7-PROSPECTWEB-IF00010-server.tar.gz
[flexpm] $ tar -xvpf 2.2.7-PROSPECTWEB-IF00010-server.tar
5. Run the upgrade command
[flexpm] $ ./wminstall -j <JBOSS_ZIP_DIR>
Note: It is strongly recommended to run the previous command with the –preview option before performing installation to identify potential problems.
[flexpm] $ ./wminstall -j <JBOSS_ZIP_DIR> -preview
The installation of the upgrade might take a while to complete .You can view the installation progress from the log file (with filename like <YYYY>__<MM>__<DD>__<HH>__<MM>__<SS>) under /tmp or /var/tmp from another console during the installation for the installation progress.
Note: When upgrading the Prospect® Web, the installation will use the spec.xml file in the same directory as wminstall. Specify the option -spec spec.xml if you changed it (for example to halt only Prospect® Web server before performing installation)
Note: It is also possible to fully automate the upgrade using nohup and the -r <responseFile.txt> option for wminstall.
a. Read the license agreement file, license.txt which will be in the $FLEXPM_HOME/tmp directory and make sure you understand the terms and conditions of the Prospect license.
b. Edit the response file, responseFile.txt in the $FLEXPM_HOME/tmp directory and find the entry:
LICENSE_ACCEPTANCE = false
c. Change the entry to the following to indicate that you agree to the terms and conditions of the Prospect license:
LICENSE_ACCEPTANCE = true
d. Run the installation by entering the following commands:
[flexpm] $ nohup ./wminstall -j <JBOSS_ZIP_DIR> -r $FLEXPM_HOME/tmp/responseFile.txt </dev/null &
The output will look like:
Sending output to nohup.out
The screen output of the wminstall command will go to $FLEXPM_HOME/tmp/nohup.out. In addition, the usual install log will be generated in the /var/tmp directory.
e. At this point wminstall is running via nohup. It is now safe to exit the console if you wish to. Type exit twice to quit from the console:
[flexpm] $ exit
You have running jobs.
[flexpm] $ exit
6.
Examine the Logs
After wminstall has completed, please examine the detail.log under the directory of $FLEXPM_HOME/audit/< YYYY>_<MM>_<DD>_<HH>_<MM>_<SS>_<PID> for any error messages.
Prospect® Web 2.2.7.10 assumes the LDAP administrator DN is the following:
cn=admin,cn=Administrators,cn=config
If you are using an alternate administrator DN, you will need to update the $FLEXPM_HOME/.profile.custom file with the following environment variables:
|
Variable Name |
Default Value |
|
LDAP_ADMIN_PREFIX |
cn= |
|
LDAP_ADMIN_SUFFIX |
cn=Administrators,cn=config |
For example if your administrator DN is the following:
uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot
1. Edit the $FLEXPM_HOME/.profile.custom file
[flexpm] $ vi $FLEXPM_HOME/.profile.custom
2. Append these two lines to the end of the file:
export LDAP_ADMIN_PREFIX="uid="
export LDAP_ADMIN_SUFFIX="ou=Administrators,ou=TopologyManagement,o=NetscapeRoot"
3. Save and close the file.
4. To have the variables take effect you need to log out and log back in as user flexpm and re-source the environment using the appropriate procedure as per the Upgrade Installation Steps above.
5. Restart the middleware:
[flexpm] $ ps-mgr stop all
[flexpm] $ ps-mgr halt
[flexpm] $ ps-mgr init
1. Stop middleware
[flexpm] $ ps-mgr stop all
[flexpm] $ ps-mgr halt
2. Edit profile.flexpm
[flexpm] $ vi $FLEXPM_HOME/.profile.flexpm
3. Change below variable in profile.flexpm file in the workspace
a. JAVA_HOME
i. Change it to point to java1.7
· JAVA_HOME=/usr/java
Note: Here /usr/java can be a soft link pointing to Java 1.7 installed directory.
b. WM_JVM_VERSION
i. Change this value to 1.7.0 as below
· WM_JVM_VERSION="1.7.0"
4. To have the variables take effect you need to log out and log back in as user flexpm and re-source the environment using the appropriate procedure as per the Upgrade Installation Steps above.
5. Check below details
a. echo $JAVA_HOME
b. echo $WM_JVM_VERSION
c. java -version
· export PERL5BIN="/usr/perl5/5.8.4/bin";
For upgrading oracle from 10.2.0.4 patch set to 10.2.0.5 patch set please refer to “Upgrading Oracle 10.2.0.4 Patch set to 10.2.0.5 Patch set” under “Documentation Addendums”.
Log out and log back in as user flexpm and re-source the environment using the appropriate procedure as per the Upgrade Installation Steps above.
Verify that the middleware started:
[flexpm] $ ps-mgr watch
If the middleware is not running then start it.
[flexpm] $ ps-mgr init
The server can be initialized after the upgrade has completed in one of 2 ways:
1. Open the Prospect® Web Administration Client and log in as a Prospect System Administrator user.
2. Run the following command to initialize the server after the upgrade has completed and the middleware has been restarted.
[flexpm] $ initserver.sh -username <<ldap_user>> -password <<ldap_password>>
The ldap_user and ldap_password are the username and password of a Prospect System Administrator
1. Copy 2.2.7-PROSPECTWEB-IF00010-client.zip on your Windows system in a temporary directory.
2. Unzip 2.2.7-PROSPECTWEB-IF00010-client.zip.
3. Go to the directory where you unzipped the file and run setup.exe
The installer creates the necessary system and application files, updates the system’s registry, and adds entries to Windows START menu.
To uninstall the Prospect® Web Administration client, use the ADD/REMOVE PROGRAMS component of the Windows Control Panel.
IBM Prospect® Web 2.2.7 Interim Fix 10 contains the following features, enhancements and resolved issues as outlined below:
Table 1 – Release Details – New Platform support in 2.2.7.10
|
Platform |
Release |
Description |
|
Java 1.7.0 support |
2.2.7.10 |
Provides Java SDK 7 support |
|
Perl 5.8.4 support |
2.2.7.10 |
Provides Perl v5.8.4 support |
|
Oracle 10.2.0.5 support |
2.2.7.10 |
Provides Oracle 10.2.0.5 patch set support |
Table 2 – Release Details – Features in 2.2.7.10
|
Feature |
Release |
Description |
|
SSL Enhancement |
2.2.7.10 |
Support for SSL Enhancement |
Table 3 – Release Details – Resolved issues in 2.2.7.10
|
Issue Tracking Number |
Release |
Resolved Issues |
|
IV02147 / alm00242217 |
2.2.7.10 |
EDIT_FRAGMENT.JSP NOT FOUND DURING REPORT GROUP CREATION |
|
IV08365 / alm00253551 |
2.2.7.10 |
MULTIPLE SELECTION OF ATTRIBUTE IN FIELD SELECTION |
|
IV08353 / alm00248055 |
2.2.7.10 |
MOTCM-TBD: HTTP 500 error when opening a report |
|
alm00210865 |
2.2.7.10 |
8077 d3: Slash should be change '/' and mandatory option Script usage portion in move_pweb_document.sh and delete_pweb_docum. |
|
alm00221233 |
2.2.7.10 |
8078 d2: ProgressDialog box appear when feting the data from the server in pweb |
Table 4 – Release Details – Resolved issues in previous Prospect® Web 2.2.7 Interim Fixes
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
IZ92549 / alm00224816 |
2.2.7.9 |
RDA CHART FAILED TO HANDLE DST CHANGE |
|
IZ96486 / alm00228682 |
2.2.7.9 |
OUT OF MEMORY ERROR |
|
IZ96101 / alm00228929 |
2.2.7.9 |
NOT ALL REPORTS ARE RUNNING IN A SCHEDULED REPORT GROUP |
|
IZ91934 / alm00223344 |
2.2.7.9 |
FOLDERS ARE NOT BEING PURGED AS EXPECTED IN PROSPECT WEB |
|
IZ96488 / alm00228939 |
2.2.7.9 |
USAGE OF REPORTIMPORTEXPORT FOR -PASSWORDFILE PARAMETER |
|
IZ92465 / alm00224819 |
2.2.7.9 |
ATTRIBUTES WITH BRIDGE FUNCTION DON'T WORK IN DASHBOARD |
|
IZ92549 / alm00224816 |
2.2.7.9 |
RDA CHART FAILED TO HANDLE DST CHANGE |
|
IZ96486 / alm00228682 |
2.2.7.9 |
OUT OF MEMORY ERROR |
|
IZ96101 / alm00228929 |
2.2.7.9 |
NOT ALL REPORTS ARE RUNNING IN A SCHEDULED REPORT GROUP |
|
IZ91934 / alm00223344 |
2.2.7.9 |
FOLDERS ARE NOT BEING PURGED AS EXPECTED IN PROSPECT WEB |
|
IZ96488 / alm00228939 |
2.2.7.9 |
USAGE OF REPORTIMPORTEXPORT FOR -PASSWORDFILE PARAMETER |
|
IZ92465 / alm00224819 |
2.2.7.9 |
ATTRIBUTES WITH BRIDGE FUNCTION DON'T WORK IN DASHBOARD |
|
IZ89097 / alm00215534 |
2.2.7.8 |
AFTER UPGRADING PWEB TO 227.7, SCHEDULED REPORTS DID NOT RUN. |
|
IZ84654 / alm00204084 |
2.2.7.8 |
REPORT PAGE IS STUCK ON FIELD SELECTIONS WITH "LOADING DATA" |
|
IZ88932 / alm00215255 |
2.2.7.8 |
PWEB 227.7 MONITOR IS NO LONGER DISPLAYING FUTURE SCHEDULED REPORT JOBS (NEXT JOB TIME) WITH MESSAGE 'SCHEDULED TO RUN' |
|
IZ79897 / alm00155772 |
2.2.7.7 |
COVER OF HELP PAGES ON PM SERVER SHOWING EMPTY |
|
IZ80763 / alm00196717 |
2.2.7.7 |
PIE CHART DISPLAYS NULL VALUE AS ZERO IN REPORT |
|
IZ85498 / alm00206232 |
2.2.7.7 |
PAB START-UP ISSUE |
|
IZ77180 / alm00155435 |
2.2.7.6 |
SOFT ALARM GROUPS SHOULD NOT SHOW IN THE REPORT GROUP DEFINITIONS IN PWEB. |
|
IZ78030 / alm00155576 |
2.2.7.6 |
USER CAN NOT HIDE FIELDS/ATTRIBUTES FROM SCP PAGE. |
|
IZ78228 / alm00155615 |
2.2.7.6 |
RDA TOOL IS NOT IN SYNC WITH CURRENT INTERVAL. |
|
IZ72941 / valnt00106603 |
2.2.7.5 |
ISSUES WITH 'SCHEDULED TO RUN" JOBS |
|
IZ74123 / valnt00109475 |
2.2.7.5 |
PWEB 2.2.7 ADMIN CLIENT RECEIVES "OUT OF MEMORY" AND "GDI+ E |
|
IZ75084 / valnt00112185 |
2.2.7.5 |
ISSUE PREVENTS ADEQUATE IMPORT OF REPORTS |
|
IZ75629 / valnt00113356 |
2.2.7.5 |
UNKNOWN ERROR WHEN SAVING REPORT GROUP WITH EXISTING NAME |
|
IZ76621 / valnt00115960 |
2.2.7.5 |
PROSPECT WEB REPORT HEADINGS GOT CHANGED AFTER PWEB 227.4 UPGRADE. |
|
IZ73009 / valnt00107645 |
2.2.7.4 |
ENTRIES IN WMLDAPAPI.PROPERTIES.TEMPLATE FILE NEED TO MOVE INTO.PROFILE.CUSTOM |
|
IZ72202 / valnt00104850 |
2.2.7.4 |
OMMISSION IN 8.0.7.1 RELEASE NOTES |
|
IZ72126 / valnt00104741 |
2.2.7.4 |
RELEASE NOTES NEED TO SPECIFY IF NOHUP CAN BE USED WITHWMINSTALL IN UPGRADES. |
|
IZ71764 / valnt00104531 |
2.2.7.4 |
8.0.7.2 AND 8.0.7.3 RELEASE NOTES ARE MISSING INFORMATIONREGARDING JBOSS |
|
IZ69093 / valnt00102340 |
2.2.7.4 |
KCI TRENDED REPORT ISSUES: TOO MANY LEGENDS AND CORRUPTED CHARTS |
|
IZ69063 / valnt00102308 |
2.2.7.4 |
CHART BY OPTIONS PUT ALL ENTITIES AND FIELDS IN A SINGLE CHART |
|
IZ69070 / valnt00102302 |
2.2.7.4 |
LINE AND AREA CHARTS DO NOT SHOW THE VALUE OF DATA POINT. |
|
IZ69152 / valnt00101892 |
2.2.7.4 |
NSBH & SBH NOT IDENTICAL |
|
IZ61286 / valnt00095201 |
2.2.7.4 |
WMINSTALL PROCEEDS TO INSTALL WHEN GTAR FAILS |
|
IZ72474 / valnt00105511 |
2.2.7.4 |
MISSING DOCUMENTATION IN THE ADMIN GUIDE HOW TO HAVE A LOGOAPPEAR ON THE PWEB LOGIN SCREEN |
|
IZ69072 / valnt00102305 |
2.2.7.4 |
KCI TRENDED REPORT ISSUE: CHART DATE LABELS ARE REPEATED |
|
IZ69561 / valnt00102860 |
2.2.7.4 |
ADDUSERTOLDAP.SH FAILS ON SYSTEM WHERE 2 LDAP REPLICAS AREDEPLOYED |
|
IZ70753 / valnt00103919 |
2.2.7.4 |
DETAIL LOG SHOWS SUCCESS / NO ERRORS DESPITE CRITICAL ORA ERRORS |
|
IZ72098 / valnt00104729 |
2.2.7.4 |
WRONG HELP POPUP DISPLAY WHEN POINT TO EDIT AND SAVE BUTTON |
|
IZ74164 / valnt00109674 |
2.2.7.4 |
EXPORT/IMPORT DOCS API IN PROSPECT DOES NOT WORK AS EXPECTED. |
|
IZ50854 / valnt00090676 |
2.2.7.3 |
PWEB(WEB03): USER REPORTS FAILED WITH ORA-00904 |
|
IZ66907 / valnt00100001 |
2.2.7.3 |
PM REPORTS: UNEXPECTED FONT CHANGE TO SMALL FONT |
|
IZ67516 / valnt00100384 |
2.2.7.3 |
MISLEADING ERROR MESSAGE WHEN CREATING REPORT GROUP |
|
IZ67527 / valnt00100381 |
2.2.7.3 |
WRONG ERROR MESSAGE WHEN DELETING REPORT GROUP |
|
IZ68293 / valnt00101097 |
2.2.7.3 |
WRONG TIME SLOT DISPLAYED IN REPORT SCHEDULE OR DEFINITION WITHDATE-TIME OVERRIDE OPTION |
|
valnt00099486 |
2.2.7.3 |
Extended forecasting chart displays a field's missing data as zeros |
|
valnt00099549 |
2.2.7.3 |
ORA error on BSC Std Report (Pcalc) |
|
IZ54679 / valnt00091154 |
2.2.7.2 |
OVER TIME, THE PWEB UI BECOMES VERY SLOW. $PM_HOME/PM/PAS/BIN/MEMORY.SH SCRIPT SHOWS AVERAGE AVAILABLE MEMORY DECREASES DAIL |
|
IZ55664 / valnt00091901 |
2.2.7.2 |
PWEB REPORT FIELDS LOST AFTER FAILED UPGRADE ON A REMOTEPROSPECT SERVER |
|
IZ65825 / valnt00099074 |
2.2.7.2 |
SCHEDULED REPORT FAILED WITH "UNEXPECTED SQL ERROR: ORA-00904 |
|
IZ65826 / valnt00099068 |
2.2.7.2 |
PROJTIME FUNCTION RETURN NEGATIVE VALUE |
|
IZ65827 / valnt00099065 |
2.2.7.2 |
SORTING OF PM REPORT ATTRIBUTES, ENTITY IDS ARE NOT NUMERICSORTED |
|
IZ65830 / valnt00099071 |
2.2.7.2 |
SEVERAL CHART RELATED ISSUES FOUND AFTER 807 UPGRADE |
|
IZ65972 / valnt00097261 |
2.2.7.2 |
NUMBERS FORMATTING ISSUE |
|
IZ66599 / valnt00094810 |
2.2.7.2 |
Header in downloaded CSV file is not concatenation of headlines 1 & 2. |
|
IZ56488 / valnt00092644 |
2.2.7.1 |
PWEB REPORT PERFORMANCE AFFECTED BY FULL TABLE SCANS ON THEWM_INSTANCE_CONTEXT TABLE ON THE REMOTE DATASOURCE SERVER. |
|
IZ61976 / valnt00096043 |
2.2.7.1 |
PWEB REPORTS RETURN BLANK AND INCORRECT VALUES AFTER CORE PATCH 8.0.6.3 IS APPLIED TO THE REMOTE PROSPECT SERVER. |
|
valnt00079499 |
2.2.7.1 |
MyProspect Page - SQL Reports, Data Loading Issues |
|
valnt00081050 |
2.2.7.1 |
Pweb Hybrid: Monitor jobs/tasks page displays all the reports irrespective of the server selected i.e Web server/Remote server |
|
valnt00085644 |
2.2.7.1 |
Issues with SET button in Extended Functions |
|
valnt00086351 |
2.2.7.1 |
The report save dialog box shows invalid folder name. |
|
valnt00086405 |
2.2.7.1 |
PWEB 2.2.7 FI - Wrong destination folder were showing when Opening a vault report from reporting->open report page and saving |
|
valnt00092844 |
2.2.7.2 |
Trend values not overlayed on projectTime values in forecasting charts when "show limits" checkbox enabled |
|
valnt00094048 |
2.2.7.1 |
Links in prospect web not identifiable |
|
valnt00094064 |
2.2.7.1 |
Health Check command fails on PM server. |
|
valnt00094068 |
2.2.7.1 |
Unable to change password from pweb Account Management Tab |
|
valnt00094080 |
2.2.7.1 |
The start and end time drop down list in the context of day, week and month should not be present |
|
valnt00094084 |
2.2.7.1 |
Wrong schedule name gets displayed (while deleting a schedule) |
|
valnt00094098 |
2.2.7.1 |
Submitting new page number in HTML reports functioning incorrectly |
|
valnt00094103 |
2.2.7.1 |
Report Need have a mechanism to handle stuck PWEB report |
|
valnt00094115 |
2.2.7.1 |
Failed Activities on Traffic Agents |
|
valnt00094119 |
2.2.7.1 |
Analysis Agent Failing Issues |
|
valnt00094268 |
2.2.7.1 |
The programming error's were found under MyProspect Pages. |
|
valnt00094306 |
2.2.7.1 |
Favourite Page in Chart format fails to be displayed |
|
valnt00094307 |
2.2.7.2 |
Choosing Histogram option to report displays non-blocking error message |
|
valnt00094407 |
2.2.7.1 |
Privilege" The Power Web User with write privilege can able to Edit the system admin's report group. |
|
valnt00094415 |
2.2.7.1 |
reportImportExport.sh always returns code 0 |
|
valnt00094467 |
2.2.7.1 |
deleteUserDocs.sh script needs to be ported over to Pweb 2.2.7 |
|
valnt00094476 |
2.2.7.1 |
PWeb Performance Metrics Not Sorted & Scripts not runnable outside of $FLEXPM_HOME/pm/pas/bin/perf dir |
|
valnt00094810 |
2.2.7.1 |
Header in downloaded CSV file is not concatenation of headlines 1 & 2. |
|
valnt00094819 |
2.2.7.1 |
Space in auto-organized output in schedule definition |
|
valnt00095169 |
Analyze Job creating invalid statistics |
|
|
valnt00095520 |
2.2.7.1 |
Loading flexpm environment take's too much time, this enhancement would reduce the time taken to source the environment |
|
valnt00096835 |
2.2.7.1 |
Add support for elemprotect to pweb/classic rep-gens |
Table 5 - The known issues for Web 2.2.7 Interim Fix 10
|
alm00253551 |
Issue: Multiple selections of attributes in field selection.
Description: Duplicate fields can be added into Field Selections dashboard by double clicking on selected field multiple times and “Delete Selected Fields” only remove one field each time when duplicate field are selected.
Expected Result: Only unique field can be selected in “Field Selections” dashboard.
Actual Result: Duplicate fields are selected.
Work Around: Not Applicable. |
|
alm00238076 |
Issue: Worksheet name is displayed incorrectly when user choose to download and open CSV file directly from Prospect Web.
Description: Worksheet name will be added addition prefix ".csv]" when user selects “Download CSV" in Prospect Web and c "Open" on "File Download" dialog. The root cause is because Internet Explorer will automatically appends additional character "[" and "]"that eventually cause excel appends unexpected prefix in worksheet name. Kindly refer to http://support.microsoft.com/kb/325630 for unexpected Internet Explorer behavior, and http://support.microsoft.com/kb/306656 for Microsoft Excel behavior.
Expected Result: Worksheet name should consistence with filename.
Actual Result: Worksheet name displays with additional prefix ".csv]".
Workaround: Choose” Save" instead of "Open" on "File Download” dialog to save file into local disk, then open the file from saved location. |
An optional synchronisation delay has been introduced in the addUserToLdap.sh CLI functionality. This introduces a pause between LDAP commands that are invoked by the addUserToLdap.sh CLI.
This feature is enabled by defining in the environment a variable whose value is the synchronisation delay time in milliseconds. The instructions for using the synchronisation delay feature are as follows:
1. Shutdown the Prospect Middleware
[flexpm] $ ps-mgr stop all
[flexpm] $ ps-mgr halt
2. Edit the $FLEXPM_HOME/.profile.custom file
[flexpm] $ vi $FLEXPM_HOME/.profile.custom
3. Append this line to the file:
export LDAP_SYNC_DELAY=<<N>>
Where N is number of milliseconds to pause between LDAP actions.
4. Save and close the $FLEXPM_HOME/.profile.custom file.
5. Log out and log back in as user flexpm and re-source the environment using the appropriate procedure as per the Upgrade Installation Steps above.
6. Validate that the new LDAP parameter is defined
[flexpm] $ env | grep LDAP_SYNC_DELAY
The LDAP_SYNC_DELAY variable setting should be displayed.
7. Start up the middleware
[flexpm] $ ps-mgr init
Note that the addUserToLdap.sh command is used as previously regardless of whether the LDAP_SYNC_DELAY variable has been set in the environment.
System variable, web.reporting.226.compatible, is introduced to control the 2.2.6 report header compatible mode for CSV/Excel downloads. (Please refer to APAR IZ76621 for more information)
|
System Variable |
Action |
Purpose/Remarks |
|
web.reporting.226.compatible |
Set value to TRUE |
CSV/Excel Report download uses entity.field as report header. |
|
web.reporting.226.compatible |
Removed from system |
[Default] CSV/Excel Report download uses headings 1/2 as report header. |
The following steps are to set value to TRUE
1. Log on to the database by typing the following command:
$sqlplus $DB_CONNECT
2. Run the following SQL:
SQL> exec wm_sysval.newsysval('web.reporting.226.compatible','TRUE');
commit;
3. Exit the sqlplus.
The following steps are to remove the system variable.
1. Log on to the database by typing the following command:
$sqlplus $DB_CONNECT
2. Run the following SQL:
SQL> exec wm_sysval.deletesysval('web.reporting.226.compatible');
commit;
3. Exit the sqlplus.
The system value may be applied prior to upgrading to version 2.2.7.5. However, it will only take effect after 2.2.7.5 or greater is installed. If you apply the system value after upgrading to 2.2.7.5, it may take 5 ~ 30 minutes to take effect for report results generated prior to applying the system value.
Note: When choosing the combination of variables for naming the report results contained within a scheduled report group, it is recommended to include a unique variable (e.g. $ID or $REPORTNAME) that will uniquely name a report result within each individual report definition in the group. If a unique variable is not included, all the report results will be overwritten to the same dynamic file name.
This will have the effect of making it appear as if only one report ran within the Report Group.
Note: You may notice an additional and duplicated hour with no data activity on the day where DST (Daylight savings time) fallback is happened. For example, in time zone "US/Central", you will see a red gap from 2011-11-06 01:00:00 to 2011-11-06 02:00:00 which is happened an hour before the DST time ends.
The Java 7 JDK is a development environment for building applications, applets, and components using the Java programming language. If you do not have Java version 1.7 installed on your system, then you must install the Java 7 JDK. IBM Prospect supports Java version 1.7.XXXX only.
To determine the version of the Java 7 JDK, use the following command:
# java -version
If Java is installed in your current path, then the response is similar to:
java version "1.7.XXXX"
To install JDK 1.7 on Solaris SPARC machine
Note: 32-bit and 64-bit packages are required to be installed in order to support Java 1.7.
1.Download the packages from:
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html.
jdk-7u<version>-solaris-sparc.tar.Z (32-bit)
jdk-7u<version>-solaris-sparcv9.tar.Z (64-bit)
2.Extract or Unzip the packages with the help of the following commands:
#zcat jdk-7u<version>-solaris-sparc.tar.Z | tar xf -
#zcat jdk-7u<version>-solaris-sparcv9.tar.Z | tar xf -
3.Run the following command to install the 32-bit Packages:
#pkgadd -d . SUNWj7rt SUNWj7dev SUNWj7cfg SUNWj7man SUNWjavadb-client SUNWjavadb-common SUNWjavadb-core SUNWjavadb-demo SUNWjavadb-docs SUNWjavadb-javadoc SUNWjavadb-service
4.Run the following command to install the 64-bit support Packages:
#pkgadd -d . SUNWj7rtx SUNWj7dvx SUNWj7dmx
5.Verify that the folder ‘JDK1.7.0_version’ exists at the ‘/usr/jdk/’ location.
The upgrade asserts that there are no other active Oracle sessions for the instance being upgraded.
Scenarios that may give rise to this include the following,
This appendix describes how to deal with each of these scenarios.
Partition maintenance jobs may cause the upgrade to abort, this is normal. Upgrade may be postponed until partition maintenance is completed or partition maintenance may be stopped and prevented from restarting using the following procedure.
Note that this procedure may also stop partition maintenance session on other instances on a multi instance installation.
1. Log on as user flexpm
2. Using the system administrator password, connect to sqlplus as the sysdba user
[flexpm] $ sqlplus sys/<SYSPASSWD> as sysdba
3. Run the following SQL,
-- Kill off part_maint jobs before upgrade
DECLARE
BEGIN
FOR indx1 IN (SELECT job
FROM user_jobs
WHERE what LIKE '%part_maint.part_session%') LOOP
dbms_job.remove(indx1.job);
END LOOP;
COMMIT;
END;
/
-- Remove any part_maint
sessions that may still be running for partition maintenance.
DECLARE lv_session_info VARCHAR2(100);
lv_sqlstr VARCHAR2(300);
BEGIN
FOR indx1 IN (SELECT sid,
serial#
FROM v$session
WHERE module LIKE 'Part%') LOOP
BEGIN
lv_session_info := '''' || indx1.sid ||
',' || indx1.serial# || '''';
lv_sqlstr
:= 'ALTER SYSTEM KILL SESSION ' || lv_session_info ||
' IMMEDIATE';
EXECUTE IMMEDIATE lv_sqlstr;
EXCEPTION
WHEN OTHERS THEN
NULL;
END;
END LOOP;
COMMIT;
END;
/
If there is extensive data loading ongoing in another instance that shares the same database host as the upgrade target instance it is possible that there will be Row exclusive table locks that will cause the upgrade to abort. This is normal behaviour for the upgrade process. The upgrade may be postponed until the data loading has completed or data loading may be suspended in the instances until the upgrade has completed.
To suspend data loading in other instances use the following procedure:
1. Log on as user flexpm
2. Suspend the sentry
[flexpm] $ ps-mgr suspend sn
3. Run ps-mgr watch and wait for all loaders to finish
[flexpm] $ ps-mgr watch
4. Proceed with the upgrade.
5. Resume data loading by resuming the sentry
[flexpm] $ ps-mgr resume sn
This section describes how to upgrade an existing Oracle database from version 10.2.0 (with 10.2.0.4 patch set) to 10.2.0.5.
Before starting the Oracle upgrade, it is recommended that you read the Oracle Database Documentation.
The system should contain enough disk space to allow for a full backup of the database. If the backup is done by means of the Database Upgrade Assistant (DBUA), then the space needed for the backup is equal to the current size of the database data files. To save space, you can also manually back up the database before the upgrade.
The following tasks involve backing up the Oracle database and Prospect files, then installing Oracle 10.2.0.5.
Make sure you have followed the instructions in the Server Preparation Guide, chapter Installing and Configuring Solaris, including disk setup, user creation, and system patches.
Pre-requisites
Solaris 10 U6 (5.10-2008.10), or later
To determine the distribution and version of Solaris installed, enter the following command:
# uname -r
Sample output: 5.10
In this example, the version shown is Solaris 10 (5.10). If necessary, refer to your operating system documentation for information about upgrading the operating system.
$ cat /etc/release
Note: Make sure that the Solaris update level is upgrade patch 6, or higher.
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008 Sun Microsystems, Inc. All Rights Reserve
Use is subject to license terms.
Assembled 27 October 2008
The following packages (or later versions) are required for Oracle Database 10g Release 2 (10.2.0.5) for Solaris Operating System:
SUNWarc
SUNWbtool
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs (ISO8859-1)
SUNWi15cs (ISO8859-15)
SUNWxwfnt
SUNWcsl
Verifying Packages
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibC SUNWlibms SUNWsprot SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
Install packages that are currently not installed in your system. Refer to your operating system or software documentation for information about installing packages.
Executing the pkginfo -i command will display results similar to following output:
system SUNWarc Lint Libraries (usr)
system SUNWbtool CCS tools bundled with SunOS
system SUNWhea SunOS Header Files
system SUNWi15cs X11 ISO8859-15 Codeset Support
system SUNWi1cs X11 ISO8859-1 Codeset Support
system SUNWi1of ISO-8859-1 (Latin-1) Optional Fonts
system SUNWlibC Sun Workshop Compilers Bundled libC
system SUNWlibms Math & Microtasking Libraries (Usr)
system SUNWsprot Solaris Bundled tools
system SUNWtoo Programming Tools
system SUNWxwfnt X Window System platform required fonts
Table 7: Required Patches for Solaris
|
Installation Type or Product |
Requirements |
|
All installations |
Patches for Solaris 10: • 120753-06: SunOS 5.10: Microtasking libraries (libmtsk) patch • 139574-03: SunOS 5.10
|
|
Pro*C/C++, Pro*FORTRAN, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer’s Kit (XDK) |
Patches For Solaris 10: • 119963-14: SunOS 5.10: Shared library patch for C++ • 124861-15: SunOS 5.10 Compiler Common patch for Sun C C++. Note: This patch is optional depending on your server requirements. Ignore this warning when you install Oracle 11g. |
|
Database Smart Flash Cache (An Enterprise Edition only feature.) |
The following patches are required for Solaris Operating System (SPARC 64-Bit) if you are using the flash cache feature: • 125555-03 • 140796-01 • 140899-01 • 141016-01 • 139555-08 • 141414-10 • 141736-05 |
Verifying Patches
Install patches that are currently not installed in your system. Refer to your operating system or software documentation for information about installing patches.
Run the following command to check the patch availability:
# /usr/sbin/patchadd -p | grep patch_number (without version number)
For example, executing this command:
/usr/sbin/patchadd -p | grep 120753
Will display results similar to the following output:
Patch: 120753-07 Obsoletes: Requires: Incompatibles: Packages: SUNWlibm SUNWlibmsr
Before you can perform a backup, you must first shut down the IBM Prospect software and the Oracle instance.
To shut down the IBM Prospect software
ps-mgr halt
ps -ef | grep perl | grep $prodname | cut -c10-14 | xargs kill -9
To stop Oracle
[oracle] $ sqlplus /nolog
SQL> connect sys/<password> as sysdba
where <password> is the password for the sys user.
SQL> shutdown immediate;
SQL> exit;
[oracle] $ lsnrctl stop
To perform the backup
· When Oracle is in NOARCHIVELOG mode, back up the database in cold backup mode.
· When Oracle is in ARCHIVELOG mode, back up the database in either cold backup or hot backup mode.
a. Back up the files under $FLEXPM_HOME.
b. Upgrade to Oracle 10.2.0.5
The Oracle 10.2.0.5 upgrade involves two major steps as follows:
It is recommended to perform the upgrade in this order; however, your setup may have special requirements then you may need to contact your system administrator.
Install Oracle 10g (Version 10.2.0.5, 64 bit) database software, including partition licenses.
When installing Oracle, use the following directories:
ORACLE_BASE -> /u01/apps/oracle
ORACLE_HOME -> /u01/apps/oracle/product/10.2.0
Note: Perform the installation using oracle user permissions. Do not run the Oracle Universal Installer (OUI) as root.
Download 10.2.0.5 installation files for Solaris from My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com/
p8202632_10205_SOLARIS64.zip
This installation procedure assumes that you have already prepared the server as described in the preceding sections:
· Install the appropriate version of Solaris and its patches
· During the installation, some scripts need to be run as the root user. If you do not have access to root, have someone from your IT department available during the installation to run these scripts.
The Installer is a Java-based interface that uses the X Window system. Use a workstation with an X Window display, not a console. Start the Installer according to the following procedure.
To start the Oracle Installer
1. Use the following commands on the X session host to enable access to the X Window server.
$ xhost +
Note: Make sure that the xhost command is available in your PATH environment variable. For Solaris, include /usr/openwin/bin in the PATH.
2. Use telnet or rlogin to log on to the database server host. Use the IBM Prospect Oracle logon account:
$ rlogin 'hostname' -l oracle
Substitute the appropriate server name for hostname.
3. Set the DISPLAY variable so that the Installer can access the X Window server:
$ export DISPLAY ; DISPLAY='hostname':0.0
Substitute the appropriate display hostname.
4. Copy the install packages p8202632_10205_SOLARIS64.zip into a temporary directory, not the one that oracle is going to be installed in. For example, /10.2.0.5
5. Set two variables for installation parameters.
$ export ORACLE_BASE; ORACLE_BASE=/u01/apps/oracle
$ export ORACLE_HOME; ORACLE_HOME=/u01/apps/oracle/product/10.2.0
6. Unpack the installation packages:
Unzip p8202632_10205_SOLARIS64.zip
Run the Installer in the background by using the ampersand (&).
./runInstaller
This allows the command shell to accept additional commands.
After running some initial checks, the Java client launches which configures and begins the installation.
A typical Oracle installation takes about an hour.
Select installation parameters such as product components, component locations, and authentication methods.
To select installation parameters
1. On the Welcome Screen ,Click Next
2. On the SPECIFY HOME DETAILS Screen, path should be same as /u01/apps/oracle/product/10.2.0 , Click Next.
3. Enter your email address and your My Oracle Support password Click Next.
Note: If you do not have oracle support email then deselect email option and ignore error message and Click Next.
4. On the PRODUCT-SPECIFIC PRERQUISITE CHECKS Screen, make sure all prerequisites are fulfilled then Click Next otherwise Click on Retry.
5. On the SUMMARY Screen, Click Install.
6. There is a popup screen that requires you to run a script called root.sh with root privilege. Open another TELNET session with login as root. Return to the installation screen when the session is complete.
Script Location -> /u01/apps/oracle/product/10.2.0/root.sh
7. Exit the installer when the installation is complete.
Post installation upgrade steps need to be done with oracle user login
$sqlplus ‘/ as sysdba’
SQL>startup upgrade;
SQL>@catupgrd.sql
SQL>shutdown immediate;
SQL>startup;
SQL>@utlrp.sql
|
Note: If there are any error like below after running utlrp.sql SQL>show errors Errors for PROCEDURE LOGMNR_KRVRDLUID3: LINE/COL ERROR -------- -------------------------------------------------------- 1669/9 PL/SQL: SQL Statement ignored 1669/23 PL/SQL: ORA-02289: sequence does not exist
And while checking dba_registry if Oracle Database Packages and Types is in invalid state Then perform this step login as system user
$ sqlplus system/manager@flexpm SQL>DROP SEQUENCE SYSTEM.LOGMNR_SEQ$; SQL>CREATE SEQUENCE SYSTEM.LOGMNR_SEQ$ START WITH 1 MAXVALUE 999999999999999999999999999 MINVALUE 1 NOCYCLE CACHE 20 ORDER; SQL> grant all on SYSTEM.LOGMNR_SEQ$ to SYS; Then connect again as SYS user and check again dba_registry; |
Then check for dba_registry objects and all should be in valid states.
SQL> select comp_name, version, status from dba_registry;
COMP_NAME VERSION STATUS
Oracle XML Database 10.2.0.5.0 VALID
Oracle Expression Filter 10.2.0.5.0 VALID
Oracle Rule Manager 10.2.0.5.0 VALID
Oracle Workspace Manager 10.2.0.5.0 VALID
Oracle Database Catalog Views 10.2.0.5.0 VALID
Oracle Database Packages and Types 10.2.0.5.0 VALID
JServer JAVA Virtual Machine 10.2.0.5.0 VALID
Oracle XDK 10.2.0.5.0 VALID
Oracle Database Java Packages 10.2.0.5.0 VALID
9 rows selected.
This is completion of Upgrade steps for 10.2.0.5.
This section describes how to upgrade an existing Oracle database from version 10.2.0 (with 10.2.0.4 patch set) to 11.2.0. Oracle upgrades should be performed by an Oracle Database Administrator (DBA). This document assumes that expertise.
Before starting the Oracle upgrade, it is recommended that you read the Oracle Database
Upgrade Guide 11g Release 1 (11.1) B28300-02 on My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com/. You can use the Database Upgrade Assistant (DBUA), but it is useful to read the manual to gain an awareness of the issues.
The system should contain enough disk space to allow for a full backup of the database. If the backup is done by means of the Database Upgrade Assistant (DBUA), then the space needed for the backup is equal to the current size of the database data files. To save space, you can also manually back up the database before the upgrade.
The following tasks involve backing up the Oracle database and Prospect files, then installing Oracle 11g.
1.1 Set Up the Prospect Server
Make sure you have followed the instructions in the Server Preparation Guide, chapter Installing and Configuring Solaris, including disk setup, user creation, and system patches.
1.1.1 Pre-requisites
Solaris 10 U6 (5.10-2008.10), or later
To determine the distribution and version of Solaris installed, enter the following command:
# uname -r
Sample output: 5.10
In this example, the version shown is Solaris 10 (5.10). If necessary, refer to your operating system documentation for information about upgrading the operating system.
$ cat /etc/release
Note: Make sure that the Solaris update level is upgrade patch 6, or higher.
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008 Sun Microsystems, Inc. All Rights Reserve
Use is subject to license terms.
Assembled 27 October 2008
The following packages (or later versions) are required for Oracle Database 11g Release 2 (11.2.0) for Solaris Operating System:
SUNWarc
SUNWbtool
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWi1cs (ISO8859-1)
SUNWi15cs (ISO8859-15)
SUNWxwfnt
SUNWcsl
Verifying Packages
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibC SUNWlibms SUNWsprot SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
Install packages that are currently not installed in your system. Refer to your operating system or software documentation for information about installing packages.
Executing the pkginfo -i command will display results similar to following output:
system SUNWarc Lint Libraries (usr)
system SUNWbtool CCS tools bundled with SunOS
system SUNWhea SunOS Header Files
system SUNWi15cs X11 ISO8859-15 Codeset Support
system SUNWi1cs X11 ISO8859-1 Codeset Support
system SUNWi1of ISO-8859-1 (Latin-1) Optional Fonts
system SUNWlibC Sun Workshop Compilers Bundled libC
system SUNWlibms Math & Microtasking Libraries (Usr)
system SUNWsprot Solaris Bundled tools
system SUNWtoo Programming Tools
system SUNWxwfnt X Window System platform required fonts
Table 7: Required Patches for Solaris
|
Installation Type or Product |
Requirements |
|
All installations |
Patches for Solaris 10: • 120753-06: SunOS 5.10: Microtasking libraries (libmtsk) patch • 139574-03: SunOS 5.10
|
|
Pro*C/C++, Pro*FORTRAN, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer’s Kit (XDK) |
Patches For Solaris 10: • 119963-14: SunOS 5.10: Shared library patch for C++ • 124861-15: SunOS 5.10 Compiler Common patch for Sun C C++. Note: This patch is optional depending on your server requirements. Ignore this warning when you install Oracle 11g. |
|
Database Smart Flash Cache (An Enterprise Edition only feature.) |
The following patches are required for Solaris Operating System (SPARC 64-Bit) if you are using the flash cache feature: • 125555-03 • 140796-01 • 140899-01 • 141016-01 • 139555-08 • 141414-10 • 141736-05 |
Verifying Patches
Install patches that are currently not installed in your system. Refer to your operating system or software documentation for information about installing patches.
Run the following command to check the patch availability:
# /usr/sbin/patchadd -p | grep patch_number (without version number)
For example, executing this command:
/usr/sbin/patchadd -p | grep 120753
Will display results similar to the following output:
Patch: 120753-07 Obsoletes: Requires: Incompatibles: Packages: SUNWlibm SUNWlibmsr
1.2 Shut Down IBM Prospect and Oracle
Before you can perform a backup, you must first shut down the IBM Prospect software and the Oracle instance.
To shut down the IBM Prospect software
ps-mgr halt
ps -ef | grep perl | grep $prodname | cut -c10-14 | xargs kill -9
To stop Oracle
[oracle] $ sqlplus /nolog
SQL> connect sys/<password> as sysdba
where <password> is the password for the sys user.
SQL> shutdown immediate;
SQL> exit;
[oracle] $ lsnrctl stop
1.3 Back Up the Oracle 10g Database and IBM Prospect Files
To perform the backup
· When Oracle is in NOARCHIVELOG mode, back up the database in cold backup mode.
· When Oracle is in ARCHIVELOG mode, back up the database in either cold backup or hot backup mode.
Back up the files under $FLEXPM_HOME.
1.4 Oracle 11g Naming Conventions
The Prospect client expects the installation to follow the Optimal Flexible Architecture (OFA) standards concerning naming conventions. The software also expects Oracle to be installed into the directory /u01/apps/oracle/product/11.2.0. If it is installed in another location, you must create a symbolic link from /u01/apps/oracle/product/11.2.0 to the directory.
The Oracle 11.2.0 upgrade involves two major steps as follows:
It is recommended that you perform the upgrade in this order; however, your setup may have special requirements.
Consult the Oracle 11g Upgrade Companion, Note 601807.1, on the Oracle Metalink Web site for the latest information provided by Oracle.
2.1 Install Oracle 11g Software
Install Oracle 11g (Version 11.2.0.1, 64 bit) database software, including partition licenses.
When installing Oracle, use the following directories:
ORACLE_BASE -> /u01/apps/oracle
ORACLE_HOME -> /u01/apps/oracle/product/11.2.0
Note: Perform the installation using oracle user permissions. Do not run the Oracle Universal Installer (OUI) as root.
Download 11g installation files for Solaris from My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com/
2.1.1 Before You Begin
This installation procedure assumes that you have already prepared the server as described in the preceding sections:
· Install the appropriate version of Solaris and its patches
· During the installation, some scripts need to be run as the root user. If you do not have access to root, have someone from your IT department available during the installation to run these scripts.
2.1.2 Start the Installer
The Installer is a Java-based interface that uses the X Window system. Use a workstation with an X Window display, not a console. Start the Installer according to the following procedure.
To start the Oracle Installer
1. Use the following commands on the X session host to enable access to the X Window server.
$ xhost +
Note: Make sure that the xhost command is available in your PATH environment variable. For Solaris, include /usr/openwin/bin in the PATH.
2. Use telnet or rlogin to log on to the database server host. Use the IBM Prospect Oracle logon account:
$ rlogin 'hostname' -l oracle
Substitute the appropriate server name for hostname.
3. Set the DISPLAY variable so that the Installer can access the X Window server:
$ export DISPLAY ; DISPLAY='hostname':0.0
Substitute the appropriate display hostname.
4. Copy the install packages solaris.sparc64_11gR2_database_1of2.zip and solaris.sparc64_11gR2_database_2of2.zip into a temporary directory, not the one that oracle is going to be installed in. For example, /u01/oinstall
5. Set two variables for installation parameters.
$ export ORACLE_BASE; ORACLE_BASE=/u01/apps/oracle
$ export ORACLE_HOME; ORACLE_HOME=/u01/apps/oracle/product/11.2.0
6. Unpack the installation packages:
unzip solaris.sparc64_11gR2_database_1of2.zip
unzip solaris.sparc64_11gR2_database_2of2.zip
7. Run the Installer in the background by using the ampersand (&).
./runInstaller &
This allows the command shell to accept additional commands.
After running some initial checks, the Java client launches which configures and begins the installation.
A typical Oracle installation takes about an hour.
2.1.3 Select and enter Installation Parameters
Select installation parameters such as product components, component locations, and authentication methods.
To select installation parameters
1. On the first installation screen, enter your email address and your My Oracle Support password Click NEXT.
2. Select the INSTALL DATABASE SOFTWARE ONLY option. Click NEXT.
3. Select SINGLE INSTANCE DATABASE INSTALLATION and click NEXT.
4. Select English as SELECTED LANGUAGES. Click NEXT.
5. Select the ENTERPRISE EDITION option and click NEXT.
6. On the SPECIFY INSTALLATION LOCATION screen, enter /u01/apps/oracle for the ORACLE BASE DIRECTORY and /u01/apps/oracle/product/11.2.0 in the SOFTWARE LOCATION section. Click NEXT. “The ORACLE BASE LOCATION IS IN THE HOME DIRECTORY. ARE YOU SURE YOU WANT TO CONTINUE?” dialog box opens. Click YES to continue.
7. On the next installation screen, leave DBA as the Database Administrator Group and Database Operator Group and click NEXT.
8. Make sure all installation requirements are fulfill Click NEXT.
9. Make sure all summary values are correct and click FINISH. The installation begins.
The installation log can be viewed in the /u01/apps/oracle/oraInventory/logs/ path on the server, for example:
/u01/apps/oracle/oraInventory/logs/installActions2010-10-08_08-26-22PM.log
10. Exit the installer when the installation is complete.
2.2 Upgrade to 11g using dbua
The DBUA provides a graphical user interface (GUI) that guides a user through an in-place upgrade of a database. It is the recommended method for performing either a major release upgrade or patch release upgrade.
The DBUA automates the upgrade process by performing all of the tasks that would otherwise need to be performed manually. It can be launched as a standalone tool at any time after installation is complete.
Note: Do not launch DBUA during Oracle 11g installation.
The DBUA is a very useful tool because it evaluates the current database and makes appropriate recommendations for configuration options such as tablespace sizes, cluster checks, initialization parameters, and Oracle Automatic Storage Management (ASM) upgrades.
The following procedure includes a step that backs up your current database. If you want the database upgrade utility to back up your database, be prepared to supply a directory capable of holding a full backup of your database.
Note: The following is just an example; choose your own preferred upgrade method
$ export ORACLE_BASE=/u01/apps/oracle
$ export ORACLE_HOME=$ORACLE_BASE/product/11.2.0
$ export ORACLE_SID=flexpm
$ export PATH
$ PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
$ export LD_LIBRARY_PATH
$ LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
$ export TNS_ADMIN
$ TNS_ADMIN=$ORACLE_HOME/network/admin
dbua &
Note: You need to input the password for the DBSNMP, and SYSMAN users.
DBSNMP password: dbsnmp
SYSMAN password: manager
If the PASSWORD ENTERED DOES NOT SATISFY ORACLE RECOMMENDED PASSWORD
COMPLEXITY POLICY dialog box appears, click YES.
2.3 Perform Post Upgrade Steps
Note: To set system performance parameters, refer to Oracle documentation to enable Automatic Shared Memory Management. The following steps are other 11g post-upgrade related actions.
$ export ORACLE_BASE=/u01/apps/oracle
$ export ORACLE_HOME=$ORACLE_BASE/product/11.2.0
*:/u01/apps/oracle/product/10.2.0:N
Comment out this line, as follows:
#*:/u01/apps/oracle/product/10.2.0:N
Edit $ORACLE_BASE/admin/flexpm/pfile/initflexpm.ora
Then change:
$ log_archive_format="LOG_%t_%s.ARC"
to:
log_archive_format="LOG_%t_%s_%r.ARC"
$ cd /u01/apps/oracle
$ rm network
$ ln -s ./product/11.2.0/network network
$ exit
4. Log on to Oracle as sysdba
$ sqlplus / as sysdba
SQL> ALTER SYSTEM SET open_cursors=1000 SCOPE=SPFILE;
SQL> ALTER SYSTEM set recyclebin=off scope=spfile;
SQL> purge recyclebin;
Recyclebin purge
SQL> select * from recyclebin;
No rows selected
SQL> exit
SQL> ALTER SYSTEM SET COMPATIBLE= '11.2.0' SCOPE=SPFILE;
SQL> ALTER SYSTEM SET "_optimizer_connect_by_cost_based"=false
scope=spfile;
SQL> ALTER SYSTEM SET log_archive_format='LOG_%t_%s_%r.ARC' scope=spfile;
SQL> shutdown abort
SQL> startup
SQL> shutdown immediate
SQL> quit
Note: If Oracle ORA errors 119 and / or 132 are encountered, refer to Metalink ID: 415362 for instructions on how to restore Oracle.
$ORACLE_BASE/product/11.2.0/network/admin/
First, check if the tnsnames.ora and listener.ora files are in the $ORACLE_BASE/product/11.2.0/network/admin/ directory. If the files are not in the directory, run the following command:
$ cp /u01/apps/oracle/product/10.2.0/network/admin/*ora /u01/apps/oracle/product/11.2.0/network/admin
Edit the files to conform to the following network configuration file details.
Note: The flexpm entry may differ from the example below (protocol may be IPC, for example), but you must make sure that the hostname and port are define Hostname may be either the server name or the IP address. On a split server environment, the tnsnames.ora file resides on the Oracle server.
# tnsnames.ora Network Configuration File: /u01/apps/oracle/product/
11.2.0/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
#.
# @(#) tnsnames.ora = Oracle 'tnsnames' configuration for FLEXPM
# NOTES:
# can be 'generated' by Oracle Net8 Assistant
#
# @(#) %M% ; %I%.%B% %E% %U%
flexpm = (DESCRIPTION =
(ADDRESS =
(PROTOCOL = TCP)(HOST = <hostname>)(PORT = <port #>)
(KEY = flexpm))
(CONNECT_DATA =
(SID = flexpm)
(SERVER = DEDICATED))
)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
)
(CONNECT_DATA =
(SID = PLSExtProc)
)
)
The file listener.ora should look like the following; replace <hostname> with the name of your server:
# @(#) listener.ora = Oracle 'listener' configuration for FLEXPM
# NOTES:
# can be 'generated' by Oracle Net8 Assistant
#
# @(#) %M% ; %I%.%B% %E% %U%
LOG_DIRECTORY_LISTENER = /u01/apps/oracle/network/log
LOG_FILE_LISTENER = listener.log
TRACE_LEVEL_LISTENER = NONE
LISTENER =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <hostname> )(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC))
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = flexpm )
(ORACLE_HOME = /u01/apps/oracle/product/11.2.0 )
(SID_NAME = flexpm )
)
(SID_DESC =
(ORACLE_HOME = /u01/apps/oracle/product/11.2.0 )
(SID_NAME = PLSExtProc)
(PROGRAM = extproc32)
(ENVS =
"EXTPROC_DLLS=ANY,LD_LIBRARY_PATH=<FLEXPM_HOME>/pm/lib/wm: <FLEXPM_HOME>/pm/lib/tp: <FLEXPM_HOME>/pm/lib/ln/ora:/u01/apps/oracle/product/10.2.0/
lib32")
)
)
#.
Before restarting the listener, enter the following commands:
$ sqlplus /nolog
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started
Note: The sga_target parameter enables or disables Automatic Shared Memory Management (ASMM). In order to enable the ASMM feature, this must be set to a non-zero value following the Oracle 11g upgrade and before any report groups are submitte sga_max_size can have approximately 25% of RAM (for example, if you have 10 GB of RAM, sga_max_size =2G) and sga_target (about 85% to 95% of sga_max_size) less than sga_max_size.
The following values within <> are examples only. Note that values must only be entered as integers, for example 1G = 1024M, where either value can be use When sga_target is set to non-zero, the parameter shared_pool_size must also be non-zero, and the parameter statistics_level must be set to TYPICAL or ALL.
SQL> ALTER SYSTEM SET sga_max_size=< 1200M > SCOPE=SPFILE;
SQL> ALTER SYSTEM SET sga_target=< 1000M > SCOPE=SPFILE;
SQL> ALTER SYSTEM SET shared_pool_size=<400M> SCOPE=SPFILE;
SQL> ALTER SYSTEM SET statistics_level=<TYPICAL OR ALL>
SQL> SHUTDOWN IMMEDIATE;
SQL> EXIT;
Restart the listener by issuing the following command:
$ lsnrctl start
Restart the database
$ sqlplus '/ as sysdba'
SQL> startup
SQL> quit
The installation of Oracle is now complete.
13. Run preset_oracle_paths
Log on as flexpm and source the profile:
$ . ./.profile
$ cd $PM_HOME/sw/oracle
$ preset_oracle_paths -f
The upgrade of Oracle from 10.2.0 to 11.2.0 is successful after these tasks are complete
The upgrade is complete. Exit the server.
Sample output of preset_oracle_paths:
: flexpm@perftest1 ; preset_oracle_paths
Oracle installation is 10.2.0 Client
Linking commander10g to commander
Linking controlLogLoader10g to controlLogLoader
Linking loader10g to loader
Linking sentry10g to sentry
Linking sescfg10g to sescfg
Linking /u01/apps/oracle_client/network to /u01/apps/oracle/product/11.2.0/network
Linking /u01/apps/oracle_client/product/10.2.0/dbs to /u01/apps/oracle/product/11.2.0/dbs
Linking /u01/apps/oracle_client/admin to /u01/apps/oracle/admin
Copying /u01/apps/oracle/product/11.2.0/bin/lsnrctl to /u01/apps/
oracle_client/product/10.2.0/bin
oracle@perftest1$ pwd
ls -ltr /u01/apps/oracle_client
lrwxrwxrwx 1 flexpm dba 39 Sep 22 06:12 network -> /u01/apps/
oracle/product/11.2.0/network
lrwxrwxrwx 1 flexpm dba 22 Sep 22 06:12 admin -> /u01/apps/oracle/admin
ls -ltr /u01/apps/oracle_client/product/10.2.0
lrwxrwxrwx 1 flexpm dba 35 Sep 22 06:12 dbs -> /u01/apps/
oracle/product/11.2.0/dbs
ls -ltr /u01/apps/oracle_client/product/10.2.0/bin
-rwxr-x--x 1 flexpm dba 152096 Sep 22 06:12 lsnrctl
You might note some differences when using the sqlplus Oracle tool after upgrading to Oracle 11g database software. You will be directed to different sqlplus versions when you log in as oracle or flexpm user. However, you will still be connected to the 11g database server regardless of the sqlplus version being use
The following can be observed when you log in as oracle. With this profile, you will be using the 11g version of sqlplus.
$ id
uid=10021(oracle) gid=600(dba)
$ env | grep ORACLE
ORACLE_FLAG=Y
ORACLE_BASE=/u01/apps/oracle
WM_ORACLEVERSION=ORACLE10
ORACLE_SID=flexpm
ORACLE_VERS=1120
ORACLE_HOME=/u01/apps/oracle/product/11.2.0
$ env | grep PATH
PATH=/u01/apps/oracle/product/11.2.0/bin:/usr/bin:/usr/sbin:/usr/openwin/bin:/usr/dt/bin:/usr/ccs/bin:/opt/SUNWspro/bin:/usr/ucb:/usr/local/bin:/usr/bin/nsr
LD_LIBRARY_PATH=/pm/lib/ln/ora:/u01/apps/oracle/product/11.2.0/lib:/usr/lib:/usr/openwin/lib:/usr/dt/lib:/usr/ccs/lib:/opt/SUNWspro/lib:/usr/local/lib
$ sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 13 05:16:23 2010
Copyright (c) 1982, 2009, Oracle. All rights reserve
SQL> conn system/manager
Connecte
SQL> set lines 150
SQL> select instance_name, host_name, version, startup_time, database_status from v$instance;
INSTANCE_NAME HOST_NAME VERSION STARTUP_TIME DATABASE_STATUS
---------------- ---------- ----------------- ---------------- ---------------
flexpm whale 11.2.0.1.0 2010-10-11 00:27 ACTIVE
The following can be observed when you log in as flexpm. With this profile, you will be using the 10g client version of sqlplus, but it will still direct you to the 11g database.
$ . ./.profile
$ id
uid=10020(flexpm) gid=600(dba)
$ env | grep ORACLE
ORACLE_BASE=/u01/apps/oracle_client
WM_ORACLEVERSION=ORACLE10
ORACLE_SID=flexpm
ORACLE_VERS=1020
ORACLE_HOME=/u01/apps/oracle_client/product/10.2.0
$ env | grep PATH
PATH=/usr/perl5/5.6.1/bin:<FLEXPM_HOME>/pm/adm:<FLEXPM_HOME>/pm/run:<FLEXPM_HOME>/pm/bin:<FLEXPM_HOME>/wm/bin:<FLEXPM_HOME>/vendor/Common/NE/1.3/scripts:<FLEXPM_HOME>/vendor/Common/NE/1.3/../part_maint:<FLEXPM_HOME>/vendor/Common/NE/1.3/bin:.:<FLEXPM_HOME>/pm/adm:<FLEXPM_HOME>/pm/run:<FLEXPM_HOME>/pm/bin:<FLEXPM_HOME>/wm/run:<FLEXPM_HOME>/pm/pas/bin:/usr/java/bin:::/u01/apps/oracle_client/product/10.2.0/bin:/usr/bin:/usr/sfw/bin:/usr/sbin:/usr/openwin/bin:/usr/dt/bin:/usr/ccs/bin:/opt/SUNWspro/bin:/usr/ucb:/usr/bin/nsr:<FLEXPM_HOME>/sw/oracle:<FLEXPM_HOME>/db/Oracle8i/scheduler/sched:/u01/apps/WatchMark/FlexPM/motR23t//MotorolaSplash/vendor/MotorolaSplash/bin:/u01/apps/WatchMark/FlexPM/motR23t//MotorolaSplash/vendor/MotorolaSplash/bin/sso:<FLEXPM_HOME>/pm/pas/bin/perf:/usr/sfw/bin:/u01/apps/WatchMark/FlexPM/bin
LD_LIBRARY_PATH=<FLEXPM_HOME>/sw/perl/lib:<FLEXPM_HOME>/pm/lib/wm:<FLEXPM_HOME>/pm/lib/tp:<FLEXPM_HOME>/pm/lib::<FLEXPM_HOME>/pm/lib/wm:<FLEXPM_HOME>/pm/lib/tp:<FLEXPM_HOME>/pm/lib::<FLEXPM_HOME>/pm/lib/ln/ora:/u01/apps/oracle_client/product/10.2.0/lib32:/usr/lib:/usr/openwin/lib:/usr/dt/lib:/usr/ccs/lib:/opt/SUNWspro/lib
$ sqlplus /nolog
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Oct 13 05:23:57 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserve
SQL> set lines 150
SQL> conn system/manager@flexpm
Connecte
SQL> select instance_name, host_name, version, startup_time, database_status from v$instance;
INSTANCE_NAME HOST_NAME VERSION STARTUP_TIME DATABASE_STATUS
---------------- ---------- ----------------- ---------------- ---------------
flexpm whale 11.2.0.1.0 2010-10-11 00:27 ACTIVE
In addition to the above sqlplus logins, when flexpm connects with the Prospect flexpm login, it clearly indicates the 10.2.0.4.0 sqlplus binary usage, and the 11.2.0.1.0 database.
: flexpm@whale ; sqlplus $DB_CONNECT
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Oct 13 11:02:25 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserve
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
|
Created/Revised By: |
Date of Creation/Update: |
Summary of Changes: |
|
Goutham P N |
17 June 2013 |
First Draft – QA Drop 2 |
|
Goutham P N |
5 July 2013 |
Second Draft – QA Drop 3 |
Notices
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 jurisdictions 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.
Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation
in the United States, other countries, or both.
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.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Other company, product, or
service names may be trademarks or service marks of others.
THIRD-PARTY
LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION
The license agreement for this product refers you to this file for details
concerning terms and conditions applicable to third party software code
included in this product, and for certain notices and other information IBM
must provide to you under its license to certain software code. The relevant
terms and conditions, notices and other information are provided or referenced
below. Please note that any non-English version of the licenses below is
unofficial and is provided to you for your convenience only. The English
version of the licenses below, provided as part of the English version of this
file, is the official version.
Notwithstanding the terms and conditions of any other agreement you may have
with IBM or any of its related or affiliated entities (collectively
"IBM"), the third party software code identified below are
"Excluded Components" and are subject to the following terms and
conditions:
the Excluded Components are provided on an "AS IS" basis
IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.