Exceeded session limit on CPU usage

[Former Member]

Hi All,

We are getting message while generating some reports. Pl. see the Error Text below for message. For time being we have bumped the session limit to unlimited to take care of this problem for now. But the question is u201CIs there a way available in MII to refresh(cycle) the Data source connectionu201D So that the DB session limit can be kept un altered?

When we search this on different forums, we got a solution which we aleady implemented(bumping the session limit to unlimited). But we are looking for a solution from MII side.

Any help will be appreciated

Regards,

Rajesh.

Error Text:

Error occurred while processing data stream, A SQL Error has occurred on query, ORA-02392: exceeded session limit on CPU usage, you are being logged off . com.lighthammer.Illuminator.logging.LHException: Error occurred while processing data stream, A SQL Error has occurred on query, ORA-02392: exceeded session limit on CPU usage, you are being logged off . at com.lighthammer.Illuminator.logging.ErrorHandler.handleError(Unknown Source) at com.lighthammer.Illuminator.logging.ErrorHandler.handleError(Unknown Source) at com.lighthammer.Illuminator.connectors.Proxy.Proxy.processRequest(Unknown Source) at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source) at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source) at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.lighthammer.Illuminator.servlet.ServletRunner.run(Unknown Source) at com.lighthammer.Illuminator.servlet.ServletRunner.runAsXmlQuery(Unknown Source) at com.lighthammer.xacute.actions.illuminator.queries.IlluminatorQueryObject.LoadDocument(Unknown Source) at com.lighthammer.xacute.actions.illuminator.queries.IlluminatorQueryObject.Invoke(Unknown Source) at com.lighthammer.xacute.core.Action.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.core.Conditional.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.core.ActionSequence.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Process(Unknown Source) at com.lighthammer.xacute.engine.TransactionEngine.Execute(Unknown Source) at com.lighthammer.Illuminator.connectors.Xacute.XacuteRequestHandler.processQueryRequest(Unknown Source) at com.lighthammer.Illuminator.connectors.Xacute.XacuteRequestHandler.QueryRequest(Unknown Source) at com.lighthammer.Illuminator.connectors.Xacute.XacuteConnector.processRequest(Unknown Source) at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source) at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source) at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638) at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236) at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283) at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96) at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source) at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60) at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159) at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823) at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937) at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091) at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973) at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167) at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204) at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)

[Former Member · Accepted solution]

Hi,

Kindly try out the below option from database side.

Error : ORA-02392: exceeded session limit on CPU usage, you are being logged off

Cause : An attempt was made to exceed the maximum CPU usage allowed by the CPU_PER_SESSION clause of the user profile.

Action : If this happens often, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile.

If you looking for solution in MII end,

Check with SAP MII administrator on log files.

Check Data server tab for configuration details. (eg : Pool Size, Pool Max etc)

Kindly let us know the version of SAP MII.

Thanks

Rajesh Sivaprakasam.