I tried importing metadata via ODBC, plugin-9iOCI and also with a Orchestrate schema definition import, but in any case, When i read from the table, though the column definition(in the stage) says NUllability NO, i get a warning saying that i am implicitly converting nullable source to non-nullable..
I dont want to use Modify stage, as my main concern is that though metadata defines it and also the table definition say that this column is NOT Nullable, how come the source oracle stage still sees it as a Nullable column?
any suggestions?
I am just trying to read this table and do a straight dump into a Dataset..
Nullability changes during Metadata import
Moderators: chulett, rschirm, roy
So you have a column that, according to the DDL in the database, is NOT NULLABLE, and when you import that via the manager it also states NOT NULLABLE yet when you view or run a job using that metadata you get the warning message regarding the nullable-to-not-nullable conversion? How did you get the DDL description?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>