Thinking Out Loud

August 25, 2013

Apply PSU 11.2.0.3.7 for Grid Infrastructure Standalone and DB with Oracle Restart

Filed under: 11g,oracle,PSU — mdinh @ 2:15 pm

So there I was, moving through a maze trying to figure out how to apply 11.2.0.3.7 for Grid and Database Standalone.

Now I understand why my former manager storage guy does not like ASM in preference of EMC SAN.

Why would anyone introduced the added convoluted complexity to the environment and are the added benefits justified?

Here’s the maze.

From README – Oracle Grid Infrastructure Patch Set Update 11.2.0.3.7 (Includes Database PSU 11.2.0.3.7) – 16742216 >>>

For other configurations listed below, see My Oracle Support Document 1494646.1  (Oracle Grid Infrastructure 11.2.0.3.x Patch Set Update SUPPLEMENTAL README) >>>

Doc ID 1089476.1 – Patch 11gR2 Grid Infrastructure Standalone (Oracle Restart) >>> documentation has wrong instructions

If you can figure this out, then please let me know.

If you don’t want to waste your time, here’s the solution I have¬†Apply PSU 11.2.0.3.7 for Grid Infrastructure Standalone and DB with Oracle Restart

Happy Patching.

About these ads

10 Comments »

  1. Thanks Michael, that’s extremely helpful.
    Regards
    Greg

    Comment by Greg — August 26, 2013 @ 7:48 am | Reply

  2. Michael, just to confirm. Oracle is GRID home owner as well as ORACLE_HOME ie no priviledge separation ?

    Comment by Greg — August 26, 2013 @ 10:20 am | Reply

    • That is correct, there is no user/role separation. However, the separation between GI and DB is identifiable from the OS prompt which displays ORACLE_SID (+ASM/pdb01).

      Comment by mdinh — August 27, 2013 @ 3:06 am | Reply

  3. Hi Michael,
    Very good material. On oracle documentations for other PSU version they say to apply the patch for cluster as root. You applied as oracle. It is ok? Many grid homes have also root owner.
    Thank you

    Comment by aydov — October 11, 2013 @ 7:18 pm | Reply

    • What should be run as root depends on the configuration and steps.

      The configuration I have was not in the README but from other notes in the post.

      Case 1: GI Home and the Database Homes that are not shared and ACFS file system is not configured.
      As root user, execute the following command on each node of the cluster:
      # opatch auto -ocmrf

      HTH

      Comment by mdinh — October 13, 2013 @ 12:30 pm | Reply

  4. Many thanks for process of 16742216 installation !!!
    One question – i have fresh installation, GRID(+ASM) + only DB software and wish install 16742216 to grid and oracle software.

    SQL> @?/rdbms/admin/catbundle.sql psu apply

    Should I run catbundle.sql on DB after it creation or it’s not necessary?
    I mean – DB will be created with patched soft.

    Comment by Nait — October 12, 2013 @ 2:31 pm | Reply

    • If you installed the software and then the PSU before creating the database, then you do not need to run catbundle.

      I had to make sure and found this – Introduction To Oracle Database catbundle.sql (Doc ID 605795.1)

      Execution of catbundle.sql is not always required for new and upgraded databases. The Readme documentation indicates when it is required. However, you can execute catbundle.sql when it is not required so that the new or upgraded database has an updated dba_registry_history table.

      Starting with Database 11.2.0.2.0, a dummy catbundle.sql is run at database upgrade and creation time, which creates a dba_registry_history entry with bundle series PSU and ID = “0”. Reports that query on this view for the PSU series returns a row for every upgraded and newly created database.

      Also, look at sys.registry$history which I like better.

      Comment by mdinh — October 13, 2013 @ 12:45 pm | Reply

      • Thanks again, I used your article second time for patching RAC installation.
        For RAC, the next step must be applied at the second node also, because of it will patch only 1 (local) node:
        [oracle@san:pdb01:16742216]$ $ORACLE_HOME/OPatch/opatch apply -local -oh $ORACLE_HOME 16619892 -ocmrf /home/oracle/ocm.rsp

        Next, I was not able to repeat this:

        Stop database home on the node
        [oracle@san:pdb01:~]$ srvctl stop home -o $ORACLE_HOME -s /tmp/statefile.out

        I stoped crs at the both nodes before running patches(execute it at all nodes before run patches):
        crsctl stop crs

        Comment by Nait — November 9, 2013 @ 3:17 pm

  5. Hi Michael,
    we have separated OS User for GI and DB and we did it as described in PSU Readme.
    We use it not shared and ACFS file system is not configured.
    In a RAC Env. it works fine but same steps in Single didn’t patch DB only GI.

    Regards

    Comment by Hans-Peter — October 17, 2013 @ 10:41 am | Reply

    • I don’t believe the PSU apply for RAC and single are the same. Compare opatch lsinventory under GI and OH.

      Comment by mdinh — October 21, 2013 @ 1:42 pm | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

The Rubric Theme. Create a free website or blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.

Join 300 other followers

%d bloggers like this: