Content of container 1 not yet completely copied to container 2

[Former Member]

Hi  Community

We are facing problems with the switch procedure, we have more than 100,000,000 records in tables SXMSCLUP and SXMSCLUR so some weeks ago I Performed activitites to activate archiving and deletion procedure also I ran diferent reports to change status of some messages without final estatus and it was working

After some days we realized that tables SXMSCLUP and SXMSCLUR  were still growing so an external consultant  activated the switch procedure and after two weeks the process says that it continues, next is the screenshot that I see:

I have looked for running processes in sm50 but we don't have backgroud or dialogs proccesses running so I think the process of copy is not running anymore.

Is there a way to monitor the advance this process?

On the other hand,  tables with termination 2 are growing and we don't have more space in our storage SAN next is the screenshot with the example:

the jobs of archiving and deletion  are being cancelled this due the active switch procedure so we can't delete old messages.

Next are two parameters which we set according others discussions

I need to reduce the size of DB, please could you help me

Best regards

Alfredo

[mate_moricz · Accepted solution]

Hello Alfredo,

You should run report RSXMB_TABLE_SWITCH_CONTROL in transaction SE38 to display the status of a switch run where you can if there are messages that are not yet transferred form one container to the other.

The problem is usually caused by a pending switch. During the execution of a switch, additional table space is required to copy the valid messages to the new master table. Only after the copy job finishes can the original tables be dropped. While a switch is pending, no other reorganization job is allowed to start; in particular, neither deletion jobs nor archiving jobs can run.

To complete the pending switch, you need to schedule report RSXMB_TABLE_SWITCH and execute it once as a batch job, then the pending messages will be copied over from the inactive container to the active one as below. After the copy job finishes, the inactive container will be dropped and the deletion job  SAP_BC_XMB_DELETE_<Client> can run successfully.

Regards,

Mate

[Former Member · Accepted solution]

Thanks for the answer, I'm worrking on it' I'll share the final results

best regards

Alfredo