Skip to Main Content
  • Questions
  • "alter database rename" online-redo causes "WARNING: Cannot delete Oracle managed file"

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Eliomar.

Asked: November 11, 2020 - 8:07 am UTC

Last updated: November 13, 2020 - 6:22 am UTC

Version: 19c

Viewed 1000+ times

You Asked

Hello Team,

I'm restoring a db backup on tape, using rman, on the same host on a different new instance.

The source db/instance is running and uses ASM for online-redologs, spfile, controlfiles, datafiles, etc.

The rman restore/recover command works perfect.

Just before I do an "open resetlogs", I rename the online-redologs on the recovered db on the new instance, here is where I need some advice:

alter database rename file '+DATA/SOURCEDB_TLRSCAN1/ONLINELOG/group_1.260.1048356907' to '+DATA/NEWDB_TLRSCAN1/ONLINELOG/group_1.260.1048356907';

Completed!

The rename was done, the new db can be started, but this warning on the alert-log bothers me:

WARNING: Cannot delete Oracle managed file +DATA/SOURCEDB_TLRSCAN1/ONLINELOG/group_1.260.1048356907
Completed: alter database rename file '+DATA/SOURCEDB_TLRSCAN1/ONLINELOG/group_1.260.1048356907' to '+DATA/NEWDB_TLRSCAN1/ONLINELOG/group_1.260.1048356907'


I suppose Oracle tries to delete the online-redo-files but the ASM files are blocked by the source instance/database.

Is there a way to rename the online-redologs on a safer manner? and not get these warnings?

Thank you

and Connor said...

I don't think I've ever rename a logfile.

I would simply add a new one, and then drop the old one, ie

alter database add logfile group ...
alter database drop logfile group ...

and then open resetlogs.

Let us know how you go

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

A reader, November 12, 2020 - 8:05 am UTC

Hello,

As the source db is running on the same host using these online-redologs, i don't really want that the new instance trying to delete this ASM files.

I guess a normal rman restore/recovery wont be the best way to go in this scenario.

Maybe I need to try the rman duplicate command, perhaps with this duplicate command "rename/delete online-redologs" is not really an issue.

Thanks
Connor McDonald
November 13, 2020 - 6:22 am UTC

As the source db is running on the same host using these online-redologs

True, but don't forget that you'll be connecting to the *database* instance, not the ASM instance, so it will only logs that it has rights over.

But I understand your caution :-)

More to Explore

Administration

Need more information on Administration? Check out the Administrators guide for the Oracle Database