Applying APRIL 2014 DATABASE PATCH SET UPDATE 11.2.0.3.10 - Patch 18031683

Applying APRIL 2014 DATABASE PATCH SET UPDATE 11.2.0.3.10 - Patch 18031683

1) Download Patch 18031683 relevant for your environment

2) Verify if the patch already applied or not

$opatch lsinventory | grep 18031683

3) Check opatch version to ensure it is 11.2.0.3.0 or higher

$opatch version

Note: If Opatch version is not up to date then download patch 6880880 from Metalink

4) Check for patch conflicts

Copy patch onto target host $ORACLE_HOME/patches, unzip the patch.

opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./18031683

Note: If there's no conflict please proceed with applying the patch. In case of conflicts, contact product support.

5) Check for invalid objects in Database 

select owner,object_name,object_type from dba_objects where status='INVALID';

6) Shutdown the services and apply the patch (make sure backup is taken before applying patch).


$ opatch apply
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.
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
OPatch succeeded.

7) Check if patch is successfully applied or not.

$ opatch lsinventory | grep 18031683


8) Post patch, load modified SQL files into the Database:

Start the database

cd $ORACLE_HOME/rdbms/admin

SQL> @catbundle.sql psu apply

PL/SQL procedure successfully completed.
-------------------
SQL> COMMIT;

Commit complete.

9) Check log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors
10)Query registry$history to ensure PSU was applied.

SQL> select * from registry$history;


11) Run utlrp.sql for any invalid objects reported.