Prospect® Web 2.2.7
Interim Fix 7
(2.2.7.7)
Description
Prospect®
Web 2.2.7.7
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 IZ80104, IZ83405, IZ79897,
IZ80763 and IZ85498.
In addition
this Interim Fix includes the following new features for Prospect® Web.
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 7
[Server: Build 3]
Product/Component Release: 2.2.7
Update Name: 2.2.7
Interim Fix 7
(2.2.7.7)
Fix ID: 2.2.7-PROSPECTWEB-IF0007
Publication Date: 25
Oct 2010
Last modified date: 24 October 2010
Contents
Installation
Privileges Required
Pre Upgrade
installation Steps
Post-Upgrade
Installation Instructions
Installing the
Prospect® Web Administration Client
Add User To LDAP
Synchronisation Support
Disable/Enable
2.2.6 Report Header Compatibility Mode for CVS and Excel Downloads.
Stopping Database Activity to Enable Upgrade
Dataloading on
Multi Instance Installation
Copyright and
Trademark Information http://www.ibm.com/legal/copytrade.shtml
Download Prospect® Web 2.2.7
Interim Fix 4 from the following location:
ftp://ftp.software.ibm.com/software/tivoli_support/patches/patches_2.2.7/2.2.7-PROSPECTWEB-IF0007/
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 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® Web 2.2.7[1]
or greater.
·
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.7
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.
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-IF0007-server.tar.gz
$FLEXPM_HOME/tmp
[flexpm] $ cd
$FLEXPM_HOME/tmp
4.
Untar the server tarball
[flexpm] $ gunzip 2.2.7-PROSPECTWEB-IF0007-server.tar.gz
[flexpm] $ tar -xvpf 2.2.7-PROSPECTWEB-IF0007-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.7
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
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
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-IF0007-client.zip
on your Windows system in a temporary directory.
2. Unzip
2.2.7-PROSPECTWEB-IF0007-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.7:
|
Issue Tracking Number |
Released In |
Resolved Issue |
|
IZ80104 /
alm00155786 |
2.2.7.7 |
CLARIFICATION
REGARDING 'SHOW HINTS' IN CHART VIEW. |
|
IZ83405 /
alm00201324 |
2.2.7.7 |
PROSPECT
WEB REPORTS FAIL WITH ORA-17410 |
|
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 |
Fixes included in previous
Prospect® Web 2.2.7
Interim Fixes:
|
Issue Tracking Number |
Released In |
Resolved 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 |
There is no known issue found in this release.
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 |
CVS/Excel Report download uses entity.field
as report header. |
|
web.reporting.226.compatible |
Removed from system |
[Default] CVS/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:
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:
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.
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
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
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
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 |
|
Final Draft – QA Drop 3 |
|
Mike Liew Ing Huey |
|
Release |