RECOMMENDATIONS
1) Decide if you can delete repository log
Deciding to delete full/partially repository log has several benefits:
• Process is faster
• Process is more reliable
• Process requires less working space
• Final data will be less voluminous
2) Upgrade to most recent version available.
The version must be HOPEX V2R1 Update 3 or higher.
The objective is to benefit from recent fixes and to be under maintenance if ever an error occurs
• Make sur you are in a supported version
• Apply last CP/hotfix.
3) Use a server machine close to SQL Instances
The machine should be located as close as possible from Oracle instance and SQL server instance.
The objective is to have a performant and reliable access to data.
4) Leave the process running quietly.
In particular:
• Do not stop the HOPEX Process of the machine where it is running
• Do not stop Oracle instance (source data)
• Do not stop SQL Server instance (target data)
• Do not try to move the HOPEX environment folder used
5) Check process (test) on a copy of production
The more recent backup, the better vision you will have (duration, success).
a) Restore data according to standard procedures
b) Check that logical backup runs fully (dummy run)
If errors occur (related to logical backup step), analyze the errors with MEGA Technical Support.
c) Check complete process (dummy run)
If errors occur (likely related to import step), analyze the errors with MEGA Technical Support.
6) Loop until the processing runs without unexpected error.
You will have a good idea of
• Disk size required (logical backup file)
• SQL Server size required
• Global duration of operations
If an error occurs and the process fails or stops, do NOT reuse the target SQL Server database
For each repository involved:
• Delete the SQL Server database.
• Create a new SQL Server, possibility with same name.