PSU Application Question

From: Uzzell, Stephan <SUzzell_at_MICROS.COM>
Date: Mon, 9 Sep 2013 14:44:02 +0000
Message-ID: <DF78EADE484D37419A53F5C898629DB7A94C055F_at_usmail2k1001.us.micros.int>

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) 11.2.0.3 GI, install 11.2.0.3 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 11.2.0.3 GI), and installed 11.2.0.3 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 11.2.0.3.5 Copyright (c) 2013, Oracle Corporation. All rights reserved.

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

    from : /u01/oracle/11.2.0.3/grid//oraInst.loc

OPatch version    : 11.2.0.3.5
OUI version       : 11.2.0.3.0
Log file location : /u01/oracle/11.2.0.3/grid/cfgtoollogs/opatch/opatch2013-09-06_16-49-50PM_1.log

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?

11.2.0.3.(hopefully)7 on OEL 6.

Thanks!

Stephan Uzzell

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Sep 09 2013 - 16:44:02 CEST