Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aJPYh-0005J6-Vi for pgsql-sql@arkaria.postgresql.org; Wed, 13 Jan 2016 17:50:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aJPYh-0000na-IE for pgsql-sql@arkaria.postgresql.org; Wed, 13 Jan 2016 17:50:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aJPXg-0005Xo-R6 for pgsql-sql@postgresql.org; Wed, 13 Jan 2016 17:49:09 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aJPXd-0001K8-Qi for pgsql-sql@postgresql.org; Wed, 13 Jan 2016 17:49:07 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5AB72216DB for ; Wed, 13 Jan 2016 12:49:04 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Wed, 13 Jan 2016 12:49:04 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=n0EpXj+Dd3FtC53QQD+SH9qbrX0=; b=E/Q2Q9 VZD/2zkbR3ct/25+jFaDpgeJUoI0XY/+wx8WMKdI2JN78gNXQQ85aGIyVRA+K7RZ 6X8vq3Lg9LQgW1zzFpfq6XY0uLtOb7yQOpgx0MBZxIWpqxVO1izKvv64i/SJMp+X LY4j07bB5N8DXbYvc92UOJXAcz6omAfIiKbLI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=n0EpXj+Dd3FtC53 QQD+SH9qbrX0=; b=Q8wtVbwHrXGlBPqSOuPR9gG8aYo2Vf+9xc27sWLZbZIwHMq TnCx3L7VtdJS0EPvk9y3a6mCsz8jEWwMDkhF9Qku35jG4uU1jn7USLGLFOc9n+Hn ZIu2fM47JLQwNKTK62mrTL3C/2UT4bESk4MHq1cre+Nn5Qc6+wUDqZMVd6J0= X-Sasl-enc: u89/ZZG1uxk24tvAN3o0s3jm1mR0Iqhnrs6fTjDonnrz 1452707344 Received: from [192.168.1.2] (65-102-182-223.tukw.qwest.net [65.102.182.223]) by mail.messagingengine.com (Postfix) with ESMTPA id BB2F368011A; Wed, 13 Jan 2016 12:49:03 -0500 (EST) Subject: Re: best way sync data from Oracle to PostgreSQL? To: Michael Moore , postgres list References: From: Adrian Klaver Message-ID: <56968DDD.9070509@aklaver.com> Date: Wed, 13 Jan 2016 09:48:13 -0800 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org On 01/13/2016 08:37 AM, Michael Moore wrote: > Our DBA's want to write a home-grown ETL system. Surely there has got to > be a better way. What is the best NO COST solution for doing this? We > have CLOBS and XML datatypes. We could "toString" the XML datatypes on > the Oracle side if that helps. Have you looked at Foreign Data Wrappers?: http://www.postgresql.org/docs/9.4/static/ddl-foreign-data.html in particular: http://laurenz.github.io/oracle_fdw/ > > TIA, Mike -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql