Sunday, January 18, 2009

Further checking of broken DSO objects

You might experience following error while loading data to DSO:

System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE (see long text) Message no. BRAIN299
Unknown error in SQL interface Message no. DBMAN259
Error while extracting from source DSOXXX (type DataStore) Message no. RSBK242
Package 2 / 16.01.2009 15:28:21 / Status 'Processed with Errors' Message no. RSBK257

This is purely linked with technical problem with your ODS object. Solution is to recreate DDIC objects behind you DSO. Normal option would be to delete DSO object and create it again from scratch. Since usually there is no so much time to proceed like this you may try to fix it like following:

1. TA RSRV (Analyses and Repair of BI Objects) -> All Elementary Tests -> ODS Objects -> Foreign Key Relationship of Reporting-Relevant ODS Object and SID Table Characteristics -> put your DSO here -> Execute

Then you get message like:
Error: Too many specifications missing for InfoObject IOXXX         Message no. RSRV503
SID values missing for 2.097 specifications of characteristic IOXXX Message no. RSRV501

Moreover system generates for you an ABAP report called: GP_ERR_RSODSO_ACTIVATE. You can browse this report in TA SE38 and via ABAP syntax Check functionality you easily explore which DDIC object is broken.

2. To fix this broken DDCI object use the report RSDG_ODSO_ACTIVATE which activates the DataStore object. Run it in Activate mode. Note that this result in the creation of a new change log table and that existing data from the inconsistent change log table may be lost.
You may be able to determine from executing the report in check mode whether further inconsistent DataStore objects exist.

1 comment:

Anonymous said...

Genial brief and this mail helped me alot in my college assignement. Say thank you you seeking your information.