Quantcast
Channel: Doyensys Allappsdba Blog..
Viewing all articles
Browse latest Browse all 1640

Migrating Oracle ERP Applications from one server to another in Windows Environment

$
0
0
Below are the steps required to be done in order to migrate Oracle ERP Applications from one server to another. These steps are successfully tested in my Test Oracle ERP Servers.

Note 1: My source and Target Environment is EBS 12.1.3
Note 2: This is applicable for Windows 2008 R2 server but somewhat similar steps can be applicable to Windows 2012 R2 or Windows 2016 server)
Note 3:All the steps are done on the Target Application Server
Note 4:Make sure you change the source server name and assign the same name to target Windows server in order to have backup of source Application server and not much changes is required in CONTEXT FILE if you have same Drives on Source and Target Application server.
Note 5: Please change server names,Directory structure and Environment files based on your servers.
as one need to spend some time in order to do this activity successfully.

Preparatory Steps:

1. Install MKS Toolkit on Target Server( we can also install CYGWIN ) . It is recommended to install MKS from Oracle Support.
2.Install VISUAL Studio of same Windows OS version(2008 R2).

Planning and Execution Steps:

1.Shutdown Oracle ERP Applications(adstpall.sh) Source(ERP APPLICATIONS)
Command prompt Run As Administrator: Source Env file APPSERP.env
cd $ADMIN_SCRIPTS_HOME
./adstpall.sh


2.Check firewall and connectivity from DB to Apps Tier and verify the port is open using telnet on Target(ERP APPLICATIONS)

telnet hostname port
telnet testhost 1521
connected means it is working fine, if it says trying add the firewall rules and allow port and try again.

3.Copy Apps Files from Source to target Target Server (Initiate copy From Target Server)

4.Modify PATH Environment variable to execute perl K:\oracle\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread; => In First line and remove rest of the variables if exists.
5.Change compatibility to Windows Server 2003 SP1 in K:\oracle\apps\tech_st\10.1.2\oui\bin for setup.exe 

6.Change compatibility to Windows Server 2003 SP1 in K:\oracle\apps\tech_st\10.1.3\oui\bin for setup.exe
7.Make sure INST_TOP is renamed on new Target(ERP APPLICATIONS)

(Run as Administrator on new command prompt).
cd K:\oracle\apps\apps_st\comn\clone\bin
 Execute  perl adcfgclone.pl appsTier
8.Verify logs of adcfgclone and confirm no errors exists.
adcfgclone logs Applications tier:

$COMMON_TOP/clone/bin/CloneContext_<timestamp>.log
This log shows the entries selected during execution of adcfgclone command


9.Execute autoconfig on Apps Tier and copy env file APPSERP_testhost.cmd from backup to APPL_TOP

cd $ADMIN_SCRIPTS_HOME
./adautocfg.sh

10.Replace ADMIN Directory(K:\oracle\inst\apps\ERP APPLICATIONS_testhost\ora\10.1.2\network) with admin_bkp and Reboot the Target(ERP APPLICATIONS)
11.Compare Services properties in old and new server and set accordingly. Restart the new Target (ERP APPLICATIONS) Application server

12.Compare Firewall rules in old and New  PROD Apps servers and copy accordingly and Validate with telnet

13.Execute cmclean(K:\oracle)
14.Start the Applications (adstral.sh) Target (ERP APPLICATIONS)

cd $ADMIN_SCRIPTS_HOME
./adstral.sh

Post Execution and Sanity Checks:
1.Configure Oracle Workflow inbound and outbound server settings and validate workflow mailer is up and running and test mailer
2.Complete Sanity checks for Database ,Applications, Concurrent Programs ,SSO and Workflow Mailer

Viewing all articles
Browse latest Browse all 1640

Trending Articles