GI PSU 11.2.0.3.1 is installed successfully (with exit code 1)

I’ve just installed the GI PSU 11.2.0.3.1 for a new RAC, I figured out that the command returns 1 even if everithing it’s ok:

The patch is installed correctly, all services are up & running

The following two tabs change content below.

Ludovico

Oracle ACE Director and Computing Engineer at CERN
Ludovico is an Oracle ACE Director, frequent speaker and community contributor, working as Computing Engineer at CERN, the European Organization for Nuclear Research, in Switzerland.

5 thoughts on “GI PSU 11.2.0.3.1 is installed successfully (with exit code 1)

  1. Thanks for sharing your informations.
    I’ve to apply the same patch on a RAC with ASM and 6 database.
    I’like to know your opinion on some issue:

    1) I need to stop crs and databases before application?

    2) in the readme is wrote: “It is recommended that you download the Opatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node”. but my shared location is on ACFS filesystem, and i’ve to dismount it before proceed. The location from that you installed was shared or local.

    Best regards
    Antonio

  2. hi Antonio,
    you can patch your GI one node at time and put your Opatch inside your GI HOME to do this.
    However, you can leave the db running on the other node only if your DB Oracle Home is not shared on ACFS.

  3. Thank for your reply.
    I don’t need to leave a db running, my doubt was if i’ve to stop crs services (crsctl stop -all) before execute opatch auto command. I’ll try to leave it alive. My second question was about the need to put patch sw on a shared filesystem, since i patch one node at time.

    Antonio

  4. Hi Antonio,
    1a – you should leave your CRS alive while patching, the patch itself will stop everything as needed
    1b – if your DB Home is shared you have only to stop your databases.

    2 – you don’t need to put your patch sw on a shared filesystem, you can put it locally, eg. under your user $HOME.

    (ps, note that 11.2.0.3.2 is out)

    best regards

    Ludovico

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.