Oracle Database Migration/Upgrade Checklist

Current Database Details

Current hardware
Current operating system and version
Current database edition and version
Current storage

Database role (e.g. production, test, development) and relationship to other databases (e.g. for a production database identify its related development and test databases)
Nature of database (i.e. Online Transaction Processing, Data Warehouse, Reporting)

Business owners
Technical owners (Database Administrators, Developers)
Other relevant technical teams (e.g. Systems Administrators, Storage Administrators, Network Engineers, Testers)

Service level agreements (including uptime, maintenance windows, change freeze periods)

Application(s) accessing the database
Architecture of application(s) accessing the database, including host platform, location, database client types and versions, service names used, whether dedicated or shared server database connections

Connections with other databases, either Oracle database links or whether applications accessing this database also access other database(s)
Items external to the database (e.g. operating system users, jobs, directories, mounts, outgoing network access)
Ingoing and outgoing interfaces, data feeds and reports
Internal database scheduled jobs

Database options in use, e.g. partitioning, compression, audit vault, diagnostics, tuning

Patches applied, including Bundle Patches, Patch Set Updates and one-off patches

Database size (current footprint and actual space used within this)
Database growth
Shared and private memory (currently allocated and actual amount used, average and peaks)
Number of CPUs

Database load (average and peaks)
Database sessions (average and peaks)
Daily redo log volume (average and peaks)
Daily update, insert, delete volume (average and peaks)
Daily query volume (average and peaks)

Database block size
Initialisation parameters
Character set and language settings

Triggers on database events or schema events (e.g. startup, logon)

Backup and recovery methods (including use of archive log mode and flash recovery area)

Disaster recovery solution(s) (e.g. standby database)

Data archival processes

Monitoring and alerting


Migration/Upgrade Considerations

Target hardware
Target operating system and version
Target database edition and version
Target storage

Service level agreements (particularly desired uptime) for target environment
Performance requirements for target environment
Capacity requirements for target environment

Network connectivity between the application(s) and target database

Data protection and security implications related to re-hosting the data

How much downtime is allowed during the migration?
Is the ability to return to the original database, with minimal or zero data loss, should a serious problem be encountered some time after migration, required?
Is the database character set to be changed?
Migration/upgrade path(s) available from current to target version, including implications, advantages and disadvantages
Is there read-only, historical data which can be migrated separately?
Are current SQL execution plans to be preserved, using SQL Plan Management?

Are there any technical issues, operational issues or opportunities for improvement, which could be addressed in the scope of the migration?

Are application(s) supported on the target database version (including database client type and version)?
Have application(s) been tested on the target database version? If not, are applications planned to be tested on the target database version?
Are application(s) also being migrated? If so, on what timescale, i.e. before, after or at same time as the database?

%d bloggers like this: