12-22-2013 10:36 PM
we had an issue connecting to HPSM last night .Got resolved after a restart.
However could you please provide some inputs as to what might be the reason for this error .
PFA log file .
Solved! Go to Solution.
12-22-2013 10:49 PM
It seems an issue with Oracle db connectivity .. HPSM was trying to connect to DB but was not able to .
Also check for the network connectivity issue between the db and application servers .
12-22-2013 11:00 PM
Thank you for replying,
The DB Team says the following
"there were high number of connections came from application and because of which all memory is allocated to the existing users and new connections were not allowed. After you stopped the application, all sessions are gone and memory is released and DB came to normal state."
What do you make of it.Was it an issue from the application side.
12-22-2013 11:22 PM
Do you have some CIt services whihc is scheduled to run during the time the issue happened ..
From the log files .. it just shows users are trying to login but no response from DB .. can u check for other snippets of the log files ..
12-23-2013 01:20 AM
If memory is completely exhausted then you should ask Db to increase you SGA and PGA target size.
However only user session will not consume whole memory till memory s as low as in few Mbs.
12-23-2013 02:17 AM
we checked the alert from DB side this was just before our application was not connecting "
Major --X---- 23:28:31 12/22/13 smprolb2.corp.du.ae Oracle Ora_Conf alert
Critical ---S-X- 23:48:06 12/22/13 smprolb1.corp.du.ae HPSM HPSM report2 process is NOT Running on server smprolb1 "
12-23-2013 02:31 AM - edited 12-23-2013 03:16 AM
It is cleared form above that it is memory related issue.
Your DBA must be awared of SGA and PGA , increase of these is normal practice in such errors.
Also more parameters like pool_size etc might required configuration.
If using 10g the SGA ,in case of oracle DB 11g you have to use SGA target size.
You DBA will tackle this issue easily and might requires downtime.
12-23-2013 03:10 AM
Just one more question ;how did the issue got resolved after restarting our HPSM application.
As there was nothing done from DB side.
Thanks in advance.
12-23-2013 03:15 AM
During stop all the DB sessions will be released and automatically all the occupied memory will be regained.
When you again start the SM, connection starts piling up and memory usage increases lead to exhaust of all memory.