Skip to main content

Posts

Showing posts from August, 2019

How to Upgrade JDK 1.6 to 1.7 in GRID and RDBMS HOME

How to Upgrade JDK 1.6 to 1.7 in GRID and RDBMS HOME Pre-Patching steps: Step 1: Change the permissions for all files located under RDBMS and Grid Home JDK directory. GRID and RDBMS Homes: chmod -R 755 $ORACLE_HOME/jdk Step 2: Check the conflicts for both GRID and RDBMS homes opatch prereq CheckConflictAgainstOHWithDetail -ph ./ Step 3: Verify the current version of JDK under Grid and RDBMS homes: /u01/app/oracle/product/12.1.0.2/db_1/jdk/bin  ./java -version java version "1.6.0_211" Java(TM) SE Runtime Environment (build 1.6.0_211-b11) Java HotSpot(TM) 64-Bit Server VM (build 20.211-b11, mixed mode) /u01/app/oracle/product/12.1.0.2/db_1/jdk/bin > cd /u01/app/12.1.0.2/grid/jdk/ /u01/app/12.1.0.2/grid/jdk cd bin /u01/app/12.1.0.2/grid/jdk/bin <dbname> > ./java -version java version "1.6.0_211" Java(TM) SE Runtime Environment (build 1.6.0_211-b11) Java HotSpot(TM) 64-Bit Server VM (build 20....

To fix huge lag between primary and DR using 12c feature: 12c Recover from service

Scope If transport or apply lag is huge difference, then we can fix using 12c new feature “Recover from Service”. Prerequisites : Oracle Net connectivity is established between the physical standby database and the primary database. You can do this by adding an entry corresponding to the primary database in the tnsnames.ora file of the physical standby database. The password files on the primary database and the physical standby database are the same. The COMPATIBLE parameter in the initialization parameter file of the primary database and physical standby database is set to 12.0 or higher. Start RMAN and connect as target to the physical standby database. Detailed Steps: Step 1: Stop the MRP process in standby database. If dg broker: Edit database <dbname> set state=’APPLY-OFF’; Step 2:   Shut down the standby database and mount the same. Shut immediate;   (srvctl stop database –d <dbname>)  ...