In any auto-config enabled Oracle Apps Server will over ride the custom network entries in the tnsnames.ora and listener.ora in network/admin directories of either DB node or Apps node. But at times it is required to include some custom entries either at the DB Tier or Apps Tier and which should not be wiped out by the Oracle adautonfig script.This type of changes can be included in the ifile which can be seen at the end of those files entries. Like in the DB Tier the the custom tnsnames.ora entries can be added into <Context_name>_ifile.ora (Context Name = SID_HOSTNAME) and the custom listener.ora entries can be added on listener_ifile.ora.
Recently we were upgrading the RAC database in one our client and after successful upgradation of the database, it was our turn to integrate the database with Oracle Apps Server by enabling the adconfig for 11.5.10.2. We were successful at DB Tier, later we started the Application Services. We could able to see the login page and also able to login into Oracle, but when we tried to open the forms based application, they were not opening. It was taking very long time, but never opened the forms. Immediately we have ran the adadmin to regenerate the jar files with FORCE option and it was completed successfully. Later We bounced all the services and rechecked, but still we were stuck with the same issue.
After a very deep survey we found something, which very good lesson.Actually the the db upgrade was concluded in 2 parts: i) Upgrading the Server Configuration i.e. moving the DB from the lower-end resources to the Higher-end resources. ii) Upgrading the Database from 10g to 11g Release 2. There were some custom tnsnames.ora entries in the DB node which we were successfully over-raided while configuring the autoconfig and at the Application server node we were just making the changes in the Context file to see the new server in place of old server.But the there was an entry in ifile at Application Server node which was pointing to the old server, which internally disabling the Apache to start the Java Sessions.
Conclustion:
An ifile with custom entires are available in 3 places in Oracle Apps Server :
i) DB Tier
ii) the <806_ORACLE_HOME>/network/admin/<CONTEXT_NAME> and
iii) <IAS_ORACLE_HOME>/network/admin/<CONTEXT_NAME>
All these ifile entries are not edited by the autofig scripts.Need to check everytime before upgradation or migration of the Database or Application Server.
Recently we were upgrading the RAC database in one our client and after successful upgradation of the database, it was our turn to integrate the database with Oracle Apps Server by enabling the adconfig for 11.5.10.2. We were successful at DB Tier, later we started the Application Services. We could able to see the login page and also able to login into Oracle, but when we tried to open the forms based application, they were not opening. It was taking very long time, but never opened the forms. Immediately we have ran the adadmin to regenerate the jar files with FORCE option and it was completed successfully. Later We bounced all the services and rechecked, but still we were stuck with the same issue.
After a very deep survey we found something, which very good lesson.Actually the the db upgrade was concluded in 2 parts: i) Upgrading the Server Configuration i.e. moving the DB from the lower-end resources to the Higher-end resources. ii) Upgrading the Database from 10g to 11g Release 2. There were some custom tnsnames.ora entries in the DB node which we were successfully over-raided while configuring the autoconfig and at the Application server node we were just making the changes in the Context file to see the new server in place of old server.But the there was an entry in ifile at Application Server node which was pointing to the old server, which internally disabling the Apache to start the Java Sessions.
Conclustion:
An ifile with custom entires are available in 3 places in Oracle Apps Server :
i) DB Tier
ii) the <806_ORACLE_HOME>/network/admin/<CONTEXT_NAME> and
iii) <IAS_ORACLE_HOME>/network/admin/<CONTEXT_NAME>
All these ifile entries are not edited by the autofig scripts.Need to check everytime before upgradation or migration of the Database or Application Server.
No comments:
Post a Comment