5 Replies Latest reply: Mar 28, 2012 8:13 AM by KenO RSS

    Apply patch 7705743 (TUMS) fails in MW

    KenO
      The following is the output from "2-Run TUMS utility (Recommended)" - any ideas?

      Checking to see if the TUMS patch was applied previously...
      Downloading the latest TUMS patch...
      ###############################################################################
      SUMMARY unique NODES DETERMINED - based on NODE, USER, and APPL_TOP
      ###############################################################################
      apps
      ERROR - could not get correct node platform
      Called on node: apps sandbox.mycompany.com uname
      ###############################################################################
      ACTION: setup on node: apps, patch=7705743, driver=
      ###############################################################################
      ForceDownload set to: y
      Checking existence of patch: 7705743 on local node /apps/oracle/oracle/product/10.2.0/eof/patches
      OK - GENERIC patch appears on local machine
      Checking existence of patch: 7705743 on apps node in /apps/applmgr/11i/patches
      OK - Compressed patch(zip) appears on remote node: apps
      Found unzipped patch directory on apps, show readme.txt for: 7705743, if not above.
      Checking to see if the patch downloaded successfully...
      Successful download of the TUMS patch.
      Applying it now...
      ###############################################################################
      INFO - Help on monitoring when multiple drivers and nodes are applied.
      ###############################################################################
      If the web window times out, click on the x and rerun it to view the updated log
      file. It will change as the patch continues to run in background. Just keep marking it
      success until it is complete or check the active patch node manually:
      $ tail -f $APPL_TOP/admin/${TWO_TASK}/log/7705743_patchit11i*.log
      Each node, if multi-node, will be determined and the patch drivers will be applied
      on the right nodes in the right order. Look for the ACTION: statement.
      ###############################################################################
      SUMMARY unique NODES DETERMINED - based on NODE, USER, and APPL_TOP
      ###############################################################################
      apps
      ERROR - could not get correct node platform
      Called on node: apps sandbox.mycompany.com uname
      ###############################################################################
      ACTION: execute on node: apps, patch=7705743, driver=all
      ###############################################################################
      patchit11i.sh REMOTE SIZE: sandbox.mycompany.com LOCAL SIZE: 47535
      ERROR - patchit11i.sh - RETURNED: 255
      ERROR: The TUMS patch failed to apply successfully.
      Please have your DBA download and apply this patch manually now.
      Do not continue to the Execute until this patch applies successfully.
      Process Returned: 0 Results in: /apps/oracle/oracle/product/10.2.0/eof/log/INSTANCE_1703/script_10422.sh (39 bytes)