PCP

Oracle EBS - Configure Parallel Concurrent Processing PCP

How Parallel Concurrent Processing Works

Concurrent Managers

With parallel concurrent processing, each node with concurrent managers may or may not be running an ORACLE instance. On a node that is not running ORACLE, the concurrent manager(s) connect via SQL*Net to a node that is running ORACLE.

To each concurrent manager, you assign a primary and a secondary node. Initially, a concurrent manager is started on its primary node. In case of node or ORACLE instance failure, a concurrent manager migrates to its secondary node.

A concurrent manager migrates back to its primary node once that node becomes available. During migration, the processes of a single concurrent manager may be spread across its primary and secondary nodes.

Internal Concurrent Manager

The Internal Concurrent Manager can run on any node, and can activate and deactivate concurrent managers on the same or other nodes. Since the Internal Concurrent Manager must be active at all times, it needs high fault tolerance. To provide this fault tolerance, parallel concurrent processing uses Internal Monitor Processes.

Internal Monitor Processes

The sole job of an Internal Monitor Process is to monitor the Internal Concurrent Manager and to restart that manager should it fail. The first Internal Monitor Process to detect that the Internal Concurrent Manager has failed restarts that manager on its own node.

Only one Internal Monitor Process can be active on a single node. You decide which nodes have an Internal Monitor Process when you configure your system. You can also assign each Internal Monitor Process a primary and a secondary node to ensure fail over protection.

Internal Monitor Processes, like concurrent managers, can have assigned work shifts, and are activated and deactivated by the Internal Concurrent Manager.

Log and Output File Access

The concurrent log and output files from requests that run on any node are accessible on-line from any other node. Users need not log onto a node to view the log and output files from requests run on that node.

Parallel Concurrent Processing Configuration

1. Execute AutoConfig by running $INST_TOP/admin/scripts/adautocfg.sh on all concurrent manager nodes.2. Source the application environment.

3. Check the configuration files tnsnames.ora and listener.ora located at

$INST_TOP/ora/10.1.2/network/admin.

Ensure that you have information of all the other concurrent nodes for FNDSM and FNDFS entries.

4. Log on to Application as SYSADMIN, Then choose the System Administrator Responsibility.

Navigate to Install > Nodes screen and ensure that each node in the cluster is registered.

5. Verify whether the Internal Monitor for each node is defined properly with correct primary and secondary nodes specification and work shift details. Also ensure that the Internal Monitor manager is activated by going to Concurrent > Manager > Administrator and activating the manager.

Also the work shifts were not present. Set them as 24 hours and the processes was set to 1.Go to the Concurrent > Manager > Administrator screen and activate these managers.

6. Set the $APPLCSF environment variable on all the concurrent processing nodes pointing to a log directory on a shared file system. To do this edit the context file as follow:

$ grep -i applcsf $CONTEXT_FILE

/u01/app/PROD/inst/apps/$CONTEXT_NAME/logs/appl/conc

Changed it to :

/u01/app/PROD/inst/apps/DBNAME/logs/appl/conc

Do not run autoconfig yet, you have to make more changes in the below step.

7. Set the $APPLPTMP environment variable on all the concurrent processing 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. We need this to be on a file system, that is shared across all the concurrent manager nodes and is also writable by the owner of the oracle db.

If the UTL_FILE_DIR need to be changed; then change it and restart the DB.

Same APPLPTMP the APPLTMP needs to be point to a shared file system.

8. After those modifications Run the autoconfig.

9. Set profile option ' Concurrent: PCP Instance Check' to OFF if database instance-sensitive failover is not required. By setting it to 'ON', Concurrent Managers will fail over to a secondary Application tier node if the database instance they are connected to fails.

Set Up Transaction Managers

1. Shut down the application services (servers) on all nodes.

2. In the Oracle RAC environment, shutdown all the database instances cleanly with the command:

srvctl stop database -d PROD

3. Edit $ORACLE_HOME/dbs/_ifile.ora. Add the following parameters:

_lm_global_posts=TRUE

_immediate_commit_propagation=TRUE

4. Start the instances on all database nodes, one by one.

5. Start up the application on all application nodes.

6. Log on to Oracle E-Business Suite Release 12 using SYSADMIN login and

System Administrator Responsibility.Navigate to Profile => System and change the

profile option Concurrent: TM Transport Type to 'QUEUE' and verify the transaction manager works across the RAC instance.

7. Navigate to Concurrent > Manager > Define screen, and set up the primary and secondary node names for transaction managers.

8. Restart the concurrent managers.

9. If any of the transaction managers have a deactivated status, activate them using

Concurrent > Manager > Administrator