Actually iam loading view from one database to another database table.
One of the views has more than a billion records.
my source stage is ODBC and target is ORACLE stage.
Though it has more than 1 billion records its reading only 138 million records and righting the same number of records to the target.
The job is not erroring out.I mean status is successful.
But my question is what happend to the rest of the count.
Why it is unable to read the all the records.
I don't think your guess is right because i am running this view from production.The batch cycle in the production for the dims and facts will be done in the morning only.
I would suggest you to use bulk load rather than using the Oracle Stage.
Loading more than 1 billion records would take you for ever with the method you have choosen.
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
You need to verify the actual number of records available from the view and not perhaps the base tables that make up the view.
Views are typically used to constrain output based on whom the view is intended to be used by and to hide any (what could be complex) joins from other processes. Either of those two conditions could legitimately restrict your output to the 138M records you are getting now from the alleged billion you are expecting.
-craig
"You can never have too many knives" -- Logan Nine Fingers
