Close command : parallel

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
algfr
Participant
Posts: 106
Joined: Fri Sep 09, 2005 7:42 am

Close command : parallel

Post by algfr »

Just a quick question.

When I perform a close command and am running on 2 nodes, is this normal that the close command perform for EACH node and not only once after the load is completed ?
I use Oracle

Thanks
singhald
Participant
Posts: 180
Joined: Tue Aug 23, 2005 2:50 am
Location: Bangalore
Contact:

Post by singhald »

HI Algfr,

If you are using oracle enterprise stage to load or perform any operation on close command, it doesnt matter how many nodes you are using.

it will be executed once after completion of load operation.

Thanks,[/b]
Regards,
Deepak Singhal
Everything is okay in the end. If it's not okay, then it's not the end.
algfr
Participant
Posts: 106
Joined: Fri Sep 09, 2005 7:42 am

Post by algfr »

Did you try it ? I did and it creates me two Oracle sessions.

When I use an Open command, it works fine.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

And the same command is run on both the sessions?
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
algfr
Participant
Posts: 106
Joined: Fri Sep 09, 2005 7:42 am

Post by algfr »

Exactly,

When I get to see what takes place in the oracle sessions, it creates two sessions blocking each other.

There is just one when I use an open command.

Can be worked out of course, but still, it's weird !
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

That is wierd. Can someone reproduce this on 7.x ?
Get in touch with IBM and see what they have to say about it.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
srinivas.g
Participant
Posts: 251
Joined: Mon Jun 09, 2008 5:52 am

Post by srinivas.g »

i ran same thing in datastage 7.5.1 A with four nodes.

But it is exceutes only once.

the close command query is

BEGIN
DELETE from <table name>;
COMMIT;
END;
Srinu Gadipudi
betterthanever
Participant
Posts: 152
Joined: Tue Jan 13, 2009 8:59 am

Post by betterthanever »

[quote="DSguru2B"]That is wierd. Can someone reproduce this on 7.x ?
Get in touch with IBM and see what they have to say about it.[/quote]
it happened to me as well. i was inserting into some table on 4 nodes, and my job aborts saying " i was trying to insert duplicates" .
i am on 8.0.1 on AIX 5.3.

when i changed it to run on one node...job runs fine.

Regards.
betterthanever
Participant
Posts: 152
Joined: Tue Jan 13, 2009 8:59 am

Post by betterthanever »

srinivas.g wrote:i ran same thing in datastage 7.5.1 A with four nodes.

But it is exceutes only once.

the close command query is

BEGIN
DELETE from <table name>;
COMMIT;
END;
try to insert into the table and have a primary key.
job will abort.

Regards.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Seems like you guys have unconvered a bug on the CLOSE command in 8.x.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Post Reply