How to configure Ora Apps when changing IP address and host name? 2

[InigoMontoya]

We have to change the hostname and ip address of the unix box that hosts both the Oracle database(9 r1) and Oracle Apps(11.5.7). Our company's network restructure requires this to be done. Has anyone gone through this or a similar situation before? I have no idea where to start. I know I can easily change it over on the system (unix) side but when it comes to Oracle DB and Oracle Apps, I'm pretty sure it is far more complicated.

 

[hollisall]

Hi:
We went through something similar when we set up an internal method for failover. We kept the original IP and hostname (the one used when Oracle Apps was installed) as a virtual IP and alias in DNS. The changes needed to get the installation to run again were all tnsnames entries in the application and middle tiers. If this is something that your IT group will allow, I can list the files and entries I made. The database itself will interrogate the box for the hostname when it starts, and the application will need a value for the new node.
Good luck,
LHSallwasser
Oracle DB

 

[InigoMontoya]

Yes please I would like the list of files that you modified. This would be a big help.

 

[hollisall]

Hi:
Based on these assumptions:
1. Oracle Apps version 11.5.8
2. Node1=database, concurrent managers, report server
3. Node2=web server, form server
4. IP/hostname change made to Node1 only

these changes were made:
1. Add entry FNDFS_new_node_name to file tnsnames.ora belonging to the appl manager on the Node1 (AKA middle tier). This is a copy of any existing FNDFS_node entry for the Concurrent Manager tier, and the host should continue to be the alias.
2. Add entry FNDSM_new_node_name_<SID> to file tnsnames.ora belonging to the appl manager on Node2 (admin tier). This is a copy of any existing FNDSM_node_<SID> entry for the Concurrent Manager tier, and the host should continue to be the alias.
3. On the admin tier as the appl manager, create a new .dbc file under $FND_TOP/secure. This is a copy of the existing hostname_<SID>.dbc file, just named with your new hostname. Copy this to the middle tier, same location and user.
4. In the application itself, as user sysadmin, add a new entry via Install, Nodes. This is your new hostname, which can be added to your aliased (the old) hostname previously listed.

These are the major changes. Depending on your installation, there may be other edits. Run through each of the test in AOL/JTest, and have clean logs when you start the components, especially the <SID>.mgr log on the admin tier, and the $APACHE_TOP/Jserv/etc/logs files, so that it's easier to troubleshoot any other issues. If the app starts normally, test the ability to print reports - this is another error-prone area.

Best regards - hope things turn out well,
LHSallwasser
Oracle DBA