Patching with opatch (e.g. a PSU) will always change ONLY the last number (platform specific release number) – the way to determine this number for an Oracle database is: $ORACLE_HOME/OPatch/opatch lsinventory
Patch Set Update Availability The latest available PSUs are listed in the My Oracle Support notes indicated below: Product My Oracle Support Note Database Document 756671.1 Enterprise Manager Document 822485.1 WebLogic Server Document 859115.1 Oracle Elastic Exalogic Cloud Software Document 1456286.1
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node. For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows: cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / …
How to find latest patch sets for Oracle patching – Quick Reference to Patch Numbers oracle support doc id: 1454618.1 Applied with opatch, 12c forward datapatch, and 11gr2 backward $ORACLE_HOME/rdbms/admin/catbundle.sql
Without running runInstaller, dbca, opatch, or rman, pick up an existing DB and the Oracle binaries and move them to another server, here is one way (without all the screen shots): Assumption are: You only have one home and database under your $ORACLE_BASE – this example only does one DB – but you could modify …
Overview Here is the process I used to apply the Oracle 2016 PSU 22191676 to Grid / Oracle Stand Alone 12.1.0.2 environment using opatchauto. Effectively bringing the environment to 12.1.0.2.6 (12.1.0.2.160119) My environment has a 12.1.0.2.0 database ASM based standalone database – installed an administered with the grid infrastructure / ASM / listener owned by …
Apply 2016 PSU 22191676 to a Grid / Oracle Stand Alone 12.1.0.2 Using opatchauto Read More »