RE: PSU Application Question

From: Uzzell, Stephan <SUzzell_at_MICROS.COM>
Date: Mon, 9 Sep 2013 18:59:59 +0000
Message-ID: <DF78EADE484D37419A53F5C898629DB7A94C0DDA_at_usmail2k1001.us.micros.int>

Thank you to everyone who responded. It appears that one can also run opatch auto -oh <DB HOME> to patch that home, even if there's no database in place yet.

Stephan Uzzell

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

Hi Stephan,

if it's "clever" - I don't know, but I just do "opatch apply" in the DB $OH for the missing patches afterwards. And I alwys do it for both: Grid Home and DB home PSU, because sometimes the GI patch contains stuff to be applied to the DB home. If not, no harm is done.

NEVER forget to execute "catbundle.sql psu apply". It's always mandatory to call it - even in the case when you created the instance AFTER applying the PSU to the ORACLE_HOME.

Regards
Martin

Uzzell, Stephan schrieb:
> Hi Martin,
>
> 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
>

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


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

Received on Mon Sep 09 2013 - 20:59:59 CEST