Wednesday, July 1, 2020

Configuring Password Encryption RMAN Backups and Perform Restore/Recovery on Different host


Configuring encrypted RMAN Backups and Perform Restore/Recovery on Different host

Encryption mode:  Password Encryption of Backups (Password mode)

This mode uses only password protection. Password should be provided when creating and restoring encrypted backups.

Use the "only" keyword at the end to use only password encryption.

 Perform encrypted RMAN Backup

·         Connect to database using RMAN and perform backup

 In the RMAN script before run block execute below command

 RMAN> set encryption on identified by 'rmanbkp123' only;

 

 

·         To perform restore/recovery on same host. Password should be provided in the RMAN block;

 Startup nomount

Restore the controlfile

Mount the database

Restore the database

Recover the database

Open the database 

Perform encrypted RMAN backup Restore / Recovery on different host

·         Copy the RMAN Disk backup to the destination server.

·         In case of the Tape backup, Tape should be accessible from destination server. 

·         Perform the restore. Here we are using Duplicate command with Disk Backup.

 Below are the steps and command for duplicate

 startup nomount;

rman auxiliary /

 set decryption identified by 'rmanbkp123';

run

{

ALLOCATE AUXILIARY CHANNEL ch1 DEVICE TYPE DISK;

DUPLICATE DATABASE TO DUPTEST BACKUP LOCATION '/stage/rman_bkp/' ;

} 

                Note: In case of Multitenant both CDB and PDB will be restored

 ·         In Case of Tape restore below is the sample RMAN run block.

Depends on the Backup solution SBT_TAPE parameter changes. (below is for EMC networker)

 set decryption identified by 'rmanbkp123';

run {

 ALLOCATE AUXILIARY CHANNEL ch1 DEVICE TYPE 'SBT_TAPE' parms 'ENV=(NSR_SERVER=<Backup Server Name>,NSR_CLIENT=oraprd01,NSR_DATA_VOLUME_POOL=<Pool Name>)';

 duplicate target database to DUPTEST until time 'SYSDATE-1' ;

 }

 

                               

 

 

               

 

 


Tuesday, June 30, 2020

Configure OAM Webgate Load balancer on a EBS integrated environment

Configure OAM Webgate Load balancer

 

In a High available OAM configuration integrated with EBS 12.2,  Enable the communication via Load balancer instead of direct backend server communication.

 Log in to your OAM console & navigate to Agents

 Search for the agent "ERP*_hostname.**.**_443"                            

Change Max connections value from 1 to 4.

 Add webgate load balancer entry in the Primary List tab

Change Max connections under primary server list from 1 to 8       

 ebsoam.domain à is the Load balancer name

 

 

 Delete the oam_server1 and oam_server2 entries.

 

Save the changes & download the artifacts & copy them to webgate instance directory.

 artifacts file can be found under $OAMDomain\output\"ERP*_hostname.**.**_443"

 

In EBS artifacts files will be present under, replace it

$IAS_ORACLE_HOME/instances/EBS_web_${TWO_TASK}_OHS1/config/OHS/EBS_web_${TWO_TASK}/webgate/

 

  

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Register (adProvisionEBS) Oracle E-Business Suite with Oracle Access Manager fails


 

Register Oracle E-Business Suite with Oracle Access Manager fails

Issue Description:

 While execute adProvisionEBS.pl it fails

 Exception in thread "main" java.lang.UnsupportedClassVersionError: oracle/security/am/engines/common/identity/provider/exceptions/TestConnectionException : Unsupported major.minor version 52.0

 

 Solution:

 This is due to latest Java 1.7 update was deployed. Revert to old jdk/java and rerun the script

 cd $COMMON_TOP/util

mv jdk32_old jdk32


dipConfigurator fails with “Invalid Ldap connection details” error

dipConfigurator fails with “Invalid Ldap connection details” error

 

Issue Description:

 As part of Configuring Oracle Directory Integration Platform for Oracle Internet Directory

 While running dipConfigurator (: $ORACLE_HOME/bin/dipConfigurator setup) it fails with below error

 “Invalid Ldap Connection Details”


Solution:

 Setting jdk.tls.disabledAlgorithms with correct parameters has resolved the DIP issue.

 

jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize < 768, DESede, EC keySize < 224

 

cd to JAVA_HOME/jre/lib/security directory

Make a copy of java.security.

Open the file and locate "jdk.tls.disabledAlgorithms"

 

Comment the existing and add below

 

jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize < 768, DESede, EC keySize < 224

 

 

Reference:

 

DIP 12c: ODIP Application Is Down With "Credential Not Found" Error- dipConfigurator Fails With: Found Invalid Inputs : Invalid Ldap Connection Details Specified (Doc ID 2507206.1)

"Invalid Ldap connection details specified." When Executing 12c dipConfigurator(Doc ID 2314756.1)

SSL Connection to Remote Server Fails After JDK Upgrade to JDK 7 Update 181 or Later (Doc ID 2448170.1)