Message type: E = Error
Message class: RSCV - Analysis of BW objects (InfoCubes...)
Message number: 630
Message text: Fact table for InfoCube &1 contains &2 additional indexes
Specific indexes are created as standard by the BW system for the fact
tables that are normally sufficient to perform well. Each additionally
created index increases the amount of index maintenance when changing
data in the InfoCube.
The option to delete secondary indexes before loading data and to
rebuild after loading only concerns the standard indexes. Additionally
created indexes remain and can therefore influence the loading
performance negatively.
Also, if the secondary indexes are not deleted before loading, each
additional index increases the amount of index maintenance and, along
with it, reduces performance when loading data.
The routines for repairing secondary indexes (transaction RSRV)
exclusively concerns the standard indexes. Additionally created indexes
have to be checked manually and possibly repaired.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check each additional index to see if loss of performance when loading
data outweighs its use, which is brought about by executing queries. If
not, you need to delete it.
Since the index schema for fact tables from DB2/400 was changed, these
additional indexes can also be obsolete indexes that still come from
the old index concept. In this case, their names end in three-digit
numbers between +500 and +900 or in two-digit numbers between +50 and
+90.
With the report SAP_INFOCUBE_INDEXES_CHG_DB4, the indexes from the fact
tables can be adjusted to the new index schema. For more information
about this, see SAP Note 451808.
You can read units about the index schema for the BW fact tables from
DB2/400 in SAP Note 407528.
Error message extract from SAP system. Copyright SAP SE.
RSCV630
- Fact table for InfoCube &1 contains &2 additional indexes ?The SAP error message RSCV630 indicates that there are additional indexes present in the fact table of an InfoCube that are not expected or required. This can occur during the process of data loading or when performing certain operations on the InfoCube.
Cause: The error typically arises due to one of the following reasons: Inconsistent Metadata: The InfoCube's metadata may not match the actual structure of the underlying database table. This can happen if changes were made to the InfoCube without properly adjusting the database. Manual Changes: If someone manually added indexes to the database table outside of the SAP BW environment, it can lead to discrepancies. Transport Issues: If the InfoCube was transported from one system to another, and the transport did not include all necessary changes, it could lead to inconsistencies.
Solution: To resolve the RSCV630 error, you can follow these steps: Check the InfoCube Definition: Go to the InfoCube in the SAP BW modeling tools
Get instant SAP help. Sign up for our Free Essentials Plan.
RSCV629
DB2/400: The index &1 is &2, but &3 was expected
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSCV628
DB2/400: The index &1 is &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSCV631
Index &1 does not belong to the standard indexes
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSCV632
Index &1 does not exist in the data dictionary
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.