How To Fix RSDU_REPART034 - Übernahme der Partitionierung ist nicht möglich

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDU_REPART - Messages for Repartitioning InfoProviders

• Message number: 034

• Message text: Übernahme der Partitionierung ist nicht möglich

Was verursacht dieses Problem?

If InfoCubes already contain data, it is not possible to apply
partitioning changes using a normal activation.
If InfoCubes already contain data, you cannot normally change the
partitioning using InfoCube maintenance in the system. However, you can
import changes from the upstream test and development systems by using
transports if:

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

a) The InfoCube in the upstream systems does not contain any data, the
partitioning in these systems could therefore be changed using InfoCube
maintenance.
or
b) The partitioning in the upstream systems was changed using the
repartitioning tool.
Oartitioning of InfoCubes is a local system property that cannot be
transported for the following reasons:
In a productive system with a large volume of data, you will often want
to use different partitioning to that used in the development system
(which has a smaller volume of data), because partitioning can be
counterproductive if there is only a small volume of data.
Changing the partitioning usually means reorganizing the fact tables,
meaning that all data records have to be copied. Since the runtime on
the database depends linearly on the size of the InfoCube in the target
system and can last several hours, actions of this kind should be
scheduled and executed at times when there is less burden on the system,
for example at weekends. Otherwise, this can impair the runtime behavior
of the entire productive system.
During reorganization, all data records are copied, indexes are rebuilt,
and database statistics are calculated. This requires additional memory,
which is not always available. This can lead to system termination.
During reorganization, the relevant InfoCubes are locked to protect them
from modification actions (such as loading data, deleting data,
compressing, rolling up in aggregates, building aggregates or change
runs). This is the only way to guarantee data consistency. These 'dead
times' should be planned.
Changes to the partitioning can inadvertently enter the productive
system in transport requests. Example: Person A changes the partitioning
of InfoCube CUBE in the development system, but does not write this
change to a transport request, since s/he is aware of the consequences
for the productive system. Person B adds an additional key figure to
InfoCube CUBE and writes the InfoCube to a transport request so that the
change becomes active in the downstream systems. The change to the
partitioning would then also enter the productive system with this
transport request, without the consequences being clear to person B, who
triggered the transport request.
Changes made to the partitioning of InfoCubes by transports are only
applied if InfoCubes in the target system do not contain any data. This
behavior is an exception to the concept of 'local system partitioning
properties', but should support BW administrators in broadcasting all
settings of an InfoCube over the system landscape when a new InfoCube is
created. If an InfoCube already exists in the target system and does not
contain any data, both fact tables of the InfoCube are deleted during
the import and are rebuilt according to the new description (including
the modified partitioning).

Systemantwort

The changes to the partitioning are not applied to the active InfoCube.
All other changes are activated. There is no negative impact on the
productive system. The InfoCube can continue to be used without
restrictions.

Wie behebe ich diesen Fehler?

If you want to adjust the partitioning of the InfoCube in the system,
use the repartitioning function (transaction RSA1 --> >Administration
(bottom left) -- >Repartitioning). Make sure that you have read the
documentation and SAP Note 1008833 before doing this.

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE