ASMCMD-8016 unable to copy controlfile in ASM

During DB cloning or duplication , we may encounter below error while backing up control file or any other ASM db file within ASM disk group or on local file system


ASMCMD> cd +RECO/testdb/controlfile/
ASMCMD> cp control02.dbf /u01/oneoffpatches
copying +RECO/testdb/controlfile/control02.dbf -> /u01/oneoffpatches/control02.dbf
ASMCMD-8016: copy source '+RECO/testdb/controlfile/control02.dbf' and target '/u01/oracle/control02.dbf' failed
ORA-06550: line 3, column 9:

PLS-00306: wrong number or types of arguments in call to 'COPY'
ORA-06550: line 3, column 9:
PL/SQL: Statement ignored (DBD ERROR: error possibly near <*> indicator at char 23 in '
<*>dbms_diskgroup.copy('', '', '', :src_path, :src_ftyp, :src_blksz,
:src_fsiz, '','','', :dst_path, 1);

Although i did not find the exact solution but derived multiple checks through which it can be avoided.

1. During db cloning we may encounter multiple issue listing few of them as below.

RMAN-00600: internal error, arguments [7038] [rec_cl_delarc]
RMAN-05501: aborting duplication of target database
RMAN-03002: failure of Duplicate Db command

DB restoration failure forces us to redo certain steps like re-creating control file or changing db names in spfile etc.

Special attention required while moving these files withing ASM or out of ASM as it could be a alias to actual files as below

ASMCMD> ls control01.dbf
CONTROLFILE  HIGH    FINE     NOV 09 04:00:00  N    control01.dbf => +DATA/TESTDB/CONTROLFILE/backup.1843.564192846

2. Check the existence of the source file to be moved if it belongs the absolute path and not a soft link

3. Destination directory to which ASM files being moved has sufficient space and appropriate permissions.

4. One of the most important check is to ensure the DISK group involved in source/destination copy is mounted.

5. File being moved is not being used currently by any of the live instance (mounted/OPEN DB)

6. Any ongoing restoration/recovery to be verified before copy or move to ensure the ongoing cloning does not disturb

You may post exact solution to mentioned error which will be helpul for DBA's

No comments:

Post a Comment