Forgot your password?    
+ Reply to Thread
Results 1 to 1 of 1

Thread: Setup Parallel Concurrent Processing for Applications with RAC Database

  1. #1
    Expert Oracle Administrator
    Join Date
    Oct 2011
    Location
    New Delhi, India
    Posts
    427

    Setup Parallel Concurrent Processing for Applications with RAC Database

    In order to set up Setup Parallel Concurrent Processing

    - Applications is configured to use GSM.
    - Applications is Autoconfig Enabled.

    1. Set APPLDCP to ON

    On each cluster node edit the Applications Context file (<SID>.xml), that resides in APPL_TOP/admin, to set the variable <APPLDCP oa_var="s_appldcp"> ON </APPLDCP>. It is normally set to OFF. This change should be performed using the Context Editor.

    2. Preserve some Important Files

    Prior to regenerating the configuration, copy the existing tnsnames.ora, listener.ora and sqlnet.ora files, where they exist, under the 8.0.6 and iAS ORACLE_HOME locations on the each node to preserve the files (i.e./<some_ directory>/<SID>ora/$ORACLE_HOME/network/admin/<SID>/tnsnames.ora). If any of the Applications startup scripts that reside in COMMON_TOP/admin/scripts/<SID> have been modified also copy these to preserve the files.

    3. Regenerate the configuration by running adautocfg.sh on each cluster node

    4. After regenerating the configuration merge any changes back into the tnsnames.ora, listener.ora and sqlnet.ora files in the network directories, and the startup scripts in the COMMON_TOP/admin/scripts/<SID> directory.

    Each nodes tnsnames.ora file must contain the aliases that exist on all other nodes in the cluster. When merging tnsnames.ora files ensure that each node contains all other nodes tnsnames.ora entries. This includes tns entries for any Applications tier nodes where a concurrent request could be initiated, or request output to be viewed.

    5. In the tnsnames.ora file of each Concurrent Processing node ensure that there is an alias that matches the instance name from GV$INSTANCE of each Oracle instance on each RAC node in the cluster.

    This is required in order for the SM to establish connectivity to the local node during startup. The entry for the local node will be the entry that is used for the TWO_TASK in APPSORA.env (also in the APPS<SID>_<HOSTNAME>.env file referenced in the Applications Listener [APPS_<SID>] listener.ora file entry "envs='MYAPPSORA=<some directory>/APPS<SID>_<HOSTNAME>.env) on each node in the cluster (this is modified in step 11).

    6. Verify that the FNDSM_<SID> entry has been added to the listener.ora file under the 8.0.6 ORACLE_HOME/network/admin/<SID> directory.

    7. AutoConfig will update the database profiles and reset them for the node from which it was last run. If necessary reset the database profiles back to their original settings.

    8. Ensure that the Applications Listener is active on each node in the cluster where Concurrent, or Service processes will execute. On each node start the database and Forms Server processes as required by the configuration that has been implemented.

    9. Navigate to Install > Nodes and ensure that each node is registered. Use the node name as it appears when executing a nodename?from the Unix prompt on the server. GSM will add the appropriate services for each node at startup.

    10. Navigate to Concurrent > Manager > Define, and set up the primary and secondary node names for all the concurrent managers according to the desired configuration for each node workload.

    The Internal Concurrent Manager should be defined on the primary PCP node only.
    When defining the Internal Monitor for the secondary (target) node(s), make the primary node (local node) assignment, and assign a secondary node designation to the Internal Monitor, also assign a standard work shift with one process.

    11. Prior to starting the Manager processes it is necessary to edit the APPSORA env file on each node in order to specify a TWO_TASK entry that contains the INSTANCE_NAME parameter for the local nodes Oracle instance, in order to bind each Manager to the local instance.

    This should be done regardless of whether Listener load balancing is configured, as it will ensure the configuration conforms to the required standards of having the TWO_TASK set to the instance name of each node as specified in GV$INSTANCE. Start the Concurrent Processes on their primary node(s).

    This is the environment that the Service Manager passes on to each process that it initializes on behalf of the Internal Concurrent Manager. Also make the same update to the file referenced by the Applications Listener APPS_<SID> in the listener.ora entry "envs='MYAPPSORA= <some directory>/APPS<SID>_<HOSTNAME>.env" on each node.

    12. Navigate to Concurrent > Manager > Administer and verify that the Service Manager and Internal Monitor are activated on the secondary node, and any other addititional nodes in the cluster. The Internal Monitor should not be active on the primary cluster node.

    13. Stop and restart the Concurrent Manager processes on their primary node(s),and verify that the managers are starting on their appropriate nodes. On the target (secondary) node in addition to any defined managers you will see an FNDSM process (the Service Manager), along with the FNDIMON process (Internal Monitor).

+ Reply to Thread

Similar Threads

  1. How to Setup SCAN in RAC 11g
    By Hemant in forum RAC Performance,LoadBalancing,TAF,FAN,Troubleshooting
    Replies: 0
    Last Post: 08-17-2012, 08:19 PM
  2. Setup auto start and shut of the Oracle database in linux
    By shoaibansari in forum Core Database Administration and Monitoring
    Replies: 0
    Last Post: 02-14-2012, 07:57 PM
  3. Query to display all current database locks for Oracle Applications users
    By Amit in forum SCRIPTS : Users,Profiles,Applications,Responsibilities,Forms,JDBC,Patch,Versions,Products
    Replies: 0
    Last Post: 11-04-2011, 12:24 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

DBA Lounge (P) Ltd. deals in Oracle Technologies on Consulting, Resourcing, Corporate Training


Online and corporate training available on Oracle Database 11g, Oracle 11g Real Application Cluster (RAC), Oracle Applications 11i/R12, Oracle Fusion Middleware 11g, Oracle Identity Management-OIM, Oracle Internet Directory 11g-OID, Oracle Business Intelligence Enterprise Edition-OBIEE, Oracle Golden Gate, Oracle Access Management-OAM, Oracle Internet Directory-ODS, Oracle Identity Analytics Architecture-OIA Statistics