DSXchange

No, they are not one and the same - they perform similar functions, but for two totally different databases. So, if your target is Oracle you could use the ORABULK stage. Similarly, if your target is Red Brick you could use the RDBLOAD stage. Stick with command line sqlldr. Just because you've got a...

ray.wurlod wrote:It may be - and I'm guessing here - that the XML stage you've used is limited to 2GB and the file is actually slightly larger.

Don't believe that that is the case as I'm using the XML Output stage to generate ~300MB XML files.

Actually, you don't need to change it around.

If your destination target is a DATE field in Oracle, then simply declare it as a Timestamp datatype. I'll say it again - No conversion required, simply send it to the OCI stage as is.

What 'update action' are you using in the DRS stage? Not something user defined, I hope? The error indicates you are having a problem converting character data to numeric data. Check this link for probably more details than you really wanted. In a nutshell: Character Source to Numeric Target Followi...

This makes absolutely no sense.

Are you sure your problem isn't at the other end with SQL Server? Copy and paste the exact error from the job log into your next post, please.

What you posted is easy as it's exactly what it needs to look like for an Oracle DATE field declared as a Timestamp in DataStage: YYYY-MM-DD HH24:MI:SS So for that just send it on through - no conversion needed. For something coming in like '2005/04/15', it's just a matter of rearranging the bits us...

You should be able to get the SQL code, I would think, as long as 'code' means the SQL error number. Sometimes people want the verbose error message as well and that typically can only be farmed from the logs post-job... unless you look it up yourself in a procedure, as you mentioned.

Yes, what you need comes with the 'standard' installation of DataStage and the XML plugins are in the Designer palette under the 'Real Time' category. What you are looking for is the XML Output stage.

There should also be a .pdf in your 'Docs' folder that explains how they are used.

Welcome aboard, Jim. :D I'm not familiar at all with the DB2 API stage, but as long as it works like any other passive database stage you should be able to capture what you need. The first order of business would be to setup a 'reject' link to capture rows that have been spit back by your target dat...

You use the LOGTO command when you have come in from the command line, not the Administrator window. When you click Command to open the 'TCL' window from the Administrator, you are automatically 'logged to' whichever project you had highlighted when you clicked the button. And, as you have discovere...

I believe that some of this behaviour is version dependant. For example, in 7.0.1 job parameters do not resolve in either field. Glad that they seem to have 'fixed' it in later versions, but they should have fixed it proper, allowing them in both fields.

This link does not seem to work ....... can any body view this link The link would have worked fine if it was posted properly as a link. The way it was done, it needed to be cut-and-pasted into the Address line of your browser to see. The URL tags allow you to link to other postings rather easily, ...

The 'bad' rows will never even make it to the transformer unless you handle the problem columns as Ken suggested.

Otherwise you need to bring the records in as one long string, 'validate' them in some fasion and then parse out the appropriate fields only on the rows that pass the validation.

Exactly. Glad "it worked", however.

Actually, was looking for a little more detail than that. Examples of input and output formats are always good. If what you mean is that you need to strip formatting characters from the date, look at - in no particular order - the Trim and EReplace functions. The latter can be used to replace a char...