DSXchange

Nor does it look like DD-MON-YY which is what your TO_DATE (which you obviously already have) is expecting. Your routine will need to produce a date in *that* format for it to work with that generated sql. Doing that properly can't give you "the above" error again, if you think it is - post your lat...

The Google Toolbar has a built in spell-checker. Works for any text field where you can input data, like when posting to a web forum.

There's an option in Server to tell DataStage that a column 'Contains Terminators' and thus treat them as data rather than record delimiters. I would think a similar option would exist in PX... somewhere.

Sounds to me like the 'input' is indeed YYYYMMDD and the 'routine' (whatever it is) is successfully converting it to YYYY-MM-DD. Oracle then rejects it as there is no TO_DATE() conversion specified and it is not in the default NLS_DATE format for the target database. Or the generated mask doesn't ma...

What are these other 'special characters' for the field and record delimiters in the file? Have you configured the stage to use them?

Are you using a supported compiler?

... and then delete them, either individually or by Category, from the GUI. Hope you have a good backup!

Your method is perfectly fine, just needs a little tweak. I wouldn't use 'After' anything for this, what would you do if only the after part failed? Rerun everything? Take your Sequential to ODBC job and remove the Sequential stage. Add a stage variable, it is required to satisfy the compiler but yo...

Ah... Toad does that automatically behind the scenes based on your setting for the Option that controls what a Date or Timestamp looks like your in data grid. The TO_CHAR() I mean. Forgot about that.

You should be able to see that if you spool out the generated SQL Toad used.

Yes, it sounds like it is time to reindex. I tend to do that from the DS.TOOLS menu after a LOGTO of the project so I don't have to worry about the exact syntax. It runs a 'DS.REINDEX ALL' command from what I remember. Word of warning. Make sure there are no other processes of any kind attached to y...

The OCI stage doesn't return the error description in any link variable that I recall. Perhaps with a 10g client? Or via ODBC?

Any reason to not use an XML Input stage to parse that for you?

Whatever works for your email server, typically space or comma. Better answer would be to create a group.

That's a pretty PX-specific answer for a Server question.

What datatypes are you using for DATE1 and TIME1 in your job?