![]() ![]() Sql "alter database backup controlfile to ''your_backup_path/controlfile.ctl''" Sql "create pfile=''your_backup_path/initSID.ora'' from spfile" The reason for this trouble is that after the “backup current controlfile for standby” command, another controlfile backup or backup copy has been started.īackup filesperset 10 archivelog all delete input format 'your_backup_path/your_backup_format' īackup incremental level 0 filesperset 10 database format 'your_backup_path/your_backup_format' īackup current controlfile for standby format 'your_backup_path/ctl_stdby.ctl' This can appear even if the “backup current controlfile for standby” commandwas included in the the RMAN script. However in some cases, RMAN might complain since the the used backup controlfile is not a “standby controlfile”. ![]() ![]() In order to create a Data Guard configuration, you need a standby database on the standby server.įor this purpose you might use a “duplicate for standby” with RMAN. It exists since at least RMAN 10g, it is called the “Restore Failover”. In fact, the feature itself is not very new. #Ora 19571 archived log recid stamp not found in control file fullYou have certainly also received this error once in you Oracle DBA career: “ORA-01665: control file is not a standby control file” while trying to create a standby database with RMAN through a full database backup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |