New answers tagged rman
The backup operation will run on the database server, and the backup pieces may be created on the database server, attached storage disk, a backup server through a 3rd party library (Networker, TSM, etc.), or any other server through network shares (NFS, samba), depending on your configuration.
You have to specify the format string twice, once for database backupsets, and once for the archivelog backups, for example: backup as compressed backupset database format '/path/%U' plus archivelog format '/path/%U';
If diskgroup DATA already exists in you ASM instance, the correct syntax is: BACKUP AS COPY DATABASE FORMAT '+DATA'; regards Giova
In the simplest case, when you restore a database, you tell RMAN to recover it to the most recent point in time by applying all the redo (archived and online) that is available. That will re-apply any statements that were executed during normal database operations including things like dropping tables and deleting data. If you want to restore a database to ...
1 - Make sure Recovery Catalog DB is created either on a different server or a different disk (because in case of failure of target DB and lost of access to its files, if your recovery catalog db stills up and running, you'll have access to control file and probably be able to restore and recover failed instances, given all backups/ archivelogs are ...
Use crosscheck copy before deleting RMAN>crosscheck copy RMAN>delete noprompt obsolete;
No. RMAN is aware of that possibility, hence why it creates a snapshot controlfile before performing backup. Rman needs to access control file to map objects to be backed up, and as controlfile is always in use, snapshot is used for that specific point in time. When you restore a backup, you're simply telling oracle to place those files from the backup back, ...
Top 50 recent answers are included