DSXchange

it seems DS does have issues executing sub queries or say group by queries. No, it doesn't. There's nothing about DataStage that would make your joins 'not work' - that's between you, your query and your source tables. Get the query working in your favorite tool - Toad, sqlplus, whatever - and it w...

You can't. They are only available in the BASIC Transformer stage, with all the issues and caveats that come with it.

Checkpoints. Have you not looked into the following options available on the General tab of a Sequence job's properties? * Add checkpoints so sequence is restartable on failure * Automatically handle activities that fail The first is the primary option you need but those two generally work well tog...

Your conversion seems fine. However, you haven't told us what your target database / table is, the nature of your sql nor what the actual error is that you get. So... Database? Target field type in database (not the job)? SQL is generated or user defined? Post it. Error when target field is declared...

Wow... I so want to say "Have you searched the forums?" or "What did your official Support provider have to say when you asked them?" but I guess I won't. Sorry, but I for one don't recall ever seeing this particular behaviour, but then I haven't seen anything near the variety of installs that you h...

Doh... didn't see this one. deleted my reply to the other post so it can still be deleted.

I don't really "do" Sql Server, but it just sounds like you've violated a foreign key contraint. Your target table has a FK constraint to another table and a field in your inserted record does not have a matching value in the constraining table. If I had to guess, it's probably the 'name' field and ...

That's because of the 'reference' checks going on. Go to the 'Tools / Options' menu in the Manager and check the Usage Analysis section. Turning off: * Warn if deleting/renaming referenced item * Warn if compiling referenced routine Can speed things up considerably. Make sure you understand what tur...

Did I do anything wrong? Yes. As noted, you are using an 'external' function internally. There's no need for it and it may very well be unnecessarily slowing things down. Replace your function call in the derivation with simply FileDate and see if things speed up again. Derivations are one of those...

What kind of problem are you having with it? Any valid SQL can be run as 'user defined' in the stage.

Oracle may be 'installed properly' but it sounds like you haven't configured DataStage for Oracle. Check the Install and Upgrade Guide for the procedure. The documentation for the Oracle stages should also contain the information.

First off, it's the Sybase OC stage where 'OC' stands for Open Client. OCI is the Oracle stage. 1) The OC stage requires the actual Sysbase Open Client be installed on the DataStage server to function. DataStage leverages that to connect just like any other application would. How it works beyond tha...

There's a period between the two.

Ray's 'no' was in answer to your 'Could I be admin in Sever but not in Parallel?' question. He then commented that 'Further research is required' in an effort to solve your problem.

Yes, there would be issues and you don't want to be deleting things like that from the O/S. Instead, issue a 'CLEAR.FILE RT_LOG1917' from the Administrator client, then re-establish your Auto-Purge settings.

At it's heart, it's no different than any other 'upgrade' from one server to another. Simpler in some ways than an 'in place' upgrade as you've still got your old version to fall back on. You've just got a new O/S adding a little wrinkle. So, first step is to install the new version of DataStage on ...