Beruflich Dokumente
Kultur Dokumente
-------
This paper is intended to give full instructions for installing and setting up Parallel
Concurrent Processing in Unix Server
Additionally, you create Node 2, which has same APPL_TOP in Node 1, and connect to
the same operating system.
Parallel Concurrent Processing requires two OR more nodes with identical APPL_TOP
Under this setup, when applying a patch you need to apply the copy(C) and
generate(g)driver To all nodes and apply the database patch driver only once since both
nodes go Against the same database instance.
1. On Node 1, log in as applmgr user and Source all your environment files to fully set
your environment.
You need this information when you are creating the applmgr user on
Node 2. If the applmgr user on Node 2 does not have the same exact
uid and gid Then this will cause errors later when one of the nodes
tries to login and Start processes on the other node.
2. On Node 2, create the applmgr users with the same uid and gid as
found In Step #1.
Example text within the .rhosts file that would be located on Node 2:
Node1.us.oracle.com applmgr
Example text within the .rhosts file that would be located on Node 1:
Node2.us.oracle.com applmgr
4. Make sure the PATH variable for the applmgr user on each node
includes the ping utility. You can type "which ping" to check if it
is already in your path. If it is not type "where is ping" to find
it. Then include this directory in your PATH.
5. While logged into Node 2 as applmgr make sure you can make a sqlplus
connection to the database on Node 1 without having to use the sign.
Example: sqlplus system/manager
7. On each Node edit the dcpstart file located under the $FND_TOP/bin
directory:Check How to edit dcpstart file in in the end of thisnote.
9. On each node modify the TNSNAMES.ORA file to include FNDFS entry for
other node. The TNSNAMES.ORA file located under 8.0.6 oracle home:
<ORACLE_HOME>\<SID>ORA\8.0.6\NET80\ADMIN
10. Create symbolic links between the top level directories on each
node to be able to view the report output file generated on another
node, or use the NFS to mount the log and output files to eachnode.
REPORTS60_NO_DUMMY_PRINTER="YES"
export REPORTS60_NO_DUMMY_PRINTER
TK_PRINT_STATUS="echo %n is valid"
export TK_PRINT_STATUS
12. Start the Internal Concurrent Manger, you should be able to do that
from Node1 Or Node2.
2. Navigate to Install > Nodes and register the names of all the
potential Nodes in the PCP setup
3. Navigate to Concurrent > Manager > Define and set up the primary
node for your Internal Concurrent Manager. This is the node on
which the ICM Prefers to run, when the node is available.
4. Navigate to Concurrent > Manager > Define and define a new manager
of type: Internal Monitor
a. To do this, from the manager type pull down list choose FNDIMON.
b. Define the primary and secondary node names and assign a standard
work-shift with one process
5. Repeat the step above and define one Internal Monitor "IM" for
Each node in the setup, except the primary node of ICM
6. Finally, set up the primary and secondary node names for all the
concurrent managers according to the desired distribution.
If you are setting up parallel concurrent processing, you need to edit the file dcpstart in
$FND_TOP/bin directory of each concurrent processing server to set Environment
variable values for the server.
To edit a dcpstart file, open the file with an editor and find the following lines:
Below this line find the line that runs the environment file.The environment filenames Is
typically<dbname>.env, where <dbname>is the name of the database in which the
current product group is installed.
Specify here the full path and filename of the concurrent processing server's Environment
file. If you installed product files on a local disk, the environment file is in the server's
top applications directory. Otherwise it is in the applmgr Home directory. Here is an
example: . /d01/appl/11.5.0/appsora.env
-Each server needs a copy of the edited dcpstart file in its applmgr home directory.
RELATED DOCUMENTS
-----------------
Oracle Applications System Administrator's Guide Release 11i Page: 5-63