DSXchange

Can anybody plz send me the designer,manager,administrator and director guide on my mail id i.e. datastageforum@yahoo.com As noted, if your company owns the software then you have access to the documentation. It is not freely available out there for the masses, at least not in any legal fashion. An...

I have absolutely no idea - let us know what you find out when you ask IBM.

I don't have anything to add other than -

Don't quote yourself to fix problems in a post, go back and edit the problematic post. You can do that at any time, unlike a delete which can only be performed if there are no replies to the post.

What task? A job cannot reset itself, period, before or after. And if it's Aborted, how do you run it to get to the 'before' part without manually resetting it first?

Can you clearly state exactly what the requirements are you're trying to implement?

What database is this?

What are you using to perform the metadata import, specifically what 'Table Definition' option did you choose? And what stage do you use in your jobs to connect to DB2? Is the answer to both questions ODBC?

Rather than attempt the log purge / clear from the Director, you'd be much better off connecting to that project via the Administrator and issuing a CLEAR.FILE RT_LOG438 command. Make sure you re-establish your Auto Purge settings as they will be removed by that command as well.

Sorry, but I'm going to state the obvious - you really shouldn't be using a client version that doesn't match your server version, no matter how minor that difference seems to be. Strange things happen.

Still seems to me that all depends on exactly why they feel the need to split their files in two.

True, there can be various "levels" of directories but they will be in an "rc" (or "runcom") directory.

http://en.wikipedia.org/wiki/Configuration_file

A job can't reset itself "after job" as it's still running at that point. Better to reset before the next run rather than immediately after the abort.

You would send them the query, the explain plan and the table ddl and the Server query and explain plan as well I would imagine. Let them take it from there.

No, there's no configuration step or Oracle options you're missing here.

What 'input stage'? One in particular? Depends on the data?

Cut down your Display sizes to avoid the warning noted.

Still not following. You're wondering if Server is faster because you are 'misusing' the OCI stage there?

Me, I'd be asking IBM why the OE stage is not using the 'right' explain plan.

There are sparse lookups in the 7.x release, so "yes" all around to your questions. Well, except for the "I thought we needed to upgrade" one.