XI Archiving: Restarting a terminated archived job.

[Former Member]

Hi All,

Due to some constraints, our PI server (devt) has only 9.5 GB of disk space for the archive directory. We have 300,000 messages that is flagged for archiving and it seems that the archiving job will terminate with a dataset_write_error which we assume is caused because there is not enough disk space in the archive folders.

After moving the previous archive files out of the directory to reclaim the disk space, we restarted the archive job.Will restarting the archive job allow the archive job to pick up from where it was terminated or will it "restart" from beginning?

Anyone experienced something similar before?

[former_member334189 · Accepted solution]

Dear Lugman,

the behaviour of the new archiving job depends on the configuration of archiving object BC_XMB (transaction AOBJ). If the option "Do Not Before End of Write Phase" is set (default), then the next archiving job will start from the very beginning. In this case all archive file written by the previous job can be deleted. If the option is de-selected the new archiving job will start with the last archiving file. All files that were written sucessfully before the error ocurred are safe.

In general you might also want to increase the retention period temporarily. This way you reduce the number of messages to be archived in one single blow and you have better control on the data volume that is written to file.

Best regards,

Harald Keimer

XI Development Support

SAP AG, Walldorf