Steps to change the Output post processor name for PCP setup in Oracle EBS R12 applications

 Hi DBAs,

Below are the steps to change the Output post processor name for PCP setup in Oracle EBS R12 applications:

Step 1:Edit the output post processor:
=======================================

From the Oracle EBS Home page,Navigate to concurrent mangager Define tab,edit the name and save the changes.


Step 2:Run the 'cmclean' script
================================

Login as applmgr to Node1,Navigate to the path $ADMIN_SCRIPTS_HOME and run 'cmclean.sql' script.


applmgr@[Nodeapp01]-> sqlplus apps

SQL*Plus: Release 10.1.0.5.0 - Production on Tue Oct 23 19:55:18 2012

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

SQL> @cmclean.sql
DOC>
DOC>WARNING : Do not run this script without explicit instructions
DOC>from Oracle Support
DOC>
DOC>
DOC>*** Make sure that the managers are shut down ***
DOC>*** before running this script ***
DOC>
DOC>*** If the concurrent managers are NOT shut down, ***
DOC>*** exit this script now !! ***
DOC>
DOC>#
If you wish to continue type the word 'dual': dual



-----------------------------------------------------------------------
-- Updating invalid process status codes in FND_CONCURRENT_PROCESSES

Manager short name   Process id Status code
-------------------- ---------- ------------
WFWSSVC                  191590 U
FNDCPOPP                 189590 U
FNDOPP18288              189592 U
                         189593 U
WFMLRSVC                 191671 U
WFALSNRSVC               191591 U

8 rows updated.


-----------------------------------------------------------------------
-- Updating running processes in FND_CONCURRENT_QUEUES
-- Setting running_processes = 0 and max_processes = 0 for all managers

51 rows updated.


-----------------------------------------------------------------------
-- Updating invalid control_codes in FND_CONCURRENT_QUEUES

Manager short name   Control code
-------------------- ------------
FNDOPP18288          A

1 row updated.


51 rows updated.


-----------------------------------------------------------------------
-- Updating any Running or Terminating requests to Completed/Error

0 rows updated.


-----------------------------------------------------------------------
-- Updating any Runalone flags to 'N'

Updated 0 rows of runalone_flag in fnd_conflicts_domain to 'N'

-----------------------------------------------------------------------
Updates complete.
Type commit now to commit these updates, or rollback to cancel.
-----------------------------------------------------------------------

Step 3: Verify the Node names after running cmclean utility
==============================================================

SQL> SELECT NODE_NAME||' '||STATUS FROM FND_NODES;

AUTHENTICATION
ICMPAPP02 Y
EX0201 Y
EX0202 Y
EX0203 Y
EX0204 Y
Nodeapp01 Y


Step 4:Bounce the Concurrent Managers in PCP setup:
===========================================================
In the PCP set use the below steps to Bounce the Concurrent Managers.

Identify the Primary node,In our case Nodeapp01 is the prmary node of PCP setup.


a) stop apps listener on node1(Nodeapp01)
=>APPS_ICMPRD
Node1 /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/admin/scripts >./adalnctl.sh stop

adalnctl.sh version 120.3

Shutting down listener process APPS_ICMPRD.

adalnctl.sh: exiting with status 0


adalnctl.sh: check the logfile /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/logs/appl/admin/log/adalnctl.txt for more information ...


b)Stop apps listener on node2(icmpapp02)

Node2 /product/app/ICMPRD/inst/apps/ICMPRDX2_icmpapp02/admin/scripts >./adalnctl.sh stop

adalnctl.sh version 120.3

Shutting down listener process APPS_ICMPRD.

adalnctl.sh: exiting with status 0


adalnctl.sh: check the logfile /product/app/ICMPRD/inst/apps/ICMPRDX2_icmpapp02/logs/appl/admin/log/adalnctl.txt for more information ...

c)Stop the apps concurrent managers from node1
===============================================
Since ICMPRDX is having PCP setup,stop the Concurrent managers from node1(Primary node)


Node1:Nodeapp01

/product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/admin/scripts >./adcmctl.sh stop

You are running adcmctl.sh version 120.17.12010000.5


Enter the APPS username : APPS

Enter the APPS password :
Shutting down concurrent managers for ICMPRD_CM2 ...
ORACLE Password:
Submitted request 2532852 for CONCURRENT FND SHUTDOWN


adcmctl.sh: exiting with status 0


adcmctl.sh: check the logfile /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/logs/appl/admin/log/adcmctl.txt for more information ...


step d): Check and Kill all processes by finding the concurrent processes:
==========================================================================

On Node 1 and Node 2 make sure no concurrent manager process is running.

Node1: Nodeapp01

ps -ef|grep FNDLIBR|grep applmgr

ps -ef|grep FNDSM|grep applmgr

kill -9 pid

Node 2: icmpapp02

Node2: icmpapp02

ps -ef|grep FNDLIBR|grep applmgr

ps -ef|grep FNDSM|grep applmgr

kill -9 pid


Step e: Start apps listener on node1 and node2
=====================================================

Node 1:
-------------
 Node1 /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/admin/scripts >./adalnctl.sh start

adalnctl.sh version 120.3

Checking for FNDFS executable.
Starting listener process APPS_ICMPRD.

adalnctl.sh: exiting with status 0


adalnctl.sh: check the logfile /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/logs/appl/admin/log/adalnctl.txt for more information ...

Node 2:
--------

Node2 /product/app/ICMPRD/inst/apps/ICMPRDX2_icmpapp02/admin/scripts >./adalnctl.sh start

adalnctl.sh version 120.3

Checking for FNDFS executable.
Starting listener process APPS_ICMPRD.

adalnctl.sh: exiting with status 0


adalnctl.sh: check the logfile /product/app/ICMPRD/inst/apps/ICMPRDX2_icmpapp02/logs/appl/admin/log/adalnctl.txt for more information ...


Step f:Start the concurrent manager from node 1(Nodeapp01)
====================================================================

Since ICMPRDX is having PCP setup start the Concurrent managers from node1(Primary node)


Node1 /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/admin/scripts >./adcmctl.sh start

You are running adcmctl.sh version 120.17.12010000.5


Enter the APPS username : APPS

Enter the APPS password :
Starting concurrent manager for ICMPRD_CM1 ...
Starting ICMPRD_0216@ICMPRD_CM1 Internal Concurrent Manager
Default printer is noprint

adcmctl.sh: exiting with status 0


adcmctl.sh: check the logfile /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/logs/appl/admin/log/adcmctl.txt for more information ...

 Node1 /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/admin/scripts >ps -eaf|grep FNDLIBR
  appstest 18179 18170   0 04:46:03 pts/12      0:00 FNDLIBR FND CPMGR FNDCPMBR sysmgr="" sleep=30 pmon=4 quesiz=1 diag=N logfile=/p
  appstest 18280 16419   0 04:46:25 pts/12      0:00 grep FNDLIBR
 Node1 /product/app/ICMPRD/inst/apps/ICMPRDX1_Nodeapp01/admin/scripts >ps -eaf|grep FNDSM
  applqb 15336     1   0   Feb 12 ?           0:04 FNDSM
  appstest 18556 16419   0 04:46:50 pts/12      0:00 grep FNDSM
  appstest 18554 18179   0 04:46:50 pts/12      0:00 tnsping FNDSM_Node2_ICMPRD

 Note:If any services is already started and if you try to start again,
we will get message status code 2 message and if it start successfully in first attempt
 we will see status code 0,there is no harm in trying to start the services which are already running but please verify the services and Check EBS home page by login as 'SYSADMIN' and check all the managers are up & running and Concurrent Processing Server is up & runing on both the node.

Step g:Verify on both the nodes:
================================

On both the nodes check the FNDLIBR and FNDSM processes.

Node 1:Nodeapp01:
-----------------

applmgr@[Nodeapp01]-> ps -ef|grep FNDLIBR|grep appmgr
applmgr@[Nodeapp01]-> ps -ef|grep FNDLIBR|grep applmgr
 applmgr  4794     1   0 20:16:05 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4784     1   0 20:16:04 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4782     1   0 20:16:04 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4789     1   0 20:16:05 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4792     1   0 20:16:05 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4786     1   0 20:16:04 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C

applmgr@[Nodeapp01]-> ps -ef|grep FNDSM|grep applmgr
 applmgr  7349  1777   0 02:07:54 pts/5       0:00 grep FNDSM
 applmgr  7065     1   0 02:06:37 ?           0:00 FNDSM


Node 2:icmpapp02:
------------------

applmgr@[Nodeapp01]-> ps -ef|grep FNDLIBR|grep appmgr
applmgr@[Nodeapp01]-> ps -ef|grep FNDLIBR|grep applmgr
 applmgr  4794     1   0 20:16:05 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4784     1   0 20:16:04 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4782     1   0 20:16:04 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4789     1   0 20:16:05 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4792     1   0 20:16:05 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C
 applmgr  4786     1   0 20:16:04 ?           0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGB44E179A7BC94375178D975C

applmgr@[Nodeapp01]-> ps -ef|grep FNDSM|grep applmgr
 applmgr  7349  1777   0 02:07:54 pts/5       0:00 grep FNDSM
 applmgr  7065     1   0 02:06:37 ?           0:00 FNDSM


Step h:Verify from Oracle EBS Home page
===========================================

In Oracle EBS Home page Navigate to OAM,check the Concurrent Managers,make sure the actual and target processes have the same value for all the managers.



Step 5:Verify the  Output Post Processor name
===========================================================

In Oracle EBS Home page Navigate to OAM => Concurrent Managers=> Output Post Processor
Now we see the node names are correct for Output Post Processor,check the status and make sure the actual and target processes have the same values.

Enjoy Apps DBA Tasks...






Best regards,

Rafi.

Troubleshooting APP-FND-01630:

Hi DBAs,

Few days back when I was working with FNDLOAD utility,got the below error.

FNDLOAD apps/DEV2APPLSYS O Y UPLOAD $FND_TOP/patch/115/import/aflvmlu.lct lookup_XXTWC_YIELD_DIGITALPHONE.ldt
Log filename : L6977176.log


Report filename : O6977176.out
APP-FND-01630: Cannot open file L6977176.log for appending

Cause: FDPFOP encountered an error when attempting to open file L6977176.log for appending.

Action: Verify that the filename is correct and that the environment variables controlling that filename are correct.

Action: If the file is opened in read mode, check that the file exists. Check that you have privileges to read the file in the file directory. Contact your system administrator to obtain read privileges.

Action: If the file is opened in write or append mode, check that you have privileges to create and write files in the file directory. Contact your system administrator to obtain create and write privileges.


Solutions:
Check the permission in the Directory where you are trying to do FNDLOAD upload.

touch file1

       If you are able to create the file and have the required permission and still the issue exists,perform the below steps.

Note 1:

In R12. Context File is no more in $APPL_TOP/admin directory.It has been moved to $INST_TOP/appl/admin directory

Note 2:
Check env variables APPLTMP and APPLPTMP
$env|grep TMP
APPLTMP=/product/app/TESTAPPS/inst/apps/TESTAPPS_NodeApps/appltmp
APPLPTMP=/ora_backup/u0001
REPORTS_TMP=/product/app/TESTAPPS/inst/apps/TESTAPPS_NodeApps/temp
NodeApps(TESTAPPS)  /product/app/TESTAPPS/inst/apps/TESTAPPS_NodeApps/admin/install

Change the value of the APPLTMP and APPLPTMP environment variable in context file to point to new Directory and run autoconfig to make changes saved.Also make sure
utl_file_dir has the same value.


sqlplus / as sysdba (On DB Tier)
show parameter utl_file_dir;

Step 1:Run cmclean.sql
>sqlplus apps

SQL*Plus: Release 10.1.0.5.0 - Production on Wed Nov 7 23:42:44 2012

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options

SQL> @cmclean.sql

Note:CMCLEAN.SQL is the Non Destructive Script to Clean Concurrent Manager Tables

Step 2:Bounce the middle Tier applications services


Hope now the issue is resolved...

Enjoy Apps DBA Troubleshootings.


Best regards,

Rafi.

Oracle RAC 11gR2 crsctl all resource start and stop

Hi DBAs,

Oracle RAC 11gR2 came up with new crsctl command which can be use to start particular resource like asm,listener
grid services or at a time we can start all resource and stop all resources.

Below are the commands to do:


crsctl start resource
   

crsctl start resource -all

crsctl stop resource
   

crsctl stop resource -all


Reference:http://docs.oracle.com/cd/E11882_01/rac.112/e16794/crsref.htm#CHDFEEEG



Hope it helps ...

Enjoy RAC DBA learning....


Best regards,


Rafi.