Solved

Oracle Restore Out of Place damages source database


Userlevel 4
Badge +13

Hi,

I’ve been running some tests with customer lately and we came across some very troubling situation during out of place restore of Oracle database. Specifically restore out of place is trying to delete source database redo logs. If the source database is running it fails, but if source database is closed it succeeds damaging source database

 

You can find alert.log snippet below:

Source DB shutdown

Deleted Oracle managed file +DATA/BMSTST1/ONLINELOG/group_3.1951.1090834209

Completed: alter database rename file '+DATA/BMSTST1/ONLINELOG/group_3.1951.1090834209' to '+DATA/BMSTST2/ONLINELOGS/redo_1.log'

alter database rename file '+DATA/BMSTST1/ONLINELOG/group_2.1950.1090834207' to '+DATA/BMSTST2/ONLINELOGS/redo_2.log'

Deleted Oracle managed file +DATA/BMSTST1/ONLINELOG/group_2.1950.1090834207

Completed: alter database rename file '+DATA/BMSTST1/ONLINELOG/group_2.1950.1090834207' to '+DATA/BMSTST2/ONLINELOGS/redo_2.log'

alter database rename file '+DATA/BMSTST1/ONLINELOG/group_1.1949.1090834207' to '+DATA/BMSTST2/ONLINELOGS/redo_3.log'

Deleted Oracle managed file +DATA/BMSTST1/ONLINELOG/group_1.1949.1090834207

Completed: alter database rename file '+DATA/BMSTST1/ONLINELOG/group_1.1949.1090834207' to '+DATA/BMSTST2/ONLINELOGS/redo_3.log'

Source DB Open

WARNING: Cannot delete Oracle managed file +DATA/BMSTST1/ONLINELOG/group_3.542.1105103707

Completed: alter database rename file '+DATA/BMSTST1/ONLINELOG/group_3.542.1105103707' to '+DATA/BMSTST2/DATAFILE/redo_BMSTST21.log'

alter database rename file '+DATA/BMSTST1/ONLINELOG/group_2.531.1105103707' to '+DATA/BMSTST2/DATAFILE/redo_BMSTST22.log'

WARNING: Cannot delete Oracle managed file +DATA/BMSTST1/ONLINELOG/group_2.531.1105103707

Completed: alter database rename file '+DATA/BMSTST1/ONLINELOG/group_2.531.1105103707' to '+DATA/BMSTST2/DATAFILE/redo_BMSTST22.log'

alter database rename file '+DATA/BMSTST1/ONLINELOG/group_1.535.1105103707' to '+DATA/BMSTST2/DATAFILE/redo_BMSTST23.log'

WARNING: Cannot delete Oracle managed file +DATA/BMSTST1/ONLINELOG/group_1.535.1105103707

Completed: alter database rename file '+DATA/BMSTST1/ONLINELOG/group_1.535.1105103707' to '+DATA/BMSTST2/DATAFILE/redo_BMSTST23.log'

 

Source and destination DBs are on the same server.

Can anyone explain why is this happening?

icon

Best answer by Robert Horowski 24 June 2022, 13:16

View original

2 replies

Badge +1

Hi,

I’ve been running some tests with customer lately and we came across some very troubling situation during out of place restore of Oracle database. Specifically restore out of place is trying to delete source database redo logs. If the source database is running it fails, but if source database is closed it succeeds damaging source database

….

 

Have you opened an support incident? If not, could you please do so as this requires a detailed review/investigation. I wouldn’t be comfortable drawing conclusions with the subset of what has been provided.

Userlevel 4
Badge +13

Hi,

 

I just wanted to leave that here for the benefit of the community:

 

Cross instance restore on the same machine is not supported as per documentation

https://documentation.commvault.com/11.24/expert/111457_configuring_source_and_destination_instance_for_cross_instance_restores.html

 

If you try to do that from Java GUI it won’t even let you, but unfortunately for me Command Center is not that smart.

Reply