New answers tagged rman
It's the moment of the last redolog archival, before some point in time during the RMAN duplicate command. You can test this easily, if you either manually provoke redolog switches (and thus subsequent archivals), or even better: write some script to provoke very frequent and unnecessary redolog switches. In which you perform some insert/update/delete, to ...
No, you can't. https://docs.oracle.com/database/121/BRADV/rcmcncpt.htm#BRADV107 You can use the COPIES parameter in the CONFIGURE, SET, or BACKUP commands to specify duplexing of backup sets when using the BACKUP command. RMAN can duplex backups to either disk or tape, but cannot duplex backups to tape and disk simultaneously.
The message indicates that no archivelog exists with this sequence in the current incarnation. Failover starts a new incarnation, and log sequences start from 1 again. Let's say your database is at sequence 10 now, and the log sequence was 159 before the failover. V$ARCHIVED_LOG at this point still contains entries about previous incarnation, so the above ...
Maybe those files are not cataloged by RMAN? I would CATALOG them and then DELETE OBSOLETE once again.
I would think you can, have a look here (for old 10g database, but it may do) : https://docs.oracle.com/cd/B19306_01/backup.102/b14192/maint004.htm
You should be able to backup an 22.214.171.124 database using RMAN with an RMAN repository that is set to 126.96.36.199. There seems to be some invalid objects in your RMAN repository schema. You may want to try compiling all of the invalid objects in your RMAN repository to see if they become valid. This probably has nothing to do with you backing up an 188.8.131.52 ...
Top 50 recent answers are included