DSXchange

Not sure what's so confusing about that message. It didn't need to wait at all as the file was there the first time it checked. Nothing more mysterious than that.

It would be simple in a Server job... does this really need to be PX?

Unfortunately, none of that means squat. As noted, the only thing that will shed some light on this is the 'From previous run...' entry if it shows up. It doesn't always. Keep at it, reset the job after failure and see if that log entries appears... without it we really don't know where to start. BT...

kcbland wrote:Set the derivation of the stage variable to itself (FRED = FRED).

Actually, just leave it blank.

Been discussed a number of times, here is one example.

Clear is transactional, so that part may have failed and you ended up inserting into a non-empty table. Either that or there's duplicates in your source. One of the two... or perhaps both reasons.

Search the forum, causes for this have been covered a number of times.

Database (lack of) space issue - take it to your DBA for resolution. Heck, if they are any good they should already know about it and be out looking for more space.

Ignore any Fatal errors logged during the reset, they aren't germain to any problem but are an artifact of the reset. All that matters is the 'From previous run...' entry if it exists, as it will pull the appropriate entry from the &PH& phantom directory and (hopefully) provide a clue as to ...

sheema wrote:I have used user defined Sql, where i am not doing any conversion.

You have to follow all of the suggestions, not just some. Let the stage generate the sql.

Reset the job from the Director and let us know if you get a new entry in the log that says "From previous run...". If so, double-click on it and post the contents.

Knock it off with the User Defined, let the stage generate the sql for you unless you've got absolutely no other choice. Define it in the job as a size 19 Timestamp and then format the date as the sql expects it: YYYY-MM-DD HH24:MI:SS Use something very much like this to achieve that: OCONV(ICON...

A colon is the concatenation operator and for some reason an empty string is being appended to the field. [shrug]

You might also want to elaborate on what your problem is. Saying "this is not working" doesn't help us help you. What's not working about it?

All would work and be fine, not sure any one is 'best' or especially better than the other unless it more closely aligns with your company's standards. In any case, the job (or script) could be scheduled and run each day and if there's nothing to do then do not run the processing job. If you want to...