Himanshu Sinha - Oracle Apps DBA , Oracle DBA, Oracle Cloud DBA , Enterprise Architect.

Output Post Processor TroubleShooting Issue 1 Output Post Processor is Down with Actual Process is 0 And Target Process is 1 1. Shutdown Concurrent Managers 2. To ensure concurrent manager down; check there is no FNDLIBR process running. ps -ef | grep FNDLIBR 3. Run adadmin to relink FNDSVC executable. a. Invoke adadmin from command prompt b. Choose option 2 (2. Maintain Applications Files menu) c. Choose option 1 (1. Relink Applications programs ) d. Then type FND When prompted; ( Enter list of products to link (all for all products) [all] : FND ) e. Ensure adrelink is exiting with status 0 4. Start Concurrent Managers 5. Check the Output Post Processor Issue 2 Concurrent Processing  R12 Output Post Processor Service Not Coming Up Reason : If Service Manager for the node is not running.  Possible cause might be service manager definition is missing under Concurrent ->Manager ->Define form. If the Service Manager is not pr...

Issue while running the adadmin utility: adadmin error Error in addgbc(): Multiple Sets of Books is not compatible with MultiOrg The issue is caused by the following setup: Duplicate entries for BSDK Bestseller application in FND_PRODUCT_INSTALLATIONS table. ========================================================== When the following queries are executed, two entries are found for the same application in FND_PRODUCT_INSTALLATIONS table with same application name and application id but different oracle id. 1 . SELECT APPLICATION_ID,COUNT(*) FROM FND_PRODUCT_INSTALLATIONS GROUP BY APPLICATION_ID HAVING COUNT(*) > 1; ---------------------------------------------------------- Upon execution the result will be as follows: APPLICATION_ID COUNT(*) -------------- ---------- 703 2 ---------------------------------------------------------- 2. SELECT FPI.APPLICATION_ID, FPI.ORACLE_ID, FAL.APPLICATION_NAME FROM FND_PRODUCT_INSTALLATIONS FPI, FND_APPLICATION_TL FAL...

Concurrent Manager Issue : Internal Concurrent Manager but not Other managers. FND_DCP.REQUEST_SESSION_LOCK / DBMS_LOCK.Request Error in Concurrent manager logfile : ========================= Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request. Possible DBMS_LOCK.Request resultCall to establish_icm failed The Internal Concurrent Manager has encountered an error. Resolve the issue in two ways: Solution 1 (Bounce database): 1. Stop all the services and make sure that all the concurrent managers completely down. 2. Stop and restart the database 3. Restart all the services and concurrent managers Solution 2 (Without database bounce): 1. Stop the concurrent managers cleanly. 2. Check for the database locks and kill the locks related to CM. 3. Run cmlean.sql with apps user. 4. Start the concurrent managers. Check for CM Locks: SQL> SELECT v$ access.sid , v$session.serial# FROM v$session,v$access WHERE v$...

Outbound Notification Emails : 1. Check if the notification is present in the recipient/user's Worklist/Notifications page.If it does not exist     then it means that notification itself is not created and need to check the corresponding workflow     status.You may also query the notification from the wf_notifications table SQL> select recipient_role,notification_id,status,mail_status from wf_notifications where recipient_role like '&user_name';    The e-mail notification is sent only if all of following are true.                --Notification status is OPEN or CANCELED                --Notification mail_status is MAIL or INVALID 2. Check Recipient role has a valid e-mail address and notification preference MAIL% SELECT email_address, nvl(WF_PREF.get_pref(name, 'MAILT...

WF Mailer Setup for Load Balancer Setting. Here is the Steps:  What is considered as an Advanced Configuration Setting in the Oracle Application environment? Using Dematerialized Zones (DMZ) Using Secured Socket Layer (SSL) Using BigIP Configured Server Using Virtual Naming Conventions Using a Reversed Proxy Server Using Load Balancers >>>>> 1. Find out from the Network Administrator (DBA or System Administrator) at the site as to what is the actual hostname of the Web Tier: The uname –a, uname –n,  or hostname commands can be used to determine the name.  These commands should yield almost the same information, but the uname –a command returns information on the operating system and version of the kernel. $ uname -a $ uname –n $ hostname 2. Cross Reference the Web Tier Name with the hostname setting in the AutoConfig Context file on the Web Tier by running the following commands on the Web Server:  $ grep ...