How could I detect situation that 'Cluster no. exceeds maximum of 3999'

[Former Member]

How could I detect situation that 'Cluster no. exceeds maximum of 3999' or 'Cluster no. exceeds maximum of 9998' for a table.

E.g. I got from SAP note number 168728 which describes this two situations and has different solutions. Howewer I do not find a message describing which situation belongs to a table

[Former Member]

Hi,

It may happen to any cluster table when you are trying store more records than the allowed one.

then you have to modify the table EWUCLSTAT as per the correction mentioned.

this OSS note just gives the solution for the error, don't say where it will happen..

Summary

Symptom IMPORTANT NOTE: Implement Note 393505. This way, the corrections from this note are applied and symptom I is prevented. However, symptom II may still occur and cannot be prevented by other program corrections. In case of this error, an entry into table EWUCLCT is the only solution.

1. A program termination occurs during the CONVERSION phase with the following error message: 'Cluster no. exceeds maximum of 3999.'

2. A program termination occurs during the CONVERSION phase with error message MQ(350): 'Cluster no. exceeds maximum of 9998'.

Additional key words

EWUCLU, Cluster, EWU, EMU, MQ, MQ350, MQ-350,

Cause and prerequisites

The program termination occurs when selecting and writing in cluster EWUCLU. A restart is possible.

Ad 1.:

3999 blocks are available in table EWUCLU (= Cluster) to store data of a table. This limit was exceeded. Consequently, not all the required data can be stored. As a result, the system terminates the program with the above error message.

Ad 2.:

It has become apparent that tables have exceeded the maximum cluster block number. For this reason, an enhancement was developed to 9998 cluster blocks and the error cluster blocks limited to a single error cluster block 9999 instead of to 4000 upwards. A further enlargement is not possible due to the field length. Nevertheless, this enhancement is not sufficient for your table. For your table, you must make an entry into exception table EWUCLCT with which you increase the size of the cluster block. In the standard system, the cluster block size is set to 5 MB.

Moreover, for performance reasons, you must consider to possibly reduce data, for example, by archiving.

Solution Ad 1.:

You can either make a data backup, then import the Support Package or implement the advance correction and start with an new package (I.) or make an exception entry into table EWUCLCT and again start the conversion via the IMG (II.).

If you carry out possibility II, we recommend to implement the corrections before you execute the next test run.

When you implement the advance corrections you must make the following change to table EWUCLSTAT in addition to the source code:

Transaction SE11: table EWUCLSTAT

Append field PROCESSED as the last field to the table:

Field name: Data ele.: Type: Length: Short text:

PROCESSED EWUERLKZ CHAR 1 Completed indicator

Save and activate the table after this change!

In addition, you must create a message in message class MQ:

Access Transaction SE80 - individual object - further objects - edit and create message number MQ350 with the following text: 'Cluster no. exceeds maximum of 9998'.

Save this message.

Ad 2.:

The problem is only solved if you make an entry into exception table EWUCLCT. With this entry, you enlarge the cluster block size. As a result of this, less cluster blocks are written.

To do this proceed as follows:

Create program ZEWUCLCT in your system. You find the program in Note 189908. Call up the program and enter the following parameters: PACKAGE: active package

TABNAME: Name of terminated table

CLU_SIZE: 10000000

COM_BLOCK: 01000000

TASK_NUMB: 04

JOB_NUMB: 04

PARABCLU: 0020

Execute the program and check via Transaction SE16 in table EWUCLCT whether the entry has been made correctly.

With this record, the cluster block size was increased from 5 MB to 10 MB (parameter CLU_SIZE).

In general:

For more information on the parameters and influencing factors, refer to Note 181476. There you also find program ZEWUCLCT.

Source code corrections

Header Data

Release Status: Released for Customer

Released on: 07.06.2001 22:00:00

Priority: Correction with high priority

Category: Program error

Primary Component: CA-EUR-CNV Local Currency Conversion

Releases

Software

Component Release From

Release To

Release And

subsequent

SAP_APPL 30 31I 31I

SAP_APPL 40 40B 40B

SAP_APPL 45 45B 45B

SAP_APPL 46 46B 46B

SAP_APPL 46C 46C 46C

Regards,

Anji