DSXchange

Isn't one of the requirements to doing that that the stage must actually be used to create the sequence? If true, was that in fact done? :? it should genarate the seq but itsn't.... Regardless of what you think it should or should not do, this is what I was referring to and asking if you had done -...

More obvious and 'DataStage like' to simply constrain things after the file is read to only pass rows where the value in that column is 10. Something has to 'read' the entire file (being sequential media and all) so why not your job? Then (as a general comment) you don't have to worry about what to ...

probal wrote:I guess if I am using istool utility to export assets I must use the istool utility to import those.

Yes.

I got 17 other matches when I did an exact search for "There are irreconcilable constraints on the number", perhaps one of them will help you out.

kksr wrote:we are unable to find the mentioned patch (96576 for DS EE 7.5.1A ) in IBM web site. Please share the Patch/ fix details for this issue.

That would need to come from your official support provider.

That would indeed be what he said.

You cannot export jobs 'in dsx format' using istool, I would guess that means you are specifying that as the extension rather than .isx and thinking the format is changing to match? :? You are correct, however - you must use istool for the import of these files as well, the client tools only support...

You're the first to post anything like that. Probably best to involve your official support provider in helping track this one down.

Can you share any information on when exactly this happens? What your job looks like? Stages used? (etc etc etc)

Of course. In that case reverse the choice. That or (as noted) take the extra effort to convert the pair to a single character you "know" won't occur in the source data.

I'm pretty sure you'll find that one of the Best Practices people will advocate here is to not bring your PX executables over to new environments but rather to recompile them there once the design time information has been transferred.

ps: Marking your post as Resolved.

Isn't one of the requirements to doing that that the stage must actually be used to create the sequence? If true, was that in fact done?

Or the other way 'round. :wink: That would usually be the answer to the question if the attempt to schedule the job had failed. Since we're not talking about the 'Add to Schedule' step but rather the actual scheduled run, something else is going on, some kind of difference in the environments betwee...

Well... the assertion that the ODBC driver 'sits atop the Oracle client' would be incorrect in this case since we're talking wire drivers, which means no client is involved. Perhaps that's part of the issue, these particular drivers may not support 8i - that would have to be something you confirm or...

Now that I have a better idea of what you speak, that would be my advice as well. Move it aside 'after job' with a date/timestamp as noted.

Sounds like Teradata to me, if so have you asked this question of your Teradata DBA? I'm assuming these "report files" are something specific to the database and outside of DataStage's direct control.