Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Oracle rman restore error RMAN-06023

2025-04-02 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

When building the dg, I used the complete equipment of the main database to restore in the slave database. After the first recovery, gap appeared, and then I wanted to use the latest backup to restore the data again, so the following problems occurred:

The error is as follows:

RMAN-00571: = = RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = RMAN-00571: = = RMAN-03002: failure of restore command at 03 found to restoreRMAN-06023 25 09:56:55RMAN-06026: some targets not found-aborting restoreRMAN-06023: no backup or copy of datafile 4 found to restoreRMAN-06023: no backup or copy of datafile 3 found to restoreRMAN-06023: no backup or copy of datafile 2 found to restoreRMAN-06023: no backup or copy of datafile 1 found to restore

Looking at the backup information of datafile 1, you can clearly see that the backup file is normal.

RMAN > list backup of datafile 1

And then checked this:

List incarnation

After comparing the master and standby database, it is found that the standby database has a record of 2015-03-24 more than the main database, and the status of the standby database is current. The date is 2010-07-07.

Then execute the following statement:

RMAN > reset database to incarnation 2

Then continue to recover, everything is normal.

Then I recalled the operation of preparing the database at this point in time, and the log record is as follows:

Resetting standby activation ID 607536602 (0x243645da) Completed: alter database recover managed standby database finish forceTue Mar 24 16:14:46 CST 2015alter database commit to switchover to primaryTue Mar 24 16:14:46 CST 2015ALTER DATABASE SWITCHOVER TO PRIMARY

This happens because I forcibly switched the standby library as the primary library at this point.

Then query the information, it is because after resetlogs, after resetting scn, the database entity will change, and it will appear that the backup cannot complete the recovery using the entity number is the previous backup, and it will be OK if the entity number needs to be changed to be consistent with the main database.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report