DSXchange

Let's play the 'please give us some sample data' game again. This time, using code tags much like Ray did, can you supply a small set of your actual input data and what the desired output should look like? Three separate examples would be best, not side by side so they don't all run together like l...

The problem persists because... you haven't changed anything? Or is this now a separate job that checks another job or jobs? Describe it, this problem job - in detail - especially why it needs to call this routine in the transformer.

There's really nothing all that fundamentally different about a UNIX install. You'll have an 'install.sh' script to run rather than (I assume) a setup.exe to double-click on. The Installation and Upgrade Guide has sections for UNIX installs, things to do before and after the install... it's all there.

Would not the CFF stage handle these?

I'm not sure. I'm familiar with how you'd do all this on a UNIX server but have never had the pleasure of working with DataStage on Windows. So some other kind soul will need to step in and help with that aspect of this issue, before I lead you too far astray.

There is no RTIAgent without the SOA Edition being installed. They are leveraging the Web Services PACK, a different animal from RTI.

Oh, you betcha. As Ray would say, you just need to bring buckets of cash!

What was confusing about my reply posted: Fri Mar 16, 2007 11:12 pm?

Time to call Support, it seems.

So, by "connection" you must mean the tnsnames.ora file entry aka the Data Source Name. That's not client specific, per se. It's just a text file that generally lives in the $ORACLE_HOME/network/admin directory of the current client. If you are using the 9i client then you'd need to ensure the conne...

No, the 'OCI' stages leverage the client directly and have nothing to do with ODBC. Now, you could use the ODBC stage (or the DRS in ODBC mode) to use that connection, but you are much better off getting the 'native' connectivity working. IMHO.

You'll need to leverage the dsjob command line command in your UNIX script (and it should be a generic script that all jobs can use) and then schedule that via your Enterprise Scheduling software. You'll find a couple of such scripts posted here and much discussion on the subject. You'll also find a...

You sure you want to do that in a transformer? Once for every row processed by the job?

Use the 'Initial Value' area of a Stage Variable to do that if you only need to check once, then leverage that variable in the constraint for the job run.

No. That's exactly what it means. And there's no "option" where you can change that timeout value. Run fewer jobs at the same time.

Yup. Been there, done that.