>> 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 :
First perform table data migration. Row count verification between source and target tables. Random data checks between source and target at row level.
Applying primary key, constraints and indexes
Applying triggers
Then sequences migration
Database configuration: configuration of postgres.config , shared_buffers, max_connections, configuring maintenace jobs
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
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.
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
