Problems with NCLOB from Oracle table
Moderators: chulett, rschirm, roy
Problems with NCLOB from Oracle table
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.
This is just the first step of this project.
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.
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.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
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?
Also, can you describe your job design? Is it your basic bare bones SRC -> TRANSFORMER -> TGT kind of job or something more complex?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
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.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
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.DelValle wrote:When checking operator: Schema field CODE in input data set 0 not present in design time
Please double check your SQL statement, and the DDL of the source table(s) you are trying to access.
-T.J.