Copyright International Business Machines Corporation 2011. 
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Databases: Oracle Agent,
           Version 6.1.0

Component ID: 5724B96OO

Interim Fix 0014, 6.1.0.1-TIV-ITM_ORA-IF0014
        
Date: May 18, 2011

Contents:

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


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


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

  2.1 APARs 
  -------------
  APAR    :  IZ97870
  Abstract:  MEMORY LEAK OF KORCOLL
  Additional Information: The korcoll process has memory leak when 
    there are many "Open Probe pipe errno" error messages.

  2.2 Defects 
  --------------
  None.
  
  2.3 Enhancements
  -----------------
  None.

  2.4 Superseded fixes 
  -------------------------
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  IF0013 - (6.1.0.1-TIV-ITM_ORA-IF0013)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  IF0012 - (6.1.0.1-TIV-ITM_ORA-IF0012)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  IF0011 - (6.1.0.1-TIV-ITM_ORA-IF0011) 
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0010 - (6.1.0.1-TIV-ITM_ORA-LA0010)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0009 - (6.1.0.1-TIV-ITM_ORA-LA0009)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0008 - (6.1.0.1-TIV-ITM_ORA-LA0008)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0007 - (6.1.0.1-TIV-ITM_ORA-LA0007)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0005 - (6.1.0.1-TIV-ITM_ORA-LA0005)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0004 - (6.1.0.1-TIV-ITM_ORA-LA0004)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0003 - (6.1.0.1-TIV-ITM_ORA-LA0003)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  LA0002 - (6.1.0.1-TIV-ITM_ORA-LA0002)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  IF0001 - (6.1.0.1-TIV-ITM_ORA-IF0001)
  IBM Tivoli Monitoring for Databases, Version 6.1.0: Oracle Agent
  FP0001 - (6.1.0-TIV-ITM_DB-FP0001)
  
  2.5 APARs and defects included from superseded fixes
  ---------------------------------------------------------------
 
    6.1.0.1-TIV-ITM_ORA-IF0013
    ---------------------------
    APAR    :  IZ67453
    Abstract:  AGENT CANNOT MONITOR OVER 128 LISTENERS
    Additional Information: The Oracle agent cannot read more then 128 listener
         definitions from the listener.ora file, and cannot read more then
         500 lines of listener definitions from the listener.ora file.
         The maximum listener definition has been extended from 128 to 
         2048 and the maximum line number has been extended from 500 
         to 10,000.
         
         If the agent takes more than default 45 seconds to get all 
         listeners' status, extend WAIT_TIMEOUT and COLL_WAIT_TIMEOUT
         as the following steps:
         On Unix systems, append two lines in the agent instance 
         configuration file:
         export WAIT_TIMEOUT="300"
         export COLL_WAIT_TIMEOUT="300"
         On Windows system, open Manage Tivoli Enterprise Monitoring 
         Services. Right click the agent instance, select Advanced, and
         select Edit Variables. Click Add button on the poped window, 
         add Variable: WAIT_TIMEOUT and COLL_WAIT_TIMEOUT with value 300.
         Restart the agent.
         
    APAR    :  IZ74822
    Abstract:  SERVER_CPU_PCT CALCULATE WORNG 
    Additional Information: The Oracle agent returns wrong value 
         in the Server\CPU\Percent column in the Server Summary 
         workspace for the UNIX or Linux operating systems.
  
    APAR    :  IZ75900
    Abstract:  AGENT GENERATES CORE DURING STOP IN HP-UX 11.31 IA64
    Additional Information: The Oracle agent generates a core file 
         each time the agent stops on HP-UX 11.31 IA64 systems.
  
    APAR    :  IZ80502
    Abstract:  AGENT LOG ERROR MESSAGE 'WRITE PIPE ERROR 22'
    Additional Information: 
        On HP-UX Itanium 64-bit platforms, the agent cannot get a value 
        of WAIT_TIMEOUT correctly. The error message "Write Pipe error 22" 
        can be found in the koragent log files.
        For example,
        4C2C907D.0002-5:kor19agt.cpp,153,"TakeSample") Entered KORLISTD
        TakeSample. (kddsampl)
        (4C2C907D.0003-5:kor19agt.cpp,462,"TakeSample") Write Pipe error
         22. 
        Pipe=/db2/liuc/610/tmp/tivhpi04_or_orcl2/col_orcl2_kor_pipe.(kdd
        sampl)

    APAR    :  IZ92790
    Abstract:  ORACLE SERVER STATUS INACTIVE SITUATION DOES NOT FIRE
    Additional Information: 
        The Oracle Server Status Inactive situation does not fire. This 
        problem occurs when the agent uses default opened pipe method to 
        communicate with the collector on Linux/Unix systems. If user
        set WAIT_TIMEOUT as multiple 60 seconds, this problem has much more
        oppotunities to occur. 
    
    Defect: 96965
    Abstract: Enable WAIT_TIMEOUT when collector uses shared memory
    Additional Information: The agent cannot get a value of WAIT_TIMEOUT when 
        the collector uses shared memory to communicate with the agent.
  
    Defect: 136143
    Abstract: QUERY ON V$DBFILE CAUSES ORACLE SERVER PROCESS HIGH CPU
    Additional Information: The query on v$dbfile causes high CPU 
    for the Oracle server process in the KORHART4 cursor.
        
    6.1.0.1-TIV-ITM_ORA-IF0012
    ---------------------------
    APAR: IZ48362
    Abstract: ITM ORACLE AGENT UNABLE TO RETURN DATA IF PARAMETER 
        WAIT_TIMEOUT/COLL_WAITTIMEOUT WAS SPECIFIED ON HP-UX ITANIUM
        64 PLATFORM.   
    Additional Information: On HP-UX Itanium 64-bit platforms, if the 
        WAIT_TIMEOUT or COLL_WAITTIMEOUT parameter is specified in the
        agent instance configuration file, no data is displayed
        on the IBM Tivoli Enterprise Portal view. The error 
        message "Write Pipe error 22" can be found in the koragent log
        files.
    
    Defect: 95753
    Abstract: Enable customization of the severity level of Oracle 
          message ID
    Additional Information: The data displayed in the IBM Tivoli 
             Enterprise Portal "Alert Log" view does not correspond to
             the customization of the severity level of the Oracle 
             message ID, which is saved in the file 
             $CANDLEHOME/misc/regExp<orcl>.properties on UNIX systems,
             or %CANDLE_HOME%\TMAITM6\regExp<orcl>.properties on 
             Windows systems.
    
    6.1.0.1-TIV-ITM_ORA-IF0011
    ---------------------------
    APAR: IZ40669
    Abstract: AGENT CAN NOT START AFTER APPLYING 
          6.1.0.1-TIV-ITM_ORA_LA0009 ON ZLINUX SUSE 9 
    Additional Information: After appling 6.1.0.1-TIV-ITM_ORA-LA0009 
          or 6.1.0.1-TIV-ITM_ORA-LA0010, the following error occurs
          when starting the agent:
          "/opt/IBM/ITM/ls3246/bin/kddexec.sh: [-2146988960]:             
          /opt/IBM/ITM/tmp/pdlnx15d0001dl_or_DCENTR05/kddsignl: 
          not found".
                  
    Defect: 93604
    Abstract: The agent fails to find the alert_<sid>.log file
    Additional Information: If the Oracle parameter BACKGROUND_DUMP_DEST
               is set to a directory outside of $ORACLE_HOME, the agent
               does not find the alert_<sid>.log file and, therefore does
               not report messages written to that log file.
 
    6.1.0.1-TIV-ITM_ORA-LA0010
    ---------------------------
    APAR: IZ31728
    Abstract: ITM FOR DB 6.2 ORACLE AGENT GOES DOWN BY CTRL+C ON 
          SOLARIS.
    Additional Information: The Oracle agent is 
          terminated when Ctrl+C is entered in the session in which the
          agent was started on Solaris.
    
    APAR: IZ32259
    Abstract: KDDSIGNL COREDUMPS ON LINUX
    Additional Information: Stopping the Oracle agent 
          results in a core dump error of kddsignl on Linux systems.
    
    APAR: IZ34666
    Abstract: 6.1 ORACLE AGENT SERVER SUMMARY WORKSPACE SHOWS 0 AND 
          BLANKS.
    Additional Information: The Server Summary Workspace shows 
          inaccurate values for all archive-related attributes, which 
          includes Archive Dest Pct Full, Percent Archive Free Space, 
          Archive Free Space(kb), Archie Used Space(kb).
 
    6.1.0.1-TIV-ITM_ORA-LA0009
    ---------------------------
    APAR: IZ23699
    Abstract: SQL IN KORLCK05 CURSOR NEEDS TO BE MODIFIED FOR 10G
    Additional Information: When running the Oracle agent 
          against Oracle 10g, the following message is written 
          to the file {hostname}_or_{instancename}_col.log: 
          "CMA3530E (131512) Math statement PLKHIT for cursor KORLOCKS
          references KORLCK05 which has no rows, setting answer to 0".

    APAR: IZ25541
    Abstract: korcoll.exe intermittent crash in UTF8 conversion 
    Additional Information: This problem is intermittent. The
          collector log ({hostname}_or_{instancename}_col.out) shows a
          UTF8 conversion failure and sometimes the collector fails to
          start. This problem occurs on Microsoft Windows(R) with any 
          Oracle version.

    APAR: IZ25849
    Abstract: TACMD STOPAGENT -T OR -FAILS KDDEXEC: CAN'T CONTINUE
          W/STOP
    Additional Information: 'tacmd stopAgent -t or' fails with the 
          error 'kddexec: Can't continue with the stop'.

    APAR: IZ27931
    Abstract: KOR_PATCHDEPOT.* IN 6.1.0.1-TIV-ITM_ORA-LA0008 IS WRONG.
    Additional Information: During the install of 
          6.1.0.1-TIV-ITM_ORA-LA0008, when running either the 
          kor_patchdepot.bat on Windows or kor_patchdepot.sh on 
          UNIX(R), the script fails with the message:
          "or_dd_061001004.xml was not found. 
          You must run kor_patchdepot.bat from the 
          extracted 6.1.0.1-TIV-ITM_ORA-LA0004 directory...
          kor_patchdepot.bat exiting... "

    APAR: IZ29151
    Abstract: REDOLOGS NOT ARCHIVED COLUMN IS WRONG
    Additional Information: If the database is in NOARCHIVELOG mode, the 
         'Redo Logs Not Archived' attribute should have a value of zero.
          However, the attribute does not always return a value of zero.

    APAR: IZ29527
    Abstract: KORERR COREDUMPS ON ZLINUX
    Additional Information: The problem only occurs on a zLinux 
          operating system. 
 
    6.1.0.1-TIV-ITM_ORA-LA0008
    ---------------------------
    APAR: IZ16555 
    Abstract: ITM 6.1FP6-ORACLE AGENT CORE DUMPS ON ALERT LOG FILES
    Additional Information: The Oracle agent core dumps on 
          alert log files when the Oracle message is more than the
          expected length.
		
    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 FOR SITUATION 
          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.
   
    6.1.0.1-TIV-ITM_ORA-LA0007
    --------------------------
    APAR: IZ11539 
    Abstract: KDDOS.EXE ERROR HAPPENS ON LARGE DB ENV ON WINDOWS
    Additional Information: This problem occurs when you are
          logging in to a server where numerous database agents are 
          running. During logon, numerous windows are displayed that  
          require acknowledgement. 		 
		
    APAR: IZ17115
    Abstract: ORACLE AGENT (KORCOLL) USES >10% OF THE CPU
    Additional Information: The performance tools shows 10% utilization
		       on an AIX system though the performance report 
		       indicates that the Oracle agent 
		       uses only about 0.2% of the CPU. 
    
    APAR: IZ13162
    Abstract: ORACLE AGENT COREDUMPS WITH THE INCOMPLETE ORA-02 MESSAGE.
    Additional Information: The Oracle agent dumps core
		       when the database workspace navigator item and 
		       database workspace "alert log" are clicked.

    APAR: IZ13922 
    Abstract: FREE SPACE DEFICIT SHOWS NEGATIVE VALUES.
    
    APAR: IZ17118 
    Abstract: FAIL TO DO RE-SEEDING AFTER UPDATING THE AGENT SUPPORT 
		       FROM LA05/LA06.
  
    APAR: IZ17400
    Abstract: kddos.exe is crashing every 5 mins after LA05/LA06.
    Additional Information: kddos.exe is stopping when  
          'USE_DB_RECOVERY_FILE_DEST' is used as the ARCHDEST value.
    
    6.1.0.1-TIV-ITM_ORA-LA0005
    --------------------------  
    APAR: IZ06412
    Abstract: THE "SESSION HIT PERCENT" ATTRIBUTE IN "SESSIONS"  
          WORKSPACE SHOWS NEGATIVE VALUE
    Additional Information: None.
       
    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 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, step 7 and 8 for more information.
         
    APAR: IZ07142
    Abstract: ORACLE AGENT ON SOLARIS FAILED TO START 'COLLECTOR'
    Additional Information: This error message is in the collector
          log ld.so.1: ko9coll: fatal: libclntsh.so.9.0: open failed: 
          No such file or directory                                               
                                                               
    APAR: IZ08736
    Abstract: ARCHIVE DESTINATION FULL SITUATION IS FIRED INCORRECTLY
    Additional Information: 'korgrant.sql' or 'korgrantcustom.sql' must
          be run after installing this patch.  See section 5.2, step 5
          for more information.   

    6.1.0.1-TIV-ITM_ORA-LA0004
    --------------------------         
    APAR: IY92195
    Abstract: ORACLE AGENT PROCESS USES A HUGE AMOUNT OF MEMORY
    Additional Information: See Section 2.3 Enhancements before applying
          this fix.

    APAR: IY95785
    Abstract: DUPLICATE ALERTS BEING SENT FOR ORACLE_SERVER_ACTIVE 
          SITUATION 
    Additional Information: See Section 2.3 Enhancements 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 Oracle agent, 
          you must wait at least 30 seconds before restarting
          the agent to make sure all the agent processes have stopped
          normally.

    6.1.0.1-TIV-ITM_ORA-LA0003
    -------------------------- 
    APAR: IZ02447
    Abstract: physical_reads and physical_writes of ITM 6.1 Oracle 
          Agent have negative value in first hour of the day.

    APAR: IZ03033
    Abstract: ORACLE_ARCH_ACTIVE_WARNING tripping incorrectly.
    
    APAR: IZ03849
    Abstract: Verification steps error in 'itmcmd config -A or'
    Additional Information :
          When you select "Verification Steps" in the itmcmd config
          module on Linux AMD64/Linux ppc, you get a "cannot open
          file ..." error.
          
          For example,
          OMA for or installed                                                      
          kddos:  permissions OK for user oracle                                    
          Servers configured for TESTBOX:                                          
          TEST:  config status is CONFIGSUCCESS                                
          TEST:  starting koragent for CMS seed test                           
          TEST:  Database server is up                                         
          /opt/test/itm/lx8266/bin/kddivp.sh: =/oracle/product/10.
          2.0/lib32:/oracle/product/10.2.0/lib:/oracle/product/10.
          2.0/lib64:$: not found                                                       
          awk: cmd. line:6: fatal: cannot open file `TESTBOX_or_
          TEST_col.out' for reading (there are no file or directory.)                             
          TEST:  connection failed                                             
          TEST:  OMA for or will not work                                      
          
          This problem only happens on Linux AMD64 and Linux ppc.

    APAR: IZ03914
    Abstract: SOME TABLE VIEWS FOR ORACLE AGENT ARE NOT SHOWN IN JAPANESE    
          LANGUAGE ON IBM Tivoli Enterprise Portal DESKTOP AFTER ITMFDB
          6.1 FP01.

    APAR: IZ04293
    Abstract:  Collector failed to run with "Wrong ELF class: ELFCLASS32"
          error when using 64bit ITM 6.1 Oracle Agent with 64bit 
          OS and Oracle.
    Additional Information : This error message is in the collector
          log:
          ld.so.1: korcoll: fatal: $ORACLE_HOME/lib32/libclntsh.so.10.1:
	  wrong ELF class: ELFCLASS32

    Defect: 58834
    Abstract: 0 byte *dd* log files in CANDLEHOME/logs.

    Defect: 60233
    Abstract: Assign new Jar certificate.

    6.1.0.1-TIV-ITM_ORA-LA0002
    -------------------------- 
    APAR: IZ01194
    Abstract: An unexpected process was stopped when stopping the Oracle 
          agent.

    APAR: IZ03843
    Abstract: AE APAR against the problem in IY98181 fix - 'go' process 
          crashed on Solaris 9 and 10. 

    6.1.0.1-TIV-ITM_ORA-IF0001
    -------------------------- 
    APAR: IY97023
    Abstract: The user & password for Oracle are stored unencrypted in
          the file korproc.ctl

    APAR: IY97419
    Abstract: Password not masked when configuring DB 
    Additional Information: 
	         "CandleDBConfig or" or "itmcmd config -A or" shows the 
           password on the screen in clear text as it is typed in.

    APAR: IY97648
    Abstract: "total extents allocated" attribute incorrectly named 
         "total extents not allocated"

    APAR: IY98181
    Abstract: Oracle Agent Start/Stop corrupting who command on all 
          UNIX/Linux platforms.        

    APAR: IY99098
    Abstract: ITM6.1-Trace from ko*coll and ko*sql causes log files to
          continually grow with some situations implemented 
                   
    Defect: 49662
    Abstract: NavTree-Configure for Oracle requires TNS_ADMIN parameter.
    Additional Information: 
	       After upgrading to 6.1.0-TIV-ITM_DB-FP0001, selecting 
	       "Configure on Linux" from the Navigator tree, and selecting "OK"
               to save, results in the following error: 'A value must be given
               for TNS_ADMIN'.

    6.1.0-TIV-ITM_DB-FP0001
    ------------------------ 
    APAR: IY96212  
    Abstract: Customer can't display Oracle Alert.log in TEPS client on
          a Japanese Windows system. 
    Additional Information:
          The fopen command was using the UTF8 alert log file name
          instead of the local code page value. 
                         	   
    APAR: IY93698  
    Abstract: KO9COLL cores when an unexpected value comes back from
          UPARMVALUE.
    Additional Information:
          There was a 'UTF-8 Conversion failed' error in the
          collector log. ORU0210W (151538)
          UTF-8 conversion failed for column: <UPARMVALUE>

    APAR: IY89919  
    Abstract: When 40 Monitoring instances of Oracle on an AIX system
          the 'popen()' function call to 'korlog' or 'korerr' didn't 
          work consistently. 
    
    APAR: IY85214  
    Abstract: Message Text Truncated in Alert Log detailed view.
    Additional Information:
          The first 10 characters are deleted because they contain
          the message ID. This text is acceptable for messages like:                            
          ORA-12012: error on auto execute of job 61. 
          In the IBM Tivoli Enterprise Portal view, the message is
          displayed as: 
            error on auto execute of job 61.

          However, this message is incorrect for messages of the following
          format:             
          ORA-1031: signalled during: 
          ALTER TABLESPACE TS_INVAINDX_06 ADD DATAFILE '/u06                                                         
                                                                                  
          In the IBM Tivoli Enterprise Portal view, you see the 
          following truncated message:
          signalled during:
          ALTER TABLESPACE TS_INVAINDX_06 ADD DATAFILE '/u06

    Defect: 40414
    Abstract: After installing the IBM Tivoli Monitoring V6.1: Oracle Agent
            on zSeries(s390) running RHEL4, the korcoll binary is not
            present so the collector cannot be started.


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM 
Tivoli Monitoring for Oracle Database: Oracle Agent User's Guide, 
version 6.1.0.

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
  --------------------------------
  The prerequisite level for this fix is as follows:
  - IBM Tivoli Monitoring 6.1.0 Fixpack 5 or higher 
    (6.1.0-TIV-ITM-FP0005)
  - IBM Tivoli Monitoring for Databases, Version 6.1.0: 
    Database Agent Fix Pack 0001 
    (6.1.0-TIV-ITM_DB-FP0001).
  Because this fix is cumulative, it can be installed on any fix level for
  this version, release, and modification level above the prerequisite. 

4.0 Image directory contents
===================
This fix image contains the following files:
- 6.1.0.1-TIV-ITM_ORA-IF0014.README - This README file
- 6.1.0.1-TIV-ITM_ORA-IF0014.tar - Fix archive .tar format
- 6.1.0.1-TIV-ITM_ORA-IF0014.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(R) environment; use the .zip file if 
you are working in a Windows(R) environment. 

The fix archive file contains the following files:
- 6.1.0.1-TIV-ITM_ORA-IF0014/inst_prereq_patch.sh
- 6.1.0.1-TIV-ITM_ORA-IF0014/inst_prereq_itmpatch.exe.bat
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_patchdepot.sh
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_patchdepot.bat
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_aix513_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_hp11_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_hp116_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_hpi116_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_li6243_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_lia266_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_ls3243_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_ls3246_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_lpp266_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_lx8266_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_sol283_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_sol286_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_sol606_tema_if0018.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_aix513_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_hp11_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_hp116_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_hpi116_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_li6243_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_lia266_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_lpp266_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_ls3243_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_ls3246_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_lx8266_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_sol283_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_sol286_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_sol606_tema_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_tems_teps_tepd_if0014.tar
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_tems_teps_tepd_if0014.zip
- 6.1.0.1-TIV-ITM_ORA-IF0014/kor_winnt_tema_if0014.cab
- 6.1.0.1-TIV-ITM_ORA-IF0014/kdd_winnt_tema_if0018.cab
- 6.1.0.1-TIV-ITM_ORA-IF0014/KORWINNT.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/koraix513.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korhp11.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korhp116.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korhpi116.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korsol283.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korsol286.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korsol606.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korli6243.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korlia266.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korlpp266.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korls3243.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korls3246.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/korlx8266.dsc
- 6.1.0.1-TIV-ITM_ORA-IF0014/or_dd.properties
- 6.1.0.1-TIV-ITM_ORA-IF0014/or_dd_061001014.xml.

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

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

  5.1 Before installing the fix 
  -------------------------------
  - The prerequisites listed under section 3.1 entitled 'Prerequisites
    for this fix' must be installed before this fix can be installed.
    
  - For the purpose of this README, the <CANDLEHOME> symbol is the 
    IBM Tivoli Monitoring installation directory. The default value
    for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
    on Windows systems.

    Before installing this fix on UNIX systems, set the CANDLEHOME  
    environment variable to the IBM Tivoli Monitoring installation 
    directory.
        
    For example: 
    > CANDLEHOME=/opt/IBM/ITM 
    > export CANDLEHOME
     
  - If you have customized the Oracle agent korcoll.ctl file, 
    this file is backed up during the fix install
    as korcoll.ctl.61.{timestamp}.  After this fix is installed,
    edit the latest korcoll.ctl file, and merge your modifications
    into this korcoll.ctl file. 
    
  - Because there is no uninstall utility for this fix, be sure to
    perform a backup of your environment before installing this fix.

  5.2 Local agent update
  --------------------------
  1. Transfer the appropriate archive file (6.1.0.1-TIV-ITM_ORA-IF0014.tar
     or .zip) to a temporary directory on the system that contains the
     agent code to be updated.  For the purpose of this README, the 
     <TEMP> symbol represents the fully qualified path to this 
     directory. Note: On a Windows system, 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 included prerequisite
     fix for the target agent platform. For more information on the 
     "itmpatch" command, see section 6.2.         
   
     On UNIX systems, if the fix was expanded to 
     <TEMP>/6.1.0.1-TIV-ITM_ORA-IF0014, the install command is:

     > itmpatch -h <CANDLEHOME>
                -i <TEMP>/6.1.0.1-TIV-ITM_ORA-IF0014/kdd_xxxxxx_tema_if0018.tar
        
       where:
         - xxxxxx corresponds to the value in the first column
           returned by the ./cinfo -i command. 
       
         In the following example, the file is "kdd_li6243_tema_if0018.tar":
         > ./cinfo -i
           Distributed Database common code
           li6243  Version: 06.10.01.18
                                                   
     On a Windows system, if the fix was expanded to 
     <TEMP>\6.1.0.1-TIV-ITM_ORA-IF0014, the install command is:

     > itmpatch -h <CANDLEHOME>
                -i <TEMP>\6.1.0.1-TIV-ITM_ORA-IF0014\kdd_winnt_tema_if0018.cab

  4. 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.R.M-TIV-ITM_ORA-IF0014, 
     the install command is:
     
     > itmpatch -h <CANDLEHOME> 
                -i <TEMP>/6.1.0.1-TIV-ITM_ORA-IF0014/kor_xxxxxx_tema_if0014.tar
                
       where:
         - xxxxxx corresponds to the value in the first column returned
           by the ./cinfo -i command. 
       
         In the following example, the file is "kor_li6243_tema_if0014.tar".
         > ./cinfo -i
           Monitoring Agent for Oracle
           li6243  Version: 06.10.01.14

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

     > itmpatch -h <CANDLEHOME> 
                -i <TEMP>\6.1.0.1-TIV-ITM_ORA-IF0014\kor_winnt_tema_if0014.cab

  5. If you upgrade the agent from version 06.10.01.12 or older version, 
     the 'korgrant.sql' or 'korgrantcustom.sql' script must be run after 
     installing fix 6.1.0.1-TIV-ITM_ORA-IF0014. See the IBM Tivoli 
     Monitoring for Databases: Oracle Agent User's Guide. 
      
     Or, if you upgrade the agent from version 06.10.01.12, the 
     following grant command can be executed instead of running 
     the 'korgrant.sql' or 'korgrantcustom.sql' script.

        grant select on   V_$DATAFILE_HEADER   to <connection id> ;

        where: <Connection id> is the user id setup for the IBM Tivoli 
               Monitoring Oracle Agent connection.
     
  5.3 Remote agent update
  ----------------------------
  1. Transfer the appropriate archive file (6.1.0.1-TIV-ITM_ORA-IF0014.tar
     or .zip) to a temporary directory on the IBM Tivoli Enterprise 
     Monitoring Server system. For the purpose of this README, the 
     <TEMP> symbol represents the fully qualified path to this
     directory. Note: On Windows, this path includes the drive letter.
     
  2. Expand the archive file using the "tar" command on UNIX systems or 
     an 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.R.M-TIV-ITM_ORA-IF0014:
     > $CANDLEHOME/bin/tacmd addBundles -n 
                                        -i <TEMP>/6.1.0.1-TIV-ITM_ORA-IF0014

     On Windows systems, 
     if the fix was expanded to <TEMP>\6.R.M-TIV-ITM_ORA-IF0014:
     > %CANDLE_HOME%\bin\tacmd addBundles -n 
                                          -i <TEMP>\6.1.0.1-TIV-ITM_ORA-IF0014
      
     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. From the <TEMP>/6.1.0.1-TIV-ITM_ORA-IF0014 directory, run the 
     appropriate script based on the operating system.
  
          kor_patchdepot.bat - Windows
          kor_patchdepot.sh  - UNIX
  
     This script is provided to copy the or_dd_061001014.xml and
     or_dd.properties files from the <TEMP>/6.1.0.1-TIV-ITM_ORA-IF0014
     directory to the 061001000 version of the Tivoli Enterprise 
     Monitoring Services depot. 
     
     Note: The following error messages are displayed during 
           'tacmd addSystem' if the script is not executed.
  
     ================================================================
        KUICAR010I: The agent type OR is being deployed.
  
        KUICAR020E:  The addSystem command did not complete because a 
        deployment error occurred.  See the following error returned 
        from the server:
  
        The property DBSETTINGS.db_extparms is invalid for version 
        061001000 of the OR agent.
  
        The property name is not valid.
     ================================================================
  
  5. To login 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 or
                                         -n <Managed system name> 
                                         -v 061001014

     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 OR
                                           -n <Managed system name> 
                                           -v 061001014
                              
     Note:
     - The component (-t) for the "tacmd updateAgent" command is 
       specified as two characters (or), not three characters (kor).
     - 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 an "tacmd 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. If you upgrade the agent from version 06.10.01.12 or older version, 
     the 'korgrant.sql' or 'korgrantcustom.sql' script must be run after 
     installing fix 6.1.0.1-TIV-ITM_ORA-IF0014. See the IBM Tivoli 
     Monitoring for Databases: Oracle Agent User's Guide. 
      
     Or, if you upgrade the agent from version 06.10.01.12, the 
     following grant command can be executed instead of running 
     the 'korgrant.sql' or 'korgrantcustom.sql' script.

        grant select on   V_$DATAFILE_HEADER   to <connection id> ;

        where: <Connection id> is the user id setup for the IBM Tivoli 
               Monitoring Oracle Agent connection.
  
  5.4 Agent support update
  ------------------------
  If you have already installed 6.1.0.1-TIV-ITM_ORA-IF0012 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.1.0.1-TIV-ITM_ORA-IF0014.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 (kor_tems_teps_tepd_if0014.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. Start the Application Support Installer GUI to install the fix.  
     The GUI can be started by using the following command from within 
     the CD-ROM directory where setup.jar is located.
      
     On a UNIX system:
  
     > $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar 
  
     On a Windows system:
  
     > <"C:Program Files\IBM\Java142">\jre\bin\java -jar setup.jar
      
       where <"C:Program Files\IBM\Java142"> is the default drive and 
       location of IBM Java 1.4.2.  The location of IBM Java 1.4.2
       on your system might vary.                                       
  
     When prompted by the Application Support Installer for the fix 
     directory, select the CD-ROM directory, not the component directory.
     The installer can install updates for multiple components at the 
     same time.       
  
  5. The next panel presented by the Application Support Installer asks
     for the selection of Tivoli Monitoring components to which you want
     to add application support. 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 Oracle 
     06.10.01.14 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.
  
  7. To add the application support for the new situation, from the Tivoli
     Enterprise Monitoring Server and Tivoli Enterprise Portal Server, 
     select 'Advanced' and then 'Add TEMS application support'.
     Choose the 'kor_upg.sql' script during the 'Application Support' 
     installation. 
     See the "Adding application support to the hub monitoring server'
     section in the IBM Tivoli Monitoring Installation and Setup Guide.
     
  8. From the Tivoli Enterprise Portal Server, run 'buildpresentation.bat' 
     on Windows or 'InstallPresentation.sh' file on UNIX or Linux to 
     reconfigure the Tivoli Enterprise Portal Server. 

6.0 Additional installation information
========================
 
  6.1 Installation instructions for agent baroc file
  -----------------------------------------------------
  This fix incorporates changes to the agent baroc file, which needs to 
  be reinstalled. Please refer to IBM Tivoli Monitoring, Version 6.1, 
  Installation and Setup Guide under "Installing monitoring agent .baroc
  files on the event server" in "Installing the IBM Tivoli Enterprise
  Console Event Synchronization" section.
  
  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 a Windows systems, this path must include
  the drive letter.
  <TEMP> represents the fully qualified directory specification where
  the fix is located. On a 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 current version of the agent 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 or

     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 OR 

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

     When the agent update is successful, the agent version is: 
     06.10.00.14.
  
    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.10.01.14. 
    For the agent on UNIX systems, the version number is
    06.10.01.14. 

  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.      
    
     Sample output for the kincinfo command on Windows systems
     --------------------------------------------------------------
     To validate that all components have been installed, run the
     following command:
  
     %CANDLE_HOME%\InstallITM\kincinfo -i
     
    
     Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server,
     and Tivoli Enterprise Portal Desktop update:
  
     OR        Oracle Support
               WINNT Version: 06.10.01.14 Build: 201104200000
  
     OR        Oracle Support
               WINNT Version: 06.10.01.14 Build: 201104200000
  
     OR        Oracle Support
               WINNT Version: 06.10.01.14 Build: 201104200000

     
     
     Monitoring Agent for Oracle update:
     
     DD        Distributed Database Common Code
               WINNT Version: 06.10.01.18 Build: 201104200000
     
     OR        Monitoring Agent for Oracle
               WINNT Version: 06.10.01.14 Build: 201104200000

7.0 Known problems and workarounds
==================================
 - Problem: If you updated the agent from 06.01.00.03 or older version 
            on Unix systems by remote deploy or local upgrade, it 
            fails to stop the agent. The error mesasage is like,
            andleDBAgent warning: cannot stop <sid>, running=no, continuing ...
            kddexec: Can't continue with the stop	
               
   Workaround: This problem occurs since the agent updates kddexec.sh 
            from 06.01.00.04. You need to manually kill all processes 
            of Oracle agent including "/bin/ksh go <sid> <install_dir>", 
            "koragent", and "korcoll". The agent will works after 
            restart the agent.
 
 - 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-M's. When this fix is 
            remotely deployed to a UNIX computer from the IBM Tivoli 
            Enterprise Monitoring Server or depot on Windows, the 
            installation fails. The CTRL-M's are caused by extracting
            the fix using WinZip with the "TAR file smart CR/LF conversion"
            option enabled. This extraction causes WinZip to put CTRL-M's in text 
            files when they are extracted on UNIX through remote deployment.
               
   Workaround: If you are using Winzip for the fix installation for the 
            Tivoli Enterprise Monitoring Server on a Windows system, the default 
            "TAR file smart CR/LF conversion" option must be disabled.  
              
 - Problem: If the Oracle agent is uninstalled after 
            applying this fix, the KOR and KDD files are removed, but
            the KDDWICMA.ver file with patch version remains. 
            The presence of this KDD .ver file prohibits the Oracle
            agent from being successfully installed again.

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

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

   Workaround: No workaround is needed.  

 - Problem: For IY98181/IZ03843, after applying this fix, utmpx is still
            in a corrupted state.
                 
   Workaround: The user needs to nullify /var/adm/utmpx file manually 
            to remove the corrupted information in utmpx file. 
            This action 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
                       ...

            In this case, the problem is that the length of the managed
            node name, <SID>:<HOSTNAME>:ORA, exceeds the length
            supported by the portal. A possible cause is that the
            fully qualified host name is being used. If 'uname -n'
            on the Oracle agent computer returns a 
            fully qualified host name, then this name 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 Oracle agent receives an ORA-12546 error.
            After installing Oracle 10gR2 (10.2.0.1) on Linux/PPC64, 
            the Oracle agent receives an ORA-12546
            error. Also, the root user is unable to log in as any
            Oracle user through sqlplus. 

   Workaround: This problem is caused by a UNIX file permissions error.

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

               Install Oracle Patch 4516865
               <http://updates.oracle.com/ARULink/PatchDetails/
                       process_form?patch_num=4516865>
    
               This patch installs a script that relaxes file
               permissions in $ORACLE_HOME to solve the problem. You 
               must first apply the patch using the opatch utility,
               which is found at $ORACLE_HOME/OPatch/opatch. After the
               patch is applied, you must 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 deployment, configure, start, stop, remove, 
            and restart are not available on HP-UX 11i V2 on Integrity.

   Workaround: None.
   
 - Problem: After running the following command on Linux: 
              ./cinfo -r              
            An error might occur:            
            *** glibc detected *** /oracle_NEW_1/tmp/ps5520_or_orcl2/
            kddsignl: corrupted double-linked list: 0x08077ef0 ***
            
   Workaround: 1. Remove all the core files from:
                   $CANDLEHOME/tmp/<HostName>_or_<Instance Name>.
               2. Restart the Oracle agent.


8.0 Additional product information
==================================

 - The following new feature is added by IY92195 in 
   6.1.0.1-TIV-ITM_ORA-LA0004.

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


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

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

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

 DB3,DB6,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 disabled for 'Set FREEBYTES to zero', 'Set TSNEXTS to 
 zero', and 'Set MAXEXTTS to zero'.  The SQL cursor name is case 
 insensitive.

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

  UNIX(R) file: $CANDLEHOME/config/{hostname}_or_{instance name}.cfg
  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 'Extended Parameters' field has been added to the following
 configuration operations.

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

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

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

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

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

   Disabled: Set FREEBYTES to zero

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

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

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

              Column : System TS Percent Free = 0

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

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

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

   Disabled: Set EXTENTS to zero

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

   Situation : None

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

 SQL cursor: 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;

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

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

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

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

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

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

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

   Situation: Oracle_Free_Space_Frag_Crit = always true
              Oracle_Free_Space_Frag_Warn = always false

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

 SQL cursor 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;

   Disabled : 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


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

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

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

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION 
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, 
INCLUDING,   BUT NOT LIMITED TO,   THE IMPLIED WARRANTIES OF 
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

Trademarks and service marks
------------------------------------

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

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

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

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

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

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

