IBM Tivoli Monitoring for Databases: Oracle Agent 6.2.0.1-TIV-ITM_ORA-IF0008

(C) Copyright International Business Machines Corporation 2010.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Databases: Oracle Agent,
Version 6.2.0 Fixpack 1

Component ID: 5724B96OO

Fix: Interim Fix 0008, 6.2.0.1-TIV-ITM_ORA-IF0008

Date: 31 March, 2010

Table of contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices

1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.

2.0 Problems fixed
==================
The following problems are addressed by this fix.

2.1 APARS:
----------
APAR : IZ67268
Abstract : WHEN THE ORACLE DATABASE INSTANCE HAS BEEN STANDBY OR SHUTDOWN
Additional Information: The Oracle agent cannot monitor the listener
status when the Oracle Database instance has been in standby
or shutdown.

APAR : IZ67453
Abstract: AGENT CANNOT MONITOR OVER 128 LISTENERS
Additional Information: The Oracle agent cannot read more then 128 listener
definitions from the listener.ora file, and cannot read more then
500 lines of listener definitions from the listener.ora file.
The maximum listener definition has been extended from 128 to
2048 and the maximum line number has been extended from 500
to 10,000.

APAR : IZ68097
Abstract: THE VIEW TIVOLI_KORFILES_VIEW CAUSED HIGH CPU AND MEMORY USAGE
Additional Information: The view SYS.TIVOLI_KORFILES_VIEW is created
in the korgrant.sql and used by the Oracle agent.

APAR : IZ68232
Abstract: ORACLE AGENT CONFIG PROGRAM CRASH WHEN ORACLE INSTANCE PFILEIS
Additional Information: On a Windows(R) operating system, the Oracle agent
configuration program crashes if the Oracle Server 8i/9i
PFILE defined in the Windows registry key of
SOFTWARE\ORACLE\HOME0\ORALLE_<SID>_PFILE does not exist.

APAR : IZ69132
Abstract: KORSQL CANNOT HANDLE THE OUTPUT OF DF -K ON HP-UX
Additional Information: The Oracle agent uses the "df -k" command to
retrieve the physical disk free size and usage size. This command
cannot retrieve the correct size value for an HP-UX operating system.
This problem causes the calculation of the
"Free_Space_Including_Auto_Extend" attribute to be incorrect.


2.2 Defects
-----------
Defect: 120081
Abstract: KORLOG IS NOT PACKAGED IN THE PATCH

Defect: 121499
Abstract: CANNOT MONITOR DYNAMIC LISTENER
Additional Information: The Oracle Aagent cannot monitor the dynamic
listeners of the Oracle Database Server.

Defect: 123349
Abstract: FREE_SPACE_INCLUDING_AUTOEXTEND COUNT WRONG
Additional Information: The Oracle agent count is wrong for the
'Free_Space_Including_Autoextend' attribute when one data file in a
tablespace is set with autoextend on and the maximum size of
this data file is lower then the free diskspace in the current
mount point.

2.3 Enhancements:
-----------------
None.

2.4 Superseded fixes:
---------------------
6.2.0.1-TIV-ITM_ORA-IF0007
6.2.0.1-TIV-ITM_ORA-IF0006
6.2.0.1-TIV-ITM_ORA-IF0005
6.2.0.1-TIV-ITM_ORA-IF0004
6.2.0.1-TIV-ITM_ORA-IF0003
6.2.0.1-TIV-ITM_ORA-IF0002
6.2.0.1-TIV-ITM_ORA-IF0001


2.5 APARS and defects included from superseded fixes
----------------------------------------------------

6.2.0.1-TIV-ITM_ORA-IF0007
-------------------------------
APAR: IZ63540
Abstract: ORACLE AGENT GENERATE CORE FILES WHILE ALERT LOG DELETED

6.2.0.1-TIV-ITM_ORA-IF0006
-------------------------------
APAR: IZ56685
Abstract: TOTAL EXTENTS NOT ALLOCATED DISPLAYING NEGATIVE VALUE
Additional Information: In the "Database Summary" workspace,
"Tablespace" view, "Total Extents Not Allocated" does
not make sense because each segment in a tablespace can have
a different extent size setting. So, how many extents can be
held in a tablespace is not known. The "Total Extents Not
Allocated" column is removed from the workspace, and the
following situations referring to this attribute are marked
as "Deprecated":

Oracle_Max_Extents_Tbsp_Crit
Oracle_Max_Extents_Tbsp_Warn

APAR: IZ58688
Abstract: INCORRECT OUTPUT FOR "ARCH DEST PCT FULL" VALUE ON
ORACLE AGENT
Additional Information: If multiple file systems are used as the
Oracle Archive Destination, and their mount points have the
same parent directory, the "Archive Dest Pct Full" attribute
displays an incorrect value.

APAR: IZ59224
Abstract: WRONG VALUES FOR "PCT FREE SPACE INCLUDING AUTO EXTEND"
Additional Information: If a tablespace is full, it does not
appear in the DBA_FREE_SPACE view. The full tablespace causes
the "Pct Free Space Including Auto extend" in the "Tablespaces"
attribute group to display an incorrect value.

APAR: IZ60378
Abstract: GRANTING ON TIVOLI USER FAILS
Additional Information: In some cases, after running the korgrant.sql
script, the role TIVOLI_ROLE gets the required privileges.
But, granting the TIVOLI_ROLE to the TIVOLI user does not cause
the TIVOLI user to get the corresponding privileges. So,the Tivoli
Enterprise Portal fails to have data displayed.

A new script, korgrant_user.sql, is provided to grant the TIVOLI
user directly, and the TIVOLI_ROLE is no longer required.
This script fixes the granting problem.

Defect: 113278
Abstract: Wrong value for KORSRVR.SRVRSTATUS
Additional Information: The "Server Status" attribute of the "Oracle
Server" attribute group returns an incorrect "Active" value. So,
if a situation has a condition such as "SERVSTATUS!=Active," the
situation is not triggered.


6.2.0.1-TIV-ITM_ORA-IF0005
-------------------------------
APAR: IZ54861
Abstract: THE QUERY ON V$ACCESS or V$OPEN_CURSOR CAUSES HIGH CPU
Additional Information: Querying these two views might
cause the Oracle high CPU problem, the ORA-7445 error,
or the Oracle instance coredump error in some environments.

A new setting to disable the queries on these two views:
Append "KORSESSB,KORSESSO, KORSESSX" to the "Extended
Parameters" to disable queries on V$ACCESS and
V$OPEN_CURSOR. This setting affects the values of some attributes.
See Section 8.0 for details.

The queries on these two cursors are enabled by default.
So, you must to disable these queries manually.

Defect: 105350
Abstract: KORSRVR.ARCDESTU is wrong for 64 Multiple Archive Dest
Database
Additional Information: On 64-bit operating systems, when more than
one Oracle Archive Destination is specified, the "Percent
Archive Free Space", "Archive Free Space(kb)", and "Archive
Used Space(kb)" attributes in the "Oracle Server" attribute
group show an incorrect value.

6.2.0.1-TIV-ITM_ORA-IF0004
-------------------------------
APAR: IZ52073
Abstract: SERVER STATUS IS NOT ACTIVE-RESTRICT AFTER STARTUP
RESTRICT
Additional Information: After the monitored database is started
with the restrict option, "Server Status" in the "Server
Summary" workspace does not turn into "Active-Restrict."

The database user for the agent must have the "RESTRICTED
SESSION" privilege.


APAR: IZ50796
Abstract: TEC SERVER FAILS TO PARSE EVENT FROM THE AGENT
Additional Information: "PARSE FAILED" is found in the output
of the "wtdumprl" command of the Tivoli Enterprise Console.

The "kor.baroc" file in kor_tems_teps_tepd_if0005.tar/zip must
be updated to the event server. See 6.1 for more detail.

6.2.0.1-TIV-ITM_ORA-IF0003
-------------------------------
APAR: IZ46852
Abstract: PROCESS SUMMARY VIEW COULD NOT SHOW DATA IN WORKSPACE
Additional Information: There is no data in the Tivoli Enterprise
Portal "Process Summary" view for an agent installed on a
Solaris Opteron 10 operating system, because the "kddos64" file
is missing from the install image for this operating system.

APAR: IZ44045
Abstract: ITM OR AGENT DOES NOT DISPLAY DATA ON TEP DUE TO LONG
RUNNING
Additional Information: If more than 500 sessions are open on
a heavily loaded Oracle database, the Tivoli Enterprise Portal
workspace might not display any data, because of slow
responding cursors.

Defect: 95753
Abstract: Enable customization of the severity level of Oracle
message ID
Additional Information: The data displayed in the Tivoli Enterprise
Portal "Alert Log" view does not correspond to the
customization of the severity level of the Oracle message ID,
which is saved in the following file:
$CANDLEHOME/misc/regExp<orcl>.properties on UNIX(R) systems, or
%CANDLE_HOME%\TMAITM6\regExp<orcl>.properties on Windows
systems.

Defect: 94398
Abstract: The koragent fails to retrieve data from collector process.
Additional Information: On HP-UX Itanium 64 operating systems, if the
WAIT_TIMEOUT or COLL_WAITTIMEOUT parameter is specified in
the agent instance configuration file, no data is
displayed in the Tivoli Enterprise Portal. The error
message "Write Pipe error 22" can be found in the koragent
log files.

Defect: 93604
Abstract: The agent fails to find the alert_<sid>.log file.
Additional Information: If the Oracle BACKGROUND_DUMP_DEST parameter
is set to a directory that is outside of $ORACLE_HOME, the
agent cannot find the alert_<sid>.log file, and therefore does
not report messages written to that log file.

6.2.0.1-TIV-ITM_ORA-IF0002
-------------------------------
APAR: IZ40687
Abstract: ORACLE AGENT DOES NOT AUTOMATICALLY RETRIEVE ALL THE
DATABASE INSTANCES ON AIX.
Additional Information: The Oracle agent
configuration program fails to find the Oracle instance if
the output from the "ps eww $pid" command exceeds 2048
characters on AIX, because the value of "ORACLE_HOME" is
truncated.

APAR: IZ40670
Abstract: CREATE PROCEDURE PRIVILEGE IN KORGRANT.SQL IS UNNECESSARY
Additional Information: The "Create Procedure" privilege is
unnecessary for the Oracle agent user, so it
has been removed from korgrant.sql.

APAR: IZ38498
Abstract: ORACLE_LISTENER_CRIT SHOWS LISTENER IN A WRONG STATE
Additional Information: The listener status on the Tivoli Enterprise
Portal Server is displayed as "Inactive" when the value of
ORACLE_HOME is long. The listener information cannot be
retrieved, because the output of the "ps" command is truncated
to 80 characters on Solaris.

APAR: IZ39635
Abstract: ORACLE AGENT CANNOT START BECAUSE OF THE BLANK PADDED
VARIABLE IN <HOSTNAME>_OR_<ORACLE_SID>.CFG FILE
Additional Information: The Oracle agent
configuration program throws errors or the agent does not
start with the status "CONFIGSUCESS".

APAR: IZ42703
Abstract: ORACLE_LISTENER_CRIT SITUATION NOT BE FIRED WHEN ONE
LISTENER DOWN
Additional Information: When more than one listener is configured
on the same host, and the name of one listener is a substring
of the other, then the ORACLE_LISTENER_CRIT situation does
not trigger for the superset named listener. For example, if
one listener is named LISTENER and another is named LISTENER2,
then the situation for LISTENER does not trigger when LISTENER
is down and LISTENER2 is active.

6.2.0.1-TIV-ITM_ORA-IF0001
-------------------------------
APAR: IZ34594
Abstract: CORE DUMP WHILE ORACLEDB HAVE NO PERMISSION TO TEMP FILE
Additional Information: korsql core dumps when the current user
has no permission to access the 'korsql_temp1_<instance
name of Oracle database>.txt' file.

APAR: IZ34666
Abstract: 6.1 ORACLE AGENT SERVER SUMMARY WORKSPACE SHOWS 0 AND
BLANK.
Additional Information: The "Server Summary" workspace shows
inaccurate values for all archive-related attributes, which
includes "Archive Dest Pct Full," "Percent Archive Free
Space," "Archive Free Space(kb)," and "Archive Used Space(kb)".

APAR: IZ34681
Abstract: ITMORA6.2/ORACLE AGENT GENERATE CORE EACH 5 MINS
Additional Information: korerr core dumps every 5 minutes when the
Oracle database listener process has more than 800
characters in its command line parameters.

APAR: IZ36644
Abstract: PCT FREE SPACE AUTO EXTEND DISPLAYING WRONG VALUE
Additional Information: The attribute, "Pct Free Space Auto Extend,"
in the attribute group, "Tablespace," shows inaccurate values
when "ntfsinfo.exe" fails on Microsoft Windows(R). This
attribute value might also be inaccurate when the
"TIVOLIOR_TEMP." directory in the Oracle Database points to a nonexistent
directory. The temporary directory is often destroyed after
re-installation of the Oracle agent and
must be re-created manually.

APAR: IZ36876
Abstract: TIVOLI ORACLE AGENTS NOT COLECTING DATA AND SHOWING UP
IN TEPS.
Additional Information: The SQL in cursor STATLTRN has been tuned
for performance purposes.

APAR: IZ32259
Abstract: KDDSIGNL COREDUMPS ON LINUX
Additional Information: When stopping the Oracle agent,
the following error occurs:
> ./itmcmd agent stop or
*** glibc detected ***
/usr/local/Tivoli/IBM/ITM/tmp/winda1_or_MONIT/kddsignl:
corrupted
double-linked list: 0x08077210
***

APAR: IZ31728
Abstract: ITM FOR DB 6.2 ORACLE AGENT GOES DOWN BY CTRL+C ON
SOLARIS.

APAR: IZ31051
Abstract: DATA CACHE HIT PERCENTAGE WAS NEGATIVE IN THE DATA CACHE
HIT PERCENTAGE WORKSPACE IN THE TEP.


3.0 Architecture and prerequisites
==================================
The following link is for the Tivoli platform and application support
matrix. Please refer to this matrix for the latest certification
information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix:
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring for Databases: Oracle Agent, version 6.2 Fix
Pack 0001 (6.2.0-TIV-ITM_DB-FP0001).
Because this fix is cumulative, it can be installed on any fix level for
this version, release, and modification level above the prerequisite.


4.0 Image directory contents
============================
This fix image contains the following files:

- 6.2.0.1-TIV-ITM_ORA-IF0008.README - This README file
- 6.2.0.1-TIV-ITM_ORA-IF0008.tar - Fix archive .tar format
- 6.2.0.1-TIV-ITM_ORA-IF0008.zip - Fix archive .zip format

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX environment; use the .zip file if
you are working in a Windows environment.

The fix archive file contains the following files:
6.2.0.1-TIV-ITM_ORA-IF0008/inst_prereq_patch.sh
6.2.0.1-TIV-ITM_ORA-IF0008/inst_prereq_itmpatch.exe.bat
6.2.0.1-TIV-ITM_ORA-IF0008/kor_patchdepot.sh
6.2.0.1-TIV-ITM_ORA-IF0008/kor_patchdepot.bat
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_aix523_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_aix526_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_aix533_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_aix536_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_hp11_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_hp116_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_hpi116_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_li6243_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_li6263_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_lia266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_ls3243_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_ls3246_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_ls3263_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_ls3266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_lpp266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_lx8266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_sol283_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_sol286_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_sol293_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_sol296_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_sol606_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_aix523_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_aix526_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_aix533_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_aix536_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_hp11_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_hp116_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_hpi116_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_li6243_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_li6263_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_lia266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_lpp266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_ls3243_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_ls3246_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_ls3263_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_ls3266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_lx8266_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_sol283_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_sol286_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_sol293_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_sol296_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_sol606_tema_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_tems_teps_tepd_if0008.tar
6.2.0.1-TIV-ITM_ORA-IF0008/kor_tems_teps_tepd_if0008.zip
6.2.0.1-TIV-ITM_ORA-IF0008/kor_winnt_tema_if0008.cab
6.2.0.1-TIV-ITM_ORA-IF0008/kdd_winnt_tema_if0008.cab
6.2.0.1-TIV-ITM_ORA-IF0008/KORWINNT.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/koraix523.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/koraix526.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/koraix533.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/koraix536.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korhp11.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korhp116.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korhpi116.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korsol283.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korsol286.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korsol293.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korsol296.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korsol606.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korli6243.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korli6263.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korlia266.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korlpp266.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korls3243.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korls3246.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korls3263.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korls3266.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/korlx8266.dsc
6.2.0.1-TIV-ITM_ORA-IF0008/or_dd.properties
6.2.0.1-TIV-ITM_ORA-IF0008/or_dd_062001008.xml


5.0 Installation instructions
=============================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\ibm\itm'
on Windows systems.

Before installing this fix on UNIX systems, set the CANDLEHOME
environment variable to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- If you have customized the Oracle agent korcoll.ctl file,
this file is backed up during the fix install
as korcoll.ctl.62.{timestamp}. After this fix is installed,
edit the latest korcoll.ctl file and merge your modifications
into this korcoll.ctl file.

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file (6.2.0.1-TIV-ITM_ORA-IF0008.tar
or .zip) to a temporary directory on the system that contains the
agent code to be updated. For the purpose of this README, the
<TEMP> symbol represents the fully qualified path to this
directory.
Note: On Windows, this includes the drive letter.

2. Expand the archive file using the tar command on UNIX systems or
an unzip utility on Windows systems. Expanding the file creates a directory
structure that contains fixes for all of the supported operating systems.

3. Use the itmpatch command to install the included prerequisite fix
for the target agent operating system. For more information about the
itmpatch command, see section 6.1.

On a UNIX system, if the fix was expanded to
<TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008
/kdd_xxxxxx_tema_if0008.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the ./cinfo -i command.

In the following example, the file is
kdd_li6243_tema_if0008.tar
> ./cinfo -i
Distributed Database common code
li6243 Version: 06.20.01.08

On a Windows system, if the fix was expanded to
<TEMP>\6.2.0.1-TIV-ITM_ORA-IF0008, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.0.1-TIV-ITM_ORA-IF0008
\kdd_winnt_tema_if0008.cab

4. Use the itmpatch command to install the fix for that agent operating system.
For more information on the itmpatch command, see section 6.1.

On a UNIX system, if the fix was expanded to
<TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008
/kor_xxxxxx_tema_if0008.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the ./cinfo -i command.

In the following example, the file is
kor_li6243_tema_if0008.tar
> ./cinfo -i
Monitoring Agent for Oracle
li6243 Version: 06.20.01.08

On a Windows system, if the fix was expanded to
<TEMP>\6.2.0.1-TIV-ITM_ORA-IF0008, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.0.1-TIV-ITM_ORA-IF0008
\kor_winnt_tema_if0008.cab

5. The 'korgrant.sql' or 'korgrantcustom.sql' script has to be run
after installing fix 6.2.0.1-TIV-ITM_ORA-IF0008. Refer to the IBM
Tivoli Monitoring For Databases: Oracle Agent User's Guide.

5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file (6.2.0.1-TIV-ITM_ORA-IF0008.tar
or .zip) to a temporary directory on the IBM Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
TEMP> symbol represents the fully-qualified path to this directory.
Note: On Windows, this path includes the drive letter.

2. Expand the archive file using the tar command on UNIX systems or an
unzip utility on Windows systems. Expanding the file creates a directory structure
that contains fixes for all of the supported operating systems.

3. To add the agent fix bundles into the remote deployment depot, use the
tacmd addBundles command found in $CANDLEHOME/bin on UNIX systems
or in %CANDLE_HOME%\bin on Windows systems. For more information
on the tacmd addBundles command, see Appendix A. Commands reference
of the IBM Tivoli Monitoring Administrator's Guide.

On a UNIX system: if the fix was expanded to
<TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the patch
directory does not contain any prerequisites that the fix might
require. See Section 3.1 for the prerequisites
for this fix.

-i is the directory that contains the deployment bundles to be
added to the depot.

On a Windows system: if the fix was expanded to
<TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.2.0.1-TIV-ITM_ORA-IF0008

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the patch
directory does not contain any prerequisites that the fix might
require. See Section 3.1 for the prerequisites
for this fix.

-i is the directory that contains the deployment bundles to be
added to the depot.

4. From the <TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008 directory, run the
appropriate script based on the operating system:

kor_patchdepot.bat - Windows
kor_patchdepot.sh - UNIX

This script is provided to make the copy of or_dd_062001008.xml and
or_dd.properties files from the <TEMP>/6.2.0.1-TIV-ITM_ORA-IF0008
directory to the 062000000 version of the Tivoli Enterprise
Monitoring Services depot.

Note: The following error messages are displayed during
'tacmd addSystem' if the script is not executed.

================================================================
KUICAR010I: The agent type OR is being deployed.

KUICAR020E: The addSystem command did not complete because
a deployment error occurred. Refer to the following error
returned from the server:

The property DBSETTINGS.db_extparms is invalid for version
062001001 of the OR agent.

The property name is not valid.
=================================================================

5. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following tacmd commands. For more information about the
tacmd login and updateAgent commands, see Appendix A. Commands
reference of the IBM Tivoli Monitoring Administrator's Guide.

On a UNIX system:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> $CANDLEHOME/bin/tacmd updateAgent -t or
-n <Managed system name>
-v 062001008

On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t OR
-n <Managed system name>
-v 062001008
Note:
- The component (-t) for the updateAgent command is specified as
two characters (or), not three characters (kor).
- The node (-n) for the updateAgent command is the managed system
name of the operating system (OS) agent to be updated. The
target node for an updateAgent command is always an OS agent.

-The following error might occur with the updateAgent command on
Linux(R) and UNIX endpoints, however the agent is successfully
updated. This error does not occur on Windows endpoints.

KUICUA011I: Updating the or agents.
KUICUA015E: The updateAgent command did not complete because
an error occurred. Refer to the following error
returned from the server:

The monitoring server encountered an error while updating the
managed system type.

The kuiras1.log file might provide more information about
this error. If you require further assistance resolving the
error, contact IBM Software Support.

A timeout occurred while waiting for an agent task to
complete on {node name}.

The agent task did not complete within the configured
time out period.

Verify that the target system is online. Increase the
time out value and try the operation again.


5.4 Agent support update
------------------------
Use the following steps to update the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal
Desktop.

1. Transfer the appropriate archive file (6.2.0.1-TIV-ITM_ORA-IF0008.tar
or .zip) to the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli
Enterprise Portal Servers, or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the tar command on UNIX systems or an
unzip utility on Windows systems. Expanding the file creates a directory
structure that contains fixes for all of the supported operating systems.

3. Expand the archive file (kor_tems_teps_tepd_if0008.tar or .zip)
that contains the updates for the Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop
using the tar command on UNIX systems or an unzip utility on Windows
systems. Expanding the file creates a directory structure that includes a
subdirectory called CD-ROM, with the necessary updates.

4. Start the Application Support Installer GUI to install the fix.
The GUI can be started by using the following command from within
the CD-ROM directory where setup.jar is located:

On a UNIX system:

> $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar

On a Windows system:

> <"C:Program Files\IBM\Java142">\jre\bin\java -jar setup.jar

where <"C:Program Files\IBM\Java142"> is the default drive and
location of IBM Java(R) 1.4.2. The location of IBM Java 1.4.2
on your system can vary.

When prompted by the Application Support Installer for the fix
directory, select the CD-ROM directory, not the component directory.
The installer can install updates for multiple components at the
same time.

5. The next panel presented by the Application Support Installer
asks for the selection of the three Tivoli Monitoring components
to which you would like to add application support. For this fix
(6.2.0.1-TIV-ITM_ORA-IF0008), the check boxes must be as follows:

checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the Oracle
06.20.00.05 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
Browser were running when the update was installed, it must be
restarted.

7. To add the application support for the new situation, from the Tivoli
Enterprise Monitoring Server and Tivoli Enterprise Portal Server,
select 'Advanced' and then 'Add TEMS application support'.
Choose the 'kor_upg.sql' script during the 'Application Support'
installation.
Refer to the "Adding application support to the hub monitoring server'
section in IBM Tivoli Monitoring Installation and Setup Guide.

8. From the Tivoli Enterprise Portal Server, run 'buildpresentation.bat'
on Windows or the 'InstallPresentation.sh' file on UNIX or Linux to
reconfigure the Tivoli Enterprise Portal Server.

6.0 Additional installation information
========================================

6.1 Additional information on using itmpatch command
----------------------------------------------------
The itmpatch command has the following syntax.

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }
itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

where

-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch

For example, on a UNIX system:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully-qualified IBM Tivoli Monitoring installation
directory. On Windows, this directory must include the drive letter.
<TEMP> represents the fully-qualified directory specification, where
the fix is located. On Windows, this directory must include the drive letter.

6.2 Verifying the update
------------------------
1. To verify that the agent was updated correctly, use the tacmd to view
the current version of the agent. You are required to log in to a
Tivoli Enterprise Monitoring Server before viewing the agent
version.

For example:
On a UNIX system, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory. The default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t or

On a Windows system, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory. The default location
is 'C:\ibm\itm'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t OR

When the agent update is successful, the agent version must now
be:
06.20.01.08

Note:
- The component (-t) for the tacmd listSystems command is specified
as two characters (OR), not three characters (KOR).

You can also use the GUI to verify that the agent was successfully
updated. From the Tivoli Enterprise Portal Server, right-click on
the database instance name and select Configure, then select the
Agent tab.

For the database agent on a Windows system, the version number is
06.20.01080.
For the database agent on UNIX system, the version number is
06.20.01008.

2. To verify that the agent support files were updated correctly, use the
kincinfo command on Windows systems or the cinfo command on Linux
or UNIX systems to dump the component versions on each of the
Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
Server, and Tivoli Enterprise Portal Desktop systems.

Note:

- The kincinfo and cinfo command output examples in the sections
that follow show all components that can be updated. If you do
not have all of these components installed, then components that
are not installed are not displayed in the output of these commands.


Sample output for the cinfo command on a UNIX or Linux systems
--------------------------------------------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Thu Mar 15 14:07:46 CST 2010 ******************
User: root Groups: root bin daemon sys adm disk wheel
Host name : myaixsys Installer Lvl:06.20.00.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
Monitoring Agent for Oracle update:

dd Distributed Database common code
li6263 Version: 06.20.01.08

or Monitoring Agent for Oracle
li6263 Version: 06.21.01.08
.
.
.
Tivoli Enterprise Monitoring Server update:

or Monitoring Agent for Oracle
tms Version: 06.20.01.08
.
.
.

On a Windows system:
---------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

>kincinfo -i

kincinfo output:

**************** Monday, March 15, 2010 3:05:46 PM **********
User : Administrator Group : NA
Host Name : TIVSUN18 Installer : Ver: 062001020
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
.
.
.
Tivoli Enterprise Monitoring Server update:
OR Oracle Support
WINNT Version: 06.20.01.08 Build: 201003300000

Tivoli Enterprise Portal Server and Tivoli Enterprise Portal
Desktop update:
OR Oracle Support
WINNT Version: 06.20.01.08 Build: 90971

OR Oracle Support
WINNT Version: 06.20.01.08 Build: 90971


Monitoring Agent for Oracle update:
DD Distributed Database Common Code
WINNT Version: 06.20.01.08 Build:

OR Monitoring Agent for Oracle
WINNT Version: 06.20.01.08 Build: 90971

Note:

- The date of the build displayed might not be accurate. This problem
is known and is being addressed.
- The kincinfo and cinfo command output examples in the sections
that follow show all components that can be updated. If you do
not have all of these components installed, then components not
installed are not displayed in the output of these commands.


7.0 Known problems and workarounds
==================================
- Problem: If you are installing this fix into a depot on a Windows
computer, and WinZip is used to extract this fix, text
files in the depot might contain CTRL-M's. When this fix is
remotely deployed to a UNIX computer from the IBM Tivoli
Enterprise Monitoring Server/depot on Windows, the
installation fails. The CTRL-M's are caused by extracting
the fix using WinZip with "TAR file smart CR/LF conversion"
option enabled. This extraction causes WinZip to put CTRL-M's
in text files when they are extracted on UNIX through remote
deployment.

Work-around: If you are using Winzip for the fix installation for a
Tivoli Enterprise Monitoring Server on Windows, disable the
default "TAR file smart CR/LF conversion" option.

- Problem: If the Oracle agent is uninstalled after
applying this fix, the KOR and KDD files are removed, but
the KDDWICMA.ver file with patch version remains.
The presence of this KDD .ver file prohibits the Oracle
agent from being successfully installed again.

Work-around: Delete KDDWICMA.ver manually to allow any new KDD to be
installed.

- Problem: After remote deployment by the GUI, it is not clear that the
latest available fix has been installed.
The "Install Updates" button is not greyed out and the text
indicates that the latest patch level is not installed.

Work-around: No workaround is needed.

- Problem: For IY98181/IZ03843, after applying this fix, utmpx is still
in a corrupted state.

Work-around: You must nullify the /var/adm/utmpx file manually
to remove the corrupted information in the utmpx file.
This must be done only once.

cat /dev/null >/var/adm/utmpx

- Problem: In the Tivoli Enterprise Portal, the instance name is
displayed instead of the host name in the Navigation tree.

For example the Navigation tree might look like this:
MySid
Oracle
Alert Log
...
instead of this,
MyHost
Oracle - MySid
Alert Log
...

If the Navigation tree looks like the example, then the
problem is that the length of the managed
node name, <SID>:<HOSTNAME>:ORA, exceeds the length
supported by the portal. A possible cause is that the
fully-qualified host name is being used. If 'uname -n'
on the Oracle agent computer returns a
fully-qualified host name, then using the fully-qualified
host name is the cause.

Work-around: Override the host name with an appropriate shorter name by
adding the following line to or.config:
export COLL_HOSTNAME=<short name>

- Problem: The Oracle agent receives an ORA-12546 error.
After installing Oracle 10gR2 (10.2.0.1) on Linux/PPC64,
the Oracle agent receives an ORA-12546
error. Also, the root user is unable to log in as any
Oracle user through sqlplus.

Work-around: This problem is caused by a UNIX file permissions error.

References:
SR 5721567.993
Bug 4516865 - Wrong permissions after install of 10gR2
(10.2.0.1)

Install Oracle Patch 4516865
<http://updates.oracle.com/ARULink/PatchDetails/
process_form?patch_num=4516865>

This patch installs a script that relaxes file
permissions in $ORACLE_HOME to solve the problem. You must
first apply the patch using the opatch utility,
which is found at $ORACLE_HOME/OPatch/opatch. After the
patch is applied, you must then run the
$ORACLE_HOME/install/changePerm.sh script. More details
are in the README included with the patch.

- Problem: Remote commands are not available on HP-UX 11i V2 on
Integrity. Remote deploy, configure, start, stop, remove,
and restart are not available on HP-UX 11i V2 on Integrity.

Work-around: None.

8.0 Additional product information
==================================
This fix provides a mechanism to make the changes listed in APAR
IY92195 ORACLE AGENT PROCESS USES A HUGE AMOUNT OF MEMORY. The
default is that the changes are NOT made. Contact Level 2 support for
further information and recommendations for making these changes
after reading the following detailed information.

Note: If you have changes that were made by Level 2 or Level 3 support
using a modified korcoll.ctl file, this fix resets those changes.
The changes must be made again using the mechanism discussed in
the following paragraphs. Do not merge any previously customized
korcoll.ctl file with this korcoll.ctl file. The method
provided below makes that merge unnecessary.

The cursors that are listed below take longer to return data and
consume excessive system resources in some environments. A cursor is
a mechanism by which a name is assigned to a select statement so that
the SQL statement can be manipulated dynamically. Various SQL changes
have been made to enhance the performance of the data gathering cursor
operations within the agent. You can validate the standard of
performance by running the SQL listed below for each cursor in SQL*Plus
by logging into the Oracle Server with the
Oracle agent database ID.

These changes include nine SQL modifications that can be disabled in
the agent using a new "Extended Parameters" field provided at agent
configuration time. The following values can be assigned in this new
field:

DB3,DB6,TS5,KORSESSB,KORSESS0,KORSESSX

Each comma-delimited, no-white-space value represents a change to the
SQL cursor that is executed during data gathering operations within
the agent. The values are the SQL cursor name. For example, setting
the "Extended Parameters" field to DB3,TS1 means that the DB3 and TS1
SQL cursor is disabled for "Set FREEBYTES to zero", 'Set TSNEXTS to
zero', and 'Set MAXEXTTS to zero'. The SQL cursor name is case
insensitive.

The "Extended Parameters" values are saved in the following locations
by operating system:

UNIX file: $CANDLEHOME/config/{hostname}_or_{instance name}.cfg
UNIX variable: db_extparms

Windows Registry Entry: My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\
Candle\KOR\610\{Oracle instance name}\
Environment\COLL_DISABLE_CURSORS

The new "Extended Parameters" field has been added to the following
configuration operations:

- Remote Deploy - A new GUI field labeled "Extended Parameters" and
a new db_extparms flag on the "tacmd" command. See Section 5.3.
- UNIX remote configuration - CandleManage prompts for a new
"Extended Parameters" field during manual configuration. See
Section 5.3.
- UNIX local configuration - The itmcmd config command (or
CandleConfig) prompts for a new "Extended Parameters" field
during manual configuration.
- Windows Tivoli Enterprise Monitoring Services - The
"Configure Using Defaults" has a new "Extended Parameters" field
on the Oracle agent template.

The Oracle agent must be restarted to recognize these
changes to the "Extended Parameters" value.

In the following paragraphs, each SQL cursor is described in detail.
Using the name of the SQL cursor, you can look in the korcoll.ctl file
for the SQL modification that is made when the SQL cursor is disabled.
The korcoll.ctl file is located in $CANDLEHOME/misc on UNIX and
%CANDLE_HOME%\TMAIMT6 for Windows.

When these cursors are disabled, the Oracle agent
displays the default attribute values of these cursors in the Tivoli
Enterprise Portal, meaning that the Oracle agent no longer
monitors the attributes of the disabled cursors. For each cursor,
the workspace and column names that are affected are listed:

SQL cursor: DB3 - ARCHIVE LOG DISPLAY
SQL:
SELECT TABLESPACE_NAME UTSNAME,
SUM(BYTES) FREEBYTES
FROM SYS.DBA_FREE_SPACE
GROUP BY TABLESPACE_NAME;

Disabled: Set FREEBYTES to zero

Navigation Tree: Databases->Database Summary
Workspace: Oracle_Database/Database Summary->Database Summary
(Bar Chart View)
Oracle_Database/Database Summary->Database Summary
(Table View)
Column : DB Percent Free Space = 0
System TS Percent Free = 0

Navigation Tree : Databases->Enterprise Database Summary
Workspace: Oracle_Statistics_Enterprise/Databases Global->
Database Summary(Bar Chart View)

Oracle_Statistics_Enterprise/Databases Global->
Database Summary(Table View)

Column : System TS Percent Free = 0

Situation: Oracle_DB_PctFree_Space_Low = always true
Oracle_SystemTS_PctFree_Critica = always true
Oracle_SystemTS_PctFree_Warning = always false

--------------------------------------------------------------------

SQL cursor: DB6 - ARCHIVE LOG DISPLAY
SQL:
SELECT /*+RULE*/ COUNT(*) EXTENTS
FROM SYS.DBA_EXTENTS;

Disabled: Set EXTENTS to zero

Navigation Tree : Databases->Database Summary
Workspace: Oracle_Database/Database Summary->Database Summary
(Table View)
Column : Total Extents = 0

Situation : None

--------------------------------------------------------------------

SQL cursor TS5 - TOTAL TEMP SEGMENTS
SQL:
SELECT TS.TABLESPACE_NAME UTSNAME,
COUNT(FREE.BLOCKS) TSNFREEB,
MAX(FREE.BLOCKS) MAXBLOCK,
SUM(FREE.BYTES) SUMBYTES,
MAX(FREE.BYTES) MAXBYTES,
(ROUND(SQRT(MAX(FREE.blocks)/SUM(FREE.blocks))*
(100/SQRT(SQRT(COUNT(FREE.blocks)))),2))*100 TSFSFRAG
FROM SYS.DBA_TABLESPACES TS,
SYS.DBA_FREE_SPACE FREE
WHERE TS.TABLESPACE_NAME = FREE.TABLESPACE_NAME
GROUP BY TS.TABLESPACE_NAME
UNION
SELECT FREE.TABLESPACE_NAME UTSNAME,
COUNT(FREE.BLOCKS) TSNFREEB,
MAX(FREE.BLOCKS) MAXBLOCK,
SUM(FREE.BYTES) SUMBYTES,
MAX(FREE.BYTES) MAXBYTES,
(ROUND(SQRT(MAX(FREE.blocks)/SUM(FREE.blocks))*
(100/SQRT(SQRT(COUNT(FREE.blocks)))),2))*100 TSFSFRAG
FROM V$TEMP_EXTENT_MAP FREE
GROUP BY FREE.TABLESPACE_NAME;

Disabled: Set TSNFREEB to zero
Set MAXBLOCK to zero
Set SUMBYTES to zero
Set MAXBYTES to zero
Set TSFSFRAG to zero

Navigation Tree : Databases->Database Summary
Workspace: Oracle_Tablespaces/Database Summary->Tablespace
(Bar Chart View)
Column : For all Tablespace Names,
Pct Free Space = 0.00
Workspace: Oracle_Tablespaces/Database Summary->Tablespace
(Table View)
Column : Number Free Blocks = 0
Free Space Fragmentation = 0
Largest Free Block(KB) = 0
Largest Pct Free = 0.00
Pct Free Space = 0.00

Situation: Oracle_Free_Space_Frag_Crit = always true
Oracle_Free_Space_Frag_Warn = always false

--------------------------------------------------------------------

SQL cursor KORSESSB - V$ACCESS COUNT
SQL:
SELECT /*+RULE */
v1.sid SID,
count(v2.owner) ACCOBJECTS
FROM v$session v1, v$access v2
WHERE v1.sid = v2.sid(+)
AND v2.owner(+) NOT IN ('SYS','SYSTEM','PUBLIC')
GROUP BY v1.sid;

Disabled : Set ACCOBJECTS to zero

Navigation Tree : None
Workspace: None
Attribute Group/Attribute: Oracle_Session_Detail / Access_Objects
Situation : None

--------------------------------------------------------------------

SQL cursor KORSESSO - V$OPEN_CURSOR COUNT
SQL:
SELECT count(*) TOTOPENCUR,
s.sid SID
FROM v$open_cursor o, v$session s
WHERE s.sid = o.sid(+)
GROUP BY s.sid;

Disabled : Set TOTOPENCUR to zero

Navigation Tree : None
Workspace: None
Attribute Group/Attribute: Oracle_Session_Detail / Total_Open_Cursors
Situation : None

--------------------------------------------------------------------

SQL cursor KORSESSX - V$OPEN_CURSOR COUNT
SQL:
SELECT sess.PADDR PADDR,
COUNT(op.HASH_VALUE) OPENCURS
FROM v$open_cursor op,
v$session sess
WHERE sess.SADDR = op.SADDR(+)
GROUP BY sess.PADDR;

Disabled : Set OPENCURS to zero

Navigation Tree : Session->Session Summary
Workspace: Session Summary / Session Detail (Table View)/Open Cursors
(Column)
Attribute Group/Attribute: Oracle_Session_Detail / Open_Cursors
Situation : None


9.0 Notices
===========
This information was developed for products and services offered
in the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult
your local IBM representative for information on the products and
services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply
that only that IBM product, program, or service may be used. Any
functionally equivalent product,program, or service that does not
infringe any IBM intellectual property right may be used instead.
However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or
any other country where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to you.

Trademarks and service marks
------------------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or
other companies. A current list of IBM trademarks is available on the
Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of
Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarked.