Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uhag3-001eVm-8N for pgsql-admin@arkaria.postgresql.org; Thu, 31 Jul 2025 21:19:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uhag2-003U0x-4q for pgsql-admin@arkaria.postgresql.org; Thu, 31 Jul 2025 21:19:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uhag1-003Tzt-8u for pgsql-admin@lists.postgresql.org; Thu, 31 Jul 2025 21:19:01 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uhafy-0004nw-08 for pgsql-admin@lists.postgresql.org; Thu, 31 Jul 2025 21:18:59 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-32f1df5b089so9897141fa.3 for ; Thu, 31 Jul 2025 14:18:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753996736; x=1754601536; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mpGw6p8qHmN3CcZ4VcS4zkmP2ONIH82q7GsGbKdQZC0=; b=S3+R8EFXLRkhaw2Vp1mpov0rxN4CU8nZ/7BJpnBC9R7Hz3BRHjgddmTn1B8CBF1uQe L1YYW/2WCyST86QRG564oywnd2Z+x7/EJUZ7uXWnxQxYTqLJ9tZozRTqhMW9y5OYdud9 0HiKO7uJTY4MeuGBWO8Pl756sV2gKEvButPg8f16TbQWw0zRXl3DK8aVKZbJwKep0M0a 5o9cXefPQfiuh5/BBhpW/taVp0thSha/MmY0BW15ZZprmvxanoZo4fZRjpYuQwuOAwHz 9cNL7H188nzMI5RdstlwI/AX+YpGVWXDk/8d7gF4mohfcTxMJL5nCRfQdM4rYsuQH48N AgMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753996736; x=1754601536; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mpGw6p8qHmN3CcZ4VcS4zkmP2ONIH82q7GsGbKdQZC0=; b=w39TjB1il96gEpFjr+hNfRiH0Y7PJd62AAESCWzuZqd63oewjvAQMylK9quwc9Iz3Y 09KsMNb4bgIi2uRVxScXtYuqYIOj71YVFamEdU5+h7hNQzYZt50eNAVUgIBJkjl2/7p1 JVh0/s9gz5nvcPynlBazzlMsQ2xwCUNGBlli6PyBDz1ZuzbwakaHs5oLy2njU0/SLMOP m0FwQG7eeDQrlH7P/Fb+fq4oj83zJeHgitSLzuC5/pVUjCyftOAtj1RgVAUVW/Qtfng+ 9za7qx6iulDIGUT6CRH4cO+qlJXAI1x3dj7vRqxjAjQS4aJHp9P/7FRbXEQeNiD0UiD7 yNEw== X-Forwarded-Encrypted: i=1; AJvYcCXVB0DQXmqtgBlToPZ/+oJu/Gt4MCCAYg/EIrcuKvR60AQQqJV0HQsHJOO6CyT6aMStbdnieqyP9xT2Xw==@lists.postgresql.org X-Gm-Message-State: AOJu0YwOfSLWrjl9BvE51datcb93IVhl8mOID8+Kk2dU/qpch2ys61VS VCoJVAPf0imBVRXYfMMuf7r9yxLlaeTx6r4ei6XjHLgTBISGocx2nRiWQIarFTI5qb0ELJHIJM5 YrzhH4Quubh2Hnnt+T0LG4OyfKlj0Loc= X-Gm-Gg: ASbGncsGHK3R6uqZFpm75isCHZC496/mC4F4AbyPZ7imJTgFExiy4iuechcGIN54tb0 zGAEAF99jVdaOamHJNWkAbU4tAjvUUe8MyVu1pnZGrM9I7uACsMt9UUjHZLh3aK4bg/MH0ArO0m FRW/DyINyMHZiZvuwYxF1DdXgwmSKyOAFIRUbn3+I49g+kbtfXzRizrVfFfbUMWQ3xbnoW1kV1p Tr/1sM5 X-Google-Smtp-Source: AGHT+IGTDcP/DFWEyV22sm7NLxQ6aVKM3CTSE1xCN7E2i/eE4psY9A0HaORmSRkmuhSfL4jBGDWdsmXx6dVlu2qVcWU= X-Received: by 2002:a05:651c:4187:b0:32a:7951:554 with SMTP id 38308e7fff4ca-33224a9b771mr27817191fa.11.1753996735275; Thu, 31 Jul 2025 14:18:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Raj Date: Fri, 1 Aug 2025 02:48:44 +0530 X-Gm-Features: Ac12FXwkrdQj5n1WgeF518AC2WGF6zQmGscYbsJvgQJzrNSh7rN2ZiJf61OJD-c Message-ID: Subject: Re: Post Oracle to Postgres migartion To: DINESH NAIR Cc: Kamal Lekan AbdulWahab , Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000057e528063b40309c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000057e528063b40309c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you All. In my env, darold himself is already doing migration, I just wanted to be ready with post migration steps . On Fri, 1 Aug 2025, 01:07 DINESH NAIR, wrote: > Hi , > > > > >> That "etc" is everything except what you didn't explicitly list. =F0= =9F=98=89 > > >>Did you create all the same indices and triggers? > >> Did you convert all NUMERIC and NUMERIC(38,0) to BIGINT in Ora2pg? > > Best practice followed for migration : > > > 1. First perform table data migration. Row count verification between > source and target tables. Random data checks between source and target= at > row level. > 2. Applying primary key, constraints and indexes > 3. Applying triggers > 4. Then sequences migration > 5. Database configuration: configuration of postgres.config , > shared_buffers, max_connections, configuring maintenace jobs > 6. Setting user roles and permissions > > > > > Regards > > Dinesh Nair > > > ------------------------------ > *From:* Kamal Lekan AbdulWahab > *Sent:* Thursday, July 31, 2025 7:47 PM > *To:* Raj > *Cc:* Pgsql-admin > *Subject:* Re: Post Oracle to Postgres migartion > > You don't often get email from dba.abdulwahab@gmail.com. Learn why this > is important > Caution: This email was sent from an external source. Please verify the > sender=E2=80=99s identity before clicking links or opening attachments. > You can look at SEQUENCES if they are out of sync with values in Oracle. > Sometimes, they also affect auto-increment columns. Have you checked and > recreated all users accounts? Passwords do not copy over automatically. > > On Thu, Jul 31, 2025 at 3:19=E2=80=AFAM Raj = wrote: > > Hi All, > > Post Oracle to Postgres Migration using Ora2pg, as a dba what activites w= e > may have to perform apart from checking count of objects, rows, vacuum > analyze etc > > --00000000000057e528063b40309c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you All. In my env, darold himself is already doing= migration,=C2=A0 I just wanted to be ready with post migration steps .
On Fri, 1 Aug 2025, 01:07 DINESH NAIR, <Dinesh_Nair@iitmpravartak.net> w= rote:
Hi ,

=E2=80=82=E2=80=82=E2=80=82=E2=80=82
=C2=A0

=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82= =E2=80=82=E2=80=82=E2=80=82=E2=80=82>>=E2=80=82=E2=80=82That "etc" is everything except what you didn't explicitly list.= =C2=A0=F0=9F=98=89


>>Did you create all the same indices and triggers?
>> Did you convert all NUMERIC and NUMERIC(38,0) to BIGINT in Ora2pg?=

Best practice followed for migration :

  1. First perform table data migration. Row count ve= rification between source and target tables. Random data checks between sou= rce and target at row level.
  2. Applying primary key, constraints and indexes
  3. Applying triggers=C2=A0
  4. Then sequences migration=C2=A0
  5. Database configuration: configuration of postgres.config , shared_buffers, = max_connections, configuring maintenace jobs
  6. Setting user roles and permissions



Regards

Dinesh Nair


From:= Kamal Lekan AbdulWahab <dba.abdulwahab@gmail.com>
Sent: Thursday, July 31, 2025 7:47 PM
To: Raj <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Post Oracle to Postgres migartion
=C2=A0
--00000000000057e528063b40309c--