Posted by
ErmanArslansOracleBlog on
Nov 07, 2023; 1:48pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Login-Issue-tp12162p12163.html
1)
Go through -> Oracle E-Business Suite 12.2 Data Source Connection Pool Diagnostics (Doc ID 1940996.1)
It seem connection pool is fully loaded.. Consider setting ICT..
To set the Inactive Connection Timeout parameter, follow these steps.
Login to the WLS console,
Navigate to Services-> Data Sources -> EBSDataSource -> Connection Pool -> Advanced (Expand Arrow)
Click on the Lock and Edit Button
Update the Inactive Connection Timeout to a desired value in seconds..
Also check your active connection using the following query ->
select a.node_name, 'Number of user sessions : ' || count(
distinct b.session_id) How_many_user_sessions from apps.fnd_nodes a,apps.icx_sessions b
where disabled_flag != 'Y' and PSEUDO_FLAG = 'N'
and (last_connect + decode(apps.FND_PROFILE.VALUE('ICX_SESSION_TIMEOUT'),
NULL,limit_time, 0,limit_time,apps.FND_PROFILE.VALUE('ICX_SESSION_TIMEOUT')/60)/24) > sysdate
and a.node_id=b.node_id and counter < limit_connects group by a.node_name
/
2)
You may consider adding 1 more oacore server to each of your apps node..
1 oacore JVM can handle up to 150 users approx.
Reference MOS Note 1905593.1 Step 4.4.1 Adding a new managed server.
3)Check your env with FND login analyzer.. In case, patches might be needed.
E-Business Suite Applications Login Analyzer (Doc Id 2319360.1)
4)You may increase the capacity of your EBSDatasource in case this load is expected and additional connection pool resources are really required.
5)Also see ->
https://ermanarslan.blogspot.com/2018/05/ebs-122-things-that-can-be-done-for.html