=========================================================================
Interim Patch for Base Bug: 8864918
=========================================================================

Date: Oct 8, 2009
-------------------------------------------------------------------------
 Platform Patch for      : Generic
 Product Patched         : 10.2.0.5.0
 Product Version #       : Enterprise Manager Grid Control
 Online Installable      : NO

Bugs Fixed by this patch:
-------------------------
8864918:psu 10.2.0.5.1 for enterprise manager on top of 10.2.0.5.0 generic
7303584:INTERNAL ERROR WHEN ACCESSING METRICS AND POLICY SETTING PAGE
7623620:TARGET TYPE METADATA VERSION FOR OSM_INSTANCE INCORRECT
8708612:molecule for upgrade bundle for bugs 8330438 8572609
8708893:napply pse for em upgrade bundle for 10.2.0.5.0
8219750:LOADER ERROR MGMT_DB_HDM_METRIC_HELPER IS MUTATING
8265686:USER_TAB_PARTITIONS IS ACCESSED FOR EVERY DATA FILE UPLOADED BY LOADER
8330438:STREAMS JOB LOG PAGE, DOES NOT REFLICT THE CORRECT STATUS IN 10.2.0.5 GC
8351454:PATCHING SETUP THROWS AN INVALID ERROR
8351955:ERROR-400|ORA-06533 SUBSCRIPT BEYOND COUNT WHILE LOADING ALERTS
8396767:EMCLI STOP_BLACKOUT HANGS IF THE AGENT IS SHUTDOWN AFTER THE BLACKOUT IS STARTED
8444248:DEADLOCK WHILE RECORDING AGENT HEARTBEAT
8448909:10.2.0.5PT UNABLE TO CREATE USER USING THE PROFILE MGMT_ADMIN_USER_PROFILE
8461212:ORA-6502 CHAR CONVERSION ERROR WHILE LOADING METADATA FILES
8472279:MANUAL DISCOVERY AUTOMATICALLY ADDS TARGETS TO ALL GROUPS FOR THE ADMINISTRATOR
8483321:CORRECTIVE ACTIONS ARE EMPTY AFTER APPLY TEMPLATE
8484881:A*.XML, DEADLOCK DETECTED WHILE WAITING FOR RESOURCE
8487423:PERF WR QUERY TO GET LAST TIMESTAMP FOR RAC COMPONENTS IS WRONG
8492097:ORA-20206 OCCURS ADDING TARGET DATABASE
8494916:SYSTEM DASHBOARD NOT DISPLAYING PROPERLY
8497843:INCORRECT NUMBER OF ALERTS SHOWN IN DASHBOARD
8518923:CHANGE PASSWORD FAILS WHEN PASSWORD PROFILES ARE ENABLED
8572609:10.2.0.5 DOES NOT ALLOW - IN THE TARGET NAME -
8583901:MERGE LABEL REQUEST ON TOP OF 10.2.0.5 FOR BUGS 8494916 8497843
8610662:ORA-20414 ERROR WHILE APPLYING MONITORING TEMPLATE
8639888:BLOCKING SESSION SQL FOR ECM SQL DATA ON MGMT_DELTA_IDS TABLE
8645799:MERGE LABEL REQUEST ON TOP OF 10.2.0.5 FOR BUGS 8448909 8518923
8662430:TEMPLATE FAILURES IF KEY NAMES CONTAIN '%' CHARACTER (TABLE SPACE SPACE USED)
8680162:MERGE LABEL REQUEST ON TOP OF 10.2.0.5 FOR BUGS 8492097 8483321
8742488:MERGE LABEL REQUEST ON TOP OF 10.2.0.5.0 FOR BUGS 8330438 8572609
8777255:FIX FROM 8484881 NEEDS TO HANDLE NULL VALUE CONDITION
8308190:AIX UNABLE TO START REPLAY CLIENT FROM UI - CANNOT LOAD PROGRAM WRC
8348153:DOWNLOAD AGENT SOFTWARE DOWNLOADS INCORRECT AGENT VERSION
6958353:AIX 10204GC REFRESH HOST CONFIGURATION FAILS
8437552:HPIA CREATE TEST DB JOB SUCCEEDED BUT SOME RMAN AND SQL COMMANDS ARE NOT RUN
8354040:DP STATUS SHOWS DATABASE ERROR - MOST OF THE TIME IN PORTING PLATFORM

Patch Preinstall Steps
----------------------

1. For non-recommended patches, you must have the exact symptoms
   described in the service request (SR).

2. Confirm the version of Perl installed and configured for the ORACLE_HOME.

Oracle requires that all customers have at least Perl 5.00503 installed
and configured for patching activities inside the ORACLE_HOME.  Follow
these steps to check the Perl version for the ORACLE_HOME being patched:

  - source the ORACLE_HOME environment
  - execute "perl -v"
  - verify that the returned version of Perl is 5.00503 or higher

If the Perl configured for the ORACLE_HOME is not at 5.00503 or
higher, follow the directions in this metalink note to update to
a more recent version:

 https://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=189489.1

3. Verify the OUI Inventory.

OPatch needs access to a valid OUI inventory to apply patches.
Validate the OUI inventory with the following command:

  % opatch lsinventory

If the command errors out, contact Oracle Support and work to validate
and verify the inventory setup before proceeding.

4. You must use the OPatch 10.2 version 10.2.0.4.7 or later.

Oracle recommends that all customers be on the latest version of OPatch.
Please review the following metalink note and follow the instructions
to update to the latest version if needed:

 https://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=224346.1

5. Confirm executables appear in your system PATH.

The patching process will use the unzip and the opatch executables.  After
sourcing the ORACLE_HOME environment, confirm both of these exist before
continuing:

  - "which opatch"
  - "which unzip"

If either of these executables do not show in the PATH, correct the problem
before proceeding.

6. Create a location for storing the unzipped patch.  This location
will be referred to later in the document as <PATCH_TOP>.

7. Unzip the patch zip file into the <PATCH_TOP>.

  unzip -d <PATCH_TOP>  p8864918_10205_GENERIC.zip

8.  One-off Patch Conflict Detection and Resolution

   i.   Determine whether any currently installed one-off patches conflict with
        the PSU patch as follows:
        % opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir <PATCH_TOP>/8864918

   ii.  The report will indicate the patches that conflict with PSU 8864918 and
        the patches for which PSU 8864918 is a superset. Refer to "Patch Set Updates
        Patch Conflict Resolution" in My Oracle Support Note 854428.1 Patch Set
        Updates for Oracle Products.
 
   iii. When all the 10.2.0.5.1 one-off patches that you have requested are
        available at My Oracle Support, proceed with "Patch Installation Steps".


Patch Installation Steps:
-------------------------

  1) Set <OMS_ORACLE_HOME>/bin to your PATH environment variable.
     On Unix
         setenv PATH $ORACLE_HOME/bin:$PATH
     On Windows
         set PATH=%ORACLE_HOME%\bin;%PATH%

     Shutdown OMS using the following command. In case of multi-OMS
     environment, shutdown on all OMS machines.

         % emctl stop oms
     For Windows
         % %ORACLE_HOME%\opmn\bin\opmnctl stopall

     Leave EM Repository database and its listener running.


     NOTE: A) If OMS and Repository are on same machine,then set TNS_ADMIN to (Repository Home)/network/admin
              then invoke SQLPLUS.

           B) If OMS and Repository are on different machines, then create tnsnames.ora under <OMS Home>/network/admin,
              set TNS_ADMIN to this location. Create a tns alias in tnsnames.ora, that points to Repository database.

           for eg: sqlplus sysman/<password>@<tns alias from $TNS_ADMIN/tnsnames.ora>
  Following steps needs to be run on all of the OMSs

  2) Change to the directory where the patch was unzipped.

      % cd <PATCH_TOP>/8864918;


  3) Use the following command to apply the patch to the ORACLE_HOME:

          % opatch apply

    In case of multi-OMS environment,  the step 4 needs to be executed only on one of the OMS servers

  4) Connect to sqlplus as repository owner. Run the following command

      SQL> @post_deploy_script.sql

  5) Start OMS using the following command. In case of multi-OMS environment,
      run the command on all OMS servers

          % emctl start oms


Patch Deinstallation Instructions:
----------------------------------
To de-install the patch  and restore the system to the previous state , run the following commands:

  1) Shutdown OMS. In case of multi-OMS
     environment, shutdown on all OMS servers.

         % $ORACLE_HOME/bin/emctl stop oms
     Leave EM Repository database and its listener running.

     In case of multi-OMS environment  ,execute the above step on all of the OMSs


  NOTE: A) If OMS and Repository are on same server,then set TNS_ADMIN to (Repository Home)/network/admin
              then invoke SQLPLUS.

        B) If OMS and Repository are on different servers, then create tnsnames.ora under <OMS Home>/network/admin,
              set TNS_ADMIN to this location. Create a tns alias in tnsnames.ora, that points to Repository database.

           for eg: sqlplus sysman/<password>@<tns alias from $TNS_ADMIN/tnsnames.ora>

  2) Change to the directory where the patch was unzipped.

      % cd <PATCH_TOP>/8864918;

  3) Use the following command to rollback the patch from the ORACLE_HOME:

     %  opatch rollback -id 8864918

     In case of multi-OMS environment,  the step 4 below needs to be executed only on one of the OMS servers

  4) Connect to sqlplus as repository owner and execute the following sql files

     SQL> @post_deinstall_script.sql

  5) Start OMS using the following command. In case of multi-OMS environment,
      start on all OMS machines

          % emctl start oms

     If you have any problems de-installing this PSE or are not sure
     about inventory setup please call Oracle support.

