SAP Knowledge Base Article - Preview

3038236 - CDS extractor remains as "Extraction Running" and not confirmed

Symptom

Initialization job (ODQR*_C) is finished but the status in ODQMON is still "Extraction Running" instead of "Extraction Successful".

Job log is as below:

08.03.2020 08:24:01 Extraction resumed asynchronously by provider
08.03.2021 08:24:01 Job finished

Meanwhile there might be the following errors (often in case of parallel extraction tasks)

  • The DTP monitor shows:
Task ODQR* has failed
Error while accessing
The database cursor is invalid
  • Dump CL_ODQ_QUEUED_TASK_MANAGER occurs in ST22:
Runtime Errors         ASSERTION_FAILED
ABAP Program           CL_ODQ_QUEUED_TASK_MANAGER====CP
Application Component  BC-BW-ODP
"ASSERTION_FAILED"
"CL_ODQ_QUEUED_TASK_MANAGER====CP" bzw. CL_ODQ_QUEUED_TASK_MANAGER====CM01D
"EXCEPTION"


Read more...

Environment

  • S/4HANA system
  • An ODP source system in which SAP_BW is on 754 / 755

Product

SAP NetWeaver 7.5

Keywords

CL_RSODP_ABAP_CDS_EXTRACTOR , KBA , BW-WHM-DBA-ODA , Operational Data Provider for ABAP CDS, HANA & BW , How To

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.