10 May 2011

Step by Step Configure Oracle Parallel Concurrent Processing ( Oracle PCP )

3.1 Configure Parallel Concurrent Processing

3.1.1 Check prerequisites for setting up Parallel Concurrent Processing

To set up Parallel Concurrent Processing (PCP), you must have more than one Concurrent Processing node in your environment

3.1.2 Set Up PCP

  1. Edit the applications context file via Oracle Applications Manager, and set the value of the variable APPLDCP to ON.
  2. Execute AutoConfig by running the following command on all concurrent processing nodes:

$ $INST_TOP/admin/scripts/adautocfg.sh

  1. Source the Applications environment.
  2. Check the tnsnames.ora and listener.ora configuration files, located in $INST_TOP/ora/10.1.2/network/admin. Ensure that the required FNDSM and FNDFS entries are present for all other concurrent nodes.
  3. Restart the Applications listener processes on each application tier node.
  4. Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator Responsibility. Navigate to Install > Nodes screen, and ensure that each node in the cluster is registered.
  5. Verify that the Internal Monitor for each node is defined properly, with correct primary and secondary node specification, and work shift details. For example, Internal Monitor: Host2 must have primary node as host2 and secondary node as host3. Also ensure that the Internal Monitor manager is activated: this can be done from Concurrent > Manager > Administrator.
  6. Set the $APPLCSF environment variable on all the Concurrent Processing nodes to point to a log directory on a shared file system.
  7. 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.)
  8. Set profile option 'Concurrent: PCP Instance Check' to OFF if database instance-sensitive failover is not required. By setting it to 'ON', a concurrent manager will fail over to a secondary Application tier node if the database instance to which it is connected becomes unavailable for some reason.


3.1.3 Set Up Transaction Managers ,Internal Concurrent Manager ,Standard Manager

  1. Shut down the application services (servers) on all nodes
  2. Shut down all the database instances cleanly in the Oracle RAC environment, using the command:

SQL>shutdown immediate;

  1. Edit $ORACLE_HOME/dbs/<context_name>_ifile.ora. Add the following parameters:

      • _lm_global_posts=TRUE
      • _immediate_commit_propagation=TRUE

  1. Start the instances on all database nodes, one by one.
  2. Start up the application services (servers) on all nodes.
  3. Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator responsibility. Navigate to Profile > System, change the profile option ‘Concurrent: TM Transport Type' to ‘QUEUE', and verify that the transaction manager works across the Oracle RAC instance.
  4. Navigate to Concurrent > Manager > Define screen, and set up the primary and secondary node names for transaction managers.
  5. Restart the concurrent managers.
  6. If any of the transaction managers are in deactivated status, activate them from Concurrent > Manager > Administrator.
Transaction Manager (Internal use only)

Standard Manager    

Internal Concurrent Manager      

Internal Monitor for Apps-1

Internal Monitor for Apps-2

CRP Manager

3.1.4 Set Up Load Balancing on Concurrent Processing Nodes

  1. Edit the applications context file through the Oracle Applications Manager interface, and set the value of Concurrent Manager TWO_TASK (s_cp_twotask) to the load balancing alias (OURPROD_balance>).

Note:  Windows users must set the value of "Concurrent Manager TWO_TASK" (s_cp_twotask context variable) to the instance alias.

  1. Execute AutoConfig by running $INST_TOP/admin/scripts/adautocfg.sh on all concurrent nodes.


Then restart your application tier it will work .

No comments: