Do you have any question about this error?
caract. bloc '&2' and get a step-by-step solution and expert tips...'> caract. bloc '&2' and get a step-by-step solution and expert tips...'> caract. bloc '&2' and get a step-by-step solution and expert tips...' > caract. bloc '&2'' >
Message type: E = Error
Message class: RSDD - Message class for data manager
Message number: 741
Message text: Table lecture '&4' (taille: '&3'), TAILLE BLOC=&1 ===> caract. bloc '&2'
The E or F table of the source for the aggregate structure is larger
than the parameter BLOCKSIZE in table RSADMINC. To prevent the temporary
database memory from overflowing, the aggregate structure is divided
into blocks. A characteristic whose value range is divided into
intervals is used to divide the structure up into blocks. Then only data
from such an interval is read from the source and written into the
aggregate.
Please note the following:
If the block characteristic is NOT the partition characteristic (the
request for the F table and a time characteristic for the E table), the
runtime can be much longer, because ALL partitions have to be read for
each block read. The program first tries to use the appropriate
partition characteristic as the block characteristic and only uses
another one if not enough blocks can be formed with it. In such a case,
it is very likely that the BLOCKSIZE is too small. If you can, increase
this value. (This is of course only possible if your database supports
partitioning and the InfoCube is also partitioned).
If the source is not partitioned, the program first takes the time
characteristics in the aggregate to form blocks. Only when not enough
blocks can be created does the system take other characteristics, (for
example, the aggregate only contains 0CALYEAR). It can be the case that
the blocks differ greatly in size, since the data is not shared out
equally (such a check would be too time-consuming). Try to choose the
BLOCKSIZE in such a way that the time characteristics can be used.
The least favorable option is to use a characteristic to form the blocks
that is not in the aggregate, but instead in the source. Then blocks
with a CHANGEID that is not equal to 0 have to be written into the F
table of the aggregate - and also compressed later on. Try to avoid this
case by changing the parameter BLOCKSIZE.
Unfortunately we do not have a general recommendation for the BLOCKSIZE,
since there are also large differences between the various databases
that SAP BW supports. If no value is maintained in Customizing for the
parameter BLOCKSIZE (activity in IMG: <DS:SIMG.RSDELTALIMIT>Parameters
for Aggregates</>), or if the value is 0, the SAP BW default value is
used, 100,000,000 (exception: DB Informix = 10,000,000).
Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.
Extrait du message d'erreur du système SAP. Copyright SAP SE.
RSDD741
- Table lecture '&4' (taille: '&3'), TAILLE BLOC=&1 ===> caract. bloc '&2' ?Get instant SAP help. Start your 7-day free trial now.
RSDD740
Répercuter jsq/ Comprimer jsq/ Comprimer automatiquement : &1/ &2/ &3
Quelle est la cause de ce problème? The following information is read from table RSMDATASTATE: which requests have already been released to reporti...
RSDD737
Agrégat est créé par fragment.
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
RSDD742
Bloc '&3': '&1' (taille de bloc '&2')
Quelle est la cause de ce problème? The SIDs belonging to the characteristics are used to divide the characteristics into intervals or individual v...
RSDD743
Source pour construction d'agrégats: InfoCube/agrégat '&1'
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
Cliquez sur ce lien pour rechercher tous les messages SAP.