Can you check if the heap-size is shown below? I am not sure what is our heap-size.
A month ago, similar issue occurred. Our solution was to increase value oacore_server1 below from 512 to 2048 and the issue was seemed resolved?
But we are not sure if it was the one which resolved the issue.
And now it has recurred again. How much more can we increase the oacore_server1? What is the maximum limit?
Are there another parameters to be increased along with it?
Can I increase it higher to 4096?
Try increasing the Maximum Capacity of the EBSDataSource to 2500. Also ensure your processes and sessions init parameters will support at least 3000 sessions. Processes should be maybe 4000 and sessions 8000.
Please confirm if my understaning is correct.
Task to do:
1.) No need to increase oacore_server1 from 2048 to 4096?
2.) How do you increase EBSDataSource to 2500? Which tab is it in the weblogic console shown above?
3.) I will change process=4000 and sessions=8000 in the database init.ora
Will the symptoms show in the alert logs that we are undersized processes and sessions?
It is in Services->DataSources->EBSDataSource.
I recommend leaving the heap size at 2048M.
If you allocate 2500 sessions in WebLogic, but the database cannot create that many sessions, you will see errors in the alert log and more WLS errors.
Its clear. You should not increase it to 4096.
1. You had increased to 2GB to overcome the issues in the past.You hit the issue again. But you should not further increase (example 4096 / 4 GB) again. Instead, you should add another 'Managed Server'.
2. adProvisionEBS.pl script to create new 'Managed Server'.
2.1 Steps for adding and removing managed servers are provided on Doc ID 1905593.1
Note:- As a best practice, I would suggest you to create multiple 'Managed Server' instead of one with higher memory. Make sure adequate Physical memory (RAM) available on the server when you tune heap space
Hope this answers!
Thanks Michael and Kanda,
Just to confirm if I understand it correctly:
Task to do.
1.) I will check first if alert log has session/processes limits error. If none then, no need to increase EBSDataSource to 2500.
2..) Next step is to run adProvisionEBS.pl script to create new 'Managed Server'.
Alternatively you may use this DML to get more clarity on maximum limit that you had hit.
SQL> select * from v$resource_limit
RESOURCE_NAME CURRENT_UTILIZATION ---- MAX_UTILIZATION
------------------------------ ------------------- ---------------
processes 50 71
sessions 59 80
Hope this helps!
I do it this way
sqlplus / as sysdba
show parameter sessions
show parameter processes
It shows just current configuration value.
But column(MAX_UTILIZATION) in the table v$resource_limit would have maximum that you hit since the last instance startup
you need not change if you had not hit the roof. Also look for errors in the alert.log
I need to ask and wait for the logs and the parameters from the prod admin.
I do not have direct access to the prod server.