Configure PCP [Enabling Internal monitor in distributed Application tiers

-

Set Up Parallel Concurrent Processing in Apps/EBS R12

Edit the applications context file via Oracle Applications Manager, and set the value of the variable APPLDCP to ON.Go to - System Administrator responsibility  -> OAM Setup -> Site Map -> Auto Config -> click on Edit Parameters icon of the desired application tier node 


     Repeat the same for the second Apps Tier node i.e. appsode_new.localdomain


Execute AutoConfig by running the following command on all concurrent processing nodes:
-- Node 1
[oracle@appsnode_new ~]$ hostname
appsnode_new.localdomain
[oracle@appsnode_new ~]$ adautocfg.sh
-- Node 2 
[oracle@appsnode2_new ~]$ hostname
appsnode2_new.localdomain
[oracle@appsnode2_new ~]$ adautocfg.sh

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.
-- Node 1
[oracle@appsnode_new forms_default_group_1]$ adalnctl.sh status
adalnctl.sh version 120.3
Checking status for listener process APPS_visr12.
LSNRCTL for Linux: Version 10.1.0.5.0 - Production on 13-AUG-2012 14:04:15
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=appsnode_new)(Port=1626))
STATUS of the LISTENER
------------------------
Alias                     APPS_visr12
Version                   TNSLSNR for Linux: Version 10.1.0.5.0 - Production
Start Date                13-AUG-2012 12:37:34
Uptime                    0 days 1 hr. 26 min. 41 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/visr12/inst/apps/visr12_appsnode_new/ora/10.1.2/network/admin/listener.ora
Listener Log File         /u01/app/oracle/visr12/inst/apps/visr12_appsnode_new/logs/ora/10.1.2/network/apps_visr12.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=appsnode_new.localdomain)(PORT=1626)))
Services Summary...
Service "FNDFS" has 1 instance(s).
  Instance "FNDFS", status UNKNOWN, has 1 handler(s) for this service...
Service "FNDSM" has 1 instance(s).
  Instance "FNDSM", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

-- Node 2
[oracle@appsnode2_new admin]$ adalnctl.sh  status
adalnctl.sh version 120.3
Checking status for listener process APPS_visr12.
LSNRCTL for Linux: Version 10.1.0.5.0 - Production on 13-AUG-2012 11:12:13
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=appsnode2_new)(Port=1626))
STATUS of the LISTENER
------------------------
Alias                     APPS_visr12
Version                   TNSLSNR for Linux: Version 10.1.0.5.0 - Production
Start Date                13-AUG-2012 09:51:00
Uptime                    0 days 1 hr. 21 min. 12 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/visr12/inst/apps/visr12_appsnode2_new/ora/10.1.2                          /network/admin/listener.ora
Listener Log File         /u01/app/oracle/visr12/inst/apps/visr12_appsnode2_new/logs/ora/1                          0.1.2/network/apps_visr12.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=appsnode2_new.localdomain)(PORT=1626)))
Services Summary...
Service "FNDFS" has 1 instance(s).
  Instance "FNDFS", status UNKNOWN, has 1 handler(s) for this service...
Service "FNDSM" has 1 instance(s).
  Instance "FNDSM", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully


If Entries are not find then try to restart the Applications listener processes on each application tier node. 

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.


Verify that the Internal Monitor for each node is defined properly, with correct primary node specification, and work shift details. For example, Internal Monitor: Host1 must have primary node as host1. Also ensure that the Internal Monitor manager is activated: this can be done from Concurrent > Manager > Administrator. 



Set the $APPLCSF environment variable on all the Concurrent Processing nodes to point to a valid log directory on both apps tier nodes. If the file systems are local then make sure it has proper privileges. If its on a shared file system, then make sure both apps nodes can write to it.

Set profile option 'Concurrent: PCP Instance Check' to ON. 
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.

Set Up Transaction Managers

Shut down the application services (servers) on all nodes

Shut down all the database instances cleanly in the Oracle RAC environment,

Edit $ORACLE_HOME/dbs/<context_name>_ifile.ora. Add the following parameters:
_lm_global_posts=TRUE
_immediate_commit_propagation=TRUE

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

Start up the application services (servers) on all nodes.

Log on to Oracle E-Business Suite 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.

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

Do this for all needed transaction managers and Restart the concurrent managers on all nodes.
If any of the transaction managers are in deactivated status, activate them from Concurrent > Manager > Administrator.

Test - 
Now try to stop CM Processes on all nodes and start the second node. You will be able to see that for the concurrent managers for which primary node down and secondary node up, they will start on secondary node.
That's it. You just configured the Parallel Concurrent Processing for your Apps R12!
Step : Also add primary adn secondary nodes in system administrator --> concurrent --> Manager --> Define 

 Step :  Also configure Workshifts for internal Monitor 
Restart Concurrent manager and test the issue 

Comments

Post a Comment

Popular posts from this blog

All about DataInstaller & Hrglobal.drv in Oracle Applications R12

-
All about DataInstaller & Hrglobal.drv in Oracle Applications All about DataInstaller & Hrglobal.drv in Oracle Applications This posts covers what is datainstaller & hrglobal.drv and when do we need to run them. DataInstaller and hrglobal.drv are used for installing legislative data into Oracle Applications,For example a company operates in multiple counntries and payroll and HR practices are different in each countires, So they need to have all the legislative regulations (Taxation and HR rules and regulations) of the all the countries they run their business. To achive this Oracle provides a set of patches, which need to applied to the Oracle applications. These patches are country specific, The patch matrix can be found from Latest Oracle HRMS Legislative Data Patch Available (HR Global / hrglobal) [ID 145837.1] To Install the legislative data please follow the below 4 steps: 1) PER & PAY modules need to be licenced ( This is madantory requirement) ...
Read more

EBS Oracle Database 11.1.0.7 upgrade to 11.2.0.4 steps .

-
Image
Oracle Database 11.1.0.7 upgrade to 11.2.0.4       Section 1: Upgrading an R12 Database to Oracle Database 11g Release 2 (11.2.0) Verify software versions:-   The following software component versions must exist in your environment. Software Minimum Version Tier Details Oracle Database Enterprise Edition N/A Database Read the "Determine the Upgrade Path" subsection in Chapter 2 of the Oracle Database Upgrade Guide 11g Release 2 (11.2) . Make sure that direct upgrade is supported from your current release. Oracle E-Business Suite 12.0.4 or 12.1.1 Application If you are on E-Business Suite Release 12.0, apply Patch 6435000  - Oracle E-Business Suite 12.0.4 Patch 8623536  - 11g Release 2 interoperability patch for Release 12.0.4 Patch 9868229 If you are on E-Business Suite Release 12.1, apply ...
Read more

PSU Patching step by step on RAC

-
OPatch utility version 12.1.0.1.7 or later to apply this patch. Grid Patch:---------------------------------------------------------------------------------------------------------------- From Oracle Home as oracle user:- /o001/home/oracle/product/12.1.0/db_1/OPatch/opatch lsinventory -detail -oh /o001/home/oracle/product/12.1.0/db_1 From Grid Home as grid user:- /o001/home/12.1.0/grid/OPatch/opatch lsinventory -detail -oh /o001/home/12.1.0/grid As root user:- /o001/home/12.1.0/grid/OPatch/opatchauto apply /o002/Oct_PSU_Patch/26635815 -analyze export PATH=/o001/home/12.1.0/grid/OPatch:$PATH opatchauto apply <UNZIPPED_PATCH_LOCATION>/27010872 Check Oracle permission $ORACLE_HOME/lib/libsqlplus.so --- Should be 644 From both oracle and grid users:- opatch lsinventory col ACTION_TIME for a30 col BUNDLE_SERIES for a15 select ACTION_TIME,PATCH_ID,PATCH_UID,VERSION,ACTION,STATUS,BUNDLE_SERIES,BUNDLE_ID from dba_registry_sqlpatch; ###################################Amar Jadhav ######...
Read more