Skip to Content
0

How to delete an Incomplete Archiving Sessions that are incomplete, not in error

Dec 27, 2016 at 11:17 AM

806

avatar image
Former Member

Hi Experts,

Some of our archiving jobs have ended with a status of "Incomplete Archiving Jobs" in the past, and we would like to clean them. I read from the forum that, for archiving runs with errors, we can mark them for deletion, and use BC_ARCHIVE archiving object to remove the management data.

But for "Incomplete" runs, there is no "Marked for Deletion" check box that we can update with. Any ideas?

Regarding the write files sitting on the transfer directory, there is a discrepancy between the "Incomplete Archiving Job" number and the write file. Can we simply delete these files and rerun the write job again? If there is a match between the write file and the Incomplete session, we can manually complete them by selecting the session and run the delete job again. But what if there is a discrepancy?

Thanks!

Ken

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Jürgen L Dec 27, 2016 at 11:42 AM
0

more important than the name of the archiving object that you want use later to remove the management data of archives is to tell the name of the archiving object that left the session incomplete.

I can see more than 130 OSS notes when searching with the term "Incomplete Archiving Session"

Just rerunning the archiving without any change would probably return the same status, so you better search for the root cause first, and sometimes have those notes even a remark how to deal with the incomplete sessions

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Dec 29, 2016 at 05:53 PM
0

Thanks Jurgen. I agree that finding the root cause for incomplete archiving session is more important than cleansing the runs. The incomplete archiving session happen sporadically for us. The most recent encounter is a log that suggests locking issue for FI_MKKDOC object. I think this is caused by a high commit value. But since this doesn't happen consistently, we are planning to re-run archiving to archive the data that should have been archived by now. I found this program useful for resetting archiving flag status (for some of the objects)

REA_SET_STATUS.

Will look at OSS notes for each object. Thanks.

Share
10 |10000 characters needed characters left characters exceeded