Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-01274 on Physical Standby database.

ice_cold_aswinMar 22 2009 — edited Mar 24 2009
Hi,

I have configured a physical standby database with **LGWR ASYNC ** transport services, which works fine.
When I create a set of datafiles, and users on the primary site, and then do a log switch, the alert log at standby site is being written with the error: **ORA-01274**.

I have attributed this to some configuration problem, and have did the whole excerceise right from creating the Primary database to standby databe and to configuring the dataguard, this time with **ARCH** transport services.

But still the problem persists. Is this normal? I was told that new tablespaces/datafiles will not be replicated at the standby site by the transport services. Is that true? If yes, please tell me how do I replicate them on the standby site.
If no, Please help me fix the problem.

Also, I am posting the standby alert log here for better understanding of the problem. Kindly go through it...
+
Clearing online redo logfile 1 /u02/app/oracle/oradata/asridb/redologs/r01.log
Clearing online log 1 of thread 1 sequence number 37
Sun Mar 22 12:47:42 2009
Errors in file /u02/app/oracle/admin/asridb/bdump/asridb_mrp0_20176.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u02/app/oracle/oradata/asridb/redologs/r01.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 39
Sun Mar 22 12:47:43 2009
Completed: alter database recover managed standby database disconnect from session
Using STANDBY_ARCHIVE_DEST parameter default value as /u02/app/oracle/asridb/archival
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 20213
RFS[1]: Identified database type as 'physical standby'
Sun Mar 22 12:49:04 2009
RFS LogMiner: Client disabled from further notification
Sun Mar 22 12:49:40 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: '/u02/app/oracle/asridb/archival/1_39_682125307.arc'
Sun Mar 22 12:49:42 2009
Media Recovery Log /u02/app/oracle/asridb/archival/1_39_682125307.arc
Media Recovery Waiting for thread 1 sequence 40
Sun Mar 22 12:56:33 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: '/u02/app/oracle/asridb/archival/1_40_682125307.arc'
Sun Mar 22 12:56:38 2009
Media Recovery Log /u02/app/oracle/asridb/archival/1_40_682125307.arc
File #5 added to control file as 'UNNAMED00005' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
Errors with log /u02/app/oracle/asridb/archival/1_40_682125307.arc
MRP0: Background Media Recovery terminated with error 1274
Sun Mar 22 12:56:38 2009
Errors in file /u02/app/oracle/admin/asridb/bdump/asridb_mrp0_20176.trc:
ORA-01274: cannot add datafile '/u02/app/oracle/oradata/asridb/datafiles/asrim_master.dbf' - file could not be created
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Sun Mar 22 12:56:39 2009
Errors in file /u02/app/oracle/admin/asridb/bdump/asridb_mrp0_20176.trc:
ORA-01274: cannot add datafile '/u02/app/oracle/oradata/asridb/datafiles/asrim_master.dbf' - file could not be created
Sun Mar 22 12:56:39 2009
MRP0: Background Media Recovery process shutdown (asridb)
+
Thanks in advance,
Aswin.
This post has been answered by oradba on Mar 22 2009
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 21 2009
Added on Mar 22 2009
4 comments
900 views