DSXchange

LAST_KEY is what, the stage variable that is a derivation for?

Yes, that would be the correct command to completely clear the log entries for that job.

For starters, your log issue is going to be from the zillions of warnings your failed sqlldr load is slamming into the hashed file. Best to just clear it, do you know the job number for this job? From the Administrator, issue a CLEAR.FILE RT_LOGnnn where nnn is the job number in question. If you are...

So, are you saying that when 70% of the data gets rejected, you can go in and remove the 30% that loaded, rerun the exact same data again and then they load 100%?

More than likely, your records are failing to "upsert" due to duplicate key issues... but we'd really need to know what you mean by the "clean up the table" action you do that fixes things. Truncate?

Just one more quick question ....what about if the load is ising sqlldr or direct load ? This env has no meaning in that case ....So what is the process or design you suggest to handle this ?? Not really all that quick of a question, but basically - failed sqlldr loads are not a Good Thing and gene...

When the stage "closes", technically.

Ah... so this only affects the XMETA repository then. That makes more sense.

I'm curious if you've successfully run other jobs in that Production environment with BASIC Transformer stages before this or if that is the crux of the problem. Rather than focusing on the SPLICE angle, that is.

No, too many variables. And that's really a chat you need to have with your DBA anyway.

And this literally goes in and nukes all entries from all logs in all projects on a server, even if jobs are running?

As I said, it's documented. Refer to the Plug-In Installation and Configuration Guide pdf which is the InstConf.pdf in your Docs directory. There are also specific ones for the Oracle stages as well.

You don't "pass multiple rows" to a reference link and a hashed file stage cannot return more than one row per lookup - both are singleton operations mandated by the "destructive overwrite" nature of a hashed file which does not allow duplicates per key. If you really need to ret...

"pipelines"?

OK... I'm going to ask again. Is there anyone there you are working with onsite that knows the Server product and whom can help you with this? Sorry, but you are asking very basic questions on very basic issues and people here are really not meant to be a substitute for proper training. Not to menti...

"dlls"? Who cares, none are required before. You've already got the answer to your "how" question, run the commands they gave you and you'll be good to go. If you have a question or problem after that, come back.