Capture rejects of different schemas to a single table
Moderators: chulett, rschirm, roy
Capture rejects of different schemas to a single table
Hi,
I have 3 Oracle Tables with different schemas.
Each table has a reject link and the rejected records are captured in a Sequentail file.
The rejected records need to be captured in a target table whose definition is not yet defined as it depends on how we can capture these records.
Kindly let me know how this could be desinged.
Current thoughts in my mind is to concatenate all columns in a sequential file except RejectERRORCODE,RejectERRORTEXT and have 4 column table with filename and Reject inofrmation and actual reject Data.
Thanks,
Chetan.C
I have 3 Oracle Tables with different schemas.
Each table has a reject link and the rejected records are captured in a Sequentail file.
The rejected records need to be captured in a target table whose definition is not yet defined as it depends on how we can capture these records.
Kindly let me know how this could be desinged.
Current thoughts in my mind is to concatenate all columns in a sequential file except RejectERRORCODE,RejectERRORTEXT and have 4 column table with filename and Reject inofrmation and actual reject Data.
Thanks,
Chetan.C
-
- Participant
- Posts: 111
- Joined: Mon Nov 30, 2009 7:21 am
- Location: Bangalore
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Chetan.C tells us that the table design has yet to be defined. I think that doing that is the absolutely vital first step - what information about data errors does Chetan.C need to capture?
This is not something we can do (in spite of having some experience in these areas). Chetan.C must come up with Chetan.C's requirements.
I'd be happy to design the table, but that counts as consulting and comes at a fee.
This is not something we can do (in spite of having some experience in these areas). Chetan.C must come up with Chetan.C's requirements.
I'd be happy to design the table, but that counts as consulting and comes at a fee.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
What happens if you ask a consultant the time?
He asks to borrow your watch, tells you and then keeps it.
I've "consulted" on this situation many times, and the down and dirty normally is a lot of data collected and stored for absoulutly no reason.
He asks to borrow your watch, tells you and then keeps it.
I've "consulted" on this situation many times, and the down and dirty normally is a lot of data collected and stored for absoulutly no reason.
Andrew
Think outside the Datastage you work in.
There is no True Way, but there are true ways.
Think outside the Datastage you work in.
There is no True Way, but there are true ways.
Well , Chetan.C has been asked to see how best he can be showing the data without any specification as to how they want to see it ( or even who will be seeing it)ray.wurlod wrote:Chetan.C tells us that the table design has yet to be defined. I think that doing that is the absolutely vital first step - what information about data errors does Chetan.C need to capture?
Today , I have insisted on who will be looking into this and how they want to look at it ( Querying a table or through a web portal) and waiting for an answer
As for the consulation fee Ray , I think the knowledge you all veterans have here is priceless .
Thanks,
Chetan.C
One of the easiest ways to store data of different formats into a table or file with identical format is to combine all or selected columns of a record in a single column using the Column Export Stage.
This action can be reversed using the Column Import Stage.
This action can be reversed using the Column Import Stage.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
There are the grateful those are happy." Francis Bacon