SAP Knowledge Base Article - Preview

2551733 - SUM: Error ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit in phase SCEXEC_ALIAS or UPDATE_DBSTATS_ACT_TRANS

Symptom

  • ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_ALIAS
  • Severe error(s) occurred in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_ALIAS! Last error code set:Non single errors (code > 8) found in logfile 'SQLEXEAL.LOG'46 error during parallel execution of processes, check 'SQLEXEAL.LOG' fordetails92 processes failed, check 'SCEXEC_A.*' for detailsStopped execution due to too many failed processes
  • This error can also occur in phase MAIN_TRANSEXEC/UPDATE_DBSTATS_ACT_TRANS. The following error message can be found in logfile ORA_UPDATESTAT.LOG:
    BR0301E SQL error -2391 in thread 3 at location thr_db_connect-4, SQL statement:
    'CONNECT SYSTEM/**********@SID'
    ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
    BR0310E Connect to database instance SID failed

Read more...

Environment

  • SAP SUM 1.0
  • SAP SUM 2.0
  • Oracle Database
  • Windows OS
  • Linux OS
  • Solaris OS

Keywords

Oracle, DB, max connections, maximum concurrent connections, reached, ORA-02391, exceeded simultaneous SESSIONS_PER_USER limit, Severe error(s) occurred in phase MAIN_SHDINST/SUBMOD_SHDALIASCRE/SCEXEC_ALIAS, DBSL error 99 (db code 2391): Connect failed , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-DB-ORA-DBA , Database Administration with Oracle , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.