Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 7C0181D7D623 for ; Fri, 20 Apr 2012 20:21:29 -0300 (ADT) Received: from plane.gmane.org ([80.91.229.3]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SLN8o-0006kh-A5 for pgsql-admin@postgresql.org; Fri, 20 Apr 2012 23:21:28 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SLN8a-0008UM-0f for pgsql-admin@postgresql.org; Sat, 21 Apr 2012 01:21:12 +0200 Received: from cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com ([86.21.186.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Apr 2012 01:21:11 +0200 Received: from walterhurry by cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Apr 2012 01:21:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Walter Hurry Subject: Re: Unending DB migration Date: Fri, 20 Apr 2012 23:21:00 +0000 (UTC) Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com User-Agent: Pan/0.136 (I'm far too busy being delicious; GIT 926a150 git://git.gnome.org/pan2) X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201204/114 X-Sequence-Number: 39450 On Mon, 16 Apr 2012 16:27:38 -0700, ЇЯЅHAÐ wrote: > Hi, > > We are trying to migrate from Postgres to Oracle, although our DB is > gigantic but we started on Mar 14th 2012 & its still running with an > average of 400000 records per day 400,000? That's pathetic. Why didn't you just use Postgres's "copy to" CSVS and then Oracle's SQL*Loader? How big is "gigantic"? > How can we check what is going wrong. > Any memory leak, CPU issue or anything. > > Please help me fix it Hi,

We are trying to migrate from Postgres > to Oracle, although our DB is gigantic
but we started on Mar 14th > 2012 & its still running with an average of 400000 records per > day

How can we check what is going wrong.
> Any memory leak, CPU issue or anything.

Please help > me fix it


Please don't post in HTML.