Understanding and Configuring PCP in Oracle EBS
1. What is PCP?
PCP stands
for Parallel Concurrent Processing.
It
allows Concurrent Managers in Oracle E-Business Suite to run
on multiple nodes instead of just one.
Why use
PCP?
- Load Balancing – Distributes workload across multiple nodes for better performance.
- High Availability – If one node fails, managers can failover to another node.
- Failover and Failback – Automatically moves
managers to available nodes during failure and back when the node is
restored.
2. PCP Setup Types
- RAC Database Setup – Commonly used with PCP.
- Non-RAC Setup – PCP can still work without RAC by using TNS aliases for connectivity.
3. How PCP Works
- Each node runs Concurrent Managers.
- Managers connect to the database
using TWO_TASK (TNS alias) defined in:
adcmctl.sh
gsmstart.sh
4. Internal Monitor
(IMON)
- Optional Service but recommended.
- Monitors the Internal Concurrent Manager (ICM).
- If the primary node fails:
- IMON detects failure.
- Starts ICM and other managers on another node.
- Best Practice: Enable IMON on all nodes
where ICM can start.
5. Internal
Concurrent Manager (ICM)
- Monitors other managers during PMON cycle.
- Can run on any concurrent processing node.
- Ensures managers are up and running.
6. Service Manager
(FNDSM)
- Required for PCP.
- Manages services/managers on each node.
- Started by APPS TNS Listener.
- Listener spawns Service Manager when needed.
- Stops when ICM stops.
Environment
Setup:
- Defined in gsmstart.sh and APPSORA.env.
7. Key Benefits of
PCP
- Better Performance: Workload distributed across nodes.
- High Availability: Failover capability.
- Scalability: Add more nodes easily.
Below is an
example of how these parameters appear in the EBS context file:
-bash-4.2$
cat $CONTEXT_FILE |grep s_appldcp
<APPLDCP oa_var="s_appldcp">ON</APPLDCP>
-bash-4.2$
cat $CONTEXT_FILE |grep s_applcsf
<APPLCSF
oa_var="s_applcsf">/u01/oracle/R122/DEV/fs_ne/DEV_<SERVER_NAME>/logs/appl/conc</APPLCSF
Comments
Post a Comment