Page 1 of 1

Problems with NCLOB from Oracle table

Posted: Wed May 25, 2016 8:46 am
by DelValle
New to Oracle/DataStage...trying to read Oracle table with column Message defined as NCLOB and join to another Oracle table to create new Oracle table with the Message column. Problems with NCLOB...can't insert too BIG.
This is just the first step of this project.

Posted: Wed May 25, 2016 9:19 am
by chulett
Welcome. Is this actually a Server job you are working with? You have marked the post as such but wanted to double-check.

Posted: Wed May 25, 2016 9:27 am
by DelValle
Yes

Posted: Wed May 25, 2016 9:38 am
by chulett
Just wanted to make sure before I moved your post over to the Server specific forum so that hopefully you don't get any Valid For Parallel Only advice. :wink:

Can you post the actual error message from your job log?

Posted: Wed May 25, 2016 10:16 am
by DelValle
Going to just remove that column from output.

Posted: Wed May 25, 2016 12:24 pm
by Teej
Indeed, PX solution have a distinctive different solution than Server solutions.

We need the specific error message, including the Message ID in order to help you.

-T.J.

Posted: Wed May 25, 2016 12:35 pm
by DelValle
It's gone.

Posted: Wed May 25, 2016 12:47 pm
by chulett
:idea: Just as an FYI, there's no need to 'Reply with quote' unless there's really a need to actual quote the message you are replying to and that generally isn't the case. I removed the quoted text from your post, just because I'm anal like that. The Reply to topic option is the weapon of choice in this battle, it's at the top and bottom of every page.

And by gone you mean the error is gone because the column itself was removed / is gone from the mapping. Officially an NCLOB is not supported but there are sometimes 'tricks' that work to allow you to pass one from source to target. Let us know if you want to explore any of them... but as noted, I still believe the actual error it generated would be helpful for that.

Posted: Wed May 25, 2016 2:47 pm
by DelValle
Gone...because I GAVE UP and removed the offending column...will have to add back later to be considered finished...but miserable day of trying.

Posted: Wed May 25, 2016 2:49 pm
by DelValle
Trying to setup a lookup for code to get name. Another impossible task.

Posted: Wed May 25, 2016 2:51 pm
by DelValle
You can't cut/paste the error message. When checking operator: Schema field CODE in input data set 0 not present in design time information?

Posted: Wed May 25, 2016 3:26 pm
by chulett
You should be able to copy and paste it here as people do that all the time, not sure why that wouldn't be working for you. Sorry.

Also, can you describe your job design? Is it your basic bare bones SRC -> TRANSFORMER -> TGT kind of job or something more complex?

Posted: Wed May 25, 2016 3:34 pm
by chulett
And that looks more like a PX error as seen here but for all I know it is one that could be thrown by a Server job as well.
The Technote wrote:Note: Other stages may see the same warning occur. Please contact IBM Technical Support for further assistance.

Posted: Wed May 25, 2016 6:00 pm
by Teej
DelValle wrote:When checking operator: Schema field CODE in input data set 0 not present in design time
Looks like there is a field that have not been properly defined ("CODE") within the source database, leading to a mismatch with the schema definition you made in the stage itself.

Please double check your SQL statement, and the DDL of the source table(s) you are trying to access.

-T.J.

Posted: Thu May 26, 2016 7:16 am
by DelValle
My first DataStage...my first lookup. I don't know what all this means. And you CAN'T cut/paste...been doing it since invented...won't do it.