I have a PX Job that is to upsert records to a DB2 table. The job consists of a sequential file which goes through a transformer and then the DB2 stage which performs the upsert.
The job will insert around half the records and then hang (typcially 1.5 million rows at this point). But, maybe 2 times out of 20 tries it successfully processed all 3 million rows into the table??
Does this sound like an issue with the nodepools being specified? or perhaps the database connections???
Any suggestions are appreciated...
PX db2 insert job hangs after processing...
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3
- Joined: Tue Nov 16, 2004 11:45 am
-
- Participant
- Posts: 82
- Joined: Thu Dec 02, 2004 10:27 pm
- Location: INDIA
-
- Participant
- Posts: 3
- Joined: Tue Nov 16, 2004 11:45 am
Hello nalombardi,
what is your commit frequency? Does the hang behaviour change if you change this? When a hang occurs, does the UNIX process use 0% CPU or does it disappear? Doe the hang always occur at the same place (either row or wall-clock time)? If the wall-clock time is the same, then you are getting a timeout of some sort...
what is your commit frequency? Does the hang behaviour change if you change this? When a hang occurs, does the UNIX process use 0% CPU or does it disappear? Doe the hang always occur at the same place (either row or wall-clock time)? If the wall-clock time is the same, then you are getting a timeout of some sort...
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>