DSXchange

Not that I've seen. You can, however, get an HTML file - double-click on the table def, swith to the Layout tab and right-click.

Spell your requirements out in words. That would help both us and yourself as well.

So, I take it you don't have a "load/modification date" in the target table, something you could query on to get a daily count?

Link counts aren't going to help you if the job runs constantly... unless you take a delta from day to day, of course.

Could you let us know which particular values, please? That and mark the post as 'Resolved'? Thanks!

If it was, you would be getting a 'T30 specific' message. For example:

Unable to allocate Type 30 descriptor, table is full

Yes, please try to keep up. And note that there's no "if-then-else" in Arnd's constraint, no "then N else Y' or "then @TRUE else @FALSE" as that is completely unnecessary. These are expressions and they will automagically evaluate to true or false if you let them - and you should let them do so if a...

But still if any of the subsequence S1, S2 or S3 fails then the master sequence M1 is not getting aborted, but is showing Finished(See Log) Interesting thought. I've been assuming that the 'fails' mentioned above means 'aborted' but perhaps that's not the case. If the "sub-sequences" don't abort th...

2048. Tell us why you think you would need a key size that large. What are you trying to accomplish?

Known 'issue', use the Orchestrate orchdbutil utility instead to import the metadata instead.

500, I do believe, but still...

In the meantime, while we wait - can you please explain what you mean by this? we need to install two Oracle client on DataStage Server to implement a secure connection. What do you mean by 'secure connection'? And are you saying that some jobs will need to use one client and some jobs will need to ...

I thought you meant that nothing was showing up, are you saying only the pids of certain jobs are not showing up?

I strongly believe that the NLS Settings for Oracle and DataStage should be in sync. Not necessarily. Only do this is you are sure the incoming data is appropriate for the NLS setting of the database. Setting them to be the same will mean no conversion is done during the load which could lead to 'c...

You need to open a case with your Support provider. The need for all that triggering and explicit abort handling went out the window when the 'Automatically handle' options came on the scene. The simple 'OK trigger only' flow should do exactly what you need - I do this many places in our 7.5.x relea...

Ugh. Why not write the bad vaules to a file, then send one email after the job completes if the file is populated rather than sending an email for every bad record?