We're here to help!

 Dbvisit process sometimes might fail adding datafile in standby, one of the reasons might be due to incorrect database parameters. This article explains how to resolve this issue

Problem Details

Error validating standby files: some datafiles may be corrupted or not renamed in the standby controlfile.
Consult v$_datafile and v$_datafile_header views and verify if the following datafiles are present on the server:
file#=85

A new datafile has been added to the primary database:

file#=85 name=+DATA_DG/sicpro01/datafile/apex.282.839187275

Dbvisit failed to add a datafile to the standby and terminates with an error on the standby:

Error validating standby files: some datafiles may be corrupted or not renamed in the standby controlfile.
Consult v$_datafile and v$_datafile_header views and verify if the following datafiles are present on the server:
file#=85
v_datafile.name=+DATA_DG/sicpro01/datafile/apex.282.839187275
v_datafile.checkpoint_change=93114005942
v_datafile.bytes=0
v_datafile_header.name=
v_datafile_header.checkpoint_change=0
v_datafile_header.bytes=0

Standby database was created by Dbvisit, and ASM diskgroups have been mapped: +DATA_DG on the primary to +DATA on the standby.

Create the standby datafile #85 manually:

>sqlplus / as sysdba
sql>alter database create datafile 85 as '+DATA';
sql>select name from v$datafile where file#=85;
sql>select name from v$datafile_header where file#=85;

Set db_file_name_convert parameter to map ASM diskgroups in the standby database and restart the standby database:

>sqlplus / as sysdba
sql>alter system set db_file_name_convert='+DATA_DG','+DATA' scope=spfile;

Anna MacNaughtan February 12, 2014 12:07