Search found 7 matches
- Fri Feb 02, 2007 8:46 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
The issue remains with the metadata, rather than data itself. Both hold different scales which is causing the problem. To go a littler farther, the issue is with the metadata dictated by the DataDirect driver used by DataStage. -- The driver for SQL Server says a datetime has a length of 23 and a s...
- Thu Feb 01, 2007 9:38 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
After additional searching, I have found the problem to be with the DataDirect Informix driver that maps all Informix data types of "Datetime year to fraction(x)" as fraction (5), regardless of how the data is defined in Informix. In my Informix tables, I have "Datatime year to fraction(3)" since th...
- Thu Jan 25, 2007 10:42 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
The creation_date was just one example. There are several datetime fields in the tables we maintain. There are creation dates, last change dates, active dates, inactive dates, etc. Sometimes the time part of it is not important, but other times it is important. I also have the requirement that since...
- Thu Jan 25, 2007 10:03 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
I've tried that, and there's still a warning. I can change the type to varchar with a length of 26 and no scale. Then I get following warning: "DSD.BCIOpenR results of SQLColAttributes(creation_date) gave MetaData mismatch MetaData mismatch on COLUMN.SCALE Expected = 0 Actual = 5" I can change the t...
- Thu Jan 25, 2007 9:50 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
I'm not sure how to accomplish what either of you are recommending. So here's a little more detail of what exactly I'm doing. The job consists of a sequential file stage containing the records to be loaded into the database and an ODBC stage that connects to the appropriate database based on a param...
- Wed Jan 24, 2007 4:16 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
Your suggestion worked for the extract. In the ODBC stage I cast the datetime columns as varchar(26) in the Derivation field, changed the column length to 26, and removed the scale. When the job runs against either Informix or SQL Server it does not get the metadata error. But I have the same proble...
- Wed Jan 24, 2007 3:21 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DateTime Metadata Mismatch Warnings
- Replies: 17
- Views: 10397
DateTime Metadata Mismatch Warnings
I work on a project that maintains a set of tables in SQL Server. We then make these tables available on other database platforms as needed. I am currently working on a project to put a copy of the tables on Informix. Since the Informix tables have the same structure as the SQL Server tables, I want...