Prospect® 8.0.7 Interim Fix 3 (8.0.7.3)
Description
Prospect® 8.0.7.3 is an Interim Fix for Prospect® 8.0.7.
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 introduces the solutions for IZ67526, IZ66906 and IZ68023.
Readme file for: Prospect®
8.0.7
Interim Fix 3
[Server: Build 2]
Product/Component Release: 8.0.7
Update Name: 8.0.7
Interim Fix 3
(8.0.7.3)
Fix ID: 8.0.7-PROSPECT-IF0003
Publication Date: 29
January 2010
Last modified date: 28
January 2010
Contents
Installation Privileges Required
Pre Upgrade Installation Steps
Post-Upgrade Installation Instructions
Installing the Prospect® Client
Additional Soft Alarm Message Token
Importing of UDCs using Busy Hour and Soft Alarm
Import Utilities
Description of show_part Script
Clarification on Active Scenario and Newly Created
Instances as a Result of Rehoming
Clarification on set_job_cleanup_time.sh Script
Clarification on Exclude Weekend Checkbox on Soft
Alarm Definition
Stopping Database Activity to Enable Upgrade
Dataloading on Multi Instance Installation
Copyright and Trademark Information
Download Prospect®
8.0.7
Interim Fix 3
from the following location:
ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_8.0.7/8.0.7-PROSPECT-IF0003/
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.
· 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 3 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, which is run from the installation CD.
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. More your .profile and cut and paste the following line
[flexpm] $ FLEXPM_HOME=`pwd` PORT_GROUP='' DB_CONNECT='' . ./.profile
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-IF0003-server.tar.gz $FLEXPM_HOME/tmp
[flexpm] $ cd $FLEXPM_HOME/tmp
4. Untar the server tarball
[flexpm] $ gunzip 8.0.7-PROSPECT-IF0003-server.tar.gz
[flexpm] $ gtar -xvpf 8.0.7-PROSPECT-IF0003-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 the -r <responseFile.txt> option. Please see Appendix A of the Installation Guide for further details on the use of this file.
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.
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-IF0003-client.zip on your Windows system in a temporary directory.
2. Unzip 8.0.7-PROSPECT-IF0003-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.
Fixes included in Prospect® 8.0.7.3:
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
IZ67526 / valnt00100377 |
8.0.7.3 |
8.0.7-AEMS-MOTCM01258596-ADDITIONAL TEXT TOKENS ARE REPLACED
ATFIRST (APAR=IZ67526) |
|
IZ66906 / valnt00099989 |
8.0.7.3 |
WRONG MESSAGE DISPLAYED WHEN CREATING SOFT ALARM TEMPLATE
IFMISSED TO FILL THE ADDITIONAL-TEXT FIELD. (APAR=IZ66906) |
|
IZ68023 / valnt00100745 |
8.0.7.3 |
8.0.7-AEMS-MOTCM01253172 - CLASSIC DICTIONARY UPGRADE FAILS
(APAR=IZ68023) |
Fixes included in previous Prospect® 8.0.7 Interim Fixes:
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
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 |
The known issues for Prospect® 8.0.7.3 are as follows:
|
Issue Tracking Number |
Details |
|
valnt00101892 |
Issue: Discrepancies in NSBH & SBH Report Output
Description: A classic client report NSBH report is
discounting data from the final hour of the day in the busy hour calculations
leading to discrepancy in certain NSBH report results.
Expected Result: NSBH and SBH report results for analogous reports should be identical
Actual Result: Under certain conditions there are discrepancies in NSBH Report results.
Workaround: Please contact IBM support for a test fix for this issue. A permanent fix will be delivered in 8.0.7.4 |
This release contains the following documentation addendums which will be added to the Prospect® documentation.
This new function protects the results of the formula over the network elements involved in a calculation but will not protect these results over time in the way that the Prospect Web protect function does.
Note that
in classic reporting elemprotect behaves exactly as classic protect function
does.
The following token may be added to the Additional Text field of a Soft Alarm Template and will be rendered in the Additional Text portion of the soft alarm when generated:
|
Token |
Description |
|
$DEF_ALARM_ID |
The value contained
in the Alarm ID on the Soft Alarm Definition |
It should be noted that Soft Alarm and Busy Hour imports will import any associated UDCs into the Prospect Core/Classic Data Dictionary. If there is a Pweb instance configured to this remote datasource, any new or updates to UDCs will not appear in a Pweb Data Dictionary until the Pweb Data Dictionary Import Agent Completes. This is scheduled to run every 2 hours by default.
The Prospect Core Administration Guide, incorrectly refers to a script called show_part.sh on pp153, this should refer to a script called show_part. The following description for show_part also needs to be added:
To show partitions for tables
show_part scripts lists partitions for given table types base on the standard naming convention for table types. Run show_part script using the following syntax:
> show_part
[type]
The options for show_part are described in
the following table.
|
Type |
Description |
|
-traffic | traffic | tf | TF |
Lists partitions for all of the tables where table_name like "%_TF_%_TAB" |
|
-raw | raw | Raw |
-Raw |
Lists partitions for all of the tables where table_name like "%_RAW%_TAB" |
|
-all | all | ALL |
Lists partitions for all of the tables where table_name like "%_TAB" |
Note: The raw tables contain event/call detail-based
data which in general has a higher data volume. It is used to derive aggregated
performance data. It is typically stored for a shorter period of time e.g 10 days
When a rehoming event results in the creation of a new instance, this instance will not automatically be added to the Active Scenario. The active scenario will be updated to include the new instance - should there be data loaded for it – during the next scheduled invocation of the scenario_activation maintenance job. It is possible to have this instance added to the active scenario sooner by manually invoking the AD_run.sh script, however data will still have to be loaded for the new instance.
The opening paragraph in the Adjusting Job Clean-Up Times section on Prospect Core Administration Guide pp137 needs to be updated to read as follows.
Because the logs some jobs can remain on the system for 24 hours before they are removed, you might want to change the default removal time. The script set_job_cleanup_time.sh adjusts the clean-up times for certain jobs. It controls how long logs remain on the system, i.e When the log is cleaned up by the misc_clean job. Note, it does not control job run time.
Point 6 of the Creating a Soft Alarm Definition Section in the Prospect Core Administration Guide pp 214 should read as follows.
6. Select the EXCLUDE WEEKEND or EXCLUDE HOLIDAYS check boxes to exclude weekends
and holidays from a soft alarm calculations, respectively. Note that checking these options will not stop a soft alarm from being fired at the weekend and/or holiday, rather it means that the data from a weekend and/or holiday will not be taken into account when calculating a Soft Alarm whose Time Range is set to ‘Last N Periods’, ‘Same period, last N days’ or ‘Same period, same day, last N weeks’. In order to stop a soft alarm from being fired at weekends or holidays, use the Exclude Day(s) checkbox options on the Soft Alarm Schedule.
New Administrator scripts have been added that can be used to add new instances into the scenario directly. Very large scenarios should be updated using these Scenario Update scripts which can be run from the Command line rather than using the Classic Client front end. However the Classic Client should still be used to update smaller ones. There are also scripts to backup a scenario before performing the update and a script to subsequently restore this backed up scenario if required.
There are 3 scripts provided and these are described below:
Use this script to add an instance to a scenario.
Usage:
updateScenario.sh -k fullkey -e entity -s scenario -f folder [-link] [-v]
|
Option |
Description |
|
-k |
The full key of the instance to add to the
scenario |
|
-e |
The entity name of the instance to be added |
|
-s |
The name of the scenario to add to. The scenario
name used in the scripts cannot contain spaces. |
|
-f |
The name of the folder where the scenario
resides |
|
-link |
Optional – include this if the
instance is to be linked |
|
-v |
Prints Usage Message |
Example
updateScenario.sh
-k 117-2 -e MSC -s USER-SCEN-1 -f '\Scenarios' -link
Use this script to backup scenario definition to a file
Usage:
backupScenario.sh -f folder -s scenario [-v]
The script saves the specified Scenario in a comma delimited file named
<SCENARIO NAME>_YYYYMMDDHHMMSS.bkp in the /tmp directory.
|
Option |
Description |
|
-f |
The name of the folder where the scenario
resides |
|
-s |
The name of the scenario to backup |
|
-v |
Prints Usage Message |
Example
backupScenario.sh
-f '\Scenarios' -s USER-SCEN-1
Use this script to restore a backed up scenario from a file
Usage:
restoreScenario.sh -f filename [-v]
|
Option |
Description |
|
-f |
The name of the file containing the
scenario to Restore |
|
-v |
Prints Usage Message |
Example
restoreScenario.sh
-f USER-SCEN-1_20091215142233.bkp
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
Copyright and Trademark
Information
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: |
|
David Scott |
14 January 2010 |
Document Created |
|
David Scott |
21 January 2010 |
Updated for Drop 2 to QA |
|
David Scott |
28 January 2010 |
Updated for 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.