This is a list of the items to consider when dumping and loading your Progress OpenEdge databases. Identify which ones apply to your environment and address them in your runbook, then test, test, test!
- Use ProTop RT - PAID version - to produce an optimized database structure based on your actual data, plus the scripts to dump and load your standard application tables.
- See Check your schema for "gotchas"! Do you have fields of type RECID or ROWID? (they get the unknown value "?") you'll need to write code to accommodate the transition.
- CLOB - add specific storage area to .st and update df
- LOB - add specific storage area to .st and update df
- SQL Views
- SQL Grants
- _user
- _sequence
- OE Audit Policies
- OE Authentication policies/administrators/domains
- OE DB internal privileges - Who can-read and can-write?
- Change Data Capture (CDC) policies
- Transparent Data Encryption (TDE) (policy and key stores)
- Consider implications for alternate/secondary buffer pool?
- Reseeding OE Replication target(s)
- OE version-specific D&L issues?
- Convert to UTF-8 encoding?
- Pro2 version 5 & 6 considerations?
- Who is your OE DBA? Who is your OE Security Admin? (IDs? sysprogress etc)
- Considerations for multi-tenancy?
- Considerations for partitioned tables?
- Known issue - record counts inaccurate for C/LOB (use what instead?)
Now ...
Write out your plan to address all the items that apply to your situation.
Then ...
Test, test, test!