Skip to main content

Configuring Parallel Concurrent Processing PCP in Oracle Apps (EBS) 12.2

Configuring Parallel Concurrent Processing PCP in EBS 12.2.x


I am sharing  steps to configure Parallel Concurrent Processing PCP in an EBS 12.2 environments.

Steps:

1. Edit the applications context file via Oracle Applications Manager, and set the value of the variable APPLDCP to ON.

Set the value of s_appldcp to ON for both Nodes (funebsapp1 & funebsapp2) on both RUN & PATCH file system context files.

funebsapp1 & funebsapp2 : on Run File System

[applmgr ~]$ grep APPLDCP $CONTEXT_FILE

<APPLDCP oa_var="s_appldcp">ON</APPLDCP>

funebsapp1 & funebsapp2 : on Patch File System

[applmgr ~]$ grep APPLDCP $CONTEXT_FILE

<APPLDCP oa_var="s_appldcp">ON</APPLDCP>

2. Execute AutoConfig by running the following command on all concurrent processing nodes:

[applmgr@funebsapp2 ~]$ echo $FILE_EDITION

Run

[applmgr@funebsapp2 ~]$ adautocfg.sh

funebsapp1:

[applmgr@funebsapp1 appl]$ echo $FILE_EDITION

Run

[applmgr@funebsapp1 appl]$ adautocfg.sh

3. 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. 

Edit the tnsnames.ora file on both funebsapp1 & funebsapp2 Application nodes.

[applmgr ~]$ cd $TNS_ADMIN

[applmgr ~]$ vi tnsnames.ora

[applmgr ~]$ vi listener.ora”

4. Restart the Applications listener processes on BOTH application tier node. 

[applmgr ~]$ cd $ADMIN_SCRIPTS_HOME

[applmgr ~]$ adalnctl.sh stop

[applmgr ~]$ adalnctl.sh start

5. Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator Responsibility. 
Navigate to the Install > Nodes screen, and ensure that each node is registered.


6. 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. 

7. Set the $APPLCSF environment variable on all the Concurrent Processing nodes to point to a log directory on a shared file system.

[applmgr@funebsapp1 scripts]$ echo $APPLCSF

/u02/erptest/fs_ne/inst/erptest_funebsapp1/logs/appl/conc

8. Set the $APPLPTMP environment variable on all the CP nodes to the value of the shared directory path on the 19c DB RAC node servers. Set the value of APPLPTMP correctly on both Application tier nodes in the CONTEXT_FILE, then restart the database once.

[oraebs@funebsdb1 19cHome]$ srvctl stop database -d BEE

[oraebs@funebsdb1 19cHome]$ srvctl start database -d BEE

9. Run AUTOCONFIG on both application tier nodes (first on node 2 then on node 1) on the RUN file system.

[applmgr ~]$ echo $FILE_EDITION
run
[applmgr ~]$ adautocfg.sh


10. 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.


11. 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, using the command: 
[oraebs@funebsdb1 appsutil]$ srvctl stop database -d BEE
[oraebs@funebsdb1 appsutil]$ srvctl start database -d BEE

  • Add following parameter as below (funebsdb1 and funebsdb2)
_lm_global_posts=TRUE 
_immediate_commit_propagation=TRUE


[oraebs@funebsdb1 ~]$ cd $ORACLE_HOME/dbs/
[oraebs@funebsdb1 dbs]$ vi vision1_funebsdb1_ifile.ora

  • Start the instances on all database nodes, one by one.
[oraebs@funebsdb1 dbs]$ srvctl start database -d BEE

  • Start up the application services (servers) on all nodes.
  • 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.
  • Navigate to Concurrent > Manager > Define screen, and set up the primary and secondary node names for transaction managers.
  • Restart the concurrent managers. (both Tier)
  • If any of the transaction managers are in deactivated status, activate them from Concurrent > Manager > Administrator. 


12. 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 (<service_name>_balance>).
2. Execute AutoConfig by running $INST_TOP/admin/scripts/adautocfg.sh on all concurrent nodes. 




If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

How to Create macOS Catalina ISO File

  How to Create macOS Catalina ISO File Please note these steps need to be performed on a Apple Mac System to generate an iso. Steps: 1) Download macOS Catalina From App Store or Apple download 2) Please note once you download it will be in dmg format. 3) Open Terminal in MAC.  from the top-right corner open up Spotlight.  Type in Terminal and hit Enter. 4)  Mount it to your macOS hdiutil attach /tmp/Catalina.dmg -noverify -mountpoint /Volumes/Catalina 5) Create macOS Catalina Installer sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Catalina --nointeraction 6) Unmount Catalina Disk hdiutil detach /volumes/Install\ macOS\ Catalina 7) Convert the DMG file to an ISO file hdiutil convert /tmp/Catalina.dmg -format UDTO -o ~/Desktop/Catalina.cdr 8) Rename and Move to Desktop mv ~/Desktop/Catalina.cdr ~/Desktop/Catalina.iso Now we can use this iso on any system and install on virtual machines.
Post a Comment
Read more