Page 1 of 1
"Abnormal Termination" error in server DS job
Posted: Sun Apr 20, 2008 7:07 pm
by yaminids
Hello friends,
One of our DataStage jobs fails everyday with the same error and at the same step of the job.
The job extracts data from 10 tables and populates 10 staging tables. The design is simple
ODBC1==>TRANS==>ODBC1
ODBC2==>TRANS==>ODBC2 and so on
Everyday the job fails at 'Transformer 7' with the following error
Abnormal termination of stage VNDINFO_CA.T7 detected
Any ideas why the job would fail at the same step everyday?
Thanks
Yamini
Posted: Sun Apr 20, 2008 7:21 pm
by ray.wurlod
Only the obvious one - that you're doing something in step 7 that DataStage doesn't like.
When you reset the job in Director after it fails, what extra information appears in the "from previous run..." event in the log?
Posted: Sun Apr 20, 2008 7:33 pm
by yaminids
Ray,
The following is the entry from the log after resetting the job. I am not sure why it fails only at step7 when all the steps are identical
From previous run
DataStage Job 678 Phantom 20106
Abnormal termination of DataStage.
Fault type is 11. Layer type is BASIC run machine.
Fault occurred in BASIC program DSD.BCIGetByKey at address 1de.
Can please help me in fixing the issue
Thanks in advance
Yamini
Posted: Sun Apr 20, 2008 8:18 pm
by ray.wurlod
Are you trying to do a lookup using a null-valued reference key?
DSD.BCIGetByKey is the internal routine that retrieves a row from an ODBC or UniVerse stage on a reference input link.
You did not mention doing any lookups in your original post in this thread.
Posted: Sun Apr 20, 2008 9:35 pm
by yaminids
Sorry for missing out the reference key information.
Every step retrieves the Max key from the corresponding staging table before inserting the data. The Max key is used (in place of Oracle sequence) to populate the primary key in the staging table
ODBC===>HASH FILE
------------------||
----------------- ||
ODBC====> TRANS==>ODBC
Am I doing something wrong while retrieving the Max key?
Posted: Sun Apr 20, 2008 10:32 pm
by ray.wurlod
I don't know. I can't see vital things like your reference key expression and whether the value(s) being supplied to it are null or not.
YOU need to do the detective work. Only you have access to all the details of your job design. That it fails consistently in the same place strongly suggests that there is something amiss in that place.