DSXchange

Let's try the hex dump again. Unfortunately, Ray got exactly what he asked for, but what we really need are a sample of the results of this: od -hc filename - the 'h' gets us the 'hex' part along with the 'c'haracter information.

Requests for details are usually fulfilled by reading documentation. And posting a single error from your log without any supporting detail is not any way to get help, how can we? For example... Are you able to connect via the TE stage now? If so, what changed? What other errors/warnings were logged...

Depends on what you consider necessary. If you don't, you'll get that warning once in each project when the file is created. To avoid it, 'Test' the routine once from the Manager/Designer before any job runs that uses it.

Right. As you've said, a timestamp is a timestamp so if it is formatted correctly for an insert it should be formatted correctly for an update as well. As to whether the stage is generating the correct SQL or not, I'd be surprised if it wasn't but I've been surprised before. One way to confirm or de...

The link is in his sig.

You'd have to purchase drivers for that AFAIK.

True, there's still an upper limit of around 400 or 500 MBs as noted, and it seems to vary by platform. You really should be getting many small XML files rather than a small number of really big ones.

No, you should not need to convert the timestamp in to a date (Oracle dates are effectively timestamps in that they hold date/time). I ask about it because Oracle requires a TO_DATE() function when performing an insert or an update to a DATE field unless the format you use matches the "NLS_DAT...

It's been mentioned here before, but one thing to keep in mind is the fact that it is an AIX-specific solution.

What you first tried would be the proper syntax: TO_DATE(ORCHESTRATE.STRT_DT_TM,'yyyy-mm-dd hh24:mi:ss')) However, your error implies that your timestamp is not in the format noted in the mask, which is probably also why your update is not working. I'm curious... can you peek out the actual value of...

Understand that the question was regarding Oracle log files, not the job's log. But yes, in general, issues like that would be recorded in the job's log but not for a combo action like this.

Regardless of platform, any log files would be in the scratch space defined in your config file. However, only the load option (which leverages sqlldr) creates log files, insert/update does not.

Only sqlldr creates log files.

They really don't have any updates to perform. As noted, set Upsert Mode to User-defined Update Only and use an insert statement in the Update SQL field.

Not really, you need to make sure index maintenance is enabled and that you don't have duplicate values in unique indexes.