Orchestrate was unable to write to any of the files:

[Tej]

Pls any of them can help in the issue, this is happen in production env,
these are error messages:

Orchestrate was unable to write to any of the files:
Block write failure. Partition: 0
Write to dataset on [node 8] failed: Success
The error occurred on Orchestrate node XXX(hostname XXX)

[Tej]

Pls any of them can help in the issue, this is happen in production env,
these are error messages:

Orchestrate was unable to write to any of the files:
Block write failure. Partition: 0
Write to dataset on [node 8] failed: Success
The error occurred on Orchestrate node XXX(hostname XXX)

can any one help in this issue,

[Tej]

Pls any of them can help in the issue, this is happen in production env,
these are error messages:

Orchestrate was unable to write to any of the files:
Block write failure. Partition: 0
Write to dataset on [node 8] failed: Success
The error occurred on Orchestrate node XXX(hostname XXX)

its urgent can any one help in the issue

[ray.wurlod]

If it's truly urgent sign up with your support provider for premium service, and learn how much "urgent" really costs. DSXchange is an all-volunteer site, people post as and when they can, and get really offended when you do things like demand a response twice within 30 minutes after you post.

What have YOU done to try to diagnose the cause of this message?

What makes it so urgent?

[keshav0307]

Tej
for your this urgent help, you have given very few information, which make getting any help difficult.

please full details like, what are you trying to , when did you get this error, what is your job or sequence design etc. etc.

[Tej]

Actually from transfromer output link with lookup stage that has more than 20 lookup link as teradta stage.
it is not picking the data from teradata stages

[sud]

Wow, do you really mean 20 lookups linked? Hmmm, lemme guess, you are using teradata, so must be there are large volumes. The whole thing might just be crashing. Did you check with your unix admin, during the job run did you run out of scratch etc (although datastage usually throws scratch problems into the log)? If you have put 20 lookups in the same job where each brings in a lot of data, it is downright unhealthy. Provide more info - check which lookup links failed and the anount of data coming from them etc.