Error OUI-67215 occurred while applying patch

Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.4 [Release 11.2]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

You may receive the following warning while applying the patch on Solaris platform
OUI-67215:
                            OPatch found the word "warning" in the stderr of the make command.
                            Please look at this stderr. You can re-run this make command.
                            Stderr output:
                            ld: warning: option -YP appears more than once, first setting taken
                            ld: warning: option -Q appears more than once, first setting taken


Cause
Make warnings caused due to Options for ld command appears more than once.

Solution
 These warnings are safely ignorable.

Reference : "Opatch Warning During Patch Apply : "ld: warning: option -YP appears more than once, first setting taken" (Doc ID 1571550.1)"

------------------------------------------------------------------------------------------------------
Error OUI-67215 occurred while applying PSU April 2015 to 11.2.0.4 DB

"/u01/app/oracle/product/11.2.0.4/dbhome_1/.patch_storage/19121551_Oct_7_2014_23_09_13/scratch"
[May 15, 2015 1:26:16 PM]    Size of directory "/u01/app/oracle/product/11.2.0.4/dbhome_1/.patch_storage" after cleanup is 340604187 bytes.
[May 15, 2015 1:26:16 PM]    UtilSession: Backup area for restore has been cleaned up. For a complete list of files/directories
                             deleted, Please refer log file.
[May 15, 2015 1:26:16 PM]    Composite patch 20299013 successfully applied.
[May 15, 2015 1:26:16 PM]    UtilSession: N-Apply done.
[May 15, 2015 1:26:16 PM]    --------------------------------------------------------------------------------
[May 15, 2015 1:26:16 PM]    The following warnings have occurred during OPatch execution:
[May 15, 2015 1:26:16 PM]    1) OUI-67215:
                             OPatch found the word "warning" in the stderr of the make command.
                             Please look at this stderr. You can re-run this make command.
                             Stderr output:
                             ld: warning: option -Q appears more than once, first setting taken
[May 15, 2015 1:26:16 PM]    --------------------------------------------------------------------------------
[May 15, 2015 1:26:16 PM]    OUI-67008:OPatch Session completed with warnings.
[May 15, 2015 1:26:16 PM]    Finishing UtilSession at Fri May 15 13:26:16 GMT-05:00 2015
[May 15, 2015 1:26:16 PM]    Log file location: /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2015-05-15_13-22-18PM_1.log
~

OPatch failed with error code 73

When apply Oracle Patch, check the following items first.

1. shutdown databases
2. shutdown listener
3. Opatch version
4. unzip PSU file to Non ORACLE_HOME


$> cd /tmp/20299013/
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> ls
17478514     18522509     19769489     README.html  patchmd.xml
18031668     19121551     20299013     README.txt
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> opatch apply
Oracle Interim Patch Installer version 11.2.0.3.10
Copyright (c) 2015, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/11.2.0.4/dbhome_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/11.2.0.4/dbhome_1/oraInst.loc
OPatch version    : 11.2.0.3.10
OUI version       : 11.2.0.4.0
Log file location : /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2015-05-15_13-                                                                                                00-52PM_1.log

Verifying environment and performing prerequisite checks...
Prerequisite check "CheckActiveFilesAndExecutables" failed.
The details are:


Following executables are active :
/u01/app/oracle/product/11.2.0.4/dbhome_1/lib/libclntsh.so.11.1
UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
Log file location: /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2015-05-15_13-0                                                                                                0-52PM_1.log

OPatch failed with error code 73
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> ps -ef|grep libclntsh
  oracle 27531  7686   0 14:01:24 pts/13      0:00 grep libclntsh
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> lsnrctl status

LSNRCTL for Solaris: Version 11.2.0.4.0 - Production on 15-MAY-2015 14:03:57

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Solaris: Version 11.2.0.4.0 - Production
Start Date                13-MAY-2015 15:22:22
Uptime                    1 days 22 hr. 41 min. 38 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/11.2.0.4/dbhome_1/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/ontpand0bav121/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ontpand0bav121)(PORT=1521)))
The listener supports no services
The command completed successfully
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> lsnrctl stop

LSNRCTL for Solaris: Version 11.2.0.4.0 - Production on 15-MAY-2015 14:04:33

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
The command completed successfully
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> opatch version
OPatch Version: 11.2.0.3.10

OPatch succeeded.
[10.69.11.141:ontpand0bav121:oracle@null]/tmp/20299013
$> opatch apply
Oracle Interim Patch Installer version 11.2.0.3.10
Copyright (c) 2015, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/11.2.0.4/dbhome_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/11.2.0.4/dbhome_1/oraInst.loc
OPatch version    : 11.2.0.3.10
OUI version       : 11.2.0.4.0
Log file location : /u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/opatch/opatch2015-05-15_13-                                                                                                04-47PM_1.log

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   17478514  18031668  18522509  19121551  19769489  20299013

Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Y



Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/oracle/product/11.2.0.4/dbhome_1')


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying sub-patch '17478514' to OH '/u01/app/oracle/product/11.2.0.4/dbhome_1'

Patching component oracle.rdbms, 11.2.0.4.0...

Patching component oracle.rdbms.rsf, 11.2.0.4.0...

Patching component oracle.sdo, 11.2.0.4.0...

Patching component oracle.sysman.agent, 10.2.0.4.5...

Patching component oracle.xdk, 11.2.0.4.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0...

Patching component oracle.sdo.locator, 11.2.0.4.0...

Patching component oracle.nlsrtl.rsf, 11.2.0.4.0...

Patching component oracle.xdk.rsf, 11.2.0.4.0...

Patching component oracle.rdbms.rman, 11.2.0.4.0...

Verifying the update...
... ...

Oracle Database Patch Sets Starting With 11.2.0.2

Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2 (Doc ID 1189783.1)

What has changed?
Packaging: Starting with the first patch set for Oracle Database 11g Release 2 (11.2.0.2), Oracle Database patch sets are full installations of the Oracle Database software. In past releases, Oracle Database patch sets consisted of a set of files that replaced files in an existing Oracle home. Beginning with Oracle Database 11g Release 2, patch sets are full installations that replace existing installations.

Because Oracle Database 11g Release 2 and later patch sets are a full installation, Oracle patch sets are now released as several installation bundles, just as are the base releases:

•Oracle Database Server
•Oracle Grid Infrastructure
•Oracle Database Client
•Companion/examples
•Oracle Gateways

Simplified new installation: Because the release 11.2.0.2 patch set is a full installation package, if you are installing Oracle Database on a system without an existing Oracle Database installation, then you can simply install the release 11.2.0.2 patch set. You are no longer required to install the base release, and then apply the patch set.

Upgrade process: Beginning with the release 11.2.0.2 patch set, you have two ways to apply a patch set (documented in the Oracle Database 11g Release 2 Upgrade Guide):

•Out-of-place upgrade – This is Oracle's recommended way to apply a patch set. You install the patch set into a new, separate Oracle home location. After you install the patch upgrade, you then migrate the Oracle Database from the older Oracle home. The patch set upgrade is now the same process to upgrade from one version to another. Oracle recommends that you perform an out-of-place patch set upgrade, because this patch set application option requires much less downtime, and is safer because it does not require patching an ORACLE_HOME that is already being used in production. However, you must ensure that you have sufficient free disk space to accommodate two Oracle home directories at the same time.

•In-place upgrade – You install the patch set into an existing Oracle home location. Oracle recommends that you select this option only if you do not have sufficient free disk space to perform an out-of-place upgrade, as the upgrade removes the existing Oracle installation. This patch option requires less disk space, but requires more time, and is riskier, because if you encounter an installation failure, then you must recover the entire existing Oracle home from a backup. If you choose this more risky option, then before you begin the patch installation, complete the following tasks:

◦Make a complete backup of your existing Oracle home
◦Read through the entire Upgrade Guide section dealing with in-place upgrades


Note: All Oracle Grid Infrastructure patch set upgrades must be out-of-place upgrades, in which you install the patch set into a new Grid home. In-place patch set upgrades are not supported.