RE: PSU Application Question

From: Amaral, Rui <>
Date: Mon, 9 Sep 2013 10:52:54 -0400
Message-ID: <CC45762506E4C84A8612307613CDCB2512FE4FBC9B_at_EX7T2-SV08.TDBFG.COM>


You'll need to run the eomcmrsp script to generate the ocm.rsp file. I do this on both the grid and db homes just in case. The eomcmrsp can be found in the OH/Opatch/ocm/bin directory.

Rui Amaral
Senior Oracle DBA

-----Original Message-----

From: [] On Behalf Of Uzzell, Stephan Sent: Monday, September 09, 2013 10:44 AM To:
Cc: Uzzell, Stephan
Subject: PSU Application Question

Hi all,
I'm working on a Linux test RAC (I've been working with RAC on Windows for several years now, but RAC on Linux is a new beast to me). I've hit a bit of a challenge, and not sure if this is intended, or...

Our typical build model (on Windows) is to install (and configure) GI, install DB (software only), apply the latest bundle patch to both homes, and then create the database, &c.

So, on this test RAC, I installed (and configured GI), and installed DB (software only). I'm trying to apply PSU 7, but the method seems a little different, and I'm not sure the best way to handle this. From the documentation, it sounds as though I simply run opatch auto on node 1, and it handles the rest. What I've seen looks pretty good - it shuts down the clusterware, patches, starts the clusterware back up. But it doesn't do anything about the database home.

Reviewing the opatch log, it shows

2013-09-06 16:49:52: Oracle Interim Patch Installer version Copyright (c) 2013, Oracle Corporation. All rights reserved.

Oracle Home : /u01/oracle/ Central Inventory : /u01/oracle/oraInventory

    from : /u01/oracle/

OPatch version    :
OUI version       :
Log file location : /u01/oracle/

Invoking utility "saveconfigurationsnapshot" UtilSession failed: UtilSession failed to generate configuration xml file [ PRCD-1061 : No database exists ]

OPatch failed with error code 73

2013-09-06 16:49:52: Looking for configured databases on node malnxtstdb01
2013-09-06 16:49:53: Databases configured on node malnxtstdb01 are:
2013-09-06 16:49:53: Determining ORACLE_HOME paths for configured databases

So basically, it didn't patch the DB home because we haven't created a DB home yet? It seems even running opatch auto from the DB home, with ORACLE_HOME set to the DB home, it does not find the DB home to patch. Is this intended? Is there a workaround? Or do we need to create a database before opatch auto will recognize that home and patch it? on OEL 6.


Stephan Uzzell


NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to for instructions. AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au pour des instructions.
-- Received on Mon Sep 09 2013 - 16:52:54 CEST

Original text of this message