Last digit gets truncated while loading into Oracle ODBC Stg
Moderators: chulett, rschirm, roy
Last digit gets truncated while loading into Oracle ODBC Stg
Hi,
Our current data warehouse Datastage applications are using MS SQL Server 2000 as backend database and we are in the process of migrating
to Oracle 10g. We found an issue while System Testing.
We have jobs that are reading from Complex flat file and loading it into ORACLE ODBC stage.
For a particular AMOUNT field (SQL Type DECIMAL , Length 11, Scale 2
and Display 13) source data value is 123456789.12 and while loading data
into Oracle Database using ODBC stage the last digit is getting truncated
and data is getting inserted with value 123456789.1
When we replace Target ODBC stage with DRDBMS stages (DBMS Type
ORACLE/ODBC) or Oracle OCI stage, it inserts 123456789.12 properly.
Are there any datastage functions or options available to avoid this data
truncation in Target ODBC stage?
For us to replace Target ODBC with Oracle OCI is like redoing all of our
jobs since we found this issue while System testing.
Thanks
Our current data warehouse Datastage applications are using MS SQL Server 2000 as backend database and we are in the process of migrating
to Oracle 10g. We found an issue while System Testing.
We have jobs that are reading from Complex flat file and loading it into ORACLE ODBC stage.
For a particular AMOUNT field (SQL Type DECIMAL , Length 11, Scale 2
and Display 13) source data value is 123456789.12 and while loading data
into Oracle Database using ODBC stage the last digit is getting truncated
and data is getting inserted with value 123456789.1
When we replace Target ODBC stage with DRDBMS stages (DBMS Type
ORACLE/ODBC) or Oracle OCI stage, it inserts 123456789.12 properly.
Are there any datastage functions or options available to avoid this data
truncation in Target ODBC stage?
For us to replace Target ODBC with Oracle OCI is like redoing all of our
jobs since we found this issue while System testing.
Thanks
-
- Premium Member
- Posts: 503
- Joined: Wed Jun 29, 2005 8:14 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
We tried to insert data with other stages like Ora OCI and DRDBMSray.wurlod wrote:Could be time to mark thread as resolved, then.
by keeping same width 11,2 and display 13 data is getting inserted properly.
but our issue is, when we keep same width and scale (11,2 and display 13) in ODBC Stage. Its NOT working and most of our jobs are having ODBC stage.
Thanks
And?
You've got your answer - you will need to adjust your metadata for use in the ODBC stage, it seems. You can thank Bill Gates for that. Only question in my mind is: does it make a difference if you use the Oracle 'wire' drivers over the 'non-wire' ones? Which have you tried?
Rhetorical question, but why would you use ODBC when you have a 'native' interface available, in this case OCI? To me, ODBC is the 'interface of last resort'...
You've got your answer - you will need to adjust your metadata for use in the ODBC stage, it seems. You can thank Bill Gates for that. Only question in my mind is: does it make a difference if you use the Oracle 'wire' drivers over the 'non-wire' ones? Which have you tried?
Rhetorical question, but why would you use ODBC when you have a 'native' interface available, in this case OCI? To me, ODBC is the 'interface of last resort'...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
But easier to change databases subsequently when some smooth-talking sales person convinces management that dBase IV is the only database you'll ever need and it's cheap as well.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.