DSXchange

No. You can, I would wager, fix your batch file so it doesn't "hang up". Typically, that means it has stopped to ask for permission to do something and that question never gets answered. If you would be willing to post your batch file (wrapped in tags!)[/i] we could see if we can spot the ...

Add the $APT variable to "disable operator combinality" to your job, set it to true and rerun the job. We'll get a more meaningful error that way.

No, isn't that enough?

That's your fatal and you have an UNUSABLE index on your table now. Talk to your DBA about how to fix that. And see about not skipping "index maintenance" for any future loads.

So, Job 2 actually has an Expand stage in it, yes? Your "picture" shows Compress for both, so best to just go back and edit that post to correct it. Any idea what the actual 'corrupted' timestamp value is? Perhaps add a link to a Peek stage to find out. And double-check that your metadata ...

All loaded and zero rejected doesn't mean everything was fine. Keep reading, are there any ORA errors mentioned after that? Duplicates in a unique index, perhaps?

The .log and .bad files are created in your "scratch" space defined by the config file in use at the time the job was run.

OK, that's fine. HOWEVER if you have any packed fields then a simple ASCII conversion will destroy them. Are they the fields that are not 'displaying properly'?

By fixing your config file. Go to Designer / Tools / Configurations, load it up and then press 'Check'. (you've got too many curly braces in your file, btw)

You don't "need" to if you're thinking it won't work somehow before you do that, but it certainly couldn't hurt to have that as a standard step.

First off, did you actually add the $APT_CONFIG_FILE parameter to the job and point it to your new 'two node' file?

chulett wrote:How about you go to that TRANS4 file and actually post the code from the lines mentioned plus several on either side, let us take a look?

Sainath.Srinivasan wrote:Craig after reading this = -> -> -> -> ->

Realize that the vast majority of the time there's no... 'break'... between stages, they run in a serial fashion and a single record can go all the way through the job before the next one starts. So you don't typically have one stage finishing before the next stage even starts.

My guess... perl script.

You have to forgive my lack of knowledge on uvsh...I just read one of the thread...and tried those things.. http://dsxchange.com/viewtopic.php?t=119027&sid=3349fcc6eda4324873d9b9e52173009d Ha! And mine, too, it seems. I've not seen that particular command in a long while and forgot about the wh...