DSXchange

I guess you'll need to weigh your options. Either use the more accurate orchdbutil one table at a time, or import them all at once and correct any problems one table at a time. Lesser of two evils, it seems.

What database supports 'IF' constructs like that? I've only seen syntax of that nature inside a CASE statement...

A "disordered way"? You may want to explain what that means. Sounds like you haven't even gotten to the CLOB part yet. Are you having a problem simply trying to read the file because there are newlines in one field? Move the Columns tab in the Sequential File stage over to the right and change the '...

Perhaps we should clarify the question. Devsonali, what exactly are you seeking? What 'online documentation' are you looking for in regards to SQL in ODBC stage - what kind of SQL you can use there? Or as Kim is asking, some way to create 'online documentation' from existing SQL your jobs are using?...

Check this post for a list of error codes. Specifically you'll note that -1 means "Invalid job handle". I would assume that your attach call failed.

Yes. Are you looking for PX specific functions that return external formats?

Build a generic routine to leverage DSGetLinkInfo. Use it in a Routine Activity stage to return a row count from the previous job. Branch based on the value returned. You conditionally send emails the same way - by branching your workflow in the Sequence. That's what the various Triggers control - h...

It was "SU"? Stuffed Up?

If your XPath expressions are not appropriate, it is conceivable that records came into the stage but nothing was generated. Are you certain no output file was created?

There is no such thing as an @INROWNUM of 0. You don't "need" to abort, from what I can tell you just need to conditionally execute a series of following jobs when the records selected is not zero. So, have the Sequence (no 'r') job check the job after it runs to see if it processed any rows. Only c...

Sure, both Date() and Time() are available.

Well... you ran out of space. Take the issue to your DBA.

Ok. So your Update Action is 'Truncate table then insert rows'. An OCI load of that nature would be the easiest to implement but the slowest way to perform that function. It's fine for 'small' volumes but for larger ones... not so much. For pure inserts into an empty table, switch to bulk loading - ...

What stage are you using? What 'update action'?

and executes the first it finds according to the Windows system PATH. Of course it does, that's How It Works regardless of application. This is a known issue with a known solution which has been posted both here and at the IBM site from what I recall. It's not a 'DataStage bug' but a PATH problem, ...