Configure Parallel Concurrent Processing (Note ID:362135.1)
NOTE: This section is for UNIX platforms only. Windows users should follow the instructions in Appendix F for configuration of Parallel Concurrent Processing and transaction managers.
a) PCP Prerequisites:
---------------------
It is assumed that you have more than one Concurrent processing tiers in your environment to setup PCP.
If you do not have this refer to Oracle MetaLink Note: 230672.1 for cloning of Applications tier.
b) Set Up PCP:
-------------
1. Execute AutoConfig by using $COMMON_TOP/admin/scripts/<context_name>/adautocfg.sh on all concurrent nodes.
2. Source the application environment by using $APPL_TOP/APPSORA.env
3. Check the configuration files tnsnames.ora and listener.ora located under 8.0.6 ORACLE_HOME at $ORACLE_HOME /network/admin/<context>. Ensure that you have information of all the other concurrent nodes for FNDSM and FNDFS entries.
4. Restart the application listener processes on each application node.
5. Logon to Oracle E-Business Suite Applications using SYSADMIN in login and System Administrator Responsibility. Navigate to Install > Nodes screen and ensure that each node in the cluster is registered.
6. Verify whether the Internal Monitor for each node is defined properly with correct primary and secondary node specification and work shift details. Also make sure the Internal Monitor manager is activated by going into Concurrent -> Manager -> Administrator and activate the manager.
(e.g. Internal Monitor: Host2 must have primary node as host2 and secondary node as host3)
7. Set the $APPLCSF environment variable on all the CP nodes pointing to a log directory on a shared file system.
8. Set the $APPLPTMP environment variable on all the CP nodes to the value of the UTL_FILE_DIR entry in init.ora on the database nodes. This value should be pointing to a directory on a shared file system.
9. Set profile option ' Concurrent: PCP Instance Check' to OFF if DB instance sensitive failover is not required. By setting it to 'ON' Concurrent Managers will failover to a secondary middle-tier node when database instance it is connected goes down.
NOTE: This section is for UNIX platforms only. Windows users should follow the instructions in Appendix F for configuration of Parallel Concurrent Processing and transaction managers.
a) PCP Prerequisites:
---------------------
It is assumed that you have more than one Concurrent processing tiers in your environment to setup PCP.
If you do not have this refer to Oracle MetaLink Note: 230672.1 for cloning of Applications tier.
b) Set Up PCP:
-------------
1. Execute AutoConfig by using $COMMON_TOP/admin/scripts/<context_name>/adautocfg.sh on all concurrent nodes.
2. Source the application environment by using $APPL_TOP/APPSORA.env
3. Check the configuration files tnsnames.ora and listener.ora located under 8.0.6 ORACLE_HOME at $ORACLE_HOME /network/admin/<context>. Ensure that you have information of all the other concurrent nodes for FNDSM and FNDFS entries.
4. Restart the application listener processes on each application node.
5. Logon to Oracle E-Business Suite Applications using SYSADMIN in login and System Administrator Responsibility. Navigate to Install > Nodes screen and ensure that each node in the cluster is registered.
6. Verify whether the Internal Monitor for each node is defined properly with correct primary and secondary node specification and work shift details. Also make sure the Internal Monitor manager is activated by going into Concurrent -> Manager -> Administrator and activate the manager.
(e.g. Internal Monitor: Host2 must have primary node as host2 and secondary node as host3)
7. Set the $APPLCSF environment variable on all the CP nodes pointing to a log directory on a shared file system.
8. Set the $APPLPTMP environment variable on all the CP nodes to the value of the UTL_FILE_DIR entry in init.ora on the database nodes. This value should be pointing to a directory on a shared file system.
9. Set profile option ' Concurrent: PCP Instance Check' to OFF if DB instance sensitive failover is not required. By setting it to 'ON' Concurrent Managers will failover to a secondary middle-tier node when database instance it is connected goes down.
This is Very good post..
ReplyDeleteThanks