Copy redo logs from asm to file system

Share this article :. Related Articles By Category. February 20, at PM. February 21, at AM. May 21, at PM.

November 19, at PM. Post a Comment Thank you for visiting our site and leaving your valuable comment. FILE , f. NAME "File", t. How to Upgrade to Oracle 19c.

Friday, September 25, Source Database Target Database The steps are same for any other version to 19c upgrade. Upgrading the database from It automates many things including upgrading Time zone, gathering dictionary statistics , taking restore RMAN backup or creating restore point , starting the listener with new OH etc.

Although DBUA can do many thing its recommended to everything possible that can be done upfront to minimize the overall downtime. ORA diskgroup is incomplete. At this point the migration is complete. Your database and flash recovery area are stored in ASM. This section describes procedures to use if you already have backups on disk in non-ASM disk storage and you want to start using ASM to store your flash recovery area.

You must set the initialization parameters related to the flash recovery area to refer to the ASM disk location. Then you can migrate existing backups, online logs, to the new ASM flash recovery area. Before changing the location of the flash recovery area, you should drop any guaranteed restore points. Flashback logs used to support guaranteed restore points are stored in the flash recovery area.

For this example, assume the intended size of the flash recovery area is gigabytes. If you were using flashback logging before to support flashback database, you can re-enable it now. The following procedure changes the database configuration so that the flash recovery area is used for all future backups.

If this database is a primary database and your online logs, control file or archived redo logs are in the flash recovery area, then perform a consistent shutdown of your database. If this database is a standby database and your standby online logs, control file, or archive logs are in recovery area, then stop managed recovery mode and shut down the database.

The next step is to migrate the control file from the old flash recovery area to the new flash recovery area. At this point, all future files that are directed to the flash recovery area are created in the new ASM flash recovery area location.

Because the actual flashback logs cannot be migrated, the only step required to move the location of flashback logs to the new ASM flash recovery area is to disable and then enable flashback logging. Future flashback logs will be created in the new flash recovery area. The old flashback logs are automatically deleted from non-ASM storage.

Step 8: Restore controlfile. Step 9: Mount database. Step Catalog the backup pieces. Step Restore database. Step Add TNS entry. Caution : Your use of any information or materials on this website is entirely at your own risk. It is provided for educational purposes only. It has been tested internally, however, we do not guarantee that it will work for you.