DSXchange

Why not take explicit control of the field rather than make assumptions about the format you'll get the data in? The generated SQL ensures this by wrapping a TO_CHAR() function around the field - why not do the same? Then you'll know exactly what you'll get, regardless of instance or NLS_DATE settin...

mctny wrote:.odbc.ini is located in your DataStage server where as Tnsnames.ora file is located in your client machine.

Nope - at least not in a DataStage discussion. Both must be on the Server.

No its self written SQL, which I used it in SQL Plus and it works fine there Means nothing. Your SQL is the culprit here and you'd not be having an issue if the stage generated it for you. If this is a DATE field in Oracle, DataStage can handle it just fine when declared as either a Date or a Times...

Are you letting the stage generate the sql?

Actually, this has been discussed in the posts here. I know because I've suffered from and posted about this very issue.

What is the NLS_LANG setting of your database? Of DataStage? You've got something other than 'single byte' data in that field.

Welcome aboard. :D

Did your company purchase the PeopleSoft PACK? If not, then your only option is to connect directly to the underlying database - Oracle - just like any other Oracle source.

And the port order is typically based on usage: popular platforms get converted before less popular ones. Sucked back in the day when I was on Tru64.

Oh, and an IBM product trumps all, it seems.

You've edited the template entries in the .odbc.ini file, not something you should be doing. They should be reverted back and copied to a new section of the file. Also note that the name of that entry must match to the entry in the uvodbc.config file. At the very least, those two changes need to be...

xcb wrote:...I don't know why I didn't try the test before asking my question, just lazy I guess :D

Not exactly a new phenomenon here.

[sigh] Yes, now that you've posted the actual error, the clear understanding shows me your problem isn't anything that I thought it was. ParamName does not reference a known parameter of the job Isn't that easy to understand? The parameter name being used in the Sequence job does not exist in the jo...

parag.s.27 wrote:I tried typing in the DSN Name but it doesnt work because i guess the DS Server engine and the DSN needs to be on the same machine.

Of course. Get the DSN created on the Server machine and give it another shot.

I don't know enough about DB2 to help much, but at least now there's enough information here such that someone who does, can.

Thank goodness. Time to mark the post as resolved, eh?

There are no 'leading zeroes' in a NUMBER field. This is just an artifact of the different mechanisms used to view the data and the differences are not significant. In other words, this is nothing to worry about unless you have specific formatting requirements in your target.

Server job Transformer uses server routines. Parallel job Transformer uses parallel routines. I intend to use the in-built routines and functions but they are not present in the expression editor of transformer but the same is there during a server job. What about that concept is so hard to underst...