I copied this from a posting by l_homme_de_rio made in response to "multiload utility in Parallel mode", viewtopic.php?t=90722.I guess You're trying to load a terradata tables isn't it ?? If so did you set "-sessionsperplayer" and "-requestedsessions " as DB options ???
All the best
While we have been using Torrent and now DataStage PX with DB2 for several years, we are very new to using PX with Teradata. I have gotten a read to work successfully - after some fighting. I am now having problems with the write. In my read, I had set sessionsperplayer=1, but did not use the requestedsessions option. The read worked fine.
FYI, Our setup: We are running PX 7.1 on an IBM AIX server with 8 logical nodes. We have 1 physical node for our dev Teradata database, running V2R5.1, with 7 amps.
Now that I am trying a write, I just about blew up our Teradata database with all the sessions it tried to create. I used the same settings as used in the read. In the same topic mentioned above, I noticed another posting with this comment (again, user l_homme_de_rio):
I am wondering if the bolded comment is describing what happened to me. Do I understand correctly that in PX terms, 1 node (the Unix server, that is) = 1 player? If not, how can you determine the actual number of players that are being used? I am guessing that I will need to use the RequestedSessions option? If we have 7 amps, would I set that option to 7?Note: Setting the value of SessionsPerPlayer too low on a large system can result in so many players that the step
fails due to insufficient resources. In that case, SessionsPerPlayer should be increased. The value of the optional
RequestedSessions is a number between 1 and the number of vprocs in the database. The default is the maximum number
of available sessions.
Any idea why I would run into problems with the write, when the read worked just fine?
I really appreciate the help. Thanks!