Symptom
- After a patch update on both ABAP and Java systems, the Java stack does not start and server0 fails with exit code 2150. The ABAP stack starts fine.
- Error in dev_server0: "AS Java cannot be started; core service [com.sap.security.core.ume.service] failed to start".
- An exception chain in the default traces includes: "com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: The SQL command for a FOR ALL ENTRIES select is too large.", with remote short dump referenced: DBSQL_FAE_STATEMENT_TO_BIG.
- Frequent ABAP short dumps with the same error: DBSQL_FAE_STATEMENT_TO_BIG.
Read more...
Environment
SAP NetWeaver Application Server for Java
Product
SAP NetWeaver Application Server for Java all versions
Keywords
DBSQL_FAE_STATEMENT_TO_BIG, JCO_ERROR_SYSTEM_FAILURE, exit code 2150, server0, UME service, FOR ALL ENTRIES too large, JCoException 104, PersistenceException, Java startup failure, ume.r3.max_entries_for_fae_select, rsdb/max_blocking_factor, rsdb/max_in_blocking_factor, AS Java cannot be started, UME initialization, dev_server0 logs , KBA , BC-JAS-SEC-UME , User Management Engine , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview