ITCAM Extended Agent for Oracle Database: 6.3.1.2-TIV-ITM_KRZ-IF0004

Copyright International Business Machines Corporation 2017.
All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager Extended
Agent for Oracle(R) Database Version 6.3.1 Fix pack 2

Component ID: 5724V09OR

Interim Fix: 0004, 6.3.1.2-TIV-ITM_KRZ-IF0004

Date: March 8, 2017

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 Copyright and trademark information
10.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: IV93882
Abstract: SDA support contains resources jar with expired certificate
Additional information: The help resources jar that is included in
the Self Describing Agent support files is not signed with a
current certificate. When launching the portal using the Java(R)
Web Start client, the message "Failed to validate certificate. 
The application will not  be executed" is received with details:
"java.security.cert.CertificateException: Found unsigned entry in 
resource: http://<your.itm.server>:15200/classes/krz_resources.jar"

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

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

2.4 Superseded fixes
-------------------------
6.3.1.2-TIV-ITM_KRZ-IF0003
6.3.1.2-TIV-ITM_KRZ-IF0002
6.3.1.2-TIV-ITM_KRZ-LA0001

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

6.3.1.2-TIV-ITM_KRZ-IF0003
-------------------------------

APAR: IV80814
Abstract: Oracle Database Extended Agent collector hangs at OCI
API OCIReset()
Additional information: The data collector hangs when calling the
OCI API function OCIReset() after calling the OCIBreak()
function in order to abort the query because of a time-out.
This can be seen in Oracle Enterprise Manager (OEM) where
"SQL*Net break/reset to client" shows as 100% of the activity
for a long time. Also, the Oracle agent event log displays:
"Error at appending request for handle is:
<attributeGroupName>, request id is: <requestID>, because
the number of current pending request exceeds the maximum queue
length: 50"

APAR: IV79151
Abstract: Oracle Database Extended Agent collector crashes when
sending an agent event after upgrade
Additional information: After upgrading the Oracle Database Extended
Agent to 6.3.1 Fix Pack 2 from a lower version, configuration
variables that were added in version 6.3.1 Fix Pack 2 are not
added to existing agent instances unless the agent instances are
re-configured. The agent's data collector will crash when
processing an agent event.

APAR: IV72473
Abstract: Agent fails to get all information for
SQLINFO ID="RDB_Recovery_File_Dest" attribute group
Additional information: The agent fails
to get data for the "RDB_Recovery_File_Dest" attribute group
for Oracle databases with Flashback recovery area disabled and
"db_recovery_file_dest_size=0". The agent returns the error
message: "ORA-01476: divisor is equal to zero."

APAR IV72024
Abstract: The agent fails to get all information for
"DG_MANAGED_STANDBY_STAT" and SQLINFO ID="DG_STATS" attribute
groups of RAC
Additional information: The agent fails to get information for
DataGuard attribute groups in an environment with DataGuard RAC
enabled. A symptom is that the following pre-defined situations
raise a false alert:
DG_Status_Crit
DG_Status_Warn
DG_Redo_Apply_Process_Crit

APAR: IV66538
Abstract: Extended Oracle Database Agent triggers false alert on
inactive instance status if Oracle RAC DB is started with PFILE
Additional information: If the monitoring Oracle RAC Database is
started using a PFILE, the "RDB_Active_Instance" attribute group
returns one record of "Instance Name is '*', and Status is
'INACTIVE'". This triggers a false alert of "Inactive Oracle
Instance Status".

Defect: 216240
Abstract: Refresh Java Certificates
Additional information: The previous release's Java certificates
expire on 04/16/2016. This patch includes updated Java
certificates which are valid until 11/1/2018.

6.3.1.2-TIV-ITM_KRZ-IF0002
-------------------------------

APAR: IV50803
Abstract: MAXSIZE OF TABLESPACE CALCULATE IS INCORRECT
Additional information: When an Oracle table space data file
'alloc_space' > 'max_size' and 'autoextensible' = 'YES', the
agent must use 'alloc_space' instead of 'max_size'. This problem
results in an incorrect value for the following attributes:
RDB TablespaceNormal Usage/Maximum file Size (KB)
RDB TablespaceNormal Usage/Maximum file Size (MB)
RDB TablespaceNormal Usage/% Free To Maximum

APAR: IV53354
Abstract: GETTING DIVISOR IS EQUAL TO ZERO ERROR FOR
RDB_SEGMENT_ALLOCATION ATTRIBUTE GROUP
Additional information: Sometimes, when a database is created,
a segment of type 'CACHE' is created. It is owned by 'SYS'
and is in the 'system' tablespace. It can be found by
querying 'DBA_SEGMENTS' or 'USER_SEGMENTS' with segment_type
'CACHE', it has one extent allocated but 'MAX_EXTENTS' = 0.
When the agent queries attribute group 'RDB_Segment_Allocation',
the following error occurs:
ORA-01476 divisor is equal to zero

APAR: IV55645
Abstract: '% FREE TO MAXSIZE' OF UNDO TABLESPACE CALCULATE IS
INCORRECT
Additional information: The following attribute is incorrect for
undo tablespace:
RDB TablespaceNormal Usage/% Free To Maximum

APAR: IV60530
Abstract: RZ AGENT V6.31 FP2 DATA COLLECTOR PROCESS MEMORY LEAK
Additional information: The collector process of the Oracle Database
Extended agent version 6.31 Fix pack 2 collector process has a
memory leak.

APAR: IV61410
Abstract: NO DATA IN 'NET SERVICE CONNECTION' WORKSPACE WITH
LANG=JA_JP
Additional information: The Oracle Database Extended agent uses
International Component for Unicode (ICU) regular expression
to parse listener.ora and tnsnames.ora.
With LANG=Ja_JP, the agent cannot parse these files correctly
even when these files include valid listener definition and
net service definition. The agent does not return data for
the following workspace and attribute groups:
Affected workspace:
Net Service Connection
Affected attribute groups:
Agent Listener
Agent Remote Connection

APAR: IV64051
Abstract: THE OPEN FILE HANDLES OF TNSPING INCREASE CAUSING FALSE
INACTIVE LISTERNER ALERT
Additional information: When the agent instance is configured with
Oracle Home, the open file handles of '$ORACLE_HOME/bin/tnsping'
increase for the agent collector process on Linux(R)/Unix(R). Then,
it reaches the 'max open file' limitation. This problem occurs in
Oracle Database Extended agent version 6.31 Fix pack2. The problem
causes false alerts of inactive listener and inactive net service
connection to occur. Also, it causes other issues, for example,
missing monitoring alert log.
You receive 'Too many open files' error messages from
the collector process log file.

Defect: 211289
Abstract: agent does not work with Oracle Instant Client 12c on
xLinux
Additional information: In Oracle Instant Client 12c on xLinux,
the agent fails to load the Oracle library 'clntsh' dynamically.

Defect: 211313
Abstract: Database_Information timeout and inactive db alert
Additional information: The agent uses the 'Database Information'
attribute group to determine whether the Oracle database
connection is active. If the query is timed out, the agent
reports a false alert of 'inactive' Oracle database connection.
With this change, the agent reports an 'unknown' Oracle database
connection to avoid a false alert.

Defect: 211695
Abstract: test connection shows a wrong message if a wrong password
is configured
Additional information: If a wrong password is configured in the
Extended Oracle agent 6.31 Fix pack 2, the test connection shows
the following wrong message:
If a database connection is created or configured for the first
time, run the following sql script in Oracle facilities to
make sure all required privileges are granted to the agent user.
...
With this change, the agent shows a correct message:
ORA-01017: invalid username/password; logon denied

Defect: 211925
Abstract: The DLA function does not work if an agent is started by
using a non-root account
Additional information: The agent fails to receive OracleInstance
information in IdML book when the agent is started by using a
non-root and non-oracle account.

2.6 Enhancements included from superseded fixes
----------------------------------------------------
6.3.1.2-TIV-ITM_KRZ-IF0002
-------------------------------
Enhancement: RFE 38948 - part 1/2
Link: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=38948
Abstract: New configuration item to keep the agent subnode online
Additional information: When the Oracle Database Extended agent
fails to connect to the Oracle database, by default, the
corresponding navigator subnode becomes offline. This behavior
is the correct agent default behavior. It triggers a managed
system offline alert when the subnode is offline.

From 6.3.1.2-TIV-ITM_KRZ-IF0002, New configuration item
'KRZ_SUBNODE_ONLINE' is provided (default value is 'FALSE').
When you configure the agent instance, by setting the
configuration item 'KRZ_SUBNODE_ONLINE' as 'TRUE', the navigator
subnode stays online even if the agent fails to connect to
the database.

Instructions to enable 'KRZ_SUBNODE_ONLINE':

a. Enable 'KRZ_SUBNODE_ONLINE' by using the Manage Tivoli
Monitoring Services tool:

Default Database Configuration panel:
[checked] Show advanced options ->
[checked] Always keep the navigator node online in the portal navigator tree.

b. Enable 'KRZ_SUBNODE_ONLINE' by using the command line:

Default Database Configuration section:
--------------------------------------------------------------
Always keep the navigator subnode online in the portal navigator tree
[ 1=True, 2=False ] (default is: 2): 1
--------------------------------------------------------------

c. The configuration option:

Key Name : advanced.KRZ_SUBNODE_ONLINE
Required : N
Restricted Values: "TRUE", "FALSE"
Description : When the agent fails to connect to the
Oracle database, the corresponding navigator
subnode becomes offline by default. By
configuring the configuration item as True,
the navigator subnode stays online even if
the agent fails to connect to the database.

Take configuresystem command as an example:
# bin/tacmd configuresystem -m <Managed_System_Name>
-p INSTANCE=<Instance_Name>
advanced.KRZ_SUBNODE_ONLINE=TRUE ...

Enhancement: RFE 38948 - part 2/2
Link: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=38948
Abstract: New configuration items for Data Guard
Additional information: When you use the Oracle Database Extended
agent to monitor Oracle Data Guard, the agent creates two
subnodes: One primary node (:RDB) and one standby node (:DG).
Depending on which connection is inactive, one of these two
subnode agents is always offline. As a result, a managed system
offline alert triggers.

From 6.3.1.2-TIV-ITM_KRZ-IF0002, New configuration items
(KRZ_DG_GROUP and KRZ_DG_ROLE) for Data Guard are provided.
They are required only if the database connection is part of
Data Guard environment, and you do not want the agent to create
a new navigator subnode after the database switchover or failover.

Instructions to do Data Guard configuration:

The primary database and standby database in the Data Guard
is one group, they must be configured in a single agent instance
with same KRZ_DG_GROUP value and different KRZ_DG_ROLE.

The agent generates only two subnodes for the two database
connections in one Data Guard group (KRZ_DG_GROUP):

One RDB navigator subnode with name:
Oracle RDBMS-RZ:<PrimaryDBConnectionName>-<AgentInstance>-<Hostname>:RDB
Note: <PrimaryDBConnectionName> refers to the agent Database
Connection name that is configured with KRZ_DG_ROLE=PRIMARY.
The navigator subnode always represents the real primary database
connection in the KRZ_DG_GROUP even after the database switchover
or failover.

One DG navigator subnode with name:
Oracle Data Guard-RZ:<StandbyDBConnectionName>-<AgentInstance>-<Hostname>:DG
Note: <StandbyDBConnectionName> refers to the agent Database
Connection name that is configured with KRZ_DG_ROLE=STANDBY.
The navigator subnode always represents the real standby database
connection in the KRZ_DG_GROUP even after the database switchover
or failover.

As described above, the agent switches database connection
configuration in one KRZ_DG_GROUP after the database switchover
or failover. As a result, it maybe displays the other database
connection configured in one KRZ_DG_GROUP as a result of database
switchover or failover.

a. Data Guard configuration by using the Manage Tivoli Monitoring
Services tool:

Instance Configuration panel:
[checked] Show Data Guard options
-> Input Data Guard Group Name
-> [checked] Primary or Standby radio button.

b. Data Guard configuration by using the command line:

'Database Connection' settings:
Show Data Guard Configuration Options? [ 1=Yes, 2=No ] (default is: 2): 1
Input Data Guard Group Name
Data Guard Configuration: [ 1=Primary, 2=Standby ] (default is: 1):

c. The configuration option:

Key Name : config.KRZ_DG_GROUP
Required : N
Restricted Values:
Description : A Data Guard group contains one primary
database that functions in the primary role
and one standby database that is a copy of
the primary database. Define same Data
Guard Group name for the Primary database
connection and the Standby database
connection to identify they are related.
Only letters, Arabic numerals, the underline
character, and the minus character can be
used.

Key Name : config.KRZ_DG_ROLE
Required : N
Restricted Values: "Primary", "Standby"
Description : A Data Guard group must contain one Primary
database and one Standby database, and they
must be configured in the same agent instance.

For example:

# bin/tacmd configuresystem -m <Managed_System_Name>
-p INSTANCE=<Instance_Name>
advanced.KRZ_SUBNODE_ONLINE=TRUE
config:primdb1.KRZ_DG_GROUP=dggrp1
config:primdb1.KRZ_DG_ROLE=Primary
config:stddb1.KRZ_DG_GROUP=dggrp1
config:stddb1.KRZ_DG_ROLE=Standby
config:primdb2.KRZ_DG_GROUP=dggrp2
config:primdb2.KRZ_DG_ROLE=Primary
config:stddb2.KRZ_DG_GROUP=dggrp2
config:stddb2.KRZ_DG_ROLE=Standby
...

3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Composite Application Manager Extended Agent for Oracle
Database User's Guide, version 6.3.1 Fix pack 2.

Please refer to the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Composite Application Manager Extended Agent for
Oracle Database v6.3.1 Fix Pack 2
http://www-01.ibm.com/support/docview.wss?uid=swg24035571


4.0 Image directory contents
===================
This fix image contains the following files:
- 6.3.1.2-TIV-ITM_KRZ-IF0004.README - This README file
- 6.3.1.2-TIV-ITM_KRZ-IF0004.tar - Fix archive .tar format
- 6.3.1.2-TIV-ITM_KRZ-IF0004.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(R) environment.

The fix archive file contains the following files:
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzaix523.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzaix526.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzhpi116.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzli6263.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzlia266.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzlpp266.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzls3243.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzls3246.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzlx8266.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzsol283.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzsol286.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzsol606.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzWINNT.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krzWIX64.dsc
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_aix523_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_aix526_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_hpi116_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_li6263_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_lia266_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_lpp266_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_ls3243_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_ls3246_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_lx8266_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_sol283_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_sol286_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_sol606_tema_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_tems_teps_tepd_if0004.tar
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_tems_teps_tepd_if0004.zip
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_winnt_tema_if0004.cab
- 6.3.1.2-TIV-ITM_KRZ-IF0004/krz_wix64_tema_if0004.cab
- 6.3.1.2-TIV-ITM_KRZ-IF0004/rz_dd.properties
- 6.3.1.2-TIV-ITM_KRZ-IF0004/rz_dd_063102004.xml
- 6.3.1.2-TIV-ITM_KRZ-IF0004/itmpatch.exe

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 environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

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

- Refer to section 7.0 entitled "Known problems and workarounds" before
installation.

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

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

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the "itmpatch" command to install the fix for the operating
system of that agent. For more information on the "itmpatch"
command, see section [6.2].

On UNIX systems, if the fix was expanded to <TEMP>/6.3.1.2-TIV-ITM_KRZ-IF0004,
the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.3.1.2-TIV-ITM_KRZ-IF0004/krz_xxxxxx_tema_if0004.tar

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

In the following example, the file is "krz_aix526_tema_if0004.tar".
> ./cinfo -i
rz Monitoring Agent for Oracle Database Extended
aix526 Version: 06.31.02.04

On Windows system, if the fix was expanded to
<TEMP>\6.3.1.2-TIV-ITM_KRZ-IF0004, the install command is:

> <TEMP>\6.3.1.2-TIV-ITM_KRZ-IF0004\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.2-TIV-ITM_KRZ-IF0004\krz_xxxxxx_tema_if0004.cab

4. Fix 6.3.1.2-TIV-ITM_KRZ-IF0002 included changes to the required
user privileges. In comparison to Oracle Database Extended agent
version 6.3.1 Fix pack 2, a new priviledge is needed:
grant select on DBA_LIBRARIES to <userName>
If you have already granted these user priviledges, there are no
additional installation steps.

In version 6.3.1 Fix Pack 2, if you grant privileges to Oracle
users, you can grant Oracle users the DBA_LIBRARIES new privilege
manually or run the following "krzgrant.sql" procedure:

To grant privileges to the user, after you apply the fix
6.3.1.2-TIV-ITM_KRZ-IF0004, run the "krzgrant.sql" script.
See the 'Granting privileges to users for RDBMS instances' section
(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.2.1/oracleextended/fac_config_agentspecific_grantprivileges.html)
in the IBM Tivoli Composite Application Manager Extended Agent
for Oracle Database Installation and Configuration Guide.

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.3.1.2-TIV-ITM_KRZ-IF0004.tar
or .zip) to a temporary directory on the 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 systems, this path includes the
drive letter.

2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. To add the agent fix 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 the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/6.3.1.2-TIV-ITM_KRZ-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.2-TIV-ITM_KRZ-IF0004

On Windows systems,
if the fix was expanded to <TEMP>\6.3.1.2-TIV-ITM_KRZ-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.1.2-TIV-ITM_KRZ-IF0004

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please 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. 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 "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems:
> $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 rz
-n <Managed system name>
-v 063102004

On Windows systems:
> %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 RZ
-n <Managed system name>
-v 063102004

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (rz), not three characters (krz).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.

5. Fix 6.3.1.2-TIV-ITM_KRZ-IF0002 included changes to the required user
privileges. In comparison to the Oracle Database Extended agent
version 6.3.1 Fix pack 2, a new privilege is needed:
grant select on DBA_LIBRARIES to <userName>
If you have already granted these user priviledges, there are no
additional installation steps.

In version 6.3.1 Fix Pack 2, if you grant privileges to Oracle users,
you can grant Oracle users a new DBA_LIBRARIES prvilege manually,
or run the following "krzgrant.sql" procedure:

To grant privileges to the user, after you apply the fix
6.3.1.2-TIV-ITM_KRZ-IF0004, run the "krzgrant.sql" script.
See the 'Granting privileges to users for RDBMS instances' section
(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.2.1/oracleextended/fac_config_agentspecific_grantprivileges.html)
in the IBM Tivoli Composite Application Manager Extended Agent
for Oracle Database Installation and Configuration Guide.

5.4 Agent support update
------------------------------
This fix (6.3.1.2-TIV-ITM_KRZ-IF0004) includes changes to the agent
support files which need to be installed. [If you have already
installed these updates, there are no additional installation
steps. Otherwise,] 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.3.1.2-TIV-ITM_KRZ-IF0004.tar
or .zip) to the Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal
Desktops.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

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

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

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

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Using the silent installation option for Linux and
zLinux operating systems requires the following files contained
in Interim Fix 6.2-TIV-ITM_ASI-IF0002
(http://www-01.ibm.com/support/docview.wss?uid=swg24034924):
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0002.README".

On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt".

-j <JAVAHOME> - Optional. The fully-qualified path to the "bin"
directory where Java is installed. The
location of Java on your system might vary.

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For this fix, check or clear the
check boxes as follows:

[checked | unchecked] - Tivoli Enterprise Monitoring Server (TEMS)
[checked | unchecked] - Tivoli Enterprise Portal Server (TEPS)
[checked | unchecked] - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the IBM
Tivoli Composite Application Manager Extended Agent for Oracle Database
06.31.02.04 support to complete the installation.

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


6.0 Additional installation information
========================
6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using "itmpatch" command
--------------------------------------------------------------
The "itmpatch" command has the following syntax:

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

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

itmpatch -h <installation home>
-i { <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 UNIX systems:
- 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 systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, this must include the drive
letter.

6.3 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, 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 RZ

On Windows systems, 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 RZ

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

When the agent update is successful, the agent version is:
06.31.02.04

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.

For the agent on Windows systems, the version number is
06.31.02.04.
For the agent on UNIX systems, the version number is
06.31.02.04.

2. To verify the agent support files were updated correctly, use the
"kincinfo" command on Windows systems or the "cinfo" command on
Linux or UNIX systems. The sample output below shows the versions
of the Tivoli Enterprise Portal Server, Tivoli Enterprise
Monitoring Server, or Tivoli Enterprise Portal Desktop systems
after this fix has been successfully applied.

Note: The displayed date of the build might not be accurate. This
is a known problem.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Fri Jan 6 13:46:18 CDT 2017 *******************
User: root Groups: root bin daemon sys adm disk wheel
Host name : myaixsys Installer Lvl:06.23.01.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
Tivoli Enterprise Monitoring Server update:

rz Monitoring Agent for Oracle Database Extended
tms Version: 06.31.02.04

Tivoli Enterprise Portal Server update:

rz Monitoring Agent for Oracle Database Extended
tps Version: 06.31.02.04

Tivoli Enterprise Portal Desktop update:

rz Monitoring Agent for Oracle Database Extended
tpd Version: 06.31.02.04

Monitoring Agent for Oracle Extended update:

rz Monitoring Agent for Oracle Database Extended
aix526 Version: 06.31.02.04

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

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

********* Friday, Janurary 6, 2017 2:32:06 PM ***************
User : Administrator Group : NA
Host Name : TIVX34 Installer : Ver: 062300000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
.
.
.

Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server
and Tivoli Enterprise Portal Desktop update:

RZ TEMS App Support/Monitoring Agent for Oracle Database Extended
WINNT Version: 06.31.02.04 Build:

RZ TEPS App Support/Monitoring Agent for Oracle Database Extended
WINNT Version: 06.31.02.04 Build:

RZ TEPD App Support/Monitoring Agent for Oracle Database Extended
WINNT Version: 06.31.02.04 Build:

Monitoring Agent for Oracle Database Extended update:

RZ Monitoring Agent for Oracle Database Extended
WINNT Version: 06.31.02.04 Build:

Note:

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

7.0 Known problems and workarounds
=========================

- Problem: Fails to apply 32-bit agent patch on 64-bit Windows.
Command:
<CANDLEHOME>\itmpatch.exe -h <CANDLEHOME> -i <patch_file_directory>\<patch_file>
Error message: The patch file cannot be installed.
Either the current platform architecture or the installed
components do not meet the prerequisites of the patch.

Workaround: Use the itmpatch.exe provided in the patch.
<patch_file_directory>\itmpatch.exe -h <CANDLEHOME> -i <patch_file_directory>\<patch_file>

- Problem: 6.3.1.2-TIV-ITM_KRZ-IF0004 includes new configuration
items. After upgrading the agent support file to 06.31.02.04,
click 'Add Managed System' from portal or brower, no matter
what you select in the 'Select a Monitoring Agent' panel -
version 06.31.02000 or 06.31.02000, the 'New Managed System
Configuration' panel always shows new configuration items in
6.3.1.2-TIV-ITM_KRZ-IF0004.

As a result, GUI remote deployment fails on a freshly installed
system with the following error message:
KDY0015E The property advanced.KRZ_SUBNODE_ONLINE is incorrect for version 063102000 of the rz agent

Workaround:
Use 'tacmd addSystem' command to deploy the Oracle Database
Extended agent 'base' version 6.31 Fix pack 2.

- Problem: After adding the agent bundles version 063102004 in depot,
remote deployment with the 'tacmd addSystem' command fails on a
freshly installed system with the following error messages:

KDY1008E The agent action INSTALL failed with a return code of for produce code rz.
The commmand $CANDLEHOME/tmaitm6/<arch>/bin/kdy_xa -setCMS rz produced the following error text:{4}

It is because that 'tacmd addSystem' command selects the highest
version of the agent bundle - version 063102004 from the depot
by default, but the interim fix version of the agent does not
contain the necessary binary files needed in order to perform
a new installation of the agent.

Workaround:
Use 'tacmd removeBundles' command to remove the agent bundle
version 063102004 from the depot, and then remotely deploy the
'base' version agent.

Or use bulk deployment option, and specify 'base' version of
agent bundle - version 063102000.

- Problem: Unable to remotely deploy a new agent instance to a
freshly installed system, if 'base' version agent bundle
does not exist in depot.

Workaround: To deploy the 'base' version agent remotely before
applying this patch remotely, add the 'base' version -
6.3.1 Fix pack 2 version platform bundles to depot.

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

9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.


10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

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

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

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.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates.

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

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.

 

Created/Revised by	Date of Creation/Update	Summary of Changes
MAA	2017/03/10	Document created
MAA	2017/10/19	Superseded by 6.3.1.2-TIV-ITM_KRZ-IF0005