DSXchange

I'm going to go out on a limb here and suggest you store them as... null values. Is there any particular reason why you wouldn't want to do that?

This is the FAQ post I mentioned, in case you hadn't found it yet.

Up to you, it can be done in either place. In this case it isn't complex enough that it must be done in a routine, so suggest you stick within the transformer.

You really want to suggest they CAST the INVOICE_QUANTITY to a date?

Rather than giving us things 'like' your error message, it is always best to post the actual error from the logs. That being said, there's something in your returned parameter value that is not valid in a string. Without knowing exactly what you are doing, about all we can do is guess what might fix...

This is answered in the FAQ forum. Basically all you need to do is replace the commas with the EOR characters for your O/S - in your case <CR><LF> pairs. Write out one record like that and it will read back in as many.

Use functions like Convert or EReplace along with CHAR(13):CHAR(10).

Ah... if only that were true.

OCI doth not.

Why are you counting them manually? They're numbered in the Transformer stage.

So, did you get this working? It's marked as Resolved but doesn't seem like it is.

If you still need help, explain exactly what you are doing in the OCI stage - update action primarily but the more information the better.

Oh, and please delete your duplicate post before someone replies to it.

If you let the stage generate the SQL, you would never see this error. However, since people seem to just LOVE to stuff sql created in other tools like Toad into an OCI stage, things like this happen. One of the properties of the stage is TABLE NAME. It is a required property and right now has no va...

There are carriage returns in your data. You need to decide - do you want to preserve them or remove them from the data? Load it as is or keep it looking all purty and multi-line like? Preserve? Changing things like fixed-width or delimited won't help. You need to let DataStage know that there are ...

Target SQL - Insert /*+ append*/ into <column name> from view There is nothing more to describe in job design Sure there is. Can we get a little more precise in our description of the target SQL, espcially seeing as how that's where the problem lies? You don't insert without selecting from somewher...

I did - as noted, it is in my first reply in this thread. And as noted, two words there should appear different - blue - they are the link to the topic in question.

Or simply search for NLS_LANG and you'll find a plethora of topics.

We had a similar experience with the OCI stage in 7.5.2 - junk after certain column values. For us it wasn't timestamp or decimal fields, but just varchars substringed from a CLOB. And it only happened when using a 10g client to access our 10g instance. For us, reverting back to a 9i client solved t...