Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Backup and Recovery (MOSC)

Any workaround for Bug 20876249 : COULD NOT MODIFY DB_UNIQUE_NAME RESOURCE EXISTS ?

May 7, 2015 3:00PM edited Nov 4, 2015 8:21AM in Database Backup and Recovery (MOSC) 6 commentsAnswered

Trying to 12.c rac asm to rac asm clone. Requirement is to leave CRS intact. Issuing the "duplicate target database to XXXX" returns the error:

ORA-32017: failure in updating SPFILE

ORA-65500: could not modify DB_UNIQUE_NAME, resource exists. Does anyone know if there is a workaround.

The only thing that cured this was to remove the database with srvctl which defeats the purpose.

Looks like this is the bug.

Bug 20876249 : COULD NOT MODIFY DB_UNIQUE_NAME RESOURCE EXISTS

1

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month