DSXchange

So, actually a job parameter who's defined value is $PROJDEF in the job? Just want to confirm first as it doesn't stand on it's own and I get the impression you are trying to use it that way.

Can you be more specific as to how you are passing this around?

Talk to your DBA since that's where they are coming from. Perhaps there's an option to override that behavior?

What happens when you run it from the client with APT_DISABLE_COMBINATION set to true?

:?: Just want to make sure this is in the correct forum - Server job as you've marked the post or a PX job based on the forum posted in? Doesn't change the answer, just where this should live. For a type 1 dimension where no change history is tracked then yes, the business key is the primary attribu...

But of course! :D

What does the monitor show for the target, 4M or 1.5M? What is happening on the Oracle side, inserts only / insert else update, something else?

You can easily get the message using grep and cut on the results: grep 'Job Status' (the results) | cut -d ':' -f 2 The grep would find the line you wanted and then the cut would deliver the second semi-colon delimited field. You could then further chop it down if you need. For an aborted run you wo...

I haven't, being strictly an Oracle guy for the last umpty years. Have you involved your official support provider yet?

Reset the job and try again?

FYI - the only way to 'gracefully' exit the sequence at a particular time would be from inside the sequence itself. What does the sequence do over the course of the day - loop?

Log entries cannot be 'suppressed', only removed after the fact either via your Auto Purge setting or manually.

As noted, you don't need to do this in SQL... why not just implement the logic in job as Ray suggested?

Rather then jump on the end of an eight year old topic let's get you into one of your own.

What database is this?

As I said, you don't need to pick it from a list you can add it as a 'user defined' or custom variable, I don't recall the exact type name.

I don't know... it may be a bug with the connector, you'd need to contact your official support provider to know if that's the case. It may also be something that shouldn't have worked in the earlier version and is being (properly) caught now. We've seen both general situations here before. A couple...

Are you using a function on the fields in the transformer? As to the APT_FORCE_DECIMAL_SEPERATOR variable, to see if it helps just add it manually.