Hi all,
we are importing a table definition from an Oracle DB using the Oracle enterprise stage of Datastage 8.1
The weird thing is that in oracle the column if VARCHAR2(13) and in Datastage the column has the size multiplied by 3 = 39. In Datastage the column is CHAR(39).
The same is happening with other fields. Do you have any clue why this is happening??
Regards
Jusami
Oracle table definitions got multiplied by 3
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Just accept it. With NLS enabled Oracle reports that it uses three bytes per character (and, indeed, mostly does).
DataStage's NLS map translates that into DataStage's internal UTF mapping (variable number of bytes per character) when reading, and back again when writing.
It all works OK. Don't worry about it.
DataStage's NLS map translates that into DataStage's internal UTF mapping (variable number of bytes per character) when reading, and back again when writing.
It all works OK. Don't worry about it.
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.
Hi,
we have seen a configuration parameter in Oracle Database (nls_length_semantics) which have been set as byte and can have be set as char value. Do you think this can solve the issue?
We have not tried to change the value yet because we cannot update oracle configuration due to another project is using the same database.
Thanks!!
we have seen a configuration parameter in Oracle Database (nls_length_semantics) which have been set as byte and can have be set as char value. Do you think this can solve the issue?
We have not tried to change the value yet because we cannot update oracle configuration due to another project is using the same database.
Thanks!!