opatch

11gR2 and older opatch post steps – straight from a readme.html – don't forget to run @catbundle.sql psu apply

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 / …

11gR2 and older opatch post steps – straight from a readme.html – don't forget to run @catbundle.sql psu apply Read More »

On Linux Clone a 12c $ORACLE_HOME + patches, $ORACLE_BASE, and a database to a new server

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 …

On Linux Clone a 12c $ORACLE_HOME + patches, $ORACLE_BASE, and a database to a new server Read More »

Apply 2016 PSU 22191676 to a Grid / Oracle Stand Alone 12.1.0.2 Using opatchauto

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 »