Skip to main content

Posts

Showing posts from February, 2021

/jre/Linux_x64/1.6.0/bin/java: No such file or directory

  Java Error while launching Rapidwiz  ./buildStage.sh: line 142: /u01/software/ebs/1220/startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory eror unzipping shiphome ... Rapidwiz is expecting a 32-bit version of the JDK, and the error occurs because the only version available is 64-bit. The issue is discussed in the following unpublished defect: Bug 24386615 – STARTCD SHOULD BE UPDATED TO USE 64 BIT VERSION OF THE JDK/JRE . Solution: Copy a 64 bit version of the JDK from any 12c Oracle Home or download it from internet.  1.  Backup the existing JDK located in  startCD/Disk1/rapidwiz/jre/Linux_x64/ mv 1.6.0 1.6.0_old mkdir 1.6.0 2.  Copy the contents of jre directory unded the 1.6.0 directory  3.  Retest  Rapidwiz  and confirm the error is resolved.

Rolling Forward a Physical Standby Database using RMAN Incremental Backup

   Rolling Forward a Physical Standby Database using RMAN Incremental Backup There is a huge gap around 5k between the archive logs of Standby Database and Primary Database.  Instead of waiting for the Redo Apply to sync the archive logs, we follow the below steps to sync the Standby database.  1. Cancel the Managed Recovery ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; 2. Find the SCN of the Standby Database SELECT CURRENT_SCN FROM V$DATABASE; 11878709541860 select min(checkpoint_change#) from v$datafile_header; 11878709541861 We have to use the lower of the two scn values.  11878709541860 3. Connect to Primary and Identify the datafile needed for backup SELECT FILE#, NAME FROM V$DATAFILE WHERE CREATION_CHANGE# > 11878709541860; 322 +DATA/PRODNEW/DATAFILE/data.593.1063685263 323 +DATA/PRODNEW/DATAFILE/data.594.1063879113 324 +DATA/PRODNEW/DATAFILE/data.595.1063879183 325 +DATA/PRODNEW/DATAFILE/data.596.1063879207 326 +DATA/PRODNEW/DATAFIL...