Month: May 2017
ERROR
Unable to authenticate session in Oracle apps R12 (12.0.4): Login Issue
It is in the following log file:
$INST_TOP/logs/ora/10.1.3/j2ee/oacore/oacore_default_group_1/application.log
15/09/19 05:45:20.601 10.1.3.0.0 Started
15/09/19 05:45:30.769 html: 10.1.3.0.0 Started
15/09/19 05:45:35 .132 html: oracle.apps.fnd.security.LeakDetectionFilter.initialized:1219349853132
15/09/19 05:45:38.132 html: LeakSetting:
global:true,session:false,aggressive:false,stderr:false,appslog:false,corelog:false
ignoring:null
15/09/19 05:45:45.859 html: chain failed
javax.servlet.ServletException: java.lang.RuntimeException: Unable to create user session. Please contact your System Administrator.
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.EvermindPageContext.handlePageThrowable(EvermindPageContext.java:780)
SOLUTION
1.Enable FND debug
The FND debug log would have below error:
- Oracle error -1654: ORA-01654: unable to extend index APPLSYS.FND_LOGINS_N2 by 16 in tablespace APPS_TS_ARCHIVE has been detected in FND_SIGNON.AUDIT_USER.
2.Check if the APPS_TS_ARCHIVE Tablespace is full.
3.Increase the size of tablespace APPS_TS_ARCHIVE by adding a datafile to the tablespace.
Recommended Database Parameters Updated for EBS 12.2
We publish a definitive list of Oracle Database initialization parameter settings for the optimal performance of Oracle E-Business Suite 12.2, 12.1, and 12.0:
This document covers all Oracle Database releases that are certified with EBS 12.x, including:
- Oracle Database 12c Release 1 (12cR1)
- Oracle Database 11g Release 2 (11gR2)
- Oracle Database 11g Release 1 (11gR1)
- Oracle Database 10g Release 2 (10gR1)
This document has just been updated with new information about the service_names parameter introduced in the April 2017 updates to the AD and TXK utilities.
Source: https://blogs.oracle.com/stevenchan/recommended-database-parameters-updated-for-ebs-122
ERROR
The http error_log had the below error:
oc4j_socket_recvfull timed out
The Application log has the below error:
15/09/16 05:30:20.511 html: Servlet error
java.lang.OutOfMemoryError: Java heap space
15/09/16 05:30:20.503 html: Servlet error
The opmn log had the below error:
15/09/16 05:30:20 java.lang.OutOfMemoryError: Java heap space
15/09/16 05:30:20 java.lang.OutOfMemoryError: Java heap space
15/09/16 05:30:20 java.lang.OutOfMemoryError: Java heap space
15/09/16 05:30:20 Exception in thread “Timer-1” java.lang.OutOfMemoryError: Java heap space
oracle.jbo.DMLException: JBO-26066: Error during rollback
SOLUTION
Change –Xms ( for start heap memory ) and -Xmx ( for maximum heap memory ) of the opmn.xml.
Changing the Xmx to 512 MB and Xms to 128 MB will help.
Increase Java Heap Size for the OC4J instance as per the available memory (RAM) & restart the instance.
- Do it with AS Control -> OC4J Instance -> Administration Tab -> Server Properties -> Java options.
- Update -Xms -Xmx java options.
- Once updated, stop and start the OC4J instance to pick up the changes.
ERROR
All the concurrent managers are down with a status message: system hold, fix manager.
The administer Concurrent manager screen has Actual: 0 and Target: 1 for all managers.
SOLUTION
1. Make sure all application services are down.
2.Now, check the system profile Concurrent: GSM Enabled. This should be set to ‘Y’
3. Execute Sql Script given below by APPS User
- $FND_TOP/patch/115/sql/afdcm037.sql
4. Relink the below mentioned executables:
adrelink.sh force=y “fnd FNDLIBR”
adrelink.sh force=y “fnd FNDSM”
adrelink.sh force=y “fnd FNDFS”
adrelink.sh force=y “fnd FNDCRM”
5. Execute cmclean.sql to clean out the Concurrent Manager tables.
6. Start all the application services and restest the issue.