Job failure: lookups on datasets

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
ckporter
Participant
Posts: 3
Joined: Fri Oct 06, 2006 7:01 am

Job failure: lookups on datasets

Post by ckporter »

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
samsuf2002
Premium Member
Premium Member
Posts: 397
Joined: Wed Apr 12, 2006 2:28 pm
Location: Tennesse

Post by samsuf2002 »

make sure the path u r giving is correct
hi sam here
ckporter
Participant
Posts: 3
Joined: Fri Oct 06, 2006 7:01 am

Post by ckporter »

samsuf2002 wrote:make sure the path u r giving is correct
The path looks good. What else could be causing this?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Re: Job failure: lookups on datasets

Post by ArndW »

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
...
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

(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"
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
jgreve
Premium Member
Premium Member
Posts: 107
Joined: Mon Sep 25, 2006 4:25 pm

Chris, can your DS write to C:\TEMP\bogus.ds instead?

Post by jgreve »

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"
RW, that makes sense.
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"
If so, does "marcw" have write-permissions
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.
ckporter
Participant
Posts: 3
Joined: Fri Oct 06, 2006 7:01 am

a solution

Post by ckporter »

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 :)

Chris
Post Reply