Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81gj-0001yC-RE for pgsql-admin@arkaria.postgresql.org; Thu, 13 Jan 2022 15:06:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n81gi-00019c-MV for pgsql-admin@arkaria.postgresql.org; Thu, 13 Jan 2022 15:06:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81gi-00018x-BS for pgsql-admin@lists.postgresql.org; Thu, 13 Jan 2022 15:06:52 +0000 Received: from mail-oo1-xc36.google.com ([2607:f8b0:4864:20::c36]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n81gg-0004gu-HE for pgsql-admin@lists.postgresql.org; Thu, 13 Jan 2022 15:06:52 +0000 Received: by mail-oo1-xc36.google.com with SMTP id v10-20020a4a860a000000b002ddc59f8900so1676399ooh.7 for ; Thu, 13 Jan 2022 07:06:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=jalK+S75X0UKH+ix2qAa3h1880k9UdlBb645g2zlxs4=; b=UiSF1ndDOr5N4jMlo2KqrT2bZqBqkRQ0KiYqoEtS7Ergt9N3Cnhio472lN4O6GlEix jgX1OBNpRX14AepSJgVFH0h9ZH4LXHauNC22tEfzNE5m83eGvBZJ5BvoPa/VixzfgKxc Yp2m7HtjdDAyyKRNyyQy894TzH4qC4StJbA/LHZDGwO1wPBpkfpzhnB5IStqhUDiJ3XD pe1d+MXjv8faHQl0eZ6ATK4t9j6/j3AN8JaegpqP/CS3owTmioeR2JVjM/9uT309YHZI 5+MGVoyI1UhB0A3k8vNn9Avi41bIo9mqdsRdiiZR0oo8hu7pKiOItOn5gjShYS1zGV9F aMAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=jalK+S75X0UKH+ix2qAa3h1880k9UdlBb645g2zlxs4=; b=3isYMv70JeB9lSj5HhbTYR05Sl73z/RNY+8unVMnxXoeo8gJj+Ta/f1Fz3AWP906Gq xHuw/tMih9Dg+JD7o+2fyNKA4Np0Nc73+yKhgAUllz5YeUbfBplI210XkVQaGGaDmvOi Oom+OlSr5vz+LARtCQnZbYigx/HV1HwNqK4U2aBz2OA6rMPXhOIo+Akd7GRHBZ+lEC0H caIkTA+tNwvyV5xICo77TcdWLTdYW6r6oVQKSneTdTJ8WLTvgZl4OolcYI9y8FzAV2qa R41O+pYhY0I529EkxfQOp9JoLxw/GSeBwjuuNHN21ZVOmr2THVc2KA2mDyyHojH287hk 9Wvw== X-Gm-Message-State: AOAM530ZzUPs6c+gj/ehFcNVxaX59odL4pg0g4pPjLWa8H67jVXxquIa d0321XurgxbS4K/dxM2TZtjw4FMS4xE= X-Google-Smtp-Source: ABdhPJySGsl4k6Pz6bFzA1qnkH1URkQt0m1DB7S1+6BLvl17zhekZYF8jXcguPq51oujAo6bzKWJGg== X-Received: by 2002:a4a:9c92:: with SMTP id z18mr3162436ooj.83.1642086408503; Thu, 13 Jan 2022 07:06:48 -0800 (PST) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id k5sm145437oom.18.2022.01.13.07.06.47 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Jan 2022 07:06:48 -0800 (PST) Subject: Re: New Oracle system in our house, migration chances To: pgsql-admin@lists.postgresql.org References: <5387d1e8-a7d4-f568-fef1-30489fe93bba@matrix.gatewaynet.com> <20220113141241.GV25601@aart.rice.edu> From: Ron Message-ID: Date: Thu, 13 Jan 2022 09:06:47 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/13/22 8:15 AM, Achilleas Mantzios wrote: > On 13/1/22 4:12 μ.μ., Kenneth Marshall wrote: >>>> Hi Achilleas, >>>> I would go with version B - since as I understand it's ISV >>>> solution. Meaning the postgres ddl was tested and aligned with the >>>> application layer, otherwise you would need to fix app layer after >>>> the migration. >>> Dziekuje Alicija. The powerbuilder app is in-house developed, source >>> is available, what could be wrong with the app? Browsing through the >>> powerbuilder source I don't see (by eye) anything that could break >>> something in PgSQL. >>> -- >>> Achilleas Mantzios >>> DBA, Analyst, IT Lead >>> IT DEPT >>> Dynacom Tankers Mgmt >> Hi Achilleas, >> >> If the schema and usage is straight-forward, I would recommend using >> ora2pg to give you an estimation cost for your migration by letting you >> know what cannot be automatically translated. Once you have that you >> will be better informed as to the work needed. > Thank you Ken! ora2pg worked perfectly for us in migrating 8TB of Oracle 11 data and simple triggers to Pg 12. -- Angular momentum makes the world go 'round.