Issue when Importing Metadata from oracle table..

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
jagadam
Premium Member
Premium Member
Posts: 107
Joined: Wed Jul 01, 2009 4:55 pm
Location: Phili

Issue when Importing Metadata from oracle table..

Post by jagadam »

Hi,

When I am trying to import the metadata from the oracle table, the varchar field lengths are increasing by four times when compared to length in the actual oracle table.

Version of datastage used 8.7
unix running on 4 nodes(so i doubt that its multiplying the length by 4..but dont know why)
importing it through plug in metadata option.

Any information in this regard will be helpful.

Thanks
NJ
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

No doubt an NLS issue. Use the parallel (command line?) metadata importer rather than the plugin. I don't recall its name off the top of my head, however. :(
-craig

"You can never have too many knives" -- Logan Nine Fingers
jagadam
Premium Member
Premium Member
Posts: 107
Joined: Wed Jul 01, 2009 4:55 pm
Location: Phili

Post by jagadam »

Hi Chulett,

I imported using orchestrate method and it imported with the right length. But why its giving wrong length when trying to import with plugin metadata method. what would be NLS issue and how can we fix this. thanks!!

Thanks
NJ
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You can't "fix" it. The OCI reports multiple bytes per character when metadata queries are executed.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
jagadam
Premium Member
Premium Member
Posts: 107
Joined: Wed Jul 01, 2009 4:55 pm
Location: Phili

Post by jagadam »

So, is it an issue with version 8.7 or with any version..? because we didn't have this issue in version 8.1. Thanks!!
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

I suspect NLS wasn't installed or the project had it disabled at 8.1. Hence the difference.

Have your admin check the NLS settings on the old 8.1 project and compare it to the 8.7 project if you still have access.

Note: Enabling / Disabling NLS can have significant impacts way above what you are talking about, so proceed with caution!
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
jagadam
Premium Member
Premium Member
Posts: 107
Joined: Wed Jul 01, 2009 4:55 pm
Location: Phili

Post by jagadam »

Thanks for the responses. But, when i tried to connect to other oracle database instance(version 10.2)using plug-in metadata option it is importing it with the correct length. But, when i tried to connect to an oracle instance(version 11.2) with plug-in metadata option, Its giving incorrect length. If its an NLS issue then i think it should behave same way for both instances...

Thanks
NJ
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What characterset is each instance using?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It's not entirely an NLS issue, it also relates to the way that the different OCI versions report metadata.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
jagadam
Premium Member
Premium Member
Posts: 107
Joined: Wed Jul 01, 2009 4:55 pm
Location: Phili

Post by jagadam »

Hi,

These are the NLS charactersets that are being used by different versions.

For version 10.2 : WE8ISO8859P1(NLS_CHARACTERSET)

For Version 11.2 : AL32UTF8 (NLS_CHARACTERSET)

Thanks
NJ
Mike
Premium Member
Premium Member
Posts: 1021
Joined: Sun Mar 03, 2002 6:01 pm
Location: Tampa, FL

Post by Mike »

Seems like a characters vs bytes difference... you went from a fixed width characterset in your version 10.2 (1 character = 1 byte) to a variable width characterset in your version 11.2 (1 character = 1-4 bytes).

Seems like the metadata import may be assuming a worst case scenario of every character requiring 4 bytes... hence the size multiplication by 4.

Mike
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

As suspected. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply