RE: PSU Application Question

That was sort of what we started to suspect. For our new builds, this is fine - we will simply create the DB (and register) before applying the PSU. However, we are planning on migrating some databases from Windows to Linux via EMC Snap Cloning. We'd really prefer not to have to create a database (that we will then drop) in order to apply the PSU prior to the migration, and we'd certainly prefer not to have to add the PSU to our migration windows. Any clever workarounds for this problem?

Thanks!

Stephan Uzzell

-----Original Message-----
From: Martin Klier [mailto:usn_at_usn-it.de] Sent: Monday, 09 September, 2013 11:22
To: Rui.Amaral_at_tdsecurities.com
Cc: Uzzell, Stephan; oracle-l_at_freelists.org Subject: Re: PSU Application Question

Hi,

in my experience, the response file will only patch oracle homes that have services registered with the GI. So be careful if you patch before you create a DB (and thus, don't have a db service).

Regards
Martin

Amaral, Rui schrieb:
> I have been passing the gi one and that works for both gi and home...
> so far at least ;-)
>
> Here's what I have been using for the July PSU :
>
> /u001/app/11.2.0/grid/OPatch/opatch auto
> /u001/app/oracle/software/JulyPSU2013 -ocmrf
> /u001/app/11.2.0/grid/OPatch/ocm/bin/ocm.rsp
>
> Rui Amaral
> Senior Oracle DBA
>
> -----Original Message-----
> From: Uzzell, Stephan [mailto:SUzzell_at_MICROS.COM]
> Sent: Monday, September 09, 2013 11:03 AM
> To: Amaral, Rui; oracle-l_at_freelists.org
> Cc: Uzzell, Stephan
> Subject: RE: PSU Application Question
>
> Hi Rui,
>
> Thanks for the quick response, but I have to admit I'm not quite sure I follow. If I have to pass -ocmrf as an argument, which ocm response file should I pass it? The GI one or the DB one?
>
> Thanks!
>
> Stephan Uzzell
>
>
> -----Original Message-----
> From: Amaral, Rui [mailto:Rui.Amaral_at_tdsecurities.com]
> Sent: Monday, 09 September, 2013 10:53
> To: Uzzell, Stephan; oracle-l_at_freelists.org
> Subject: RE: PSU Application Question
>
> Stephan,
>
> 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: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Uzzell, Stephan
> Sent: Monday, September 09, 2013 10:44 AM
> To: oracle-l_at_freelists.org
> 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) 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-50
> PM_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
>
>
>
> NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to www.td.com/legal 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 www.td.com/francais/avis_juridique pour des instructions.
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
Usn's IT Blog for Oracle and Linux
http://www.usn-it.de

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