DSXchange

Okay, which part do you need help with? Rather than spoon-feed an answer, would rather do more of a nudge in the proper direction. Or at least give that a shot. :wink: The Parallel Transform functions are all documented and the section on 'Date and Time Functions' will be very helpful here. You can ...

Just wanted to make sure before I moved your post over to the Server specific forum so that hopefully you don't get any Valid For Parallel Only advice.

Can you post the actual error message from your job log?

Welcome. Is this actually a Server job you are working with? You have marked the post as such but wanted to double-check.

So... just to clarify your piggy-backing... you are getting this: "Error message: Not attached to a job". And you are also migrating from an older version to a newer version? If so provide those details, please.

From what you posted, it would seem it times out when your credentials are missing - not that they are 'certainly wrong'. This is why Mike noted "In your timeout example, it does not appear that you have provided any of the acceptable authentication options".

Emphasis mine.

Well then technically you don't need to do anything as it will end at the Execute Command stage if it doesn't need to send the email. Or you can make it more obvious by sending the "Otherwise" link to a Sequencer with a meaningful name like "NoEmailNeeded" or some such. With only...

What do you want to happen? Add an "Otherwise" trigger to the EC stage to catch that and send it wherever you need.

Check $CommandOuput from the Execute Command for "<>1" in your trigger tp the Notification. And remove the Field Mark (@FM) from the output there as well.

Kinda thought that might be the issue as it had bit me in the past but I always wait for Ernie to chime in first before exposing my XML ignorance.

Asked and answered in your other post, I'm afraid. Still a no.

I'm curious why you are asking this question again when you already know the answer is NO.

Yeah, or that. Have fun.

As already noted, the most flexible way is a Date Dimension or something very much akin to one. If you don't have one as part of a Data Warehouse, you could always build one. The lookup table, not the whole warehouse. :wink: Failing that you could put together something, a custom routine or BuildOP ...

It won't if all you do is "put", to see the messages you need to call DBMS_OUTPUT.ENABLE first. And then I'm not sure as it is really a PL/SQL debugging tool so may not be possible to get the lines unless you wrap what you are doing up in a stored procedure.

And from what little I know, you really shouldn't be doing more than moving the data straight to a staging area... continuously. Some other process should be doing all the other work, I do believe.