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 !!!
Tuesday, March 1, 2011
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 !!!
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.
Solution:
Increase the value of following profiles:
Concurrent:OPP Process Timeout
Concurrent:OPP Response Timeout
Happy Troubleshooting !!!
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.
Solution:
Increase the value of following profiles:
Concurrent:OPP Process Timeout
Concurrent:OPP Response Timeout
Happy Troubleshooting !!!
Subscribe to:
Posts (Atom)
