Tags

,

Following are common problem on dataguard, this problem occurs whenever we are not set standby_file_management to auto on standby database and then modify one of tablespace by adding new datafile in primary database.

problem alert in logfile as follow:
Wed Sep 12 13:07:37 2012
Errors in file $ORACLE_BASE/admin/dump/bdump/db_mrp0_647370.trc:
ORA-01111: name for data file 29 is unknown - rename to correct file
ORA-01110: data file 29: '/home/ora10g/10.2/dbs/UNNAMED00029'
ORA-01157: cannot identify/lock data file 29 - see DBWR trace file
ORA-01111: name for data file 29 is unknown - rename to correct file
ORA-01110: data file 29: '/home/ora10g/10.2/dbs/UNNAMED00029'

step to resolve the problem:

check recovery process on dataguard

 select sequence#,process,status from v$managed_standby

if mrp exist, then cancel the recovery process with

 alter database recover managed standby cancel; 

from alert.log check datafile with “unnamed” filename and change it to missing datafile filename as in the primary database

ALTER DATABASE CREATE DATAFILE '/home/ora10g/10.2/dbs/UNNAMED00029' as '/oradata/dbname/ts_name.dbf'; 

if in the future we want every new datafile added in primary automatically created on standby dataguard then change the parameter standby_file_management to auto in primary and standby database

alter system set standby_file_management='AUTO'; 

then re-run recovery process again.

alter database recover managed standby database [using current logfile] disconnect;