Merge data from 10g database to 11g database

From: Sandra Becker <sbecker6925_at_gmail.com>
Date: Wed, 13 Jun 2012 11:21:31 -0600
Message-ID: <CAJzM94A-8hF786Oru62P+PE0x5=m2QdJ=d7Hicgxq9SJc5ibQA_at_mail.gmail.com>



We archive documents Monday-Friday using the merge statement. Sometimes the data is copied back to production but not deleted from the archive database and re-archived later, hence the use of the merge statement.  Through June 6th we could merge as many as 6,000 documents in just over an hour. Last Saturday the archive database was moved from a SLES10 server to a SLES11 server and also new, faster storage, then the database was upgraded to 11g. IT also did some work on the network but I've been told that would have no impact on the database servers, only our app servers.  Since Monday morning, it now takes over 90 minutes to archive only 300 documents. Queries run directly from the 11g archive database perform much better than they did when it was on the old server and 10g. Questions:
  1. The production database is 10g, the archive database is 11g. Does Oracle have to do some kind of conversion on the data as it merges it into the 11g database?
  2. What else should I be looking at? Specific metrics that might give me a clue where the problem is?

Thanks in advance for any guidance you can provide.

--

Sandy
Transzap, Inc.

--

http://www.freelists.org/webpage/oracle-l Received on Wed Jun 13 2012 - 12:21:31 CDT

Original text of this message