My Oracle Support Banner

DBCS: VMBM - Database Clone Operation Failed with DCS-10339:Update of DB Metadata failed.Failed to rename the asm files (Doc ID 2883110.1)

Last updated on APRIL 29, 2024

Applies to:

Oracle Cloud Infrastructure - Database Service - Version N/A and later
Linux x86-64

Symptoms

When attempting to clone a DB System, the following error occurs.

ERROR
-----------------------
The cause of the failed operation could be *Cause: Failed to update the DB Metadata for clone.. The user can take the following action to recover from the failure : *Action: Contact Oracle Support Services for assistance.

 

Symptoms #1 and #2

 

- In dcs-agent log file

  

[2022-07-03 03:15:28,953] FINE [renameASMFiles : JobId=a92a329c-22af-47c3-b3e6-e20c776dd115] com.oracle.dcs.agent.zk.DCSZooKeeper: DCS node id is - node_0
[2022-07-03 03:15:28,954] FINE [renameASMFiles : JobId=a92a329c-22af-47c3-b3e6-e20c776dd115] com.oracle.dcs.agent.task.TaskZJsonRpc: Task[TaskZJsonRpcExt_765] RPC request 'Local:node_0@renameASMFiles()' completed: Failure
[2022-07-03 03:15:28,954] FINE [renameASMFiles : JobId=a92a329c-22af-47c3-b3e6-e20c776dd115] com.oracle.dcs.agent.task.TaskZJsonRpcExt: Task[id: TaskZJsonRpcExt_765, TaskName: renameASMFiles] got exception:
com.oracle.dcs.commons.exception.DcsTaskFailureException: DCS-10339:Update of DB Metadata failed.Failed to rename the asm filesRMAN> 2> 3> 4> 5>

  

 

 

- In rman log file

 

RMAN> set echo on;
2> catalog start with '+DATA/<DB_UNQNAME>/' noprompt;
3>
4> switch database to copy;
5>
echo set on

using target database control file instead of recovery catalog
searching for all files that match the pattern +DATA/<DB_UNQNAME>/
no files found to be unknown to the database

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch to copy command at 07/03/2022 03:15:28
RMAN-06571: datafile 1 does not have recoverable copy <<<-----------------

Recovery Manager complete.

  

 

- All datafiles are Oracle Managed Files

 

Symptoms #3

 

Datafiles not in OMF Format

 

RMAN> report schema;

 

List of Permanent Datafiles
===========================
File  Size(MB)    Tablespace                      RB segs  Datafile Name
----  --------      ---------------------------- -------     ------------------------
1     1040         SYSTEM                          YES        +DATA/<DB_UNIQUE_NAME>/DATAFILE/system.261.1146758211
3     1600         SYSAUX                           NO        +DATA/<DB_UNIQUE_NAME>/DATAFILE/sysaux.268.1146758201
4        95          UNDOTBS1                     YES        +DATA/<DB_UNIQUE_NAME>/DATAFILE/undotbs1.260.1146758225
5      370          PDB$SEED:SYSTEM          NO        +DATA/<DB_UNIQUE_NAME>/DDF858C102660237E0536803640A5366/DATAFILE/system.264.1146757969
6      410          PDB$SEED:SYSAUX          NO        +DATA/<DB_UNIQUE_NAME>/DDF858C102660237E0536803640A5366/DATAFILE/sysaux.265.1146757969
7        50          PDB$SEED:UNDOTBS1      NO       +DATA/<DB_UNIQUE_NAME>/DDF858C102660237E0536803640A5366/DATAFILE/undotbs1.266.1146757969
11        5          USERS                             NO       +DATA/<DB_UNIQUE_NAME>/DATAFILE/users.271.1146758669
13   3230         <PDB_NAME>:SYSTEM     YES       +DATA/<BAD_DB_NAME>/DATAFILE/system.289.1146833023   <<------ Non-OMF

.

.

.

  

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.