Incorrect values retrieved from Oracle

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
agrvikrant
Participant
Posts: 3
Joined: Wed Oct 19, 2005 11:53 pm

Incorrect values retrieved from Oracle

Post by agrvikrant »

Hello,

We have developed a PX job that retrieves around 2 million records from a Oracle Table. We find that when we run this query some fields defined as BigInt are not retrieving proper values. For eg a field with value 9 in Oracle is shown as 9130. This is happening for some records and not all the records. If we put additional filters to restrict the number of rows to a smaller value, we get proper data. It would be of great help if someone can help me in solving this problem.

Some of the fields are defined as decimal (10) in Oracle. The metadata imported in DataStage shows them as BigInt. Can this be cause of problem.

Thanks in advance.

Regards,
Vikrant
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Welcome Aboard
What stage are you using to pull the data? How did you import the table definition? If you do a select * from your favourite sql tool (TOAD or oracle developer) do you see the same behaviour?
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
agrvikrant
Participant
Posts: 3
Joined: Wed Oct 19, 2005 11:53 pm

Post by agrvikrant »

Hi,

We are using Oracle Enterprise Stage to pull the data. Metadata was imported using Orchestrate. Whenwe viewed this data from TOAD it was completely fine.

Thanks,
Vikrant
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

What if you change the BIGINT to integer within Oracle Enterprise stage. Does that fix your problem?
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
agrvikrant
Participant
Posts: 3
Joined: Wed Oct 19, 2005 11:53 pm

Post by agrvikrant »

Yes we have tried it. It doesnt help, gave same result.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Try importing the table definition using Orchestrate orchdbutil facility, which is known to be more accurate.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
_chamak
Premium Member
Premium Member
Posts: 29
Joined: Tue Aug 24, 2010 10:29 am

Post by _chamak »

ray.wurlod wrote:Try importing the table definition using Orchestrate orchdbutil facility, which is known to be more accurate.
Hi, I am also facing the same error. I have straight forward job

Dataset ------> Copy---------->Oracle Table.

I am using Oracle Connector stage. My source is Bigint and the target is Integer.

For few records like example 4183 is in the source and in the target I am seeing 418333.

Did you find any resolution for this.
I am using DS 8.1

Thanks in Advance
-Thanks
Chamak
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

If you try to put a 64-bit integer into a 32-bit field, you can expect to run into some problems. Start a new topic if you need to...
Choose a job you love, and you will never have to work a day in your life. - Confucius
pnpmarques
Participant
Posts: 35
Joined: Wed Jun 15, 2005 9:27 am

Post by pnpmarques »

Post Reply