Tuesday, July 13, 2010

Changing hostname in ORACLE APPS

Hostname/Server Name change on Oracle Application servers
Hi All,

Below are the steps followed to change the Hostname/Server Name change on Oracle Application servers.
Note:- Refer document 338003.1 and 341322.1
1. Deregister the current database server (Required)
As the database hostname and/or port will be changed, the current database server node needs to be de-registered.
To deregister the current database server node, run the following command as the owner of the Oracle RDBMS file system and current database instance :
perl /appsutil/bin/adgentns.pl appspass= \
contextfile= -removeserver

2. Deregister the current Applications server (Required)
As the Applications hostname will be changed, the current Applications server node needs to be de-registered.
To deregister the current Applications server node, run the following command as the owner of the Oracle Applications file system and current database instance:
perl $AD_TOP/bin/adgentns.pl appspass= \
contextfile= -removeserver
3. Update the AutoConfig Context files of Database and Application servers
Open conext file using vi editor, press esc :%s/sony/sonydadc\.com/g
In the application server context file, make sure that s_javamailer_reply_to set to right value
4. Shutdown the Applications Tier Services (Required)
5. Shutdown the Database Listener (required)
6. Shutdown the Database
7. Change the machine hostname
8. Start the Database
9. Change the Listener.ora file to reflect the new host name
10. Start the listener
11. Reseed the Net Services Topology Model (Required)
a.Run AutoConfig on the Database Tier (Required)
Run AutoConfig on the database tier node using the following syntax :
cd /appsutil/bin/
./adconfig.sh contextfile=/appsutil/_.xml
b. Run AutoConfig on the Applications Tier(s) (Required)
Run AutoConfig on the Applications tier node using the following syntax :
cd /admin/scripts/
./adautocfg.sh appspass=
12. Relogin into Application server and source the environment
13. Start the Applications Tier Services
14. Finishing Tasks
Follow the steps in Note: 230672.1 Section 3: Finishing Tasks
Connect as apps
update apps.fnd_profile_option_values b
set b.profile_option_value = replace(b.profile_option_value,'http://tapplohr.sony:8000','http://tapplohr.sonydadc:8000')
where b.profile_option_value like '%http://tapplohr.sony:8000%';

commit;


select text_value from WF_NOTIFICATION_ATTRIBUTES
where upper(text_value) like ('%TAPPLOHR%');

update WF_NOTIFICATION_ATTRIBUTES
set text_value = replace(text_value,'tapplohr.sony','tapplohr.sonydadc.com')
where upper(text_value) like ('%TAPPLOHR%');

commit;

select text_value from WF_ITEM_ATTRIBUTE_VALUES
where upper(text_value) like ('%TAPPLOHR%');
update WF_ITEM_ATTRIBUTE_VALUES
set text_value = replace(text_value,'tapplohr.sony','tapplohr.sonydadc.com')
where upper(text_value) like ('%TAPPLOHR%');

commit;

connect as / as sysdba
ALTER DATABASE RENAME GLOBAL_NAME TO HRDADC.SONYDADC.COM;

Make sure Workflow services are up and running.

Login as SYSADMIN, select Workflow Administrator Web Applications responsibility, go to Business Events – Systems – Query for old system name like HRDADC.SONY, click on update , and change the system name to HRDADC.SONYDADC.COM, and then apply.

connect as apps

update WF_AGENTS
set address=replace(address,'HRDADC.SONY','HRDADC.SONYDADC.COM');

commit;
Above steps for the below items which are in RED, For green one NO action required.
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE Value starts with http://[old web host] : Update to new web host
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE Value starts with "http://[old web host] : Update to new web host
WF_SYSTEMS GUID Create a new System defined as the new global Database name using the Workflow Administrator Web Applications responsibility.
WF_SYSTEMS NAME Value needs to be replaced with the Database global name
WF_AGENTS ADDRESS Update Database link with the new Database global name.
FND_FORM_FUNCTIONS WEB_HOST_NAME Update with the new web host name
FND_FORM_FUNCTIONS WEB_AGENT_NAME Update to point at the new PLSQL listener name
FND_CONCURRENT_REQUESTS LOGFILE_NAME Update with the correct path to the logfile directory
FND_CONCURRENT_REQUESTS OUTFILE_NAME Update with the new directory path on the Target System




Best regards,

Rafi.

No comments:

Post a Comment