Hello,
I am using Datastage 7.1 (Unix) and one of the jobs fails with this error:
DSD.UVOpen mkdbfile: cannot create file /data/dstage/hash/DSBackup
Did anyone experienced this? The job is using the same hash file as both lookup/reference and output, the flag for 'Backup existent file' is set on the hash file stage.
The hash file is created/populated before by another previous job that unloads data from a database table. At the begining of the batch, all the hash files are being removed (rm -r)
Thank you,
T.
cannot create file ... DSBackup
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 15
- Joined: Tue Sep 09, 2003 10:41 pm
It will create the DSBackup directory automatically, so it's not like you have to pre-create it or anything. Make sure that you have the permissions that you would need to create/write to that directory and to overwrite any current backup copy that might already be there.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 15
- Joined: Tue Sep 09, 2003 10:41 pm
Thanks craig, permissions are there, this issue does not show up at every run and pretty hard to reproduce. DSBackup directory is there, with other files. Is this is a known bug?chulett wrote:It will create the DSBackup directory automatically, so it's not like you have to pre-create it or anything. Make sure that you have the permissions that you would need to create/write to that directory and to overwrite any current backup copy that might already be there.
No clue, you'd have to ask IBM how known it is, 7.1 is pretty darn old now and I don't recall what all didn't work properly there.
Do you really need to delete it each time? Perhaps just clearing it would help. Unfortunately, you're going to need to nail down what the failed runs have in common or what is different about them from the ones where everything works and it sounds like that could be a bit of a problem for you. I'd ping your official support provider first in your shoes, then start burning brain cells if they can't help.
![Wink :wink:](./images/smilies/icon_wink.gif)
Do you really need to delete it each time? Perhaps just clearing it would help. Unfortunately, you're going to need to nail down what the failed runs have in common or what is different about them from the ones where everything works and it sounds like that could be a bit of a problem for you. I'd ping your official support provider first in your shoes, then start burning brain cells if they can't help.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers