Hi,
I had my job failed due to resource issues in the server. After sometime i re-ran the same job and it ran fine. But when I run second time after the abend job failed with error message "When deleting data set XXX.ds, previous delete attempt not complete; removing XXX.ds.being_deleted in order to proceed."
I tried searching the same topic but for everyone looks like the immediate re-run had this problem, not the second run.
But I dont understand why the first re-run was successful and second run is having this warning message. Could someone help me in understand this?
Additional thought, Is it good to promote this warning message id to Info in project level to avoid the warning message? Does that lead to any other valid warning scenario unnotified?
.ds.being_deleted
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 111
- Joined: Mon Nov 30, 2009 7:21 am
- Location: Bangalore
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Its normal to have this warning when the job abended and could not perform necessary clean-up.
It should come in the subsequent run after the abort.
And yes it can be safely demoted to informational message as the message id is different for each type of warning and error in data stage however do a search on message id in message reference to be sure.
It should come in the subsequent run after the abort.
And yes it can be safely demoted to informational message as the message id is different for each type of warning and error in data stage however do a search on message id in message reference to be sure.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
-
- Participant
- Posts: 111
- Joined: Mon Nov 30, 2009 7:21 am
- Location: Bangalore