This content has been marked as final. Show 2 replies
I noticed that myself in our project.
Our varchars2 are defined as VARCHAR2(xxx CHAR) - OWB puts the size*4
In fact if you have special characters like umlauts (ü,ä,ö,...) it will use 4 bytes per character.
You can try it yourself. Define a Varchar2(1 CHAR) and manually change the size of the Column in your mapping inside OWB (in filters, joins or your target table).
Then shoot an umlaut through the mapping and will end up with a "too small" error.
Dont mind the size*4 issue - we totally ignored it and run without error since 4 years now.
I think this may not be a bug, but only thing is OWB is always displaying the size in bytes.
Example we have some fields in our tables whcih are of VARCHAR2(256 CHAR)(with each character of 4 bytes), but after importing them to OWB it shows as VARCHAR2(1024) which is still correct if we convert it to bytes.
But anyway you can check with Oracle Support for confirmation.