DSXchange

Correct!

You would use those if you actually wanted to access Oracle via ODBC. My general Rule Of Thumb is to use a "native" access method (like OCI for Oracle) over a more "generic" method (like ODBC) if at all possible. The standard Oracle ODBC driver would still require SQL*Net in order to operate, wherea...

Seems to depend on your platform as to whether you can use Job Parameters in the CommandExecution stage or not. From what I've seen, it doesn't work on most. Try using #Parm1# instead of $Parm1 and see if that works. If it doesn't, you'll need to fall back on a Routine that wrappers your call to the...

Still mixing your fruits. The ".odbc.ini" file has nothing to do with setting up OCI. SQL*Net is part of Oracle and you must have (at the very least) an Oracle Client (and thus SQL*Net) installed on the same server that DataStage lives on. I'm assuming you do and that is what $ORACLE_HOME is pointin...

It can be done, as far as I know. Do a search in this forum for remsh to see various discussions on this topic, that should get you started.

You seem to mixing apples and oranges. What you are setting up via 'dsenv' is for use by OCI not ODBC. If you've correctly set the $ORACLE_HOME and $SHLIB_PATH environment variables in dsenv then restarted DataStage, you should be fine. Try to import metadata using the OCI9 plugin, or drop one in a ...

I personally don't see a reason why a Sequence would ever need to 'abort' itself. A 'warning' message should do the job just fine. My .02 on that. I also never (well, hardly ever) use a 'Failed' trigger. Unless I specifically need to differentiate between "Finished (with warnings)" and "Aborted" in ...

Welcome! Sorry, only questions at this point, no answers yet.

So, when does this error happen? Only when writing to XML?

Nothing else magical in your job, IPC stages or Row Buffering turn on, anything like that? Also, for the record - operating system?

If I needed UtilityAbortToLog as well as \sdk\Utility\UtilityWarningToLog, should i add another output trigger (link) ? Yes, mostly. You can add another triggered link from a Job stage or simply chain them together, one after the other. It really depends on exactly what you are trying to accomplish...

500+ posts and getting your sig wrong, too!

See... frowned upon.

Yes. It is frowned upon by some, but as long as you understand the link ordering requirements and don't mind a little red in your jobs, it does work. I personally don't do this, but I know people that do. It's a good thing to drop an annotation about in the job so people don't think something is 'br...

Roy - You are probably going to need to share some of the information you used in the HFC before anyone can do more than take stabs in the dark. What are the gory details of your hash? Number of keys? Number of fields? Average record length? What do your keys look like? What hash type(s) are you usi...

His suggestion is based on the notion that your Repository indexing may have become incorrect Is it not a notion worth pursuing? As Ray mentioned, we all know where you are doing your export from - these are suggestions on places to go and things to try to help solve your problem. The biggest quest...

This is actually a pretty straight-forward problem to solve. We added a Routine stage to the error handle section of all of our 'Child' Sequences. When a job has problems, do your normal error handling (send an email, whatever) and then execute one of the "Utility???ToLog" routines - either "Warn" o...