Hi,
I need to extract data from a Oracle table using a Parallel Job. If I use a 4-node configuration, will the job implicitly create 4 different connections/sessions to Oracle? In that case, if I have 20 different Parallel jobs, will I end up creating 80 connections to Oracle?
Please throw some light on this...
Cheers,
Mohan
Connection to Oracle in a DSEE environment
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 66
- Joined: Tue Dec 07, 2004 12:48 pm
-
- Participant
- Posts: 66
- Joined: Tue Dec 07, 2004 12:48 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Fewer than 20 at a time! ![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
With 20 four-node jobs simultaneously you're generating over 200 processes:
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
With 20 four-node jobs simultaneously you're generating over 200 processes:
- 20 conductor processes
80 section leader processes
80n player processes (one per stage)
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: 66
- Joined: Tue Dec 07, 2004 12:48 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That's 27 conductor processes, 108 section leader processes and 216 player processes (assuming no combination), a total of 351 processes. Do you have at least 175 CPUs on your system? It is recommended (as a rule of thumb) not to use more than two processes per CPU in PX jobs.
Can you find an approach that does not run all 27 jobs simultaneously?
Can you find an approach that does not run all 27 jobs simultaneously?
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.