Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

This document covers general information about RSMDATASTATE table and common issues due to inconsistencies in this table.


 
Common issues:

Error 1:
Inconsistencies after upgrade to 7.3:

After you upgrade from SAP NetWeaver BW 7.00/7.01/7.02 to BW 7.30/7.31, there may be an inconsistency regarding the table RSMDATASTATE for specific InfoCubes. As a result, operations on this InfoCube, such as rollups, generally fail. Execute the function module RSDDTREX_AFTER_UPGRADE_70X_73X. This corrects the RSMDATASTATE entry only for those InfoCubes for which the AGGREXIST attribute is equal to X but there is neither an aggregate nor a BWA index. Please check note 1633303 for detailed information.

Error 2:
Inconsistencies after system copy:

If the management tables of the BIA server were (incorrectly) partially or completely deleted in the system copy, inconsistencies may occur in the InfoCube administration tables:  The field AGGREXIST of the table RSMDATASTATE contains the information for the InfoCube aggregates and/or BIA indexes. You must still manually clean up this table in transaction SE16. This must also be done for all InfoCubes for which there are no longer any aggregates.  Please follow note 1146983 for detailed information.

Error 3:
Inconsistenices due to mismatch in RSDDAGGRDIR & RSMDATASTATE tables:

While loading or reconstruction or rollup or any process, there would be a check on table RSMDATASTATE. The checks are more for validating the processes like data load,rollup,compression, datamart,archiving etc are in consistent state. To solve this error please deactivate the affected aggregates of Cube and reactivate it afterwards. There are inconsistencies in the administration tables for those aggregates which will be removed with this action. Please follow note 1146983 & 1838739 for detailed information.

Error 4:

Dump with error message RSM_DATASTATE_CHECK-2- happens:

The reason can be that tables RSMDATASTATE and RSDDBOBJDIR (BIA Index Objects) are not in sync. RSMDATASTATE-AGGREXIST is empty while from table RSDDBOBJDIR it can be seen that a BIA index is available (TIMESTMP). The solution for this case is to delete and rebuild the BIA index

 

Known issues and corrections:

1713123

P29:DTP:Request in BIA-only cube not autom. set to roll up

1146983

System copy and BIA server

1838739

System error in program RSMDATASTATE and form RSM_DATASTATE_CHECK-2-

1633303

RSMDATASTATE inconsistencies after upgrade from 7.0x to 7.3x

1822453

P31:DSO: Filled rollup and compr fields in RSMDATASTATE

1629957

RSMDATASTATE: Inconsistency of InfoCubes with BWA index

1626806

RSMDATASTATE: Inconsistencies after you delete the BWA index

1765637

BIA: Inconsistency between RSMDATATSTATE and RSDDBOBJDIR

1637289

P28:REDUCE:General check when changing RSMDATASTATE

1718030

P08:Manage:Flat cube:AGGREXIST indicator is set for Cube

1417057

P24: Dump: BRAIN 299: RSM_DATASTATE_CHECK -5-

1438227

P24:Manage: DM flag dissappears when going between tab pages

1659803

P29:COMPRESS:Request larger than DMALL proposed:Dump occurs

1584120

RSM1489 Compression not necessary; no requests found for compressing

1801036

RSMDATASTATE/change run problem in SAP HANA DB system

1814925

P10:DTP:Err in source req. determ. for MPRO w/ 3.X data flow

1767353

P09:DTP:Deadlock:SM12:MultiProvider:RSMDATASTATE

1760671

BW cube inconsistent time dimension w/ 0CAL* characteristics

1620674

P28:DTP:SM12 lock hangs:RSICCONT and RSMDATASTATE

1391793

Transactional InfoCube RSM_DATASTATE_CHECK-8-

1438227

P24:Manage: DM flag dissappears when going between  tab pages

1360283

P22:Dump in RSM_DATASTATE_CHECK for DSO and DMALL/DMEXIST

 

http://wiki.sdn.sap.com/wiki/x/DAFPF