When we import Oracle 10 table metadata using Orchestrate and charset/map of UTF-8 from our production database, the field sizes are correct.
When we import Oracle 10 table metadata using Orchestrated and charset/map of UTF-8 from our new data warehouse, all the varchar field sizes are multiplied by 4.
I'm sure this is an Oracle configuration problem, but we are too green to see it. Can anyone point us in the right direction?
Oracle metadata imports improper field size
Moderators: chulett, rschirm, roy
It is definitely a multiple of 4.chulett wrote:Are you sure it's not a multiple of 3? Does your new data warehouse use a multi-byte character set?
The Oracle production server whose metadata can be used in DataStage just fine is NLS_CHARACTERSET US7ASCII.
The new Oracle data warehouse server whose metadata field sizes are x4 is NLS_CHARACTERSET AL32UTF8.
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
We are using Import, Table Definitions, Orchestrate Schema Definitions with the radio button for Database table (via orchdbutil) selected and tables we import from our data warehouse with UTF-8 selected are 4 x as large as they should be. The ones we import from production are the correct size.ray.wurlod wrote:Prefer importing Oracle table definitions using the Orchestrate orchdbutil facility. It is known to be more accurate in how it retrieves metadata.
