Prospect® 8.0.7
Interim Fix 6
(8.0.7.6)
Description
Prospect® 8.0.7.6
is an Interim Fix for Prospect® 8.0.7.
It is a cumulative interim fix and includes all of the content from previous
Prospect® 8.0.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 8.0.7
release is displayed as 8.0.7.0.
This patch introduce none
solution.
In addition
this Interim Fix includes the following new features for Prospect®.
This is documented
in the Prospect® Administration Guide available on the IBM
Tivoli Netcool Information Center.
Readme
file for: Prospect®
8.0.7
Interim Fix 6
[Server: Build 2]
Product/Component Release: 8.0.7
Update Name: 8.0.7
Interim Fix 6
(8.0.7.6)
Fix ID: 8.0.7-PROSPECT-IF0006
Publication Date: 30
July 2010
Last modified date: 30 July 2010
Contents
Installation
Privileges Required
Pre Upgrade Installation
Steps
Post-Upgrade
Installation Instructions
Installing the
Prospect® Client
Setting
limit/restriction on historical data for BH computation
Stopping Database
Activity to Enable Upgrade
Dataloading on
Multi Instance Installation
Copyright and
Trademark Information
Download Prospect® 8.0.7
Interim Fix 6
from the following location:
ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_8.0.7/8.0.7-PROSPECT-IF0006/ 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 Server |
Solaris |
|
|
Prospect Client |
Windows |
Network Timeouts
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:
·
Prospect® 8.0.7 or later[1]
·
Java SDK 1.5.0_17
·
Oracle 10g 10.2.0.4
Note:
Ensure that you have sufficient file system free space to download, extract and
install the patch.
Prospect®
8.0.7
Interim Fix 6
from cannot be uninstalled. Back up the Prospect® 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® 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.
If the
Prospect® Instance is accessed via prospect web disable access to its remote
datasource in Prospect® Web using the Prospect® Web Admin Tool.
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.
1.
Log on as user flexpm
2.
Source
the Prospect® Environment to be upgraded.
If the server is running multiple Prospect schemas or
the profile for the Prospect®
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® instance to be upgraded is installed and source the
environment.
For example, if Prospect® is installed in a vendor modular configuration and the path to
FLEXPM_HOME is:
/u01/apps/WatchMark/FlexPM/vendor/ProspectBase
[flexpm] $
cd /u01/apps/WatchMark/FlexPM/vendor/ProspectBase
[flexpm] $
. ./.profile
Alternately, if a menu system is in place to allow
selection of the Prospect®
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 8.0.7-PROSPECT-IF0006-server.tar.gz $FLEXPM_HOME/tmp
[flexpm]
$ cd $FLEXPM_HOME/tmp
4.
Untar the server tarball
[flexpm]
$ gunzip 8.0.7-PROSPECT-IF0006-server.tar.gz
[flexpm]
$ gtar -xvpf 8.0.7-PROSPECT-IF0006-server.tar
5.
Run the upgrade command
[flexpm]
$ ./wminstall
Note: It is strongly
recommended to run the previous command with the –preview option before
performing installation to identify potential problems.
[flexpm]
$ ./wminstall -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 Prospect®, 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 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 -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.
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 you
disabled access to the Prospect® server from Prospect® Web, then use the admin
tool to re-enable access to the corresponding data source in Prospect® Web.
1.
Copy 8.0.7-PROSPECT-IF0006-client.zip
on your Windows system in a temporary directory.
2.
Unzip 8.0.7-PROSPECT-IF0006-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 client, use the ADD/REMOVE PROGRAMS component of the
Windows Control Panel.
Some files may not be removed after
un-installation is complete. User is required to remove it manually if that
happens. User can browse to the Program folder usually locates in C:\Program
Files\Vallent\Prospect\Program to verify file existence and remove it manually
if there is any. Otherwise, some of the program components would not get
updated after upgrade installation.
Fixes included in Prospect®
8.0.7.6:
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
IZ79897 /
alm00155772 |
8.0.7.6 |
COVER OF
HELP PAGES ON PM SERVER SHOWING EMPTY. |
Fixes included in previous
Prospect® 8.0.7
Interim Fixes:
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
IZ75091 / valnt00112440 |
8.0.7.5 |
ERRORS WHEN CREATING DEVICE INSTANCE. SYSTEMID TO LONG. |
|
IZ75321 / valnt00113897 |
8.0.7.5 |
TO AVOID POSSIBLE DEADLOCKS OCCURRING DURING DELETION OF USERS |
|
IZ75776 / valnt00113709 |
8.0.7.5 |
PROSPECT CORE 8.9.6.7 CLIENT DUMPS .TXT FILES WHEN .XLSX OR .CSV
EXPECTED. CLIENT DOESN'T HAVE THE SAME
ROW LIMIT. |
|
IZ75926 / valnt00114303 |
8.0.7.5 |
IMPORT_DOCS.SH SCRIPT IS FAILING WHEN TRYING TO IMPORTINFORMATION
FROM ANOTHER SERVER |
|
IZ73236 / valnt00107545 |
8.0.7.4 |
SOFTALARM IS CLEARING TOO EARLY IF CLEARED THRESHOLDS ARE USED |
|
IZ72202 / valnt00104850 |
8.0.7.4 |
OMMISSION IN 8.0.7.1 RELEASE NOTES |
|
IZ72126 / valnt00104741 |
8.0.7.4 |
RELEASE NOTES NEED TO SPECIFY IF NOHUP CAN BE USED WITHWMINSTALL
IN UPGRADES. |
|
IZ69697 / valnt00103064 |
8.0.7.4 |
UPDATESCENARIO.SH FAILS WITH ORA-24331 |
|
IZ69152 / valnt00101892 |
8.0.7.4 |
NSBH & SBH NOT IDENTICAL |
|
IZ61286 / valnt00095201 |
8.0.7.4 |
WMINSTALL PROCEEDS TO INSTALL WHEN GTAR FAILS |
|
IZ70753 / valnt00103919 |
8.0.7.4 |
DETAIL LOG SHOWS SUCCESS / NO ERRORS DESPITE CRITICAL ORA ERRORS |
|
IZ67526 / valnt00100377 |
8.0.7.3 |
8.0.7-AEMS-MOTCM01258596-ADDITIONAL TEXT TOKENS ARE REPLACED
ATFIRST |
|
IZ66906 / valnt00099989 |
8.0.7.3 |
WRONG MESSAGE DISPLAYED WHEN CREATING SOFT ALARM TEMPLATE IFMISSED
TO FILL THE ADDITIONAL-TEXT FIELD. |
|
IZ68023 / valnt00100745 |
8.0.7.3 |
8.0.7-AEMS-MOTCM01253172 - CLASSIC DICTIONARY UPGRADE FAILS |
|
IZ66463 / valnt00097729 |
8.0.7.2 |
SNMP token $DEF_ALARM_ID is not supported in 8.0.7 |
|
IZ40829 / valnt00074087 |
8.0.7.1 |
THE AUTODOWNLOADER FAILS TO DOWNLOAD REPORTS AND DOES NOT
CONTINUE WITH OTHER REPORTS ONCE STUCK ON ONE REPORT. |
|
IZ56296 / valnt00092649 |
8.0.7.1 |
8.0.6 P5 AUTO DOWNLOADER CAUSE PROBLEMS IF SET TO ROTATE BETWEEN
PROFILES |
|
IZ56674 / valnt00092652 |
8.0.7.1 |
FOLLOWING THE PK SWAP CHANGE INTRODUCED IN PROSPECT CORE PATCH
8.0.6.3, PM_DAILY MOVE AND ANALYZE CHANGES ARE NEEDED |
|
IZ59321 / valnt00093826 |
8.0.7.1 |
SUMMATION JOB WILL NOT COMPLETE AFTER CORE PATCH 8.0.6.3 |
|
IZ59357 / valnt00093835 |
8.0.7.1 |
EXTERNAL SOFT ALARM PROCESSING SLOW AFTER CORE 8.0.6.3 PATCH |
|
IZ61977 / valnt00096047 |
8.0.7.1 |
PROSPECT REPORTS RUN LONG WHEN THE DATE TIME SCOPE INCLUDES
NON-CONSECUTIVE DATE TIME SCOPE |
|
valnt00093052 |
8.0.7.1 |
Code for wml_load.sql.create_temp_tables fails with ORA-01430. |
|
valnt00094052 |
8.0.7.1 |
Merge Join Cartesian Rule. |
|
valnt00094064 |
8.0.7.1 |
Health Check command fails on PM server. |
|
valnt00094124 |
8.0.7.1 |
“sched_license.in_use” counter was not decrementing
correctly causing PM SA |
|
valnt00094198 |
8.0.7.1 |
createinstance.sh script will not create system level entity |
|
valnt00094267 |
8.0.7.1 |
Partition maintenance first run fails. ORA error's were found in
the bdump folder |
|
valnt00095169 |
8.0.7.1 |
Analyze Job creating invalid statistics |
|
valnt00095520 |
8.0.7.1 |
Loading flexpm environment take's too much time. |
|
valnt00095627 |
8.0.7.1 |
Analyze job computes bad stats on certain classic report tables
causing performance problems |
|
valnt00095653 |
8.0.7.1 |
Autoclean job hangs cleaning active_task/active_job |
|
valnt00096835 |
8.0.7.1 |
Add support for elemprotect to pweb/classic rep-gens |
There are
no known issues in this release.
There is an optional system variable called BH_COMPUTE_DAYS that can be set to limit the days that are included in the stored summary calculations.
Rather than including data dated back to the last available or first needed dates, the computation goes back the number of days specified by BH_COMPUTE_DAYS (the value must be greater than 1 or it is ignored).
This allows restriction of the amount of historical data the BH processes if no data
is loaded, so keeping the BH computation fast.
The following steps are to add and set value to
INTEGER:
1.
Log
on to the database by typing the following command:
$ sqlplus
$DB_CONNECT
2.
Run
the following SQL:
SQL>
begin
2 exec wm_sysval.newsysval(‘BH_COMPUTE_DAYS’,'<NO_OF_DAYS>'); commit;
3 end ;
4 /
Note: The <NO_OF_DAYS> should be replaced with desired integer value.
3.
Exit
the sqlplus.
The following steps are to modify BH_COMPUTE_DAYS
value:
4.
Log
on to the database by typing the following command:
$ sqlplus
$DB_CONNECT
5.
Run
the following SQL:
SQL>
begin
2 wm_sysval.forceSysVal(
'BH_COMPUTE_DAYS',<NO_OF_DAYS> ); commit;
3 end ;
4 /
Note: The <NO_OF_DAYS> should be replaced with desired integer value.
6.
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>
begin
2 wm_sysval.deleteSysVal(‘BH_COMPUTE_DAYS’); commit;
3 end ;
4 /
3.
Exit
the sqlplus.
Important Note:
The
system value may be applied prior to upgrading to version 8.0.7.6. However, this takes effect after 8.0.7.6 or
greater is installed.
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
http://www.ibm.com/legal/copytrade.shtml
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.
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.
|
Created/Revised By: |
Date of Creation/Update: |
Summary of Changes: |
|
Mike Liew Ing Huey |
|
First Draft – QA Drop 1 |
|
Mike Liew Ing Huey |
|
Final Draft – QA Drop 2 |
|
Mike Liew Ing Huey |
|
Release |
[1]
These upgrade instructions refer to IBM Prospect® only. If you are upgrading
IBM Prospect® for Motorola CDMA/EVDO, please refer to the separate readme file
which will be shipped with that product.