IDM disaster recovery

In Production environment there are unavoidable cases that the live servers might go down.During this failure time disaster recovery should happen.Considering that there are two live environment(DC and DR)
In case of failure in DC,DR should be brought up

Prerequisites

1.Export the OIM database schema using export from DC to DR.
2.Take the backup of the OIM_HOME in both the nodes 3.Backup the applications server files and its directories

Changes to be done in OIM

1.Bring down the application server in both the nodes.
Execute the command as given below.Goto the path

$ORACLE_HOME/opmn/bin
And execute ./opmnctl stopall

2.Copy the .xlKeystore ,.xldatabase and xlconfig.xml file from DC-Prod machine and copy these files in DR-Prod

Files to be copied	Path of the file in DC-Prod	Path of the file in DR-Prod
.xlkeystore	oim_server/xellerate/config	oim_server/xellerate/config
.xldatabasekey	oim_server/xellerate/config	oim_server/xellerate/config
Xlconfig.xml	oim_server/xellerate/config	oim_server/xellerate/config

3. Edit the xlconfig.xml file and locate the
directdb……DirectDB
Change the database details from DC-Prod to DR-Prod

4. Restart the application server in both the nodes.

Changes in DB

1.Take the backup of both dc-prod database as well as dr-prod database
2.Make sure that the DB schema username is same in both DC as sell as DR database.
Ex: xloim in both the databases.
3.Export the database from DC-Prod and import it into DR-Prod
4.Restart the database in DR-Prod.

Tips to Troubleshoot

1.After following the steps to cloning and still you are unable to login to the application using xelsysadm , login to database instances in both DC-Prod and DR-Prod and execute

select usr_password from USR where USR_LOGIN='XELSYSADM';

This will query a encrypted value.The encrypted value should be same in both DC and DR. If the value is not same, then the password is different for both the databases.

2.Login to the Admin Console and change the password as usual.
3.Open xlconfig.xml present in OIM_home/xellerate/config folder.
4.In the scheduler section, add the XLPassword line as shown below:

scheduler
xlusername xelsysadm XLUserName
xlpassword encrypted="false">NEW PASSWORD XLPassword
...
Scheduler

5.Restart the OC4J application server.
6.After confirming that you can log on to the Admin Console with the new password AND that the scheduler can start tasks with the new log on information, you can delete the backup xlconfig.xml.0 file that now exists in the config folder.