Prospect® Web 2.2.7 Interim Fix 1 (2.2.7.1)
Description
Prospect® Web 2.2.7.1 is an Interim Fix for Prospect® Web 2.2.7.
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 IZ56488 , IZ61976, valnt00079499, valnt00081050, valnt00085644, valnt00086351, valnt00086405, valnt00094048, valnt00094064, valnt00094068, valnt00094080, valnt00094084, valnt00094098, valnt00094103, valnt00094115, valnt00094119, valnt00094268, valnt00094306, valnt00094407, valnt00094415, valnt00094467, valnt00094476, valnt00094810, valnt00094819, valnt00095169, valnt00095520 and valnt00096835
Readme file for: Prospect®
Web 2.2.7 Interim Fix 1
[Server: Build 2]
Product/Component Release: 2.2.7
Update Name: 2.2.7
Interim Fix 1
(2.2.7.1)
Fix ID: 2.2.7-PROSPECT-IF0001
Publication Date: 04 November 2009
Last modified date: 04 November 2009
Contents
Installation Privileges Required
Pre Upgrade installation Steps
Post-Upgrade Installation Instructions
Installing the Prospect® Web Administration Client
Example protect
versus elemprotect
Stopping Database Activity to Enable Upgrade
Dataloading on Multi Instance Installation
Copyright and Trademark Information
Download Prospect®
Web 2.2.7 Interim Fix 1
from the following location:
ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_2.2.7/2.2.7-PROSPECT-IF0001/
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 |
Network Timeouts
If your system has a security policy in place such that a session is
disconnected after a lengthy period of apparent inactivity, you should disable
it during this upgrade. There is the possibility that an upgrade can take a
while to run. Since no user input is required during the most of the upgrade,
this can make the upgrade session appear idle. If timeouts are not disabled,
the upgrade terminal could be disconnected during the upgrade.
· Prospect® Web 2.2.7
· 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® Web 2.2.7.1 Interim Fix cannot be uninstalled. Back up the Prospect® Web system, including the Oracle schema, before upgrading.
|
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® 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 Prospect®
Web . You must download the JBoss installation
zip file (but do not extract the files). You need to know the directory name
where the JBoss zip file is located.
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 2.2.7-PROSPECT-IF0001-server.tar.gz $FLEXPM_HOME/tmp
[flexpm] $ cd $FLEXPM_HOME/tmp
4. Untar the server tarball
[flexpm] $ gunzip 2.2.7-PROSPECT-IF0001-server.tar.gz
[flexpm] $ gtar -xvpf 2.2.7-PROSPECT-IF0001-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, the log file (with filename like <YYYY>__<MM>__<DD>__<HH>__<MM>__<SS>) under /tmp or /var/tmp can be viewed 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 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
1. Copy 2.2.7-PROSPECTWEB-IF0001-client.zip on your Windows system in a temporary directory.
2. Unzip 2.2.7-PROSPECTWEB-IF0001-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.
Fixes included in Prospect® Web 2.2.7.1:
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
valnt00095169 |
Analyze Job creating invalid statistics |
|
|
valnt00096835 |
2.2.7.1 |
Add support for elemprotect to pweb/classic rep-gens |
|
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.eWeb 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 |
|
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 |
R21-Failed Activities on Traffic Agents |
|
valnt00094119 |
2.2.7.1 |
Analysis Agent Failing Issues |
|
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 |
|
valnt00095520 |
2.2.7.1 |
Loading flexpm environment take's too much time, this enhancement would reduce the time taken to source the environmen |
|
valnt00094306 |
2.2.7.1 |
Favourite Page in Chart format fails to be displayed |
|
valnt00094268 |
2.2.7.1 |
The programming error's were found under MyProspect Pages. |
|
valnt00092644 / IZ56488 |
2.2.7.1 |
PWEB REPORT PERFORMANCE AFFECTED BY FULL TABLE SCANS ON THEWM_INSTANCE_CONTEXT TABLE ON THE REMOTE DATASOURCE SERVER. |
|
valnt00096043 / IZ61976 |
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. |
The known issues for Prospect® Web 2.2.7.1 are as follows:
|
Issue Tracking Number |
Details |
|
valnt00092337 |
Issue: Pweb UPG: Unable to run a report from remote server module
Description: A classic client report could not be located for running when an attempt was made to run it via the "Browse > remote servers" interface
Expected Result: The operation should initiate a run of the classic client report.
Actual Result: The screen displays the message "The following error(s) have occurred:", and an empty error message string.
Workaround: None. (Note: this does not occur for every classic reports.) |
|
valnt00092844 |
Issue: Trend values not overlayed on projectTime values in forecasting charts when "show limits" checkbox enabled
Description: Issue relating to the display of forecasting UDCs in charts.
Expected Result: Users should be able to view trend() and projectTime() values simultaneously in a single chart
Actual Result: Only one or the other may be displayed at a time
Workaround: None |
|
valnt00094307 |
Issue: Choosing Histogram option to report displays non-blocking error message
Description: If an error is thrown when attempting to define a Histogram report, the system does not restrict the user from continuing to define the invalid report
Expected Result: The error should cause the report definition for to be fully reset, ready to detect if Histogram is again selected by the user.
Actual Result: An error appears, but the user may continue to define the report.
Workaround: None |
This release contains the following documentation addendums which will be added to the Prospect® Web documentation.
This script lists all of the Prospect Web documents owned by a given user then asks for a confirmation before deleting them. Usage is as follows:
[flexpm] $ deleteUserDocs.sh <<username>>
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 the classic protect function does.
Note the following behaviour when using elemprotect in conjunction with protect.
· protect will supersede elemprotect when encountered first in an equation, i.e. time and element protection supersedes just element protection
protect(elemprotect(a+b)
* c) ≡ protect((a+b) * c)
·
elemprotect will honour protected expressions:
elemprotect(protect(a+b) * c)
i.e, a + b will be computed for each time
period.
The result will be aggregated over time, then time aggregation (a + b) * time
aggregation (c) will be computed before aggregating over element.
The aggregation for (a+b) will be the time
aggregation of the outer UDC containing the protect formula. The
aggregation for c is c's time aggregation.
Consider a report based on 30 minute data, which is grouped by time and attribute containing data for 2 BSC network elements as follows[1]:
|
T_HOUR |
T_30 |
BSC.fullkey |
Total |
Total Usage |
|
Calls Count |
Hours |
|||
|
20 |
0 |
117-2-21 |
1000 |
100 |
|
20 |
0 |
117-2-22 |
1500 |
25 |
|
20 |
30 |
117-2-21 |
1200 |
80 |
|
20 |
30 |
117-2-22 |
1500 |
120 |
Consider 3 additional UDCs using no protect, protect and elemprotect as follows, the aggregation on these elements is sum over time and sum over element:
Now examine how these UDCs aggregate over 30 minutes and 1 hour respectively
Look at the 2 thirty minute time periods starting at 20:00 and 20:30
totalDataCallsPerUsageHours
Nothing is protected so sum over the elements for the time period before calculating the formula:
20:00 – 20:30: (1000 + 1500)/(100 + 25) = 20
20:30 – 21:00: (1200 + 1500)/(80 + 120) = 13.5
totalDataCallsPerUsageHours_elemProtect
In this case we protect over element only. The formula is calculated before the element aggregation:
20:00 – 20:30: (1000/100) + (1500/25) = 70
20:30 – 21:00: (1200/80) + (1500/120) = 27.5
totalDataCallsPerUsageHours_Protect
In this case we protect over element and time, however as this is a thirty minute time period there is no time aggregation. The formula is calculated before the element aggregation:
20:00 – 20:30: (1000/100) + (1500/25) = 70
20:30 – 21:00: (1200/80) + (1500/120) = 27.5
Look at the 1 hour time period starting at 20:00
totalDataCallsPerUsageHours
Nothing is protected so sum over the elements and the time periods before calculating the formula:
20:00 – 21:00: (1000 + 1500 + 1200 + 1500 )/(100 + 25 + 80 + 120) = 16
totalDataCallsPerUsageHours_elemProtect
In this case we protect over element only. The elements from the given time periods are aggregated before the formula is calculated:
20:00 – 21:00: ((1000 + 1200)/(100 + 80)) + ((1500 + 1500)/(25 + 120)) = 32.91
totalDataCallsPerUsageHours_Protect
In this case we protect over element and time, the formula is calculated for all time periods then aggregated:
20:00 – 21:00: (1000/100) + (1500/25) + (1200/80) + (1500/120) = 97.5
There are additional system values to control the Prospect® Web Report and Prospect® Web Agent timeouts, these are described below.
This variable represents the max agent timeout in seconds. Note that this only affects TRAFFIC and ANALYSIS agents and that the value must be set on the local Prospect Web database in order to take effect.
If this value is not set, the default value is 14400 (4 Hours). If this value is set to 0 then agent timeout functionality is disabled.
This variable represents the number of seconds the report is allowed to run. This system value must be set on the remote prospect system; this allows different remote datasources to have different report time outs. If the system variable is set on the local Prospect Web system, it will affect E2E reports only.
If the value of this variable is greater than 0, then this value will be used for the report timeout. The value 0 will disable timeouts. Values less than 0 will be treated as if the variable was not set.
If PWeb is unable to find the system value on the remote server it will use the value of the environment variable REP_TIMEOUT which can be set in .profile.custom on the local Prospect Web system.
Any changes to the environment variable require a complete middleware restart following re-sourcing the environment.
Again if the environment variable’s value less than or equal to 0 it will disable report timeouts
If neither the system nor the environment variable is set, then reports will be run with a default value of 82800 seconds which represents 23 hours.
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 |
29 October 2009 |
Document Created |
|
David Scott |
04 November 2009 |
Reviewed for Release |
[1] Similar results would be obtained for a report grouped by attribute and time; however the aggregation level for the element would have to be at the parent entity level, in this case MSC.