Applying patch to Oracle EBS 11i/R12 Applications

Applying patch to  Oracle EBS 11i/R12 Applications:
Below are the steps which I follow to apply patch to Oracle EBS 11i/R12,in the below scenario I'm using Oracle EBS 11i applications,but the same steps can be use for Oracle EBS R12 applications also

Step 1: Before applying patch:(check invalid objects in DB):

SQL> select name from v$database;

NAME
---------
TESTDB

SQL> select owner,count(*) from dba_objects where status='INVALID' group by owner;

OWNER                            COUNT(*)
------------------------------ ----------
SYS                                     1
TEST_USER1                     2
TEST_USER2                     5
APPS                                  23

Step 2:Enable Maintainance mode

 ebstest:applmgr::/home/applmgr>echo $TWO_TASK
TESTDB
Use 'adadmin' to enable maintainance mode before patching.

 5.    Change Maintenance Mode

Change Maintenance Mode
   ----------------------------------------

Maintenance Mode is currently: [Enabled].

Backing up restart files, if any......Done.

             Change Maintenance Mode
   ----------------------------------------

Maintenance Mode is currently: [Enabled].


Step 3:Applying patch using 'adpatch'(auto patch utility):
=====================================================
 Use: adpatch by going to patch directory

Go to the patch top directory,where all driver and required ldt files are present with the application
filesystem owner,makes sure all files have read,write and execute permission.
As described below:

Note:It is very important to review the readme.txt in unix vi editor before applying applying patch and follow the instruction as given in the readme.txt file and apply any pre-requistics patch if required.autoconfig run also not required unless it is specified after patch installation in readme.txt file.


ebstest:applmgr::/stage/patches/5522470>ls -altr
total 12432
-rwxrwxrwx    1 applmgr  dba            2931 Oct 29 2007  u5522470.drv
-rwxrwxrwx    1 applmgr  dba            1173 Oct 29 2007  f5522470.ldt
-rwxrwxrwx    1 applmgr  dba         6323692 Oct 29 2007  b5522470.ldt
-rwxrwxrwx    1 applmgr  dba              37 Oct 29 2007  marker1.txt
-rwxrwxrwx    1 applmgr  dba            2852 Oct 29 2007  README.txt
-rwxrwxrwx    1 applmgr  dba            5502 Oct 29 2007  README.html
drwxrwxrwx    5 applmgr  dba             256 Feb 21 01:21 po
drwxrwxrwx   54 root     dba           12288 Feb 21 01:21 ..
drwxr-xr-x    3 applmgr  dba             256 Feb 21 01:21 .
ebstest:applmgr::/stage/patches/5522470>adpatch

Review the README for pre-requisite information.

Your default directory is '/d21/TESTDB/apps/appl'.
Is this the correct APPL_TOP [Yes] ?

Verify the log file after applying patch

Step 4: Disable Maintainance mode again by using 'adadmin' utility:
=======================================================

Backing up restart files, if any......Done.

             Change Maintenance Mode
   ----------------------------------------

Maintenance Mode is currently: [Disabled].


Step 5: Bounce application after applying patch :
===================================================

Step a:Stop listener using adalnctl.sh

ebstest:applmgr::/u01/TESTDB/apps/comn/admin/scripts/TESTDB_ebstest>./adalnctl.sh stop

adalnctl.sh version 115.17

Shutting down listener process APPS_TESTDB.

adalnctl.sh: exiting with status 0

Step b:Stop applications using adstpall.sh

ebstest:applmgr::/u01/TESTDB/apps/comn/admin/scripts/TESTDB_ebstest>./adstpall.sh

You are running adstpall.sh version 115.22


Enter the APPS username: apps

Step c:Start listener using adalnctl.sh

ebstest:applmgr::/u01/TESTDB/apps/comn/admin/scripts/TESTDB_ebstest>./adalnctl.sh start

adalnctl.sh version 115.17

Starting up listener process APPS_TESTDB.

adalnctl.sh: exiting with status 0

Step d:Start applications using adstrtal.sh

ebstest:applmgr::/u01/TESTDB/apps/comn/admin/scripts/TESTDB_ebstest>./adstrtal.sh

You are running adstrtal.sh version 115.22

Step 6:After applying PATCH:
========================

Step a:Verify the patch is applied successfully:

SQL> select name from v$database;

NAME
---------
TESTDB

SQL> select bug_number,creation_date from ad_bugs where bug_number='5522470';

BUG_NUMBER                     CREATION_DATE
------------------------------ ---------------
5549427                        12-FEB-13

Step b:Run cmclean.sql
Run cmclean.sql from application node by going to $COMMON_TOP/admin/scipts/TESTDB_ebstest in 11i,where as in R12 goto $ADMIN_SCRIPTS_HOME or $INST_TOP/admin/scripts
commit;
Note:We run cmclean after clonning also to make sure the node name is updated in the FND_NODES Table correctly

SQL> select owner,count(*) from dba_objects where status='INVALID' group by owner;

OWNER                            COUNT(*)
------------------------------ ----------
SYS                                     1
TEST_USER1                    2
TEST_USER2                    5
APPS                                 22

Step c:Check the file versions got changed successfully after applying patch:

strings -a POXWARMB.pls|grep Header =>Can be used to check the file version.

ebstest:applmgr::/d21/TESTDB/apps/appl/po/11.5.0/sql>strings -a POXWARMB.pls|grep Header
 strings -a POXWARMB.pls|grep Header
/* $Header: POXWARMB.pls 115.27.11510.7 2009/02/11 11:08:59 krsethur ship $*/
/* $Header: POXWARMB.pls 115.27.11510.7 2009/02/11 11:08:59 krsethur ship $*/

Step d:Do the Health Check of Oracle EBS Application

Login TESTDB application by using Home page URL

Note :We can get HOME page URL by using below query:
SQL>Select Home_URL from icx_parameter;

 http://ebstest.abccomp.com:8035    with sysadmin/welcome123

Health check completed successfully by submitting active user Concurrent request REQUEST ID 28758820.

Step e:Intimate end User 

Make sure you intimate the end User or release your application to the end User

Enjoy Apps DBA tasks...


Best regards,

Rafi

WARNING: inbound connection timed out ORA-3136

Hi,

Recently I was troubleshootiong for this error,finally resolved.First,let me explain what exactly it mean, the cause of this error,possible method of diagnosis and finally the resolution.

INBOUND_CONNECT_TIMEOUT:
 The INBOUND_CONNECT_TIMEOUT is the parameter used to specify the time, in seconds, for the client to complete its connect request to the listener after the network connection had been established.
i.e The default timeout for a new connection to be established. This setting is called SQLNET.INBOUND_CONNECT_TIMEOUT.

 If the listener does not receive the client request in the time specified, then it terminates the connection.Check the listener.log for details.

In Oracle 9i,the value is set to unlimited and the new value in 10g is 60 seconds.In Oracle 11g also the default value is 60 seconds.

Causes:

1) Some Malicious client connections. 
2)  Connection takes a long time.
3)Database is heavily loaded and cannot process request in allotted time.

Diagnosis:

1)Check the alert log file and check from where the connection comes.
2)Check the listener is up & running.
3)Ping the server,make sure tnsping is working.

Resolution:

To identify the listener name and ORACLE_HOME,we can use the below command.

$ ps -eaf|grep tns
oracle    1643     1  0  2012 ?        04:51:49 /data01/home/oracle/product/10.2.0/bin/tnslsnr LISTENER -inherit
oracle   31682 16935  0 04:54 pts/0    00:00:00 grep tns


Check if the sqlnet.ora file is existing in $ORACLE_HOME/network/admin path,if not create one.

Adjusted the values for INBOUND_CONNECT_TIMEOUT at both listener and server side sqlnet.ora and reloaded the the listener configuration:

sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=60
listener.ora: INBOUND_CONNECT_TIMEOUT_LISTENER=60
where:Listener_name=>LISTENER
Default value for these is 60 seconds.

Below are the details:

LSNRCTL>set  INBOUND_CONNECT_TIMEOUT_LISTENER=60
[oracle@hostname admin]$ cat sqlnet.ora
#SQLNET.ORA Network Configuration File: /u01/home/oracle/product/10.2.0/network/admin/sqlnet.ora
#To eliminate inbound connection timeout
SQLNET.INBOUND_CONNECT_TIMEOUT=60

#sqlnet.authentication_services = (NONE)

#SQLNET.EXPIRE_TIME = 0

#SQLNET.ENCRYPTION_SERVER = requested

#SQLNET.ENCRYPTION_CLIENT = requested

NAMES.DIRECTORY_PATH= (TNSNAMES,hostname)
[oracle@s259722ch3el19 admin]$

[oracle@s259722ch3el19 admin]$ lsnrctl reload LISTENER

LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 19-JAN-2013 05:01:25

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

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.48.1.511)(PORT=1521)))
The command completed successfully

Keep  monitoring - alerts have stopped for now.

If the alerts continous to come,than you have to increase the value of  INBOUND_CONNECT_TIMEOUT as follows:

sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=300
listener.ora: INBOUND_CONNECT_TIMEOUT_LISTENER=300
 where:Listener_name=>LISTENER

 Hope it help.

Happy DBA tasks and troubleshooting.


Best regards,

Rafi.

Restoring a restore point in Oracle EBS Database

Restoring a restore point in Oracle EBS Database

Restoring a restore point in  Oracle EBS Database configured with PCP running on two nodes Apps Tier and two nodes DB Tier.


At a high level the steps to flashback an Oracle EBS Database are as follows:

1)Shutdown applications
2)Shutdown database (all nodes)
3)Startup mount one instance
4)Execute flashback command
5)alter database open resetlogs;
6)Startup all database nodes (typically I use srvctl start database –d and then check CRS to make sure everything is up).
7)Restart Applications

Additionally ,when starting the CM’s we can run cmclean first,
then start the CM’s, and then execute the CM purge job with a retention of 1 day or
something to attempt to clear out log files.

This is a “nice to have” as we’ve seen sometimes after a flashback the log files don’t match the process that was executed in CM.

Finally,do the Health check up by submitting the concurrent active user request.


TESTDB:
=======

srvctl disable disables target, meaning CRS will not consider it for automatic startup, failover,
or restart. This option is useful to ensure an object that is down for maintenance is not
accidentally automatically restarted.


Syntax:

srvctl disable database -d db_unique_name

srvctl disable database -d TESTDB

$srvctl status database –d TESTDB


>srvctl status database -d TESTDB
Instance TESTDB1 is running on node node1
Instance TESTDB2 is running on node node2


Step 1:Shut both the instances in the database Database normally
 
Node 1:
============

$srvctl stop database –d TESTDB


>srvctl status database -d TESTDB
Instance TESTDB1 is not running on node node1
Instance TESTDB2 is not running on node node2

(OR)

SQL>shut immediate


SQL> SELECT NAME FROM V$DATABASE;

NAME
---------
TESTDB

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.


Node 2:
==========

SQL>shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

Step 2:Startup mount and Roll Database back to restore point

SQL>startup mount


SQL> startup mount
ORACLE instance started.

Total System Global Area 1.3434E+10 bytes
Fixed Size                  2160552 bytes
Variable Size            4697622616 bytes
Database Buffers         8589934592 bytes
Redo Buffers              143785984 bytes
Database mounted.


SQLPLUS>FLASHBACK DATABASE TO RESTORE POINT 'someLOGICALNAME';

SQLPLUS>FLASHBACK DATABASE TO RESTORE POINT BASELINE_RESTORE_11DEC12;                                                                                                         ';

FLASHBACK DATABASE TO RESTORE POINT BASELINE_RESTORE;

SQL> select name from v$database;

NAME
---------
TESTDB

SQL> select * from v$restore_point;

       SCN DATABASE_INCARNATION# GUA STORAGE_SIZE
---------- --------------------- --- ------------
TIME
---------------------------------------------------------------------------
RESTORE_POINT_TIME                                                          PRE
--------------------------------------------------------------------------- ---
NAME
--------------------------------------------------------------------------------
1.2621E+13                     6 YES   3.6739E+10
19-JUL-12 02.27.07.000000000 PM
                                                                            YES
BASELINE_RESTORE


SQL> SHUT IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP MOUNT
ORACLE instance started.

Total System Global Area 1.3434E+10 bytes
Fixed Size                  2160552 bytes
Variable Size            4697622616 bytes
Database Buffers         8589934592 bytes
Redo Buffers              143785984 bytes
Database mounted.
SQL> FLASHBACK DATABASE TO RESTORE POINT BASELINE_RESTORE;
FLASHBACK DATABASE TO RESTORE POINT BASELINE_RESTORE


Step 5:Monitor progress of a flashback operation:

SQL> select opname,to_char(start_time,'MM-DD-YYYY HH24:MI:SS'),time_remaining,elapsed_seconds from v$session_longops;

OPNAME
----------------------------------------------------------------
TO_CHAR(START_TIME, TIME_REMAINING ELAPSED_SECONDS
------------------- -------------- ---------------
Flashback Database
12-14-2012 01:22:51           1395             744


Step 6 a:Open the Database with resetlogs option

SQL>alter database open resetlogs;


Step 6 b:Start and check both the Database instances are up & running.



$srvctl start database -d TESTDB

$srvctl enable database -d TESTDB


$srvctl status database –d TESTDB


>srvctl status database -d TESTDB
Instance TESTDB1 is running on node node1
Instance TESTDB2 is running on node node2


Step 6 c :Start all the Applications and Do Health Check of the Application by submitting active user request

Start the Application from the Primary node in PCP setup,first start listeners on both the nodes ,than start the concurrent managers and than finally start the Applications on both the node.







Step 7:Informed the team flashback is completed to restore point.



Hope it helps.

Happy Apps DBA learning.

 Best regards,

Rafi.

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.

I AM ATTENDING SANGAM12

Hi DBAs,

This year's Sangam is expected to be a great one specially when tom kyte is there and many more great speakers.Let us attend this to gain more and more Oracle knowledge and experts sessions to boost our skills and enhance our skills.See you at SANGAM 12.

More details we can find from the below links:

Sangam12 Page: Please spend some time to go through Sangam12 page
http://www.aioug.org/sangam12.php
Sangam12 Agenda: Plan your schedule in advance
http://www.aioug.org/sangam12/Sangam12-Agenda.htm

Best regards,

Rafi.