oracle tables replication

Hi,

 I have two tables TABLE1 and TABALE2 which I joined and build a query. Now the data fetched with this query I need to insert or update(if record already existing) into a table TABLE_REP which is in another schema but same database.
 First time I need to load all the data after that for every week I need to load the data into the new table TABLE_REP. For a week data may be appx. 10 million records.  

 One way is we need to write a Stored procedure and schedule for every week after the first full load.

 Can you please suggest is there any other better way?

Can we use Materialized view and schedule it for every week after the first complete refresh? In this way can we track and log any failed records in any log table?

 Also I need to archive the data from the TABLE_REP table for older data into another table and delete from this table. So if I use Materialized view can I achieve this also?

 Like this I have 10 reporting tables for which data needs to be fetched for every table with 2 base tables joining from another schema.

Which option is better out of these two approaches (stored proc and MV)?or Is there any better approach also other than these two options? Request you to suggest.

 Thanks,
GouthamAnandAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wasim Akram ShaikCommented:
I was answering this question just 2 hours back (I think), you had deleted it..

Anyways.. I see that you had modified requirement a little bit(archiving from mv table)

however, i don't think MV is good option here, because you said all the operations are on a single database

Populating a materialized view adds load to server.

materialized view logs improve the performance of materialized view  by using refresh concepts(fash,complete etc.,) but, they do increase the work needed to perform DDL on the base table. additional overhead of maintaining mv logs will also occur on the system.

Going for the procedure is a good option in my view that too not on weekly basis but on daily basis based on some date criteria, if done on weekly basis, seeing your transaction volume procedure may not be effective to handle those many records in a one time.

There are other options too Like Oracle Streams and Oracle golden gate , CDC but they do come with a license(cost) which you may not like.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Wasim Akram ShaikCommented:
Apart from above, there is one more option you can consider, unload the data from one schema and load in another schema and do the operations what ever you need one the same table without changing their names

you can consider this option too if you cannot afford going for licensed version software..

Unloading and Loading are not database procedural level operations they are done from OS level, so it may be performed on schema level, however as this operation also happens on the same server.

check out the site for more details on loading and unloading the data using oracle query

http://www.oracle-developer.net/display.php?id=325
0
GouthamAnandAuthor Commented:
Thank you.
0
slightwv (䄆 Netminder) Commented:
Even though you already accepted an answer to this I have some comments.

First:
Streams replication is free in Enterprise Edition.

If the tables need to be copies of each other, why not a view in schema2 that selects directly from schema1?

I would look at materialized views.

>>Populating a materialized view adds load to server.

So does physically inserting and updating manually.  Same amount of data has to move from pointA to pointB so I'm not sure the manual process is better or worse than a fast refresh MV.

I would experiment with both options and choose the one that is most efficient.  We cannot predict which method will work best on your systems.
0
GouthamAnandAuthor Commented:
Thank you slightwv.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.