Tuesday, March 1, 2011


This is the very common error in R12 instance "FND_NO_DATABASE_CONNECTION", but when you retry you won't get this error. To overcome this issue Oracle has come up with patch "9908921:R12.FWK.B Details".

Error Stack :
oracle.apps.fnd.framework.OAException: Application: FND, Message Name: FND_NO_DATABASE_CONNECTION.
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1251)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:2195)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:543)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:431)
at _OA._jspService(_OA.java:212)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:390)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:734)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:391)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:280)
at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:68)

Happy Troubleshooting !!!

Friday, February 11, 2011

Session Time out Setting in R12

Many occassions we have seen end users reporting session timed out even though they were working on. This is for sure its an issue from client end and JRE version which client is running on is the culprit for the same. Try to have the same version of JRE which is running on your server or latest one.
Even if this doesn't help try at client end following setting with running JRE:
1. Navigate to: Start > Control Panel > Java > Advanced > Java Plug-in
2. De-select the option "Enable the next-generation Java Plug-in "
3 Restart the browser
4-Retest the issue

Next if you want to increase timeout setting from server end. Do the following:
1. Change profile option ICX: Session Timeout to 60 min from 30, which is default.
2. change s_oc4j_sesstimeout value to 60 again in context file and run adconfig.
3. Bounce the apps services and check.

Happy Troubleshooting !!!

OPP jobs failing with time out

Hi All, I am back after long time. Never late then never. Now onwards I may focus on R12 issues which I have faced in my project. Here is first one.

Log file : The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.

Increase the value of following profiles:
Concurrent:OPP Process Timeout
Concurrent:OPP Response Timeout

Happy Troubleshooting !!!

Thursday, October 7, 2010

12.1.2 to 12.1.3 upgrade on Solaris

We have recently upgrade our instances to 12.1.3. Here is what we did.

1) patch 8626084
2) From Apps tier Source $INST_TOP/ora/10.1.3/sid_hostname.env file to set $ORACLE_HOME as 10.1.3 home.
3) cd /8626084/Disk1
4) ./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc
5) On fourth screen it will ask for oc4jadmin password. Kindly put "oafm".
6) Stop opmn processes, keeping same 10.1.3 env.
$ORACLE_HOME/opmn/bin/opmnctl stopall
7) Unzip patch p6880880_101000_SOLARIS64.zip in 10.1.3 and 10.1.2 OH to have latest opatch version.
8) Run Autoconfig on both Apps nodes.
9) apply patch p8999551_101350_Generic.zip in 10.1.3 home via opatch :
opatch apply
10) Confirm patchset version:
Run the command 'opatch lsinventory -detail'
Look for 'Oracle Application Server PatchSet' in the 'Product' column. 'Version' should show
11) Now apply apps patches, enable Maintenance Mode via adamin
12) Apply patch p9239089_R12.AD.B_R12_SOLARIS64.zip
Create $ORACLE_HOME/appsutil/admin on the database server.
Copy adgrants.sql (UNIX) from this patch directory to
Set the environment to point to ORACLE_HOME on the database server
Login as sysdba and run
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql APPS
13) Apply patch 9239090 12.1.3 patch. (Take 5-6 hrs)
14) Apply online help patch p9239095_R12_GENERIC.zip
15) Apply post patches p9817770_R12.ATG_PF.B_R12_SOLARIS64.zip and p9966055_R12.FND.B_R12_GENERIC.zip
16) Run autoconfig on both Apps tier
17) Run the admkappsutil.pl utility to create the file appsutil.zip in the
/admin/out directory
perl $AD_TOP/bin/admkappsutil.pl
18) On Database tier copy this file
19) And unzip in OH cd
unzip -o appsutil.zip
20) Run autoconfig on DB Tier
21) Run adpreclone on both DB Tier and Apps Tier
perl adpreclone.pl dbTier
perl adpreclone.pl appsTier
22) Disable Maintenance Mode via adamin
23) Needs to deploy forms before starting services on apps tier
24) Stop all the Application Services
25) Back up the original system-jazn-data.xml file.
cp $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml.orig
26) Add the following :
vi $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
========= file snippet original =================

OC4J Administrator
OC4J Administrator
OC4J Administrator

=========== with change ============================

OC4J Administrator
OC4J Administrator
OC4J Administrator

27) Back up the original opmn.xml file
cp $INST_TOP/ora/10.1.3/opmn/conf/opmn.xml $INST_TOP/ora/10.1.3/opmn/conf/opmn.xml.orig
28) Add the following line:
ipaddr remote="realhost.domain.com" request="virtualhost.domain.com"
notification-server interface="ipv4"
ipaddr remote="realhost.domain.com" request="virtualhost.domain.com"
port local="#local_port" remote="#remote_port" request="#request_port"
29) Run the deployment script
$FND_TOP/bin/txkrun.pl -script=CfgOC4JAppEnter
Application name for re-deployment ? forms
Enter Oc4j Instance password for re-deployment ? welcome
Run Autoconfig ? No
30) Restore both system-jazn-data.xml and opmn.xml from the backup taken under step 25 and 27 respectively
31) Run autoconfig
32) Start the services.
$ADMIN_SCRIPTS_HOME/adstrtal.sh apps/appspwd

Once done, you will be able to access forms now on 12.1.3.
Happy Troubleshooting !!!

Finding XML Publisher Version in R12

Its being long I have posted something. Got Stuck in major milestone in our project and 12.1.3 upgrade.

1) The following SQL statement will show which patches and thus with version of Oracle XML Publisher is installed on an Oracle E-Business Suite Release 12.0 and 12.1 environment:

SELECT DECODE (bug_number, '4440000', '5.6.3') PATCH, bug_number
FROM ad_bugs WHERE bug_number IN('4440000');
----- ------------------------------
5.6.3 4440000

2) The version of a specific Java Class has a one to one relationship with the currently installed version of Oracle XML Publisher. This method is suitable for both Oracle E-Business Suite 11 and Release 12.

$ adident Header $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class:
$Header MetaInfo.java 120.6 2006/08/17 01:25:30 bgkim noship $

Metainfo.class XML Publisher Patch Reference Included in ... R12
120.6 5.6.3 4440000 Note 422508.1

Happy Troubleshooting !!!