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)
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?
>> 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
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
