Can we give call a sequence in close command of a lookup ora

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
skaruturi
Participant
Posts: 10
Joined: Wed Sep 13, 2006 2:17 am

Can we give call a sequence in close command of a lookup ora

Post by skaruturi »

We are calling a function to create a sequence in close command.In our environment it is creating the sequence and job isrunning fine.When we dsx form and change the environment,The job is getting aborted saying sequence is not created
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: Can we give call a sequence in close command of a lookup

Post by chulett »

skaruturi wrote:When we dsx form and change the environment,
:? How about you rephrase this bit? Not really sure what you mean there.
-craig

"You can never have too many knives" -- Logan Nine Fingers
skaruturi
Participant
Posts: 10
Joined: Wed Sep 13, 2006 2:17 am

When we take dsx form of the job and inport in other environ

Post by skaruturi »

When we take dsx form of the job and inport in other environmnerts,the job is getting aborted saying .'Sequence is not created'
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

And you are positive that this Oracle sequence exists in this other database and your user has all the grants it needs to it?
-craig

"You can never have too many knives" -- Logan Nine Fingers
meena
Participant
Posts: 430
Joined: Tue Sep 13, 2005 12:17 pm

Re: When we take dsx form of the job and inport in other env

Post by meena »

Hi Skaruturi,
It is .dsx file, not dsx form.Can you be clear with what you are doing and about the job).
skaruturi wrote:When we take dsx form of the job and inport in other environmnerts,the job is getting aborted saying .'Sequence is not created'
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

My guess is that the OP is executing a stored procedure or some other command from the Close command of an Oracle Enterprise stage, and that this sp/command tries to invoke a sequence. The message suggests that the sequence of that name is not accessible from the instance specified by the job parameters when a non-default value is supplied. This comes as no surprise really; it suggests that the sequence has not been created in the other instance, or that someone got its name wrong. Check using some other client, such as Oracle Enterprise Manager or TOAD.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply