Null in non-nullable field?
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 353
- Joined: Mon Jan 17, 2011 5:03 am
- Location: Mumbai, India
Often when you perform an action on a field in the database it affects the resulting column nullability.
First off, add "$OSH_PRINT_SCHEMAS" to see what DataStage is getting from the Oracle stage.
First off, add "$OSH_PRINT_SCHEMAS" to see what DataStage is getting from the Oracle stage.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
We can't use the IsNull function because we are using "runtime column propagation", so we can't use any transformers.chandra.shekhar@tcs.com wrote:In the transformer, are you using IsNull function for that column ?
Andrea Vincenzi
Data Warehouse & Business Intelligence Consultant
Via A. Cesalpino 17, 52100 Arezzo
www.olap.it
Tel. 347 3853617
andrea.vincenzi@tiscali.it
Data Warehouse & Business Intelligence Consultant
Via A. Cesalpino 17, 52100 Arezzo
www.olap.it
Tel. 347 3853617
andrea.vincenzi@tiscali.it
I believe I had a case where a non-nullable column X in the database was queried with a "SELECT X as NewColumn..." and "NewColumn" arrived in DataStage as a nullable one. I can't check if that still happens, and it might be dependent upon your database and version, but this is a likely source of getting an altered nullability. Again, have DataStage print out the schemas since they represent the actual data, unlike the column definitions in your job.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>