Lookup Job aborting
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Lookup Job aborting
Hi,
Lookup Job is aboring by the fatal error "GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1: |-100|".
Structure of the job:
The job has only one OLEDB stage and one Hash file stage with 15 links. Out of 15 links, 9 links connecting to same table by different queries.
Other links are connecting to different tables.
Message by reset:
I got the message below from the previous run after reset.
From previous run
DataStage Job 304 Phantom 2192
Job Aborted after Fatal Error logged.
Program "DSD.WriteLog": Line 250, Abort.
Attempting to Cleanup after ABORT raised in stage GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT3
DataStage Phantom Aborting with @ABORT.CODE = 1
I could not identify the root cause of this problem.
could you please help me to rectify this problem?
Thanks in advance.
Regards,
Venkat
Lookup Job is aboring by the fatal error "GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1: |-100|".
Structure of the job:
The job has only one OLEDB stage and one Hash file stage with 15 links. Out of 15 links, 9 links connecting to same table by different queries.
Other links are connecting to different tables.
Message by reset:
I got the message below from the previous run after reset.
From previous run
DataStage Job 304 Phantom 2192
Job Aborted after Fatal Error logged.
Program "DSD.WriteLog": Line 250, Abort.
Attempting to Cleanup after ABORT raised in stage GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT3
DataStage Phantom Aborting with @ABORT.CODE = 1
I could not identify the root cause of this problem.
could you please help me to rectify this problem?
Thanks in advance.
Regards,
Venkat
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
-
- Premium Member
- Posts: 79
- Joined: Thu Mar 22, 2007 4:58 pm
- Location: USA
If you break down the job by link, does it work? I mean, if you make a copy of the job and remove all but 1 link, does it work as expected?
Have you tried doing this for each of the 15 links?
If you have, have you broken it down by source table (remove all links except the ones that correspond to a single source table)?
Rinse and repeat with more and more of your links until you find when/where it fails. That should permit your troubleshooting to move forward.
Have you tried doing this for each of the 15 links?
If you have, have you broken it down by source table (remove all links except the ones that correspond to a single source table)?
Rinse and repeat with more and more of your links until you find when/where it fails. That should permit your troubleshooting to move forward.
Jack Thornton
----------------
Spectacular achievement is always preceded by spectacular preparation - Robert H. Schuller
----------------
Spectacular achievement is always preceded by spectacular preparation - Robert H. Schuller
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Hi Jack,
If there are more than 2 links, it aborts by throwing the following warning messages
GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1: Failed to read the row.
GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1: OLE DB provider error HRESULT=0x80004005.
Attempting to Cleanup after ABORT raised in stage GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1
Is this giving any clue?
Regards,
Venkat
If there are more than 2 links, it aborts by throwing the following warning messages
GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1: Failed to read the row.
GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1: OLE DB provider error HRESULT=0x80004005.
Attempting to Cleanup after ABORT raised in stage GSAP_LOOKUP_CreateLkpForFormatJobs..HashLookups.IDENT1
Is this giving any clue?
Regards,
Venkat
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There's a problem with the OLEDB provider. Prove this a follows. Create a job with an OLEDB stage and an output link from it. Populate all required properties then View Data. You will get similar error messages. Since there are no other stages in the job, the OLEDB stage is clearly the culprit. Verify your OLEDB connection string and, if that's correct, verify the underlying OLEDB configuration settings.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
Hi,
Thanks Guys for your support.
This problem got resolved after applied microsoft patch mentioned in this URL - http://support.microsoft.com/kb/942861
Thanks,
Venkat
Thanks Guys for your support.
This problem got resolved after applied microsoft patch mentioned in this URL - http://support.microsoft.com/kb/942861
Thanks,
Venkat