(October 2013) Patch Set Update (PSU)


Oracle has released a new PSU (October 2013) for the 11GR2 Database and 12C Database.

Check out the Blog from GUMPX which describes a good overview for this update.

And also don`t forget to check MOS Note 1454618.1 for other PSU Patch Numbers like GI or Windows.

Here is a small example how to apply this patch. Please keep in mind that you configuration can be different so read and follow the documentation provieded by Oracle.

Check your OPatch Version

[oracle@server1 db_ee_1]$ $ORACLE_HOME/OPatch/opatch version
OPatch Version:

Create the OCM Responsefile for Patching

[oracle@server1 bin]$ $ORACLE_HOME/OPatch/ocm/bin/emocmrsp -output /home/oracle/ocm.rsp
OCM Installation Response Generator - Production
Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.

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
The OCM configuration response file (/home/oracle/ocm.rsp) was successfully created.

After then run the following command on each cluster Node (to patch RAC and GI togehter). Be aware that the original readme is missing the apply argument. In my case there are both generation of database installed (11G and 12C), so there will be a warning that some components cannot be patched. You also need more then 10 gigabyte of free Diskspace.

[root@server1 17272829]# $GI_HOME/OPatch/opatchauto apply /home/oracle/install/patch/17272829 -ocmrf /home/oracle/ocm.rsp 
OPatch Automation Tool
Copyright (c) 2013, Oracle Corporation.  All rights reserved. Alle Rechte vorbehalten.

OPatchauto version :
OUI version        :
Running from       : /u01/app/12.1.0/grid

opatchauto log file: /u01/app/12.1.0/grid/cfgtoollogs/opatchauto/17272829/opatch_gi_2013-10-27_11-17-41_deploy.log

Parameter Validation: Successful
Grid Infrastructure home:
RAC home(s):
Following home(s) are not patchable as its version is less than

Configuration Validation: Successful

Patch Location: /home/oracle/install/patch/17272829
Grid Infrastructure Patch(es): 17027533 17077442 17303297 
RAC Patch(es): 17027533 17077442 

Patch Validation: Successful

Stopping RAC (/u01/app/oracle/product/12.1.0/db_ee_1) ... Successful
Stopping RAC (/u01/app/oracle/product/12.1.0/db_se_1) ... Successful

Applying patch(es) to "/u01/app/oracle/product/12.1.0/db_ee_1" ...
Patch "/home/oracle/install/patch/17272829/17027533" successfully applied to "/u01/app/oracle/product/12.1.0/db_ee_1".
Patch "/home/oracle/install/patch/17272829/17077442" successfully applied to "/u01/app/oracle/product/12.1.0/db_ee_1".
Applying patch(es) to "/u01/app/oracle/product/12.1.0/db_se_1" ...
Patch "/home/oracle/install/patch/17272829/17027533" successfully applied to "/u01/app/oracle/product/12.1.0/db_se_1".
Patch "/home/oracle/install/patch/17272829/17077442" successfully applied to "/u01/app/oracle/product/12.1.0/db_se_1".

Stopping CRS ... Successful
Applying patch(es) to "/u01/app/12.1.0/grid" ...
Patch "/home/oracle/install/patch/17272829/17027533" successfully applied to "/u01/app/12.1.0/grid".
Patch "/home/oracle/install/patch/17272829/17077442" successfully applied to "/u01/app/12.1.0/grid".
Patch "/home/oracle/install/patch/17272829/17303297" successfully applied to "/u01/app/12.1.0/grid".
Starting CRS ... Successful

Starting RAC (/u01/app/oracle/product/12.1.0/db_ee_1) ... Successful

Starting RAC (/u01/app/oracle/product/12.1.0/db_se_1) ... Successful

Apply Summary:
Following patch(es) are successfully installed:
GI Home: /u01/app/12.1.0/grid: 17027533, 17077442, 17303297

opatchauto succeeded.

If you encounter a message like this, check your Logfiles. The error could be more then a harmless warning Message. In my case there was a error on mounting a PDB.

[WARNING] SQL changes, if any, could not be applied on the following database(s): DB12EE, ECDB1, SCDB1 ... Please refer to the log file for more details.

From the Logfile

DBD::Oracle::st execute failed: ORA-04031: unable to allocate 801456 bytes of shared memory ("shared pool","unknown object","PDB Dynamic He","PDB prmtzdini tz region") (DBD ERROR: OCIStmtExecute) 
[for Statement "ALTER PLUGGABLE DATABASE pdb$seed OPEN READ ONLY"] at /u01/app/oracle/product/12.1.0/db_se_1/sqlpatch/sqlpatch.pm line 450, <LOGFILE> line 92.

Also if you try to start the ASM Instance which is not patched you can get a error similar to this.

SQL> startup
ORA-15135: cluster is not in the rolling patch

I encounter also a error like this:

DBD::Oracle::st execute failed: ORA-20006: Number of RAC active instances and opatch jobs configured are not same
ORA-06512: at "SYS.DBMS_QOPATCH", line 1007
ORA-06512: at line 4 (DBD ERROR: OCIStmtExecute) [for Statement "DECLARE
       x XMLType;
       x := dbms_qopatch.get_pending_activity;
       ? := x.getStringVal();
     END;" with ParamValues: :p1=undef] at /u01/app/oracle/product/12.1.0/db_se_1/sqlpatch/sqlpatch.pm line 824.

What i have done is to stop the first node and Patch the second node (because of the ASM Version mismatch).  If you are able to start both instances the Patch also succeed without the error above. Keep in mind that this was my way. If you are not sure how to handle this error open a SR to Oracle.

You can also check the registry$history to see if your PSU is applied.

SQL> select namespace,version, substr(comments,1,30) from registry$history;

---------------- ---------------- ---------------------
SERVER          Patchset
SERVER          Patchset
SERVER          PSU

As always, comments are welcome.

Ein Gedanke zu “ (October 2013) Patch Set Update (PSU)

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:


Du kommentierst mit Deinem WordPress.com-Konto. Abmelden /  Ändern )

Google Foto

Du kommentierst mit Deinem Google-Konto. Abmelden /  Ändern )


Du kommentierst mit Deinem Twitter-Konto. Abmelden /  Ändern )


Du kommentierst mit Deinem Facebook-Konto. Abmelden /  Ändern )

Verbinde mit %s