DSXchange

What is your target - sequential file, database, what? How is the field defined there? I'm assuming the 'column as timestamp' applies to the DataStage job so we need to clarify how the actual target column is defined.

You probably have a filter condition set in Toad, if you are looking via the Schema Browser.

Hint: Destructive Overwrite. Are your key values unique? I would wager... not.

Have you confirmed a timeout issue or is it just a belief? I for one haven't heard of a "3 minute timeout" - a 3 minute egg, sure, but timeouts are usually more in the 30 to 60 minute range. IMHO, 3 would just be crazy and would affect more than this one job.

Why do you believe you need to "dump 400+ million" records into a hashed file? Best Practice is to constrain your hashed builds to the incremental keys so you only have "just what you need" hashed up.

And a derivation of Convert("%!?","",In.Col) will remove these "special characters" from the field. Etc.

All the monitor shows is how many records were sent down the link to the database, it is not an indication of how many were successful.

You can arrange for a "total refresh" but I really wouldn't suggest it.

Post the actual, complete, unedited error. Also curious what you believe the difference between "English text" and "Ascii text" to be.

Looking at some previously generated log files they just contain table information and rows loaded etc so i'm not so sure if it will hold any key information as to why it's not being loaded. They will if something goes wrong, you must be looking at logs from successful loads. Any "bad" file will ju...

A simple "upgrade in place" where the new version overwrites the old version will not cause any loss of job logs.

You can help yourself rather easily. This has been discussed ad nauseum here, search for the error message to find the conversations.

Click on the Help button inside the ODBC stage.

In your shoes, I would be taking a problem like this to my DBA since it has nothing to do with DataStage. You may not be able to simply disable them but rather need to drop and then rebuild them.

The equivalent seems to be the LOAD DATA command in MySQL, but you are better off asking questions like this over in the official MySQL forums.