Hi Priyanka,
If you are mvoing huge number of messages to the copy table then there should be problem with the DROP_MAX_TABLE_LOAD parameter.
Pls. see SAP Note 872338 Point i. I copied the text below.
Keep in mind that you may have activated the table switch procedure. You can check this via transaction SXMB_ADM -> Configure delete procedure. The information button on that screen explains
the switch procedure in detail. If the switch procedure is chosen, then the XML messages will only be removed (via table drop) if
A) the retention time is expired and
B) a specific fill grade of the table is reached.
The default value is 90, that is the deletion will occur when 90% of the table is filled. You can set this parameter via transaction
SXMB_ADM -> Configure Integration Engine -> Specific Configuration.
Create an entry of category DELETION, parameter DROP_MAX_TABLE_LOAD, no subparameter.
If you encounter performance problems after execution of the switch this might be due to deletion of the table metadata during the context switch. A solution for this problem is described in Note
1032733.
To monitor the Switch Procedure (Fill Level, Active Container) you
can use transaction SXMB_MONI -> Persistence Layer Analysis. Please
note: Based on the value chosen for DROP_MAX_TABLE_LOAD the
"Current Fill Level" entry might show a red alert since the
"Maximum Number of Table Entries" is exceeded. This is nothing to
be concerned about. If you choose to use the switch procedure, we recommend setting the
parameter in a way that not too many messages are being copied. The
recommendation is to set DROP_MAX_TABLE_LOAD in a way that at the
point in time when the value of DROP_MAX_TABLE_LOAD is reached, the
ratio between messages to be copied and the total number of
messages is about 20%.
The best way to determine the correct parameter value is to multiply the rough number of messages processed per day with the number of days that these messages are being retained in the system
(retention time, see section 6). The result of this is the number of messages that need to be copied at the point in time when the value of DROP_MAX_TABLE_LOAD is reached. As mentioned before it is
recommended that this value corresponds to 20% of the total messages in the system. The total number of messages at this point in time is thus the calculated value for 'messages to be copied'
times 5 (20% x 5 = 100%). The total number of messages divided by the maximum possible number of messages in the database, is the value that should be set for DROP_MAX_TABLE_LOAD. The maximum possible number of messages is determined via a DDIC function and
can be found via transaction SXMB_MONI -> Persistence Layer
Analysis -> value of entry 'Maximum Number of Table Entries'.
Example:
Daily # of messages: 25.000
Retention time: 5 days
Max. # of table entries: 900.000
Messages to be copied during switch: 25.000 x 5 = 125.000
Total number of messages for the 20% ratio = 125.000 x 5 = 625.000
DROP_MAX_TABLE_LOAD = 625.000 / 900.000 = 70 [%]
Please keep in mind that during the execution of the switch additional table space is required to copy to the valid messages to the new master table. Example: Before the switch your system
contains 5 millionen entries. 1 million of them are still in the retention period and thus have to be copied to the new master tables. Only after the copy job finished the original tables can be dropped. Therefore you temporarily need sufficient table space to save 6 Mio messages. If there is not enough space on the database to execute the copying of messages please use report RSXMB_SWITCH_DEL_OLD_ENTRIES as described in note 842187.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.