Hi BEx Community,
When consuming a BEx Query (or even a BW Infoprovider directly) or reading characteristic values (F4 value help) you might face error messages like the ones below. These terminations are propagated to all front-ends that consume the services described above, such as Web Intelligence (WebI) and other BO tools, Bex Analyzer, Analysis for Office (AO), Business Planning and Consolidation (BPC), Java Portal and many others.
Sometimes the error message received can differ a little from the ones below or, depending on the front-end message handling, the error message is not displayed very clearly. In the second case I recommend you to test the corresponding query on RSRT transaction (HTML mode) to get a clear view of the error message.
PS.: If you are using an InfoProvider instead of a BEx Query, you can execute the InfoProvider default query on RSRT by using the schema <infoprovider>/!<infoprovider>. E.g.: For a infoprovider called ZTEST, enter ZTEST/!ZTEST as query technical name.
PS2.: If transaction RSRT cannot be used for any reason, I recommend you to collect a RSTT trace. Then play the trace afterwards and you should get clear messages. More information at: 1925924 - How to enable RSTT Trace in SAP BW for Frontend Tool(SAP BI & 3rd-party Tools)
Some of the error messages that indicate this sort of issue are the following ones:
"Error(#99) TREX_DBS_AGGREGATE"
"Error (#901) Error 2,949 has occurred in the BW/SAP HANA server"
"Error initializing joins: Could not handle join condition.."
"Error 2.999 has occurred in the BWA/SAP HANA server"
"Error 2.991 has occurred in the BWA/SAP HANA server"
"table config for index ...en is not valid"
"Error reading the data of InfoProvider ...$X"
These errors are due to missing or inconsistent column views (also known as a "logical index") in SAP Hana database.
In the SAP HANA database, each InfoCube has a corresponding column view for the performance-optimized reading of data records. The same applies to DataStores with "SID Flag" (SID generation during activation), to master data providers, and to InfoObject value helps.
In most cases, the symptoms described occur because the relevant column views are missing in the database. However, you do not know or you cannot reproduce why the column view is missing or was deleted.
The solution for most of these cases is to execute report RSDDB_LOGINDEX_CREATE in order to (re)create the logical index for affected object. In below image you can see objects types you can run this program (taken from a SAP BW 7.4 system).
Please find full details on SAP note:
1656582 - Query terminations - InfoCubes, DSOs, master data in HANA DB
Hope this helps.
Cheers,
Eduardo Provenzano
See other posts:
How to verify a Workbook last used date
Bex Query going into debug mode in RSRT? Check here how to find the solution
- SAP Managed Tags:
14 Comments
