DSXchange

None, no major considerations.
(P.S. I've landed at Keene before; the area is beautiful)

Does that mean that when you run the sub-batch job it is getting the correct userid/password/instance information but it is still failing to connect to Oracle correctly?

Kumar,

that is a rather vague error description. Which database type are you trying to connect to, and how? What is the error message that you are getting when you fail to connect to the database? Where are you connecting from (i.e. Designer, Manager)?

For test purposes, change the parameter type from password to string, then you will see if you are passing the correct values from the entries in the job run log files.

There isn't a workaround. If you have a NOT NULLable VarChar2 column and the data only has spaces in it then the bulk load method won't work.

The APT_ORACLE_PRESERVE_BLANKS will work as long as the column isn't VarChar2; I assumed that it was set so was looking for the more obscure error.

Good job - glad to see it is working.

Vinay,

the column is probably an Oracle VarChar2() datatype ... and by definition the loader trims these and makes it a null field.

Vinay, have you done what the error message has told you to do? Go to your DataStage temp directory, start with node1 and look into the directory /default/Scratch and then view the file ora.3331.899749.0.log sometimes the first /tmp node doesn't have the error, in which case I would look at the log ...

Kumar,

I think it could, but the orchadmin command output can be re-routed to a file which can be processed, whereas the graphical front-end cannot be capture that way.

Brad,

I'm not at a Px installation now, but I think if you did a "orchadmin ll {my.ds}" it will, amongst the several pages of output, give you some information on that.

I am sure that there is a limit somewhere, but it is higher than your 45 lookups. These lookups will trigger off 45 x 2(nodes) jobs to do the work, so your system performance might suffer a bit if it isn't dimensioned big enough, but it will work.

Hello Fernando, you only need the ICONV function here; converting the EndDate is easy, just a ICONV(EndDate,'D4-YMD') will do the trick. The StartDate is somewhat moe of a challenge, as the lengths vary. I think that ICONV(FMT(StartDate,"8'0'R"),"D4DMY") should work, but I don't have a DS instance t...

Even though I haven't had this problem, I have read in this forum that several people have had problems with this not working correctly. The recommendation has been to use the fact that upon a failed lookup the columns are returned as NULL and can be detected with a IF ISNULL(Lookup.ColumnName) cond...

Not directly, but can you tell us about your source, what the field "END_DT" is declared as and if you have a COBOL type format?

I took a look at the page and yes, there is no guide to PERFORM anymore, but the UniVerse User Reference, Version 9.6 at the bottom contains every command that standard UniVerse has - 742 pages of thrilling reading for you. Seriously, it is too much information to learn if all you want to do is use ...