Error loading data from BEx Query – so called VirtualProvider based load

Recently I faced following error. It was on BW on HANA system and source of the load was BEx (or as now called BW Query) Query.

Parallel processing of query 1 resulted in the following messages:

Error reading the data of InfoProvider ZCUBE1$X

Error 2,949 has occurred in the BWA/SAP HANA server

TREX_DBS_AGGREGATE]

view or procedure invalidated;table or view name = 0BW:BIA:ZCUBE1/[Request Info: Object Name = "SAPXXX"."0BW:BIA:ZCUBE1", FM

Error reading the data of InfoProvider ZCUBE2$X

Error 2,949 has occurred in the BWA/SAP HANA server

TREX_DBS_AGGREGATE]

view or procedure invalidated;table or view name = 0BW:BIA:ZCUBE2/[Request Info: Object Name = "SAPXXX"."0BW:BIA:ZCUBE2", FM

Errors occurred during parallel processing of query 3, RC: 3

Error while reading data; navigation is possible

An exception occurred

Error reading the data of InfoProvider @Z_BEX_QUERY

Error reading the data of InfoProvider ZCUBE1$X

Error 2,949 has occurred in the BWA/SAP HANA server

TREX_DBS_AGGREGATE]

view or procedure invalidated;table or view name = 0BW:BIA:ZCUBE1/[Request Info: Object Name = "SAPXXX"."0BW:BIA:ZCUBE1", FM

Parallel processing of query 2 resulted in the following messages:

Error reading the data of InfoProvider ZCUBE2$X

view or procedure invalidated;table or view name = 0BW:BIA:ZCUBE2/[Request Info: Object Name = "SAPXXX"."0BW:BIA:ZCUBE2", FM

Normally this should not be an error as having a BEx Query as source system is not an issue since BW 7.x. However this time even query wasn’t runnable. In attempt to run it I got message:

X MESSAGE BRAIN 299: CL_RSR_RRK0_QCUBE_PACKAGE_CTRL INIT_CUR_QCUBE-02

X MESSAGE BRAIN 299: CL_RSR_OLAP_STATE_INVALID CONSTRUCTOR-01-

I tried to regenerate the query in in t-code RSRT but it didn’t help. Then I turned to SAP Notes search. I found a note 1656582 - Query terminations - InfoCubes, DSOs, master

Data in the SAP HANA DB. This Note suggests running ABAP rep RSDDB_LOGINDEX_CREATE for objects reported by the load error. It worked for me and after running it for both cubes reported I was able to successfully repeat the load.

The report offers to show XML output of all things that were recreated. Here’s how output message looks like: