Append to DataSet - expecting 3 segments, read 4 segments

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
pneumalin
Premium Member
Premium Member
Posts: 125
Joined: Sat May 07, 2005 6:32 am

Append to DataSet - expecting 3 segments, read 4 segments

Post by pneumalin »

Hi All,
Has anyone encountered similar warning message like:
opt/bi/datasets/bloomberg/bb_bond_price_FromFile.ds, expecting 2 segments, read 3 segments.

I have 6 instances appending to the same dataset concurrently, they finished ok with the above warnings. All the warning message states the same content, but the counting is different as following:
expecting 3 segments, read 4 segments
expecting 5 segments, read 6 segments...etc.

Any advises except Message Handler to avoid the warning is appreciated!

Thanks!
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Updating a dataset would given you very different error. May I know what is the job design?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
pneumalin
Premium Member
Premium Member
Posts: 125
Joined: Sat May 07, 2005 6:32 am

Post by pneumalin »

The Job design is very simple. It only contains 3 stages including SourceFile, Transformer and Target DataSet. The job simply uses "append" since it will be called by 6 instances using different source files and appending to the same dataset.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

How many nodes do you have in your configuration file and do you repartition?
pneumalin
Premium Member
Premium Member
Posts: 125
Joined: Sat May 07, 2005 6:32 am

Post by pneumalin »

Arnold,
I know someone will ask this question, fotgot to mention that in previous update.
I used 1 node only!
Thanks!
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Are all of the sources compatiable with the given layout?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Look in Tools > Data Set Management in Manager client. On how many partitions is each of the Data Sets actually defined?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
pneumalin
Premium Member
Premium Member
Posts: 125
Joined: Sat May 07, 2005 6:32 am

Post by pneumalin »

Only one partition# 0 showed up and the NODE name is node1.
We just use the default.apt that is configured to one node only.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

What if you run all the job serially? Will this error prompts again?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
pneumalin
Premium Member
Premium Member
Posts: 125
Joined: Sat May 07, 2005 6:32 am

Post by pneumalin »

No, The warning message goes away if the jobs are run sequentially.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

I am wondering, how it allowed you to write to a dataset in paralle. And not gave out all those errors that I got when I did the same.
Why cant you serialize the flow, unless requiered to write in parallel otherwise?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
pneumalin
Premium Member
Premium Member
Posts: 125
Joined: Sat May 07, 2005 6:32 am

Post by pneumalin »

Kumar,
We have to schedule the 6 instances to wait for the files arrival in a certain period, and we don't know when exatly the file will arrive. That's why we have to run them in parallel.
Thanks for your advise.
Post Reply