cancel
Showing results for 
Search instead for 
Did you mean: 

Archiving and Deleting Problem

Former Member
0 Kudos

Hello Everyone! We are having some problems related to archiving and deleting of messages in our PI 7.0. We have the switch procedure configured but some messages are never deleted (even after the retention period).


The messages that are not deleted are the ones that have ADAPT_STA = 0 in SXMSPMAST table. Could anyone tell us what this status means ?

We use SXMS_REFRESH_ADAPTER_STATUS report on a daily basis to convert message status 001/008 into final state. Is there something similar to convert status 000 into final ?

Accepted Solutions (1)

Accepted Solutions (1)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Julio,

With the Switch procedure it is normal that messages will not be deleted even after the retention period has expired. The messages will be "logically deleted" or flagged for deletion when the next run of the Switch jobs execute. When the actual deletion takes place depends on the value of the DROP_MAX_TABLE_LOAD parameter.

Check this wiki for more details - Overview of the Switch Deletion Procedure

Take a look at note 872388 Troubleshooting Archiving and Deletion in PI. Check if there are any errors with the jobs in trx SM37. Check the two Reorg reports to get an overview of the messages in the system.

Also check trx SM58 for the issue in note 1734067 IDoc adapter: PI outbound error messages in SM58.

Regards

Mark

Former Member
0 Kudos

Hello Mark and thank you for the reply! Acctually, we know that physical delete happens only after the  switch procedure (that is executed when DROP_MAX_TABLE_LOAD parameter is reached)! The problem is that during the last execution of the switch procedure, the messages with ADAPT_STA = 0 where copied from container 1 to container 2.

Answers (1)

Answers (1)

Bhargavakrishna
Active Contributor
0 Kudos