Production Dataset Issue

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
sureshreddy2009
Participant
Posts: 62
Joined: Sat Mar 07, 2009 4:59 am
Location: Chicago
Contact:

Production Dataset Issue

Post by sureshreddy2009 »

Hi,
My production datastage flow is
We have extract jobs loading from flat files to staging oracle database.
From staging database data quality datastage job will run and load into dataset. From there Data transformation job will run, this will extract the data from previous dataset and load into insert ready file which will insert the records into target oracle database.

Now the issue is
Some alternative days in production, the Data quality(DQ) job will load 48 records into dataset, the data transformation(DT) job will not read the records and process 0 records even the dataset is created ,jobs are successfull. And on another day DQ load 50 records, but DT will process 34 records, which were immediate previous day batch records. The production batch is running accurately for other days.
Can any one give some thoughts on this
Thanks in advance
Suresh Reddy
ETL Developer
Research Operations

"its important to know in which direction we are moving rather than where we are"
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Sounds like you have a synchronization / timing issue.
-craig

"You can never have too many knives" -- Logan Nine Fingers
sureshreddy2009
Participant
Posts: 62
Joined: Sat Mar 07, 2009 4:59 am
Location: Chicago
Contact:

Post by sureshreddy2009 »

Can you please eloborate the cause.
Suresh Reddy
ETL Developer
Research Operations

"its important to know in which direction we are moving rather than where we are"
sureshreddy2009
Participant
Posts: 62
Joined: Sat Mar 07, 2009 4:59 am
Location: Chicago
Contact:

Post by sureshreddy2009 »

Hi greggknight,

I know the meaning and definition you copied and pasted from a dictionary site :o

I mean to eloborate some more causes other than synchronization.
If you know the reasons post here
Suresh Reddy
ETL Developer
Research Operations

"its important to know in which direction we are moving rather than where we are"
greggknight
Premium Member
Premium Member
Posts: 120
Joined: Thu Oct 28, 2004 4:24 pm

Post by greggknight »

I am sure you do,
So then take the definition,
Look at the flow of your jobs makeing sure they run in the correct order and no other job is writing to the wrong dataset over writting your results.

The Problem appears to be your design.
This is not a datastage issue this is a developer issue.
"Don't let the bull between you and the fence"

Thanks
Gregg J Knight

"Never Never Never Quit"
Winston Churchill
sureshreddy2009
Participant
Posts: 62
Joined: Sat Mar 07, 2009 4:59 am
Location: Chicago
Contact:

Post by sureshreddy2009 »

Issue Resolved,
more over there will never be datastage problem
Its always developer work matters. I came to know yesterday the sequence is failed. When I triggered that event it started from that point and that dataset contains yesterday records.

Thanks,
Suresh Reddy
ETL Developer
Research Operations

"its important to know in which direction we are moving rather than where we are"
sureshreddy2009
Participant
Posts: 62
Joined: Sat Mar 07, 2009 4:59 am
Location: Chicago
Contact:

Post by sureshreddy2009 »

Issue Resolved,
more over there will never be datastage problem
Its always developer work matters. I came to know yesterday the sequence is failed. When I triggered that event it started from that point and that dataset contains yesterday records.

Thanks,
Suresh Reddy
ETL Developer
Research Operations

"its important to know in which direction we are moving rather than where we are"
Post Reply