We only have one server available to us.ray.wurlod wrote:Is node1 a different machine from the conductor node? ...
Search found 119 matches
- Mon May 18, 2009 9:00 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Basic Transformer within Parallel Job
- Replies: 7
- Views: 6975
- Mon May 18, 2009 8:52 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Basic Transformer within Parallel Job
- Replies: 7
- Views: 6975
- Fri May 15, 2009 6:45 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Basic Transformer within Parallel Job
- Replies: 7
- Views: 6975
The initial error on the Basic Transformer was: 1885 FATAL Thu May 14 22:45:56 2009 BASIC_Transformer_18,0: dspipe_wait(1597): Writer timed out waiting for Reader to connect. On trying to re-run the job after this failure (job is reset) we got the following on every other attempt: Event Id: 1995 Tim...
- Fri May 15, 2009 5:25 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Basic Transformer within Parallel Job
- Replies: 7
- Views: 6975
Basic Transformer within Parallel Job
We have a parallel job which incorporates a Basic Transformer. When running a job there was a failure around the Basic Transformer due to some resources error on the UNIX server. When we restarted the job it kept failing as the Basic Transformer job was left in an invalid state. This is despite us d...
- Mon Dec 04, 2006 4:00 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Deadlock on SQL Server
- Replies: 6
- Views: 13636
I'm afraid that I never ever sorted this problem - my jobs run almost every night without any deadlocks and it is not too important if they fail as the missed data will be picked up the following error. Still don't understand how there can be deadlock on a select statement - it maybe on a worktable ...
- Fri Dec 23, 2005 7:53 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Deadlock on SQL Server
- Replies: 6
- Views: 13636
Thanks for the reply. I have been over at the DBA's desks and have gone through logs/housekeeping etc all of which have shown nothing up. My area of expertise is in the Database area so I have (in my mind) exhausted all areas of the database. It is doubtful that there were adhoc queries running as i...
- Fri Dec 23, 2005 6:16 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Deadlock on SQL Server
- Replies: 6
- Views: 13636
Deadlock on SQL Server
I have a Multi Instance Job Sequence (10 wide) that is started concurrently. The first thing the Job Sequence does is to run an underlying Server Job (again multi instance) which attaches to a SQL Server selecting between 50 - 500 rows per instance. Each result set is written back to a different has...
- Thu Dec 22, 2005 9:13 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Use of 'C' in Parallel Jobs
- Replies: 2
- Views: 2383
Use of 'C' in Parallel Jobs
I've read a great many threads on Parallel Jobs vs Server Jobs on topics such as which to use and when, BASIC vs 'C', and the future threat to Server Jobs being removed from the Product going forward. These fears have been alleviated somewhat by some of the comments on this forum. However, it seems ...
- Fri Dec 02, 2005 5:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Getting Job Logs
- Replies: 5
- Views: 5217
This is what I have done to get the log information for datastage job runs. (1) RESET Job before running it and then run following commands dsjob -lognewest $Project $SequencerName.$DSN > Filename first_event_id=`cat FileName |grep Newest | awk '{print $4}'` first_event_id=`expr $first_event_id + 1`...
- Wed Nov 30, 2005 9:44 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Strange Behaviour in Loop
- Replies: 7
- Views: 4975
I tried to create a simple loop Job Sequence that I could send to Support that mimicked the behaviour described above rather than send the entire Job Sequence that I have(had). Each example that I created worked differently (and as expected) contrary to the problem I have described. I can only imagi...
- Mon Nov 21, 2005 9:17 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Strange Behaviour in Loop
- Replies: 7
- Views: 4975
- Mon Nov 21, 2005 8:48 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Strange Behaviour in Loop
- Replies: 7
- Views: 4975
- Mon Nov 21, 2005 8:16 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Strange Behaviour in Loop
- Replies: 7
- Views: 4975
- Mon Nov 21, 2005 5:05 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Strange Behaviour in Loop
- Replies: 7
- Views: 4975
Strange Behaviour in Loop
I have a Job Sequence where I FTP files to another server. The FTP activity is within a StartLoop...EndLoop activity which is set for 1 to 3. i.e. if the first FTP attempt fails then the process will go round the loop and retry it 3 times. If the FTP fails on the 3rd attempt then it should follow th...
- Mon Oct 10, 2005 1:15 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Hawk/Serrano Release
- Replies: 4
- Views: 3124
Thanks for the response - looks like we won't be going towards Hawk for a while until I find the time to learn PX. I'd love to come out to the conference but seeing as I have never even had a local based training course I think the chances are very remote but I'll keep asking !!. Looks like I'll hav...