Page 1 of 1

Warning while deleting dataset by Job

Posted: Tue Dec 03, 2013 2:18 pm
by pavi
Hello Team,

I am getting a warning while I am running the job.

When deleting data set <DataSET Descriptor File.ds>, previous delete attempt not complete; removing <DAATSETDescriptorFile.DS>.being_deleted in order to proceed.

But when I re run the job it finishes with out warning.I do fear that when this code goes to prod it will be difficult to re run.

How to remove this warning?

Thanks!
Pavan

another warning after the previous on

Posted: Tue Dec 03, 2013 2:20 pm
by pavi
<DATAFile>,0: Could not delete descriptor file: <Descriptor file.ds>
filesystem related error

Posted: Wed Dec 04, 2013 3:46 am
by ray.wurlod
Do you have write permission to the parent directory of the Data Set descriptor file? You need rwx permission to a parent directory in order to be able to delete any of its contained objects.

Posted: Wed Dec 04, 2013 12:39 pm
by pavi
We have write permission.If I run the job second time it finishes with out warning and there is no pattern regarding the warning.

Posted: Wed Dec 04, 2013 2:04 pm
by Mike
This can occur if you run out of tmp space while DataStage is in the middle of deleting a dataset. As the message indicates, a subsequent run will clean up the partially deleted dataset.

No need to do anything to remove the warning since it would only re-occur if you run out of tmp space in the middle of another delete operation.

Just make sure you have adequate tmp space.

Mike

Posted: Thu Dec 05, 2013 8:47 am
by Klaus Schaefer
I faced this error once having a corrupted dataset afterwards. I was able to delete the dataset with the dataset manager. Having done so the job then ran fine creating a new proper dataset.

Klaus

Posted: Wed Dec 18, 2013 5:01 pm
by pavi
When datastage deleted the descriptor file and datafiles,does it directly deletes the files from its location or it moves the files in to some tmp space and deletes them?

Posted: Wed Dec 18, 2013 5:17 pm
by chulett
They are deleted directly.

Posted: Fri Jan 03, 2014 3:42 pm
by pavi
Admin had increased the Ulimit from 1000 to 10000 which resolved this issue.Thanks to all for looking into it and providing your thoughts.