![]() The main problem with this approach is the fact that you end the process by opening the target database with RESETLOGS, which make it to be a new incarnation, almost as if it was a new database. Open the database with RESETLOGS option.In the cutover window, perform a last incremental backup of the source with the database mounted, then copy and apply it to the target. ![]() While you are waiting for the cutover window, perform periodic incremental backups in the source and update the target with them.Copy the backup files to the target and restore the database from it.Perform a full backup of the source database.Copy all Oracle configuration files (spfile, password file, listener.ora, tnsnames.ora, etc) and make the necessary adjustments.Prepare the new host (install Oracle software, etc).It’s also well known the technique to keep updating the target with all the changes in the source until the cutover window. It’s well known the technique of moving an Oracle database to a new host, as explained for example in this documentation link.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |