Hi. I was wondering if anyone could shed some light on the meaning of this fatal error:
"OUTWARDS_RI_TRANSACTION_NAME,0: Fatal Error: I/O subsystem: Open of /E=/Ascential/DataStage/Datasets/OUTWARDS_RI_TRANSACTION_NAME.ds.marcw.APHRODITE.0000.0000.0000.10dc.c6f6873b.0000.85ce82bd failed: Not a directory"
I have several lookups on datasets in this job, but for some reason 2 of my lookups are throwing this error. Even on the same lookup stage, I have 5 datasets being referenced but only 2 have this error.
I don't think the error is caused by a missing directory, since my other jobs use the same directory and work fine.
Thanks in advance,
Chris
Job failure: lookups on datasets
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
Re: Job failure: lookups on datasets
I'm not sure, put the path doesn't look good to me. Particularly the 3rd character
ckporter wrote:...
/E=/Ascential/DataStage/Datasets/OUTWARDS_RI_TRANSACTION_NAME.ds.marcw.APHRODITE.0000.0000.0000.10dc.c6f6873b.0000.85ce82bd failed: Not a directory
...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Chris, can your DS write to C:\TEMP\bogus.ds instead?
RW, that makes sense.ray.wurlod wrote:(a) you appear to have "=" rather than ":" after the drive letter
(b) the pathname should be that of the control file; that is, end at ".ds"
While I would swear I saw path-names somewhere
(like in KSH or OSH) using C=/whatever (instead
of the normal C:\whatever), I can't find it now.
Anyway... the err msg Chris posted might be from that.
Chris, what is the value for your DataSet FILE="...." property?
Perhaps this?
FILE="OUTWARDS_RI_TRANSACTION_NAME.ds"
Based on the full name of the (attempted) dataset in
your post, I'm guessing your job is running under
Code: Select all
userid="marcw"
machine name = "APHRODITE"
to make new folders in APHRODITE's
"E:\Ascential\DataStage\Datasets" folder?
And is Ascential actually installed
on APHRODITE's E: drive?
(just checking...)
Anyay-
Just for fun, Chris, try running that job with
your DataSet's FILE="C:\TEMP\bogus.ds"
and see if it can write to that dataset.
If that works, I'd try
DataSet's FILE="bogus.ds"
and see if it makes a file something like this:
"E:\Ascential\DataStage\Datasets\bogus.ds.marw.APHRODITE.00000..."
Good luck!
John G.
a solution
Thanks for the replies everyone.
I re-created the datasets (by re-running the jobs that create them) and now I receive no error.
Another example of the "when all else fails, re-do and re-run" axiom of datastage debugging![Smile :)](./images/smilies/icon_smile.gif)
Chris
I re-created the datasets (by re-running the jobs that create them) and now I receive no error.
Another example of the "when all else fails, re-do and re-run" axiom of datastage debugging
![Smile :)](./images/smilies/icon_smile.gif)
Chris