DSXchange

From what I recall, to load into a SQL Server "datetime" you need to define your data type in the job as a Timestamp and then get your date in:


format, where .TTT is milliseconds which must be included. Is that something you tried?

Very interesting... changed LongVarChar to VarChar of 20K in size and (with the to_char function still in place on the select) - it worked! Without any kind of data type mismatch complaint, either.

Thanks!

I get the dubious distinction of resurrecting this thread as - now that I actually need to do the same thing - I can't make it work. We were able to successfully load a CLOB field from XML into Oracle using the LongVarchar datatype. However, success trying to select the darn thing back out is eludin...

Your problem is fully spelled out in the Fatal error message. As one would expect, the OCI stage needs three pieces of information to connect to an Oracle database - a Data Source Name or DSN (aka SID), a User ID and a Password. The message tells you that you haven't supplied a User ID in the Genera...

But what i need to have is to get the Status of the job which failed. I.e its like dynamically it should capture the status of the job activity which triggered the Error handler job. I think you're out of luck on that, at least out of the box. Scroll down to almost the bottom of this post and you'l...

I dont understand what I need exactly to do to set sharing in system level. I know. I almost didn't reply to this originally because I didn't want to get sucked into an endless thread of questions, something I really don't have the time or energy to handle right now. This is an advanced subject, a ...

The advantage is the fact that one copy of the hashed file would be shared by your three jobs, rather than having three identical copies of the hashed file in memory.

Yes, it works just fine and nothing about reading it with multiple jobs simultaneously will corrupt it. For required reading on the subject of Hash Stage Disk Caching check out the dsdskche.pdf document of the same name included in your 'Docs' directory. This includes the option of sharing hashed fi...

Nature of the beast, I'm afraid.

Check the value of the parameter being passed back. An Integer datatype requires a valid numeric value, so trying to set it to a non-numeric ( or even null) will result in that error message.

That's a different problem, when a non-zero return code is interpreted as a failure when that "Automatically handle" option is checked. This is a parameter passing problem. It sounds like your parameter value being passed back from the routine is "not appropriate" for the parameter's datatype in the...

What does your routine do? Sounds more like an internal problem trying to put that input argument to use rather than an issue of actually calling the routine.

Include any datatypes of the various parameters involved.

This doesn't look like a DataStage error to me.

Please explain what "from the server" means in this regard. Are you working with a database and it is generating the error? What stage / source / targets are involved?

Write a custom routine. Build a alphabet string with all letters from A to Z. Loop through the input argument two bytes at a time and build an output string, concatenating on the results of pulling AlphaString[number,1] each time. Or build an array to pluck letters from and take AlphaArray<number>. ...

Was wondering if 'D' was debit.

So look at using FMT for everything except the 'D' and manually tack the appropriate trailer character on based on the sign of the amount.