Datastage termination error

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
karry450
Participant
Posts: 201
Joined: Wed Nov 14, 2007 11:31 pm
Location: HYD

Datastage termination error

Post by karry450 »

Hi friends,

Im trying to load a dimensional table from ORACLE TO ORACLE.

Here in MY Targey key field is a Database sequence generated, have taken ORACLE stage and written seq.next val as custom sql.

This is actually working fine in DS7.5.2.

We have migrated the same job to DS8.1 , the job doesnt work here.

And the error is
Abnormal termination of DataStage.
Fault type is 6. Layer type is BASIC run machine.
Fault occurred in BASIC program DSP.Open at address 574.


But when I replace the database sequence with this function KeyMgtGetNextValueConcurrent(<COLUMN_NAME>) my job is working fine.

can anyone help me regarding this.

Thanks
Karthik
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Does the user with which you are connecting to Oracle via DataStage have select priviledges on the sequence ?
karry450
Participant
Posts: 201
Joined: Wed Nov 14, 2007 11:31 pm
Location: HYD

Post by karry450 »

Sainath.Srinivasan wrote:Does the user with which you are connecting to Oracle via DataStage have select priviledges on the sequence ? ...
Yeah I am the user and I have select privilages on the Datastage Sequence.

Thanks
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What other errors are logged? I'm assuming that's your "From previous run..." message after you reset it, yes?
-craig

"You can never have too many knives" -- Logan Nine Fingers
karry450
Participant
Posts: 201
Joined: Wed Nov 14, 2007 11:31 pm
Location: HYD

Post by karry450 »

[quote="chulett"]What other errors are logged? I'm assuming that's your "From previous run..." message after you reset it, yes? ...[/quote

my job is getting struck when it reaches SELECT SEQ.NEXTVAL even after 1 hour time it doesnt show up anything. So I forcibly stopped it and reset it then that the error I have posted is the message after resetting the job.

thanks
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Any idea what "getting stuck" actually means? An issue on the database side I would assume. Has your DBA monitored the job to see what happens when it runs?
-craig

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