SAP Knowledge Base Article - Preview

2981055 - Import of SLD CR Content causes OOM in HANA DB


  • You are importing data from one System Landscape Directory (SLD) to another SLD in any SAP Java based system e.g. Process Orchestration, Solution Manager, AS Java which run on a HANA Database.
  • An OutOfMemoryError error occurs when loading the initial CR Content
  • On the Application side defaultTrace, you will find trace entries similar to:
    Thrown: CIM_ERR_FAILED: [145]: transaction rolled back by an internal error: Allocation failed ; $size$=26753168; $name$=Uncompressed; $type$=pool; $inuse_count$=1089; $allocated_size$=165679216; $failure_type$=GLOBAL_ALLOCATION_LIMIT; $failure_flag$=(input position -1) 

     OpenSQLExceptionCategories: [TRANSIENT, TRANSACTION_ROLLBACK]...

  • In the HANA Client trace, you may see an error similar to:
    Error in method call SAPBatchTransaction: [170]SAP DBTech JDBC: [4]: cannot allocate enoughmemory: Out of memory on query open

  • On the HANA DB side, if you generate the FullSystem Info Dump, you may find an indexserver OOM trace e.g.
  • In this, you will see an entry for Allocation failure type: GLOBAL_ALLOCATION_LIMIT 
  • If you check the view M_PREPARED_STATEMENTS (Select * From M_PREPARED_STATEMENTS) 
  • Under this, many SLD related entries similar to:



  • SAP HANA, platform edition;
  • SAP NetWeaver


SAP HANA, platform edition all versions ; SAP NetWeaver 7.5


SAP HANA, platform edition, sap_hana, database, db, saphana, Pool/RowEngine/QueryExecution/SearchAlloc, SLD bridge , KBA , HAN-DB-PERF , SAP HANA Database Performance , BC-CCM-SLD-JAV , System Landscape Directory Java Client & Server , 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.