IBM Tivoli Monitoring for Databases: Oracle Agent 6.2.0-TIV-ITM_DB-FP0001

Downloadable files


Abstract

This fix pack contains updates for the Monitoring Agent for Oracle. The Monitoring Agent for DB2, MSSQL and Sybase are included but not updated - Updated 2013/11/26.

Download Description

(C) Copyright International Business Machines Corporation 2008.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Databases: Oracle Agent,
Version 6.2.0 - Revised 2009/03/24

Component ID: 5724B96OO

Fix: Fix Pack 0001, 6.2.0-TIV-ITM_DB-FP0001

Date: 07 November, 2008

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 and provides the enhancements listed
in the "Problems Fixed" section below. This fix also includes the superseded
fixes listed in section 2.4. This fix pack contains only updates for the
Monitoring Agent for Oracle.

You can download the IBM Tivoli Monitoring for Databases, version 6.2 Fix Pack
0001 files from Passport Advantage(R) or from the Downloads section of the IBM
Software Support Web site:
http://www-306.ibm.com/software/sysmgmt/products/support/
IBMTivoliMonitoringforDatabases.html.

When this fix pack image is downloaded from the IBM Software Support Web site,
these rules apply:
* You can only locally install the fix pack on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases. Similar to other
upgrade software, the fix pack image cannot be locally installed on a
computer where the product software is not already installed.
* You can populate agents to the depot.
* You can remotely deploy agents to existing or new installations.

When this fix pack image is downloaded from Passport Advantage, these rules
apply:
* You can locally install the fix pack on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases.
* You can locally install the fix pack on a system that does not already host
a licensed copy of IBM Tivoli Monitoring for Databases.
* You can populate agents to the depot.
* You can remotely deploy agents to existing or new installations.

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

2.1 APARS:
----------

APAR : IZ07276
Abstract : MSSQL AGENT WILL NOT STOP, TACMD UPDATEAGENT FAILS
Additional Information: The agent does not stop when installed on a Windows(R)
system with a path name containing one or more subdirectories
that are longer than 8 characters. For example, if the agent
is installed in the directory: C:/Program Files/IBM/ITM.
This can also affect the IBM Tivoli Monitoring for Databases:
Sybase and Oracle agents. To get this fix, at least one
monitoring agent from this fix pack must be installed. Once
one agent from this fix pack is installed, all currently
installed agents from IBM Tivoli Monitoring for Databases will
have this fix.

2.2 Defects
-----------
None

2.3 Enhancements:
-----------------

2.3.1 Data Collection Optimization
----------------------------------
This fix pack optimizes the methods used to collect the following
attribute groups to improve performance. The amount of improvement
depends on the environment.

Attribute Group Name
--------------------
Oracle_Advanced_Queue_Summary
Oracle_Contention_Summary
Oracle_Database
Oracle_Files
Oracle_Lock_Conflicts
Oracle_Logging_Summary
Oracle_Rollback_Segments
Oracle_Server
Oracle_Session_Detail
Oracle_Statistics_Detail
Oracle_Statistics_Summary
Oracle_Tablespaces

2.3.2 Support for 64-bit database on 64-bit Windows
---------------------------------------------------
This fix pack adds support for 64-bit Oracle databases on 64-bit Windows
operating systems. The agent is a 32-bit application, not native 64-bit.
Because the agent is a 32-bit application/client, the following special
installation and configuration steps are required:

1) Install the Oracle 32-bit client (from the Oracle media).
2) When configuring the Oracle instance, change the Database Home Directory
from the ORACLE_HOME of the Database Server to the ORACLE_HOME of the
32-bit client (installed in step 1).
3) Configure a "Local Net Service Name" in the 64-bit Oracle environment to
connect to the current Oracle database. The net service name should be
the same as the Oracle SID.
4) Ensure the listener for the Oracle database is started.
5) Add a new environment variable named LOCAL, and set it to the instance
name that you want to monitor:
a. Local Configuration - From the Tivoli Enterprise Services Manager,
select the Monitoring Agent for Oracle instance, In the "Advanced"
menu, click "Edit Variables", add a new environment variable "LOCAL",
where the value is the Oracle SID for this instance. (for example,
"orcl")
b. Remote Configuration - Adding the new environment variable is not
supported remotely.

2.3.3 Oracle 11 support on Windows, AIX, and Solaris
----------------------------------------------------
This fix pack adds support for monitoring Oracle 11 on the following
operating systems:
Windows
AIX
Solaris (SPARC)
See section 3.0 for the specific operating system versions supported.

2.3.4 Situation sampling interval and startup changes
-----------------------------------------------------
This fix pack changes the "Run at startup" and "Sampling interval" for
some situations so that there is less load on the database when using
the default situations. The support files containing these changes will be
installed on an IBM Tivoli Enterprise Monitoring Server which does not
currently have support files installed for the Monitoring Agent for Oracle. See
section 6.2 for information on installing these changes when upgrading.
The following "Run at startup" and "Sampling interval" default values are
used (situations not mentioned below are unchanged):

Situation Name: Oracle_Archiv_DestFull_Critical
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Archive_DestFull_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:30
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Buf_Cache_Hit_Int_Crit
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Buf_Cache_Hit_Int_Warn
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Cursors_Per_Tran_High
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Data_Cache_Inefficient
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_DB_Archiving_Disabled
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_DB_PctFree_Space_Low
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:03:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Deadlocks_Timeouts_High
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Dictionary_Cache_Hit_Cri
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Dictionary_Cache_Hit_War
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Enqueue_Waits_High
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Free_Space_Frag_Crit
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 001 / 00:00:00
New Sampling interval: 001 / 00:00:00

Situation Name: Oracle_Free_Space_Frag_Warn
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 001 / 00:00:00
New Sampling interval: 001 / 00:00:00

Situation Name: Oracle_Largest_Waiters_Critical
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Largest_Waiters_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Library_Reloads_Pct_Crit
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Library_Reloads_Pct_Warn
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Max_Extents_Tbsp_Warn
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 01:00:00
New Sampling interval: 000 / 01:00:00

Situation Name: Oracle_Max_Extents_Warn
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 001 / 00:00:00
New Sampling interval: 001 / 00:00:00

Situation Name: Oracle_Pct_MAX_DML_Lock_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Pct_MAX_DML_Locks_Critic
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_PctMax_File_Open_Critica
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:03:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_PctMax_File_Open_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:03:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_PctMax_Processes_Critica
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:02:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_PctMax_Processes_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:05:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_PctMax_Sessions_Critical
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:03:00
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Processes_Crit
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 02:00:00
New Sampling interval: 000 / 02:00:00

Situation Name: Oracle_Processes_Wait_Latch
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:02:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_Processes_Warn
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 02:00:00
New Sampling interval: 000 / 02:00:00

Situation Name: Oracle_Redo_Immediate_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Redo_Log_Spc_Waits_Crit
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:10:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Redo_Log_Spc_Waits_Warn
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:10:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Redo_Log_Waits_Critical
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Redo_Log_Waits_Warning
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Redo_Miss_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:20:00

Situation Name: Oracle_Server_CPU_Pct_Critical
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_Server_CPU_Pct_Warning
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:01:30
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Server_Not_Active
Current Run at startup value: Yes
New Run at startup value: Yes
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Server_Status_Inactive
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:02:00
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_SGA_FreeSpace_Inefficien
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Sort_To_Disk_Percent_Hig
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_SystemTS_PctFree_Critica
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:03:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_SystemTS_PctFree_Warning
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:03:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Time_Between_Checkpoints
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:05:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Too_Many_Rollbacks
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:01:00
New Sampling interval: 000 / 00:30:00

Situation Name: Oracle_Total_Applctn_Proces_CPU
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:02:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_Total_Rollback_Critical
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_Total_Rollback_Warning
Current Run at startup value: Yes
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_Total_Sessions_Killed
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:02:00
New Sampling interval: 000 / 00:05:00

Situation Name: Oracle_Total_System_Process_CPU
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:02:00
New Sampling interval: 000 / 00:15:00

Situation Name: Oracle_DB_Archive_Mode_Disabled
Current Run at startup value: No
New Run at startup value: No
Current Sampling interval: 000 / 00:15:00
New Sampling interval: 000 / 00:30:00

2.3.5 Ability to disable data collection
----------------------------------------
This section describes a mechanism to enable the changes listed in
APAR IY92195. The default is that the changes are NOT enabled.
After reading the following detailed information, contact Level 2
support for further information and recommendations for enabling
these changes.

Note: For changes that were made by Level 2 or Level 3 support
using a modified korcoll.ctl file, this fix disables
those changes. You must enable the changes again using the
mechanism discussed in the following paragraphs. Any previously
customized korcoll.ctl file should not be merged 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. 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 Monitoring Agent
for Oracle database ID.

These changes include nine SQL modifications that can be enabled 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,KF1,KF4,STATLTRN,TS1,TS3,TS5,TS6

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 enabled 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(R) file: $CANDLEHOME/config/{hostname}_or_{instance name}.cfg file
UNIX variable: db_extparms

Windows(R) 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:

1.) Remote Deploy - a new GUI field labeled 'Extended Parameters' and a
new db_extparms flag on tacmd.
2.) UNIX remote configuration - CandleManage prompts for a new
'Extended Parameters' field during manual configuration.
3.) UNIX local configuration - itmcmd or CandleConfig prompts for a new
'Extended Parameters' field during manual configuration.
4.) Windows local configuration - Manage Tivoli Enterprise Monitoring
Services(TEMS) - the 'Configure Using Defaults' has a new 'Extended
Parameters' field off the Monitoring Agent for Oracle Template.

The Monitoring Agent for Oracle must be recycled 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, look in the korcoll.ctl
file for the SQL modification that is done when the SQL cursor is
enabled. The korcoll.ctl file is located in $CANDLEHOME/misc on UNIX
and %CANDLE_HOME%\TMAIMT6 for Windows.

When these cursors are enabled, the Monitoring Agent for Oracle
displays default attribute values of these cursors in the Tivoli
Enterprise Portal. The Monitoring Agent for Oracle no
longer monitors the attributes of the enabled 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;

Enabled: 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;

Enabled: 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: KF1 - LARGEST PERCENT FREE
SQL:
SELECT FIL.FILE_ID FILERID,
FIL.FILE_NAME UFILENAME,
FIL.TABLESPACE_NAME UTSNAME,
DATFIL.STATUS FILESTAT,
FIL.BYTES RAWFILESIZE
FROM SYS.DBA_DATA_FILES FIL,
V$DATAFILE DATFIL
WHERE FIL.FILE_ID = DATFIL.FILE#
ORDER BY FIL.FILE_ID;

Enabled: WHERE FIL.FILE_ID = DATFIL.FILE# FIL.FILE_ID < 128

Navigation Tree : None
Workspace: Oracle_Files->Tablespace File
Column : File ID < 128

Situation : None

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

SQL cursor: KF4 - LARGEST PERCENT FREE
SQL1 to get the number of FILERID:

SELECT FIL.FILE_ID FILERID,
FIL.FILE_NAME UFILENAME,
FIL.TABLESPACE_NAME UTSNAME,
DATFIL.STATUS FILESTAT,
FIL.BYTES RAWFILESIZE
FROM SYS.DBA_DATA_FILES FIL,
V$DATAFILE DATFIL
WHERE FIL.FILE_ID = DATFIL.FILE#
ORDER BY FIL.FILE_ID;

SQL2:
SELECT DAT.FILE_ID FILERID,
COUNT(*) FILEXTENTS
FROM SYS.DBA_EXTENTS EXT,
SYS.DBA_DATA_FILES DAT
WHERE EXT.FILE_ID(+) = DAT.FILE_ID
AND DAT.FILE_ID IN ( 1, 2, ... ) where 1, 2, ...
are the FILERID from SQL1
GROUP BY DAT.FILE_ID
ORDER BY DAT.FILE_ID;

Enabled: Set FILEXTENTS to -1

Navigation Tree : None
Workspace: Oracle_Files->Tablespace File
Column : Number Extents = 0

Situation : None

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

SQL cursor: STATLTRN - Blocked Transactions Longest Time
SQL:
SELECT d.ctime BLKTRANS,
b.username, c.sid,
substr(c.owner||'.'||c.object, 1,
length(c.owner||'.'||c.object)),
b.lockwait, a.sql_text
FROM v$sqltext a,
v$session b,
v$access c,
v$lock d
WHERE a.address = b.sql_address
AND a.hash_value = b.sql_hash_value
AND b.sid = c.sid
AND c.sid = d.sid
AND c.owner != 'SYS'
AND b.lockwait = d.kaddr;

Enabled: Set BLKTRANS to zero

Navigation Tree : Servers->Server Statistics Summary
Workspace: Oracle_Statistics_Summary/Throughput Statistics
Summary (6.1.0)->Throughput Statistics

Column : Blocked Transactions(sec) = 0
Situation : None

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

SQL cursor: TS1 - TABLESPACE DETAIL
SQL:
SELECT TS.name UTSNAME,
TS.blocksize * TS.dflinit INITEXTS,
TS.blocksize * TS.dflincr NEXTEXTS,
TS.dflminext TSMINEXTS,
TS.dflmaxext TSMEXTS,
TS.dflextpct TSPEXSIZI,
decode(TS.online$, 1, 'ONLINE', 2, 'OFFLINE', 4,
'READ ONLY', 'UNDEFINED') TSSTAUS,
TS.NAME MAXEXTSP,
COUNT(EXT.EXTENT_ID) TSNEXTS,
round(COUNT(EXT.EXTENT_ID) / decode (TS.dflmaxext,
0,1,TS.dflmaxext)*10000) MAXEXTTS
FROM sys.ts$ TS, SYS.DBA_EXTENTS EXT
WHERE TS.NAME = EXT.TABLESPACE_NAME(+)
GROUP BY TS.NAME,TS.blocksize,TS.dflminext,TS.dflmaxext,
Ts.dflextpct,TS.online$ ,TS.dflinit,Ts.dflincr;

Enabled: Set TSNEXTS to zero
Set MAXEXTTS to zero

Navigation Tree : Databases->Database Summary
Workspace: Oracle_Tablespaces/Database Summary->Tablespace
Column :
Number Extents = 0
Max Extents Specified = maximum allowed extents
Total Extents Not Allocated = maximum allowed extents

Situation: Oracle_Extents_Tbsp_Crit = always false
Oracle_Extents_Tbsp_Warn = always false
Oracle_Max_Extents_Crit = always false
Oracle_Max_Extents_Warn = always false

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

SQL cursor: TS3 - COUNT TOTAL FILES/TOTAL BYETS IN KB
SQL:
SELECT TS.NAME UTSNAME,
COUNT(SEG.SEGMENT_NAME) TSNSEGS
FROM SYS.ts$ TS,
SYS.sys_dba_segs SEG
WHERE TS.NAME = SEG.TABLESPACE_NAME(+)
GROUP BY TS.NAME;

Enabled: Set TSNSEGS to zero

Navigation Tree : Databases->Database Summary
Workspace: Oracle_Tablespaces/Database Summary->Tablespace
(Table View)
Column : Total Segments = 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;

Enabled: 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 TS6 - ROLLBACK SEGMENTS
SQL:
SELECT TS.TABLESPACE_NAME UTSNAME,
COUNT(SEG.SEGMENT_NAME) TSTMPSEG,
COUNT(SEG1.SEGMENT_NAME) TSNROLB
FROM SYS.DBA_TABLESPACES TS,
SYS.DBA_SEGMENTS SEG,
SYS.DBA_SEGMENTS SEG1
WHERE TS.TABLESPACE_NAME = SEG.TABLESPACE_NAME(+)
AND TS.TABLESPACE_NAME = SEG1.TABLESPACE_NAME(+)
AND SEG.SEGMENT_TYPE(+) = 'TEMPORARY'
AND SEG1.SEGMENT_TYPE(+) = 'ROLLBACK'
GROUP BY TS.TABLESPACE_NAME;

Enabled : Set TSTMPSEG to zero
Set TSNROLB to zero

Navigation Tree : Databases->Database Summary
Workspace: Oracle_Tablespaces/Database Summary->Tablespace
(Table View)
Column : Number Temp Segments = 0
Number Rollback Segments = 0

Situation : None



2.4 Superseded fixes:
---------------------
IBM Tivoli Monitoring for Databases, Version 6.2.0: Oracle Agent
LA0005 - (6.2.0-TIV-ITM_ORA-LA0005)

IBM Tivoli Monitoring for Databases, Version 6.2.0: Oracle Agent
LA0004 - (6.2.0-TIV-ITM_ORA-LA0004)

IBM Tivoli Monitoring for Databases, Version 6.2.0: Oracle Agent
LA0003 - (6.2.0-TIV-ITM_ORA-LA0003)

IBM Tivoli Monitoring for Databases, Version 6.2.0: Oracle Agent
LA0002 - (6.2.0-TIV-ITM_ORA-LA0002)

IBM Tivoli Monitoring for Databases, Version 6.2.0: Oracle Agent
LA0001 - (6.2.0-TIV-ITM_ORA-LA0001)


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

6.2.0-TIV-ITM_ORA-LA0005
------------------------

APAR : IZ29151
Abstract: REDOLOGS NOT ARCHIVED COLUMN IS WRONG
Additional Information: If the database is in NOARCHIVELOG mode, the
'Redo Logs Not Archived' attribute has a value of zero. However, the
attribute does not show as 0 when it is in NOARCHIVELOG mode.

APAR : IZ29527
Abstract: KORERR COREDUMPS ON ZLINUX
Additional Information: The problem specifically occurs on
zLinux operating systems.

6.2.0-TIV-ITM_ORA-LA0004
------------------------

APAR : IZ23699
Abstract : SQL IN KORLCK05 CURSOR NEEDS TO BE MODIFIED FOR 10G
Additional Information: The Monitoring Agent for Oracle against
Oracle 10g writes the following message to the file
{hostname}_or_{instance name}_col.log:
"CMA3530E (131512) Math statement PLKHIT for cursor
KORLOCKS references KORLCK05 which has no rows,
setting answer to 0".

APAR : IZ24733
Abstract : KORERR COREDUMP IN DEBUG MODE
Additional Information: Debug mode of korerr binary causes memory fault on
Linux.

APAR : IZ25541
Abstract : korcoll.exe intermittent crash in UTF8 conversion
Additional Information: This is an intermittent problem. The collector log
shows a UTF-8 conversion failure, and sometimes, the collector
fails to start. This occurs on Windows with any Oracle version.

6.2.0-TIV-ITM_ORA-LA0003
------------------------

APAR : IZ19880
Abstract : ITM 6.1-SOME ATTRIBUTES IN 'ORACLE SGA MEMORY' GROUP ARE ZERO.
Additional Information: The values for several Oracle SGA Memory
attributes are incorrectly returned as zero. The attributes
include Data Cache size (MB), SGA pct data cache,
SGA pct dict cache, and shared pool size.

APAR : IZ20186
Abstract : ITMCMD DBCONFIG RESETS THE DB_TNS
Additional Information: The non-default path of the listener.ora
file specified in DB_TNS is reset to the default location
when using the ./itmcmd dbconfig -A to change the password.

APAR : IZ21587
Abstract : FREE SPACE CALCULATIONS FORSITUATION ORACLE_FREE_TBSP_WARN SEEMS
TO BE INCORRECT
Additional Information: If a tablespace is created with auto extend
disabled and no free space, then the percentage of free
space value is wrong.

APAR : IZ22007
Abstract : FREESPACE INCLUDING AUTO EXTEND VALUE INCORRECT
Additional Information: Attribute Free space including auto extend
is incorrect when the tablespaces have the autoextend enabled


6.2.0-TIV-ITM_ORA-LA0002
--------------------------

APAR : IZ18824
Abstract : ERROR IN VERIFYING OMA FOR DISTRIBUTED DATABASES INSTALLATION
Additional Information: "Verify Monitoring Agent for Oracle installation"
option reports that <hostname>_or_<oracleinstname>_col.out
file is not found or unable to open the file.

APAR : IZ19112
Abstract : ORA-01476: DIVISOR IS EQUAL TO ZERO ON KSS9 CURSOR
Additional Information: The problem is caused by the v1.value being 0
for parallel_max_servers in the table v$parameter.

APAR : IZ16555
Abstract : ORACLE AGENT CORE DUMPS ON ALERT LOG FILES
Additional Information: The Monitoring Agent for Oracle core dumps on
then alert log file when the Oracle message is more than the
expected length.

APAR : IZ17115
Abstract : ORACLE AGENT (KORCOLL) USES >10% OF THE CPU
Additional Information: The performance tool shows 10% utilization
on an AIX operating system, though the performance report
indicates that the Monitoring Agent for Oracle only uses
about 0.2% of the CPU.

APAR : IZ13162
Abstract : ORACLE AGENT COREDUMPS WITH THE INCOMPLETE ORA-02 MESSAGE.
Additional Information: The Monitoring Agent for Oracle dumps core
when the database workspace Navigator item and database
workspace "alert log" are clicked.

6.2.0-TIV-ITM_ORA-LA0001
--------------------------

APAR : IY92195(Defect 64543)
Abstract: ORACLE AGENT PROCESS USES A HUGE AMOUNT OF MEMORY
Additional Information: See Section 2.3.5 before applying this fix.

APAR : IY99662
Abstract: NEED TO ADD /T AFTER TIME IN INST_PREREQ_ITMPATCH.BAT
Additional Information: None.

APAR : IZ04972
Abstract: NO DATA DISPLAYED IN ORACLE AGENT ALERT LOG WORKSPACE AND
FILES(S) CREATED DUE TO ENTRY IN ALERT LOG.
Additional Information: None.

APAR : IZ05321
Abstract: CANDLEDBAGENT KILLS NON-ITM PROCESSES IF RUNINFO PIDS
ARE REUSED
Additional Information: When stopping the Monitoring Agent for
Oracle, you must wait at least 30 seconds before
restarting the agent to make sure all the agent processes
have stopped normally.

APAR : IZ06982
Abstract: AUTO ARCHIVE ATTRIBUTE VALUE IS WRONG WITH ORACLE 10G
Additional Information: Starting with Oracle 10g release 10.1,
the LOG_ARCHIVE_START initialization parameter has been
deprecated. As a result, Auto_Archive is always 'NO' and
the Oracle_DB_Archiving_Disabled situation is always false.

There is now a new situation: Oracle_DB_Archive_Mode_Disabled.

This situation has the following formula:
Oracle_Database.Archive_Log_Mode_Enabled NE Yes

This situation is similar to Oracle_DB_Archiving_Disabled,
but it does not use the "Auto Archive" column.
To use this new situation, you must add application
support to the Tivoli Enterprise Monitoring Server and
Tivoli Enterprise Portal Server after installing this fix.
See section 5.4 for more information.

APAR : IZ07142
Abstract: ORACLE AGENT ON SOLARIS FAILED TO START 'COLLECTOR'
Additional Information: The following error message appears in the
collector log:
ld.so.1: ko9coll: fatal: libclntsh.so.9.0: open failed:
No such file or directory

APAR : IZ11539
Abstract: KDDOS.EXE error happens on large DB env
Additional Information: None.

Defect: 50644
Abstract: KORFP1:SLES10 agent fails to start
Additional Information: Add support for SUSE Linux Enterprise
10 (SLES 10) and RedHat Enterprise Linux 5 (RHEL 5).

Defect: 65515
Abstract: Statically link the Rogue Wave libraries for Database agents
Additional Information: None.

Defect: 67459
Abstract: itmcmd agent stop or failed on AIX intermittently.
Additional Information: None.


3.0 Architecture and prerequisites
==================================

This fix pack adds support for the following Oracle versions and operating
systems:

Operating system: AIX 5.3
Addition: Oracle 11.1 support

Operating system: Solaris 9 (SPARC)
Addition: Oracle 11.1 support

Operating system: Solaris 10 (SPARC)
Addition: Oracle 11.1 support

Operating system: Windows 2000 Advanced Server
Addition: Oracle 11.1 support

Operating system: Windows 2000 Professional
Addition: Oracle 11.1 support

Operating system: Windows 2000 Server
Addition: Oracle 11.1 support

Operating system: Windows 2003 Data Center
Addition: Oracle 11.1 support

Operating system: Windows 2003 Data Center x64 Edition AMD64/EM64T (-5/05)
Addition: Support for Oracle 11.1: 32b agent monitoring 32b DB
Support for Oracle 10.2, 11.1: 32b agent monitoring 64b DB

Operating system: Windows 2003 Enterprise Edition
Addition: Oracle 11.1 support

Operating system: Windows 2003 Enterprise x64 Edition AMD64/EM64T (-5/05)
Addition: Support for Oracle 11.1: 32b agent monitoring 32b DB
Support for Oracle 10.2, 11.1: 32b agent monitoring 64b DB

Operating system: Windows 2003 Standard Edition
Addition: Oracle 11.1 support

Operating system: Windows 2003 Standard x64 Edition AMD64/EM64T (-5/05)
Addition: Support for Oracle 11.1: 32b agent monitoring 32b DB
Support for Oracle 10.2, 11.1: 32b agent monitoring 64b DB

Operating system: Windows XP Professional
Addition: Oracle 11.1 support

The following link is for the Tivoli Operating system 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:
--------------------------------
If you intend to use tacmd updateAgent to deploy Monitoring Agent
for Oracle, Monitoring Agent for Sybase, or Monitoring Agent for
MSSQL from this fix pack, then any Hub Tivoli Enterprise Monitoring
Server or Remote Tivoli Enterprise Monitoring Server which contains
a depot with these agents must have IBM Tivoli Monitoring, version
6.2 Fix Pack 2 (6.2.0-TIV-ITM-FP0002) or later installed. This is
represented as 06.20.02.00.

If there is an OS Agent (Monitoring Agent for UNIX OS, Monitoring
Agent for Windows NT, or Monitoring Agent for Linux OS) in the same
CANDLEHOME where you intend to deploy this fix pack, then the OS
agent must be at the IBM Tivoli Monitoring, version 6.2 Fix Pack 1
(6.2.0-TIV-ITM-FP0001) or later level. This is represented as
06.20.01.00.

If you are using the upgrade image from the support Web site, then
prior to installing this fix pack, you must install at least one
agent from IBM Tivoli Monitoring for Databases version 6.1.0 or
version 6.2.0.


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

- 6.2.0-TIV-ITM_DB-FP0001.README - This README file
- 6.2.0-TIV-ITM_DB-FP0001.tar - Fix archive .tar format

Note: The .tar file contains the images for all the platforms,
including Windows.

5.0 Installation instructions
=============================

When this fix pack image is downloaded from the IBM Software Support Web site,
these rules apply:
* You can locally install the fix pack only on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases. Similar to other
upgrade software, the fix pack image cannot be locally installed on a
computer where the product software is not already installed.
* You can populate agents to the depot.
* You can remotely deploy agents to existing or new installations.

When this fix pack image is downloaded from Passport Advantage, these rules
apply:
* You can locally install the fix pack on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases.
* You can locally install the fix pack on a system that does not already host
a licensed copy of IBM Tivoli Monitoring for Databases.
* You can populate agents to the depot.
* You can remotely deploy agents to existing or new installations.


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.

- If you have customized the Monitoring Agent for Oracle
korcoll.ctl file, this file is backed up during the fix install
as korcoll.ctl.6x.{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 install and update (including silent installation)
--------------------------------------------------------------
1. Transfer the archive file (6.2.0-TIV-ITM_DB-FP0001.tar)
to a temporary directory on the system that contains the
agent code to be updated. For the purpose of this README, the
symbol <TEMP> 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
a utility on Windows systems. This creates a directory
structure that contains fixes for all of the supported platforms.

3. Use the procedures in the "IBM Tivoli Monitoring, Version 6.2.0
Installation and Setup Guide" to install the agent.

4. Use the procedures in the specific database monitoring agent user's
guide to complete the installation and configuration.

5. When installing the Monitoring Agent for Oracle, additional database
permissions must be granted for the agent after installing fix
6.2.0-TIV-ITM_DB-FP0001. See section 6.3 Granting Oracle database
permissions for details.


5.3 Remote agent update and installation
----------------------------------------
1. Make sure that all potential targets of the remote deployment are
running version 6.2 Fix Pack 0001 level or later of the OS monitoring
agent.
2. Transfer the archive file (6.2.0-TIV-ITM_DB-FP0001.tar)
to a temporary directory on the IBM Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this directory.
Note: On Windows, this includes the drive letter.

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

4. To add the fix pack bundles into the remote deploy 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-TIV-ITM_DB-FP0001:
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/6.2.0-TIV-ITM_DB-FP0001/WINDOWS/Deploy -t or -f
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/6.2.0-TIV-ITM_DB-FP0001/unix -t or -f

where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, in this case or
represents the Monitoring Agent for Oracle
-f performs the actions without asking for confirmation

On a Windows system: if the fix was expanded to
<TEMP>/6.2.0-TIV-ITM_DB-FP0001:
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\6.2.0-TIV-ITM_DB-FP0001\WINDOWS\Deploy -t or -f
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\6.2.0-TIV-ITM_DB-FP0001\unix -t or -f

where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, in this case or
represents the Monitoring Agent for Oracle
-f performs the actions without asking for confirmation

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 on 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 062001000

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 062001000
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 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 may 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.

6. When installing the Monitoring Agent for Oracle, additional database
permissions must be granted for the agent after installing fix
6.2.0-TIV-ITM_DB-FP0001. See section 6.3 Granting Oracle database
permissions for details.


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 archive file (6.2.0-TIV-ITM_DB-FP0001.tar)
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 a
utility on Windows systems.

3. Use the procedures in the "IBM Tivoli Monitoring, Version 6.2.0
Installation and Setup Guide."

4. Use the procedures in the specific database monitoring agent user's
guide to complete the installation and configuration.

5. If the Tivoli Enterprise Monitoring Server being updated is remote (not a
Hub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise
Monitoring Server.

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

6.1 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 login
to a Tivoli Enterprise Monitoring Server prior to 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 will be
06.20.01.00

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

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
following systems: Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
Server, and Tivoli Enterprise Portal desktop.

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

This command offers you four options on the CINFO menu shown in
the example that follows. Choose the option that meets your needs.

*********** Mon Sep 22 15:40:13 EDT 2008 ******************
User : root Group: root bin daemon sys adm disk wheel
Host name : myaixsys Installer Lvl:06.20.00.00
CandleHome: /opt/IBM/ITM
***********************************************************

-- CINFO Menu --
1) Show products installed in this CandleHome
2) Show which products are currently running
3) Show configuration settings
4) Show installed CD release versions
X) Exit CINFO
1

*********** Mon Sep 22 15:41:04 EDT 2008 ******************
User : root Group: root bin daemon sys adm disk wheel
Host name : myaixsys Installer Lvl:06.20.00.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory


Unix/Linux: IBM Tivoli Enterprise Server Portal Server / IBM Tivoli
Enterprise Portal Desktop, cinfo output for Oracle:

or Monitoring Agent for Oracle
tps Version: 06.20.01.00

Unix/Linux: Monitoring Agent for Oracle

ax IBM Tivoli Monitoring Shared Libraries
aix523 Version: 06.20.01.00

dd Distributed Database common code
aix523 Version: 06.20.01.00

or Monitoring Agent for Oracle
aix523 Version: 06.20.01.00

ui Tivoli Enterprise Services User Interface
aix523 Version: 06.20.01.00


Sample output of the kincinfo command 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:

Windows: Tivoli Enterprise Server Portal Server / Tivoli
Enterprise Portal Desktop

OR Monitoring Agent for Oracle
WINNT Version: 06.20.01.00 Build: 200810221102

OR Monitoring Agent for Oracle
WINNT Version: 06.20.01.00 Build: 200810221102

OR Monitoring Agent for Oracle
WINNT Version: 06.20.01.00 Build: 200810221102

OR Monitoring Agent for Oracle
WINNT Version: 06.20.01.00 Build: 200810221102

Windows: Monitoring Agent for Oracle:

DD Distributed Database Common Code
WINNT Version: 06.20.01.00 Build: 200810221042


OR Monitoring Agent for Oracle
WINNT Version: 06.20.01.00 Build: 200810221102

6.2 Overriding previously installed situations
----------------------------------------------
If you installed the agent support files from this image, but a prior
version of the Monitoring Agent for Oracle support files had been previously
installed (this is an upgrade, not a fresh install), then the situation
changes described in section 2.3.4 will not be made.

If you have not modified the default IBM-provided Monitoring Agent for Oracle
situations and want to overwrite the default IBM-provided Monitoring Agent for
Oracle situations with the changes mentioned in section 2.3.4, the following
procedure can be used.

CAUTION: This procedure overwrites all IBM-provided Monitoring Agent for Oracle
situations and there is no way to retrieve the current situation settings after
these steps are performed.

When using a Windows Tivoli Enterprise Monitoring Server:
1. Start the Manage Tivoli Enterprise Monitoring Services.

2. Select the Tivoli Enterprise Monitoring Server.

3. Right-click and select Advanced -> Add TEMS application support.

4. In the "Select the application support to add to the TEMS" windows,
select Oracle Support, kor.sql, V620.

5. Restart the Tivoli Enterprise Portal.

When using a Linux or UNIX Tivoli Enterprise Monitoring Server:
1. Log on to the local Linux or UNIX system from which you will be adding
application support to the Tivoli Enterprise Monitoring Server.

2. Set the system variables required by the application support utility:
a. Enter the following command to set the path to the location of the SQL
files:

export SQLLIB=install_dir/tables/cicatrsq/SQLLIB

b. Enter the following command if the Tivoli Enterprise Monitoring Server
is configured to use the IP.PIPE or IP.SPIPE protocols:

export KDC_FAMILIES=PORT:port_number

where port_number is the number of the listening port used by the
Tivoli Enterprise Monitoring Server. The port number was specified
when the Tivoli Enterprise Monitoring Server was installed. The default
port number is 1918 for IP.PIPE and 3660 for P.SPIPE.

3. Run the following commands to start the application support utility:
cd install_dir/arch/ms/bin

./kdstsns

where arch specifies the operating system of this computer. For example, on
SUSE Linux Enterprise Server 9 for z/Series 64-bit, the arch directory is
ls3263. On AIX® V5.3 32-bit, the arch directory is aix533.

4. When prompted, enter the following information about the monitoring server
on this computer. This information is needed to establish a connection
between the application support utility and the monitoring server.
- The communications protocol: IP.UDP, IP.PIPE, or IP.SPIPE
- The host name or IP address
- The port number

5. At the next prompt, enter the SQL file of the application support file that
you want to add. For example, for the Monitoring Agent for Oracle, enter
kor.sql. The file name is case-sensitive and must be entered in lower case.

Note: Depending on which product you are upgrading from, 6 SQL errors might
occur. These do not impact the functionality of the agent and can be
ignored.

6. Restart the Tivoli Enterprise Portal.

6.3 Granting Oracle database permissions
----------------------------------------
The procedure for granting the additional permissions depends on the
environment prior to installing this fix pack.

1. If this is a new installation, not an update, then run 'korgrant.sql' or
'korgrantcustom.sql'. See the Monitoring Agent for Oracle User's Guide
for additional information. The additional permissions needed for this
fix pack are included in the 'korgrant.sql' and 'korgrantcustom.sql'
scripts which are installed by the fix pack installation.

2. If upgrading from Monitoring Agent for Oracle version 6.1, then run
'korgrant.sql' or 'korgrantcustom.sql'. See the Monitoring Agent for Oracle
User's Guide for additional information. The additional permissions needed
for this fix pack are included in the 'korgrant.sql' and
'korgrantcustom.sql' scripts which are installed by the fix pack
installation.


3. If upgrading from Monitoring Agent for Oracle version 6.2, and
'korgrant.sql' or 'korgrantcustom.sql' have already been run, then
following the installation of this fix pack, but prior to starting
the Monitoring Agent for Oracle, run 'korgrant62FP1.sql' as follows:
korgrant_62FP1.sql <user_role>

where: <user_role> is the name of the role that was used when
'korgrant.sql' or 'korgrantcustom.sql' were run.

Or, the following grant command can be executed instead of
running the 'korgrant62FP1.sql' script.

grant select on V_$ARCHIVE_DEST to <user_role> ;
grant select on V_$DBFILE to <user_role>;
grant select on V_$LOCKED_OBJECT to <user_role>;
grant select on SYS.DBA_LMT_USED_EXTENTS to <user_role>;
grant select on SYS.DBA_DMT_USED_EXTENTS to <user_role>;
grant select on SYS.SEG$ to <user_role>;
grant select on SYS.UNDO$ to <user_role>;


where: <user_role> is the role setup for the
IBM Tivoli Monitoring For Databases: Oracle Agent connection.

Note: the permissions may either be granted to the user id
or to the role.


7.0 Known problems and workarounds
==================================
- Problem: If you are installing this fix into a depot on a Windows
computer, and WinZip(R) is used to extract this fix, text
files in the depot might contain CTRL-Ms. 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 causes WinZip to put CTRL-Ms in text
files when they are extracted on UNIX through remote deploy.

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

- Problem: If the Monitoring Agent for Oracle 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 Monitoring
Agent for Oracle from being successfully installed again.

Workaround: Delete KDDWICMA.ver manually to allow any new KDD files to
be installed.

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

Workaround: Nullify /var/adm/utmpx file manually
to remove the corrupted information in the utmpx file.
This only needs to be done 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 so, 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 Monitoring Agent for Oracle computer returns a
fully-qualified host name, then this is the cause.

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

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

Workaround: This 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


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 run the
$ORACLE_HOME/install/changePerm.sh script. More details
can be found 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.

Workaround: None.

- Problem: Remote addSystem is not available for a 64-bit Oracle
Database on the 64-bit Windows operating system.

Workaround: Locally install the agent using the manual procedure described
in detail in section 2.3.

- Problem: Remote addSystem is not available when the GSkit is installed in
a non-default directory (For Windows, the default directory is
C:\Program Files\IBM\GSK7. For Linux, the default directory is
/usr/local/ibm/gsk7. For UNIX, the default directory is
/opt/ibm/gsk7.)

Workaround: Locally install the agent.

- Problem: Remote deploy through the GUI is not available. Even when this fix
pack is installed into the depot, the "Install Updates" button is
grey and the text indicates that the latest patch level is installed.

Workaround: Deploy this fix pack using the tacmd CLI.

- Problem: After upgrading the Monitoring Agent for Oracle support files to this
fix pack level, situations show up in the Message Log view (when the
Enterprise Navigator tree item is selected), but not in the
Situation Event Console view nor as an icon in the Navigator tree.

Workaround: Restart the Tivoli Enterprise Portal.

- Problem: After upgrading the Monitoring Agent for Oracle support files to
this fix pack level on a remote Tivoli Enterprise Monitoring Server
(not a Hub Tivoli Enterprise Monitoring Server), the managed nodes
connected to the remote Tivoli Enterprise Monitoring Server are
absent from the Monitoring Agent for Oracle Enterprise views:
Enterprise Alert Log Summary
Enterprise Cache Totals Summary
Enterprise Contention Summary
Enterprise Database Summary
Enterprise Logging Summary
Enterprise Process Summary
Enterprise Server Statistics Summary
Enterprise Servers Summary
Enterprise Session Summary
Enterprise System Global Area Summary

Workaround: Restart the remote Tivoli Enterprise Monitoring Server.

- Problem: Remote deploy commands through the GUI and through the tacmd
command line do not work on systems where "uname -n" returns
a fully-qualified host name. In both cases, a message is returned
indicating the managed system is not known.

Workaround: Stop the Oracle Agent. On the Tivoli Enterprise Portal, clear
the offline entry for all instances associated with this system.
Edit install_dir/config/or.config, and add the following line:

export CTIRA_SYSTEM_NAME='<short_host_name>'

where short_host_name is the same host name as is set for
CTIRA_HOSTNAME in or.config. for example, if or.config contains
the following line:

export CTIRA_HOSTNAME='myhost'

Then add the following line:

export CTIRA_SYSTEM_NAME='myhost'

Refer to TechNote 1233575 "Using the CTIRA_SYSTEM_NAME environment
variable" for additional information.

Problem: For SLES10 systems you may see the following error when you are
attempting to start the agent:

# ./itmcmd agent start or
CandleDBAgent : installer level 620 / 300.
itmcmd agent : considering servers: amsid1.
Bypassing server amsid1 because CandleDBConfig status is INCOMPLETE

Workaround: Reconfigure the Oracle agent.


8.0 Additional product information
==================================
None.


9.0 Notices
===========
Date of
Created/Revised by Creation/Update Summary of Changes
-------------------------------------------------------------------------------------------------
tf November 2008 Document created
--------------------------------------------------------------------------------------------------
mk March 24, 2009 Removed reference to Fix
Pack .zip file
----------------------------------------------------------------------------------------------------

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 Corporation in the United States, other
countries, or both. If these and other IBM trademarked terms are marked
on their first occurrence in this information with a trademark symbol,
these symbols indicate U.S. registered or common law trademarks owned by
IBM at the time this information was published. Such trademarks may also
be registered or common law trademarks in other countries. A current list
of IBM trademarks is available on the Web at "Copyright and trademark
information" at http://www.ibm.com/legal/copytrade.shtml.

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

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

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

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

Other company, product, or service names may be trademarks or service
marks of others.

Created/Revised by Date of Creation/Update Summary of Changes
mk November 2008 Document created.
mk March 24, 2009 Removed reference to Fix Pack .zip file.

Prerequisites

If you intend to use tacmd updateAgent to deploy Monitoring Agent
for Oracle, Monitoring Agent for Sybase, or Monitoring Agent for
MSSQL from this fix pack, then any Hub Tivoli Enterprise Monitoring
Server or Remote Tivoli Enterprise Monitoring Server which contains
a depot with these agents must have IBM Tivoli Monitoring, version
6.2 Fix Pack 2 (6.2.0-TIV-ITM-FP0002) or later installed. This is
represented as 06.20.02.00.

If there is an OS Agent (Monitoring Agent for UNIX OS, Monitoring
Agent for Windows NT, or Monitoring Agent for Linux OS) in the same
CANDLEHOME where you intend to deploy this fix pack, then the OS
agent must be at the IBM Tivoli Monitoring, version 6.2 Fix Pack 1
(6.2.0-TIV-ITM-FP0001) or later level. This is represented as
06.20.01.00.

If you are using the upgrade image from the support Web site, then
prior to installing this fix pack, you must install at least one
agent from IBM Tivoli Monitoring for Databases version 6.1.0 or
version 6.2.0.

URL LANGUAGE SIZE(Bytes)
6.2.0-TIV-ITM-FP0001 (ftp) English 999999
6.2.0-TIV-ITM-FP0001 (http) English 999999
6.2.0-TIV-ITM-FP0002 (ftp) English 999999
6.2.0-TIV-ITM-FP0002 (http) English 999999

Installation Instructions

Please refer to the 6.2.0-TIV-ITM_DB-FP0001.README contained in the Description section above for general installation instructions.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is DD?
6.2.0-TIV-ITM_DB-FP0001.README 11/7/2008 English 74927 FTP DD
6.2.0-TIV-ITM_DB-FP0001.tar 11/7/2008 English 2837985280 FTP DD

Product Alias/Synonym

Oracle Agent

Problems (APARS) fixed
IY92195, IY99662, IZ04972, IZ05321, IZ06982, IZ07142, IZ07276, IZ11539, IZ13162, IZ16555, IZ17115, IZ18824, IZ19112, IZ19880, IZ20186, IZ21587, IZ22007, IZ23699, IZ24733, IZ25541, IZ29151, IZ29527

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Monitoring for Databases

Software version:

6.2

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

4021100

Modified date:

2009-04-06

Translate my page

Machine Translation

Content navigation