X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id 0A7F0CC7D1 for ; Wed, 16 Jul 2003 22:52:11 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 35796-01 for ; Wed, 16 Jul 2003 22:52:31 +0000 (GMT) Received: from osmtp2.electric.net (osmtp2.electric.net [216.129.90.29]) by svr1.postgresql.org (Postfix) with ESMTP id 759E4CC7D0 for ; Wed, 16 Jul 2003 19:52:05 -0300 (ADT) Received: from root by osmtp2.electric.net with emc1-ok (Exim 4.10) id 19cv8S-000NTW-0W for pgsql-admin@postgresql.org; Wed, 16 Jul 2003 15:52:32 -0700 Received: by emcmailer; Wed, Jul 16 2003 15:52:32 -0700 Received: from [204.50.0.66] (helo=sysadmin) by osmtp2.electric.net with smtp (Exim 4.10) id 19cv8R-000NTH-0W for pgsql-admin@postgresql.org; Wed, 16 Jul 2003 15:52:31 -0700 From: "Dilan Arumainathan" To: Subject: Database migration Date: Wed, 16 Jul 2003 15:52:32 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3F15D3C0.4060707@e-greek.net> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Status: Scanned by norton X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/143 X-Sequence-Number: 9483 I am trying to migrate a database from Oracle to Postgresql. I am using the PgAdmin database migration wizard (1.5.60-Dev) to do this. Using ODBC I am able to migrate small tables but I have a few tables that have over 10 million rows that are failing. I know the reason as I am getting an "Snapshot too old" error from Oracle but am unable to come up with a workaround. I prefer using the wizard as it takes care of nulls etc. which I might have to handle if I went the dump and load route. Can someone give me an idea on getting around this (other than preventing updates to Oracle). Also, is there a way to turn off WAL while loading bulk data. thanks dilan