cancel
Showing results for 
Search instead for 
Did you mean: 

SAP_BC_XMB_DELETE_* is running too slow to keep up with new messages

Former Member
0 Kudos

Hi,

We are using XI 3.0 SP24 and we are processing around 1 milj. messages per day. We are working on 2 clients, 100 as the integration server, and 200 as an application system.

The SAP jobs for Archiving and Deletion are all scheduled daily. We are not archiving any messages so only messages are deleted. All the relevant notes are implemented ( #872388, #874708, #836092 ). Retention times are very short, with a maximum of 4 days for asynchronous errors, and all the configuration parameters are set to a minimal logging.

As an advice of SAP we are using the Switch procedure, so we are copying to a second container and deleting the first one.

So basicly, we are not keeping the messages too long and we do not create any overhead like tracing and measurement items.

Still, the delete jobs are running very slow. Much too slow to keep up with new messages that arive. In other posts I see that the systems are copying around 30.000 of 40.000 messages per 5 minutes. We are doing around 900 messages per 5 minutes.

Does anybody know the reason for this, or any notes that I missed, hints for solving it???

Below is a part of our joblog:

-


| Date | Time | Message text

-


| 05.07.2010 | 08:05:58 | Job started

| 05.07.2010 | 08:05:58 | Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000002, user ID KOXM)

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-RELATED_OBJECTS-ASYNC: '1'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-RELATED_OBJECTS-ROWS: '100'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-ROWS_PER_LOOP-DELETE: '100'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-PERSIST_DURATION-ASYNC: '004'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-PERSIST_DURATION-SYNC: '001'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: '001'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: 'D'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: 'D'

| 05.07.2010 | 08:05:58 | Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: 'D'

| 05.07.2010 | 08:11:03 | Messages Deleted Until Now: 949

| 05.07.2010 | 08:16:08 | Messages Deleted Until Now: 2.833

| 05.07.2010 | 08:21:10 | Messages Deleted Until Now: 4.940

(...)

| 05.07.2010 | 14:48:28 | Messages Deleted Until Now: 223.851

| 05.07.2010 | 14:53:30 | Messages Deleted Until Now: 229.461

| 05.07.2010 | 14:58:30 | Messages Deleted Until Now: 234.464

| 05.07.2010 | 15:02:54 | 238.495 XML messages deleted

| 05.07.2010 | 15:02:54 | Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000002, user ID KOXM)

| 05.07.2010 | 15:02:54 | Analyze Table Container

| 05.07.2010 | 15:02:54 | Value for parameters DELETION-DROP_MAX_TABLE_LOAD: '90'

| 05.07.2010 | 15:02:56 | Current / Maximum Number of Table ENtries: 4.330.217 / 3.400.000

| 05.07.2010 | 15:02:56 | Current Fill Level: 127 %

| 05.07.2010 | 15:02:56 | A table switch is required

| 05.07.2010 | 15:02:56 | Table Switch from Container 1 to 2

| 05.07.2010 | 15:02:56 | Value for parameters DELETION-ROWS_PER_LOOP-SWITCH: '100'

| 05.07.2010 | 15:02:56 | Value for parameters DELETION-TABLE_SWITCH-MOVE_INSTEAD_OF_COPY: ''

| 05.07.2010 | 15:02:56 | Value for parameters DELETION-TABLE_SWITCH-CLUSTER_MB_MAX: '0'

| 05.07.2010 | 15:02:57 | Processed client 200

(...)

| 05.07.2010 | 15:59:41 | Messages Copied Until Now: 64.968

| 05.07.2010 | 16:05:12 | Messages Copied Until Now: 65.868

| 05.07.2010 | 16:10:38 | Messages Copied Until Now: 66.768

| 05.07.2010 | 16:16:05 | Messages Copied Until Now: 67.668

| 05.07.2010 | 16:21:23 | Messages Copied Until Now: 68.568

| 05.07.2010 | 16:26:36 | Messages Copied Until Now: 69.468

| 05.07.2010 | 16:31:56 | Messages Copied Until Now: 70.368

| 05.07.2010 | 16:37:23 | Messages Copied Until Now: 71.368

| 05.07.2010 | 16:42:47 | Messages Copied Until Now: 72.368

| 05.07.2010 | 16:48:01 | Messages Copied Until Now: 73.268

| 05.07.2010 | 16:53:20 | Messages Copied Until Now: 74.268

| 05.07.2010 | 16:58:20 | Messages Copied Until Now: 75.168

| 05.07.2010 | 17:03:39 | Messages Copied Until Now: 76.068

| 05.07.2010 | 17:09:09 | Messages Copied Until Now: 76.968

| 05.07.2010 | 17:14:24 | Messages Copied Until Now: 77.868

| 05.07.2010 | 17:19:30 | Messages Copied Until Now: 78.768

(...)

| 06.07.2010 | 14:37:27 | Messages Copied Until Now: 265.668

| 06.07.2010 | 14:42:34 | Messages Copied Until Now: 266.568

| 06.07.2010 | 14:47:41 | Messages Copied Until Now: 267.468

| 06.07.2010 | 14:52:55 | Messages Copied Until Now: 268.468

| 06.07.2010 | 14:58:25 | Messages Copied Until Now: 269.468

| 06.07.2010 | 15:03:29 | Messages Copied Until Now: 270.368

Edited by: M. Kox on Jul 6, 2010 3:20 PM

Edited by: M. Kox on Jul 6, 2010 3:41 PM

Edited by: M. Kox on Jul 6, 2010 3:43 PM

Edited by: M. Kox on Jul 6, 2010 3:44 PM

Edited by: M. Kox on Jul 6, 2010 3:50 PM

Edited by: M. Kox on Jul 6, 2010 3:51 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

If you are using Oracle you might check the database statistics.

WL

Former Member
0 Kudos

Hi,

I'm sorry for the poor layout, I don't know how te make it better.

Thanks for your reply, that was the information I forgot to mention:

We are using Windows NT + MSSQL. Not the most ideal combination......

Gr.