public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: Post Oracle to Postgres migartion
Date: Mon, 11 Aug 2025 12:26:42 -0400
Message-ID: <CANzqJaAZxTgcUA0=OLWzOkeM+JZxtc6YOS4f0DQrcFsMEZU6kg@mail.gmail.com> (raw)
In-Reply-To: <CAJk5AtbXrw69ZiDoknA+SkBjSKqMJre+-8JsS8QXpUVQR3BgGA@mail.gmail.com>
References: <CAJk5Atb+2r430wJqONZLLYvR0ZWcQ8qPc1uuoqZGao_O2wLrrA@mail.gmail.com>
<CA+B9d-fWbhRRYaYvQXrT1Jdy9MrDS2qdbSRghdwJR9M9DBkbnQ@mail.gmail.com>
<PN4P287MB4381DBD6FDC7B959956CA9F09C27A@PN4P287MB4381.INDP287.PROD.OUTLOOK.COM>
<CAJk5Atao0y5ctNFv3oeq0fsemL+44KsucUqY2CEQstP5DF=V7g@mail.gmail.com>
<CAJk5AtbXrw69ZiDoknA+SkBjSKqMJre+-8JsS8QXpUVQR3BgGA@mail.gmail.com>
Create as little as possible before loading data. (The more indices there
are on a table, the longer it takes to insert a record; having FK
constraints means not only having to perform the check, but the records
might not exist in the referenced table, etc, etc)
On Mon, Aug 11, 2025 at 12:16 PM Raj <[email protected]> wrote:
> When using Ora2pg after taking dump of objects...while restoring which
> objects should I start first and can somebody help me with list of sequence
> of objects to be restored?
>
>
> On Fri, 1 Aug 2025, 02:48 Raj, <[email protected]> wrote:
>
>> 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, <[email protected]>
>> wrote:
>>
>>> Hi ,
>>>
>>>
>>>
>>> >> That "etc" is everything except what you didn't explicitly list. 😉
>>>
>>> >>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 <[email protected]>
>>> *Sent:* Thursday, July 31, 2025 7:47 PM
>>> *To:* Raj <[email protected]>
>>> *Cc:* Pgsql-admin <[email protected]>
>>> *Subject:* Re: Post Oracle to Postgres migartion
>>>
>>> You don't often get email from [email protected]. Learn why this
>>> is important <https://aka.ms/LearnAboutSenderIdentification;
>>> Caution: This email was sent from an external source. Please verify the
>>> sender’s 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 AM Raj <[email protected]> wrote:
>>>
>>> Hi All,
>>>
>>> Post Oracle to Postgres Migration using Ora2pg, as a dba what activites
>>> we may have to perform apart from checking count of objects, rows, vacuum
>>> analyze etc
>>>
>>>
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Post Oracle to Postgres migartion
In-Reply-To: <CANzqJaAZxTgcUA0=OLWzOkeM+JZxtc6YOS4f0DQrcFsMEZU6kg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox