DSXchange

The answer is "it depends". Probably best to talk to your DBA and get their opinion on the matter.

There's still only one log for the job but the Director will create multiple 'views' into it, one for each invocation id. If you look at the log for the main job, you'll see all of the log messages for all invocations there, jumbled together. There are a number of posts here on how to remove those i...

Your metadata is incorrect and it's saying it can't find the record delimiter you said would be there. As noted, correct that.

When you check the DDL in the OE stage, the CREATE TABLE statement it will use, does it show them in the 'proper' order there? How are you checking the actual table itself? I ask because tools like Toad can show you the columns in different orders, so just want to make sure it's not a 'viewer' issue.

Stop quoting yourself. And something is different between the two or both would be working. Do both jobs process the same data? Perhaps the second one needs more 'conditions' to handle it properly.

OK. Have you tried using the Stored Procedure stage rather than ODBC? Also, read the docs on the SP stage for the rules it needs to follow to work with DataStage.

That's it, eh? Not seen that before. Do any other warnings or errors come with it or just that is what is logged? Also, how often is 'often'? Do the jobs / times of occurance have anything in common?

Sorry, adding more stuffs while you were replying.

See if what I added makes sense.

Do you have a backup of the "Projects" directory where the jobs live? Or a copy saved somewhere of full exports of all projects? One of those two will be needed to recover if they were on the rebuilt C: drive. Actually... you can't simply copy DataStage from one drive to another and expect...

No, minor releases are not ones you see 'performance benefits' in, typically they are bug fixes with perhaps minor new functionality. Assuming you are on maintenance, you can order the upgrade at no extra cost and the 'readme' will list the changes from the previous releases.

Stroed in Datasatge perepective? Hmmm... basically in the RT_BPnnn directory, which is where the code the compiler generates goes. Probably other places as well, never really had a need to get all that intimate with the gory details of how things are stored in the DataStage perspective, as you put it.

What stage? Using the OCI stage on the Server side, the order always matches the column order if the stage is generating the DDL, but it sounds like that may not be the case on the PX side.

sysmq wrote:My apologies. I send it by mistake due to an error on my browser.

I know, just mess'n with ya, hence the smilie. We see plenty of double posts here, just not all that many 47 minutes apart. Couldn't resist.

Yup, 'IPC stages and settings' is a game changer here. :wink: On the debugger front, it can certainly be enlightening to step through a job. You just need one breakpoint to get that initial stoppage, after that you can step through the job one link at a time without worrying about needing more break...

I am confused in this as well. Sounds like all you need to do is to set your lookup to 'Continue' and then substitute 'kkk' if the result is found to be null... a.k.a. not found. Yes?