DSXchange

Excellent! Thanks for posting the solution. :D

Good start. A couple of points, qualified by the fact that this is all off the top of my head. 1) No need to reset for a RUNWARN. Probably better to check for the ones you don't need to reset and do it for any other code. Jobs do fail in more ways than just by Aborting, ya know. 2) You should check ...

In Oracle, a datatype of NUMBER is the same as NUMBER(38). Ray meant for you to change the table definition in your DataStage metadata, not in the database itself.

Oracle table name are case sensitive if you have created table with lower case... That's only true if you explicity enclosed the table name in double-quotes when you did so. And if you did, you deserve all the grief that brings upon your head. Otherwise, you can create a table in any mix of case yo...

sb_akarmarkar wrote:...if aborted then use DSJ.RUNRESET in DSRunJob else DSJ.RUNNORMAL

Small correction. If aborted, then you would need to do the reset run then the normal run. It's 'and' not 'else'.

Pretty much exactly what it says - you are trying to assign a value to a parameter name that does not exist in the job. Make sure your values are correct - including the case.

I just want to know that how can DS help us to do the same thing as version control does. As noted, it can't, which is why Ascential purchased and bundled VC into the product suite. Perhaps if you let us know why you are asking, what you have in mind or concerns that you have, we could address them.

Do you have a more specific question?

'Version Control' is the name of a client tool that is on your installation media and which you should install. There is online help and .pdf documentation that explains how it is used.

ray.wurlod wrote:What is x..y?

StageName..LinkName I do believe is how it is reported. Or perhaps the other way 'round.

The names were probably changed to protect the innocent, anyway.

If the target table was "there" you wouldn't be getting the error. So, your mission - should you choose to accept it - is to find out what piece you've got wrong. Check the instance/sid/dsn you are connecting to in the stage, the userid you are connecting with and the schema owner you have specified...

How would you solve this problem if DataStage wasn't involved?

You have no control over how it builds multiple filenames, other than supplying the 'base' name. It will then, from the second file generated onwards, append an '_?' number to that. The trigger column controls when the current file is closed and a new one opened. Where you put the Key column is what...

No, not really. They can be running but not accessible for a number of reasons, some on the RTI Server side and some on the RTI Agent side. For example, we've already seen times where everything is running except for the RTI Agent daemon on the ETL server and without that nothing works. Need some wa...

That would be the proper way to handle it. The one project that was deemed to be the source of any common objects should be the only place where the code is not protected - i.e not read only. Any changes made there would need to be distributed - promoted - to every other project. Best done through V...

USERSTATUS.