Column BATCH_ID floating point decimal is not fully supporte

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
smithasri
Participant
Posts: 23
Joined: Wed Sep 09, 2009 2:27 pm

Column BATCH_ID floating point decimal is not fully supporte

Post by smithasri »

Hi Friends,

Actaully in my oracle 10 g database batch_id clumn datatype is integer, when i importe metadata through orchestrate schema define, I am getting decimal(38,0) in metadata.
But I am getting the waring in DS8

"Column BATCH_ID floating point decimal is not fully supported; adjusting the scale."

I referred lot of topics in DSE. I don't get right ANS
Please respond any one if you know .

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

Post by chulett »

So, it's actualy INTEGER rather than NUMBER in Oracle? What happens if you change the metadata to Decimal(38,10)?
-craig

"You can never have too many knives" -- Logan Nine Fingers
smithasri
Participant
Posts: 23
Joined: Wed Sep 09, 2009 2:27 pm

Post by smithasri »

Thanks Chulett

I tried this way and other possible ways also .Still i am getting same warning message.

I am thinking do we need any patch for this warning?

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

Post by chulett »

You'd have to ask your support provider about a patch. How about answering my first question?
-craig

"You can never have too many knives" -- Logan Nine Fingers
colhogan
Premium Member
Premium Member
Posts: 4
Joined: Fri Oct 13, 2006 7:39 am

Re: Column BATCH_ID floating point decimal is not fully supp

Post by colhogan »

Smith, Did you get this issue resolved. I am also having the same issue . Pls. Let me know If you know any alternate for this.

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

Post by ray.wurlod »

It's all Oracle bin Larry's fault for not having a proper Integer data type.

You can not prevent this message without adjusting your metadata precisely to match that of Oracle, and even then you will get a message logged (a slightly different one).

This is one of those alert messages that it is safe to ignore, and therefore I tend to demote it to informational using a message handler. (I never suppress messages from the log.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply