This content has been marked as final. Show 6 replies
On Oracle 11 I believe this is not normal.
There was a similar question here a week or so ago and I checked my 11 system and the standby redo was there.
I used this command :
My short notes :
duplicate target database for standby from active database NOFILENAMECHECK;
Yes, I believe cannot explain this but they are easy enough to create after the fact.
Will post command here as insurance after I make some coffee.
If I remember correctly you have to stop redo apply then
alter database add standby logfile '/oracle/redo/prod1/stdby_redo03a.rdo'
alter database recover managed standby database cancel;
alter database add standby logfile group <n> (<filename>) size <size>;
alter database recover managed standby database disconnect;
Edited by: mseberg on Apr 5, 2012 5:44 AM
Edited by: mseberg on Apr 5, 2012 5:51 AM
Edited by: mseberg on Apr 5, 2012 5:53 AM
Nothing is mentioned about standby redo logs in the documentation when talking about duplicate and ASM
Maybe they should always be created manually when using ASM?
Edited by: usersp on Apr 16, 2012 4:48 PM
I am using OMF files, this is why standby redo logs were not created as we can see in the primary alert file
Use the following SQL commands on the standby database to create standby redo logfiles that match the primary database: ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800; ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800; ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800; ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800; ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800; WARNING: OMF is enabled on this database. Creating a physical standby controlfile, when OMF is enabled on the primary database, requires manual RMAN intervention to resolve OMF datafile pathnames. NOTE: Please refer to the RMAN documentation for procedures describing how to manually resolve OMF datafile pathnames.