SAP Knowledge Base Article - Preview

3436090 - IBP: Integration or extraction job/task fails with error "A database error occured"; and error containing "...intermediate result..."

Symptom

  • SAP CI-DS task which uploads/extracts data to/from SAP IBP fails with either of the below errors:
    •  "A database error occurred".
      In the CI-DS task's debug package, in the '<DATAFLOW_NAME>.error' file, the error is shown:
      • (R)(1000:000000000)R3C-150417      |Data flow <DATAFLOW_NAME>
        RFC function call failed: <I: MESSAGE - Time aggregation set to requested level 1 (Day, field PERIODID0).
        E: MESSAGE - A database error occured. The error message in the database was:
        "column store error: "SAPHANADB"."(DO statement)": line 2 col 3 (at pos 12): search table error:  [6957] AttributeEngine: Number of intermediate results exceeds
        supported limit;exception 70006957: AttributeEngine: Number of intermediate results exceeds supported limit
         ,Exception in executor plan<...>
         E: MESSAGE - column store error: "SAPHANADB"."(DO statement)": line 2 col 3 (at pos 12): search table error:  [6957]
        AttributeEngine: Number of intermediate results exceeds supported limit;exception 70006957: AttributeEngine: Number of intermediate results exceeds supported limit
          ,Exception in executor <...>
         E: MESSAGE - An error occurred. Please refer to the logs of batch <BATCH_ID>..

    • (R)(1000:00000)   R3C-150417      |Data flow <DATAFLOW_NAME>
                                                                     ...
                                                                     E: MESSAGE - A database error occured. The error message in the database was: "column store error: "SAPHANADB"."(DO
                                                                     statement)": line 2 col 3 (at pos 12): search table error:  [34104] Intermediate result too large". .

  • In IBP Application Logs app, Error log item shows "Issue in 'Time-Series-Based Integration' SCM-IBP-INT-TS, contact your admin and mention log handle <BATCH_ID>".

    Note: To make sure that the correct log entries are checked, the 'batch <BATCH_ID>' or 'Query id' in the CI-DS Task's >> View History >> Error log tab
    and the mentioned log handle of the Error log item in the IBP Application Logs app should be the same.


Read more...

Environment

  • SAP Integrated Business Planning
  • SAP Cloud Integration for data services

Product

SAP Cloud Integration for data services all versions ; SAP Integrated Business Planning all versions

Keywords

IBP, data integration job failed, extraction, data transfer, task failed, CI-DS, A database error occurred, Number of intermediate results exceeds supported limit, 2 billion records, best practices, filters, [6957], transfer, post-processing, external ID, batch id, cpi, HCI, dataflow, task, column store error, search table error, [34104], Intermediate result too large , KBA , SCM-IBP-INT-TS , Time-Series-Based Integration , SCM-IBP-INT-TS-DS , CPI-DS Integration , LOD-HCI-DS , HANA Cloud Integration for Data Services , 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.