Error, running with 4 nodes

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
Madhu1981
Participant
Posts: 69
Joined: Wed Feb 22, 2006 7:49 am

Error, running with 4 nodes

Post by Madhu1981 »

Hi,

I have two jobs. First job will create a dataset, which is the source of the second job.

My sencond job looks like

Dataset --> Copy --> DB2. I am unsing Upsert menthod in DB2 stage.

When i ran the job with 1 node it is runnig succewsfully. When i ran with 4 nodes it is throwing the following error

main_program: Fatal Error: There are irreconcilable constraints on the number of
partitions of an operator: parallel Db2udb_SCR_TYPE_REAS_W.
The number of partitions is already constrained to 1,
but an eSame partitioned input virtual dataset produced by
parallel Copy_Recds has 4.
This step has 3 datasets:
ds0: {/work/EDWCST/WHSE/working/ds_TEDSZ06002JB_00001.ds
[pp] eSame=>eCollectAny
op0[4p] (parallel Dset_TEDSZ06002JB_00001)}
ds1: {op0[4p] (parallel Dset_TEDSZ06002JB_00001)
[pp] eSame#>eCollectAny
op1[4p] (parallel Copy_Recds)}
ds2: {op1[4p] (parallel Copy_Recds)
[pp] eSame>>eCollectAny
op2[1p] (parallel Db2udb_SCR_TYPE_REAS_W)}
It has 3 operators:
op0[4p] {(parallel Dset_TEDSZ06002JB_00001)
}
op1[4p] {(parallel Copy_Recds)
}
op2[1p] {(parallel Db2udb_SCR_TYPE_REAS_W)
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Why did you post 2 identical new questions when you already have a current thread on the same error message and same subject? That will not get you any quicker or better answers.

This is the active thread that should be responded to
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The other thread has "while" in the subject; this one has a comma. :wink:
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply