PCP configuration in R12.

Pleasefollow the below steps

1)In DB, run these two commands as sysdba:
a. alter system set �_lm_global_posts�=TRUE scope=spfile sid=�*�;
b. alter system set �_immediate_commit_propagation�=TRUE scope=spfile sid=�*�;
2) For each internal node, set autoconfig parameter APPLDCP to ON.
3) For each internal node, verify autoconfig parameters APPLCSF and APPLPTMP match.
(typically APPLPTMP will not be correct on secondary nodes�make it match the
primary node).
4) Shut down application tier services and run autoconfig to implement changes.
5) While application is down, bounce the DB for initialization parameters to take
effect.
a. srvctl stop database �d
b. srvctl start database �d
6) Log into SQL*Plus and confirm parameters have been set:
a. show parameter lm
b. show parameter immediate
7) On application tier, set your environment again and make sure $APPLDCP
environment variable is set:
a. echo $APPLDCP (it should return ON�this variable is turned on after setting
APPLDCP autoconfig parameter to ON)
8) If $APPLDCP is set to ON, start the environment. This will trigger the
concurrent managers to start in PCP mode.
9) Don�t forget to check $APPLDCP on the other internal node before starting the
environment there. If it�s not
set on the second node after resetting your environment, then you may have
forgotten to run autoconfig to enable
that parameter. But, if it is set, then also start services on the other internal
node.
10) Log in to the application and make sure the following profiles are set:
a. Concurrent: PCP Instance Check set to ON at site level
b. Concurrent: TM Transport Type set to QUEUE at site level
11) Navigate to Concurrent|Manager|Define and make the following changes:
a. Query for �Internal Monitor� and you�ll see there is an internal monitor for
each node (there is a node
mentioned in the name � i.e. �Internal Monitor: Mode2�). Make sure the primary
node field matches the node in
the name. Click �Work Shifts� button and select the Standard work shift and set
Processes to 1. Leave Secondary node field blank.
b. Next query the �Internal Concurrent Manager�. Set both primary and secondary
nodes and make sure the
Standard Work Shift is in place with 1 process.
c. Next go through the rest of the enabled managers and set both primary and
secondary nodes and make sure
Standard Work Shift is in place with 1 process.
12) Navigate to Concurrent|Manager|Administer and perform the following:
a. Find the �Internal Monitor: � and click the �Activate� button.
b. Find the �Internal Monitor: � and click the �Activate� button.
c. Click �Refresh� button and wait for these two managers to start with 1 process
each.
13) Bounce concurrent managers on all nodes for changes to take effect.
14) You should see several FND* processes on Node 1. And you should see FNDSM and
FNDIMON started on node 2.
1) In DB, run these two commands as sysdba:
a. alter system set "_lm_global_posts"=TRUE scope=spfile sid='*';
b. alter system set "_immediate_commit_propagation"=TRUE scope=spfile sid='*';

col ParameterName for a30

col sessval for a30
col instval for a30
SELECT pi.ksppinm ParameterName, pcv.ksppstvl SessVal, psv.ksppstvl InstVal
FROM x$ksppi pi, x$ksppcv pcv, x$ksppsv psv
WHERE pi.indx = pcv.indx AND pi.indx = psv.indx AND pi.ksppinm LIKE
'_immediate_commit_propagation'

PARAMETERNAME SESSVAL INSTVAL

------------------------------ ------------------------------
------------------------------
_lm_global_posts TRUE TRUE
_immediate_commit_propagation TRUE TRUE

2) For each internal node, set autoconfig parameter APPLDCP to ON.

FROM
[applmgr@cvm-928 clone]$ grep -i APPLDCP $CONTEXT_FILE
OFF

[applmgr@cvm-929 ~]$ grep -i APPLDCP $CONTEXT_FILE

OFF

TO

[applmgr@cvm-929 ~]$ grep -i APPLDCP $CONTEXT_FILE

ON

[applmgr@cvm-928 clone]$ grep -i APPLDCP $CONTEXT_FILE

ON

3) For each internal node, verify autoconfig parameters APPLCSF and APPLPTMP
match.
(typically APPLPTMP will not be correct on secondary nodes�make it match the
primary node).

FROM

[applmgr@cvm-928 clone]$ grep -i APPLCSF $CONTEXT_FILE

/ERPAPP/SIT/fs_ne/inst/SIT_cvm-928/logs/appl/conc
[applmgr@cvm-928 clone]$ grep -i APPLPTMP $CONTEXT_FILE
/ERPAPP/SIT/inst/fs1/inst/apps/SIT_cvm-928/appltmp
 [applmgr@cvm-929 ~]$ grep -i APPLCSF $CONTEXT_FILE
/ERPAPP/SIT/fs_ne/inst/SIT_cvm-929/logs/appl/conc
[applmgr@cvm-929 ~]$ grep -i APPLPTMP $CONTEXT_FILE
/ERPAPP/SIT/inst/fs1/inst/apps/SIT_cvm-928/appltmp

TO

[applmgr@cvm-928 clone]$ grep -i APPLCSF $CONTEXT_FILE

/ERPAPP/SIT/fs_ne/inst/SIT_cvm-928/logs/appl/conc
[applmgr@cvm-928 clone]$ grep -i APPLPTMP $CONTEXT_FILE
/ERPAPP/SIT/inst/fs1/inst/apps/SIT_cvm-928/appltmp

[applmgr@cvm-929 ~]$ grep -i APPLCSF $CONTEXT_FILE

/ERPAPP/SIT/fs_ne/inst/SIT_cvm-929/logs/appl/conc
[applmgr@cvm-929 ~]$ grep -i APPLPTMP $CONTEXT_FILE
/ERPAPP/SIT/inst/fs1/inst/apps/SIT_cvm-929/appltmp

4) Shut down application tier services and run autoconfig to implement changes.

After autoconfig---

[applmgr@cvm-928 admin]$ grep -i APPLCSF $CONTEXT_FILE

/ERPAPP/SIT/fs_ne/inst/SIT_cvm-928/logs/appl/conc
[applmgr@cvm-928 admin]$ grep -i APPLPTMP $CONTEXT_FILE
/ERPAPP/SIT/inst/fs1/inst/apps/SIT_cvm-928/appltmp
[applmgr@cvm-928 admin]$ grep -i APPLDCP $CONTEXT_FILE
ON

[applmgr@cvm-929 scripts]$ grep -i APPLCSF $CONTEXT_FILE

/ERPAPP/SIT/fs_ne/inst/SIT_cvm-929/logs/appl/conc
[applmgr@cvm-929 scripts]$ grep -i APPLPTMP $CONTEXT_FILE
/ERPAPP/SIT/inst/fs1/inst/apps/SIT_cvm-929/appltmp
[applmgr@cvm-929 scripts]$ grep -i APPLDCP $CONTEXT_FILE
ON

5) While application is down, bounce the DB for initialization parameters to

take effect.
6) Log into SQL*Plus and confirm parameters have been set:

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------
_lm_global_posts boolean TRUE
SQL> show parameter immediate

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------
_immediate_commit_propagation boolean TRUE

7) On application tier, set your environment again and make sure $APPLDCP
environment variable is set:
a. echo $APPLDCP (it should return ON�this variable is turned on after setting
APPLDCP autoconfig parameter to ON)

8) If $APPLDCP is set to ON, start the environment. This will trigger the
concurrent managers to start in PCP mode.

9) Don�t forget to check $APPLDCP on the other internal node before starting the
environment there.
If it�s not set on the second node after resetting your environment, then you may
have forgotten to run autoconfig to enable that parameter.
But, if it is set, then also start services on the other internal node.

***********************************************************************************
************

1. Assume that you have your Application tier is shared across all internal middle
tiers
2. Assume you have two CM nodes
3. Stop the Concurrent Managers on both the CM nodes
4. Apply patch 9074947 on application tier
5. set APPLDCP value ON in the context file of both the CM nodes.
6. Run autoconfig on Both cm nodes
7. Verify tnsnames.ora on both CM nodes has FNDFS entries of both the nodes
8. Ensure Internal Monitors on both CM nodes is defined properly and have
workshifts assigned to them
9. Make sure 2 Internal monitor Managers of both the nodes is activated. If not
activate from Concurrent -> Manager -> Administrator
10. Use the following query to find out your concurrent managers details.

SELECT distinct C.USER_CONCURRENT_QUEUE_NAME, C.MAX_PROCESSES,

C.RUNNING_PROCESSES, C.TARGET_PROCESSES, C.NODE_NAME, C.NODE_NAME2
FROM APPLSYS.FND_CONCURRENT_QUEUE_CONTENT A, APPLSYS.FND_CONCURRENT_PROGRAMS B,
APPS.FND_CONCURRENT_QUEUES_VL C
WHERE type_id = b.concurrent_program_id and c.concurrent_queue_id =
a.concurrent_queue_id;

10. Now Define Primary and secondary nodes for each concurrent manager from
Concurrent -> Manager -> Define as per your configuration.
11. Bring up Concurrent Managers on both the CM nodes.
12. Test the concurrent managers by submitting two uniqe concurrent programs that
should be running on managers on both the nodes.

Failover Testing

Test Case #1

1. Bring down Apps Listener on CM node 2 using kill -9

2. Kill all FNDLIBR process on CM node 2 using kill -9
3. Start Apps listener on CM node 2 after 5 mins.
4. Monitor CM2, you should see all the managers on CM2 should come up automatially

Test Case #2

1. Bring down apps listener on CM node2 using kill -9.

2. Start the managers on CM1, you should see managers of CM2 will start on CM node
1.
3. Bring up Apps listenr on CM2.
4. You should see, Managers of CM2 should fall back to CM2 from CM1.

Test Case #3

1. Bring down host of CM node 2. It should be shutdown.

2. You should see all the managers of CM2 should be failed over to CM1
3. Bring up host of CM node2.
4. Bring up apps listener on cm node2.
5. You should see all the managers of CM2 should fall back to CM2 fro CM1.

Posted 30th April by Manish Chaudhari

Labels: ERP-APPS-FAQ's
0 Add a comment

Oracle Application DBA Posts

Classic Flipcard Magazine Mosaic Sidebar Snapshot Timeslide

Recent
Date
Label
Author

Oracle Indexes & Types on oracle Indexes

Oracle Indexes & Types on oracle Indexes
May 16th
ADOP-Revoke & Abort Process in R12.2
ADOP-Revoke & Abort Process in R12.2
Apr 30th
Options with Adcfgclone.pl
Options with Adcfgclone.pl
Apr 30th
1
Load Balancer Setup in R12
Load Balancer Setup in R12
Apr 30th
PCP configuration in R12.
PCP configuration in R12.
Apr 30th
R12.1 to R12.2: upgrade process:High Level Steps
R12.1 to R12.2: upgrade process:High Level Steps
Apr 30th
Setup of Oracle EBS R12 on RAC+ASM
Setup of Oracle EBS R12 on RAC+ASM
Apr 30th
AD Utilities & patch failing issues
AD Utilities & patch failing issues
Apr 30th
EBS Apache Issues.
EBS Apache Issues.
Apr 30th
Custom Top Creation in R12.
Custom Top Creation in R12.
Apr 30th
Apps Interview Questions (11i &R12)
Apps Interview Questions (11i &R12)
Apr 30th
Apps Questions
Apps Questions
Apr 30th
R12 Cloning Issues
R12 Cloning Issues
Apr 30th
CM Issues in R12
CM Issues in R12
Apr 30th
IMP URL's for ERP:
IMP URL's for ERP:
Apr 30th
Performance issues in EBS
Performance issues in EBS
Apr 30th
Printer Setup in ERP
Printer Setup in ERP
Apr 30th
R12 Forms :Servlet or Socket
R12 Forms :Servlet or Socket
Apr 30th
Z-interview Que
Z-interview Que
Apr 30th
10 g and 11g differnece
10 g and 11g differnece
Apr 30th
Difference:Oracle Applications 11i and R12
Difference:Oracle Applications 11i and R12
Apr 30th
RMAN
RMAN
Apr 30th
RMAN Config & RMAN Catalog
RMAN Config & RMAN Catalog
Apr 30th
Recreate Oracle Inventory
Recreate Oracle Inventory
Apr 30th
DB Recovery Scenarios:
DB Recovery Scenarios:
Apr 30th
RAC concepts
RAC concepts
Apr 30th
RAC & ASM Basics
RAC & ASM Basics
Apr 30th
DB Questions
DB Questions
Apr 30th
Materialized Views in Oracle
Materialized Views in Oracle
Apr 30th
DB Questions
DB Questions
Apr 30th
DB Index and their types
DB Index and their types
Apr 30th
Oracle Golden gate:
Oracle Golden gate:
Apr 30th
General DB questions :
General DB questions :
Apr 30th
Database Upgrade 10g to 11g
Database Upgrade 10g to 11g
Apr 30th
Oracle ASM Basics
Oracle ASM Basics
Apr 30th
ERP Application login Process
ERP Application login Process
Apr 30th
Oracle Database Server Architecture:
Oracle Database Server Architecture:
Apr 30th
Database Upgrade 11g to 12c
Database Upgrade 11g to 12c
Apr 30th
Adding an Additional New Node
Adding an Additional New Node
Apr 30th
check privileges/role to table
check privileges/role to table
Oct 2nd
V$SESSION_LONGOPS queries
V$SESSION_LONGOPS queries
Oct 2nd
RMAN Backup details
RMAN Backup details
Oct 2nd
FND Debug profiles options enabled userd details
FND Debug profiles options enabled userd details
Oct 2nd
1
All About UNDO
All About UNDO
Oct 2nd
All About TEMP
All About TEMP
Oct 2nd
Blocking sessions details
Blocking sessions details
Oct 2nd
Tablespaces Query
Tablespaces Query
May 14th
Concurrent Request Scripts
Concurrent Request Scripts
Sep 30th
4
all important scripts
all important scripts
Apr 23rd
Different Unix commands for Oracle Apps DBA
Different Unix commands for Oracle Apps DBA
Apr 23rd
Install Oracle Applications R12 on Linux (Single-Node)
Install Oracle Applications R12 on Linux (Single-Node)
Apr 23rd