Job aborted after finish loading all records.

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
ttk1973
Participant
Posts: 6
Joined: Mon Apr 11, 2005 2:47 am

Job aborted after finish loading all records.

Post by ttk1973 »

Hi all,

When we ran a DataStage job, it aborted and encountered the following error messages when the job has extracted and loaded all the records:
-----------------------------------------------------------------------------

Attempting to Cleanup after ABORT raised in stage BGH2InvoiceExtraction1TestWilliam9..Bill_Invoice_Detail

------------------------------------------------------------------------------------------------------------------

DataStage Job 333 Phantom 21896
Program "DSD.StageRun": Line 617, COMMON size mismatch in subroutine "DSP.Close".

Program "DSD.StageRun": Line 617, Unable to load file "DSP.Close".

Program "DSD.StageRun": Line 617, Unable to load subroutine.

Attempting to Cleanup after ABORT raised in stage BGH2InvoiceExtraction1TestWilliam9..Bill_Invoice_Detail

DataStage Phantom Aborting with @ABORT.CODE = 3

--------------------------------------------------------------------------------------

We would like to know what could be the possible cause to the above error messages and is there any resolution to the problem?

Our job is read from text file(main stream), reference to 3 oracle tables in a transformer and load the data into a text file.


Thank you.

ttk9694
loveojha2
Participant
Posts: 362
Joined: Thu May 26, 2005 12:59 am

Post by loveojha2 »

Do a Reset of the Job from the Director.
And see the log from previous run whether it gives any additional information of the failure.
Success consists of getting up just one more time than you fall.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Does your job design include an after-stage or after-job subroutine?

If not, then you have incompatible versions of the internal DataStage routines DSP.Open and DSP.Close installed - check with your support provider.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ttk1973
Participant
Posts: 6
Joined: Mon Apr 11, 2005 2:47 am

Post by ttk1973 »

Hi all,

After the reset, we got the following messages:

From previous run
DataStage Job 333 Phantom 3100
jobnotify: Unknown error
DataStage Phantom Finished.
[3110] DSD.StageRun BGH2InvoiceExtraction1TestWilliam9. BGH2InvoiceExtraction1TestWilliam9.Transformation1 6 0/0/1 - core dumped.

From previous run
DataStage Job 333 Phantom 3110
Abnormal termination of DataStage.
Fault type is 10. Layer type is BASIC run machine.
Fault occurred in BASIC program DSD.StageRun at address 1

We don't have before or after subroutine for this job.

Regard
ttk9694
loveojha2
Participant
Posts: 362
Joined: Thu May 26, 2005 12:59 am

Post by loveojha2 »

Is this problem only within this job, Are other jobs running?
If it is repeating thing in other jobs also then Ray's clue need to be taken care off.
What version of DS are you using?
Success consists of getting up just one more time than you fall.
ttk1973
Participant
Posts: 6
Joined: Mon Apr 11, 2005 2:47 am

Post by ttk1973 »

Some of the jobs also encountered the same error. I'm running on DS version 7.5A. How can we check the internal version of the DS.Open & DS.Close routine.

Could this incompatible of internal DS routines caused by inproper DS installation. We are considering re-installation of DS but it is the last option that we will do.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

The COMMON mismatch is due to routines with different versions of the COMMON block in the catalog. As you surmise, this is probably due to problems during an upgrade.
ttk1973
Participant
Posts: 6
Joined: Mon Apr 11, 2005 2:47 am

Post by ttk1973 »

We have re-installed the DS Server with the latest version 7.5.2 but we still encountered the same error. Finally, we able to get rid of this error when using oracle client 9.2.0.5 or oracle client 10g instead of oracle client 9.2.0.6 on HPUX 11.11 platform. All this while, only job with reference/lookup to oracle database will encountered this problem. I think it is an incompatibility issue on the following combination: DS 7.5.2 or 7.5A + HPUX 11.11 + Oracle Client 9.2.0.6.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

In other words, a bug in the 9.2.0.6 Oracle client... who would'a thunk it? :wink:

Perhaps you should roll up and not down, I think the latest version for 9iR2 is what - 9.2.0.8?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply