STANDBY DB -Alert logfile:
Media Recovery Log /dbprod/PROD/db/apps_st/data/archive/1_138_1090708106.dbf
Media Recovery Waiting for thread 1 sequence 139 (in transit)
Thu Feb 03 11:46:15 2022
Archived Log entry 18 added for thread 1 sequence 139 rlc 1090708106 ID 0x1df3f809 dest 2:
Thu Feb 03 11:46:15 2022
Errors in file /dbprod/PROD/db/tech_st/12.1.0/admin/PROD_standbydb/diag/rdbms/prodmum/PROD/trace/PROD_rfs_26005.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 3 thread 0: ‘/dbprod/PROD/db/apps_st/data/log03as.dbf’
Thu Feb 03 11:46:15 2022
Errors in file /dbprod/PROD/db/tech_st/12.1.0/admin/PROD_standbydb/diag/rdbms/prodmum/PROD/trace/PROD_rfs_26005.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 4 thread 0: ‘/dbprod/PROD/db/apps_st/data/log04as.dbf’
Thu Feb 03 11:46:15 2022
Errors in file /dbprod/PROD/db/tech_st/12.1.0/admin/PROD_standbydb/diag/rdbms/prodmum/PROD/trace/PROD_rfs_26005.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 5 thread 0: ‘/dbprod/PROD/db/apps_st/data/log05as.dbf’
RFS[4]: No standby redo logfiles created for T-1
RFS[4]: Opened log for thread 1 sequence 140 dbid 502546441 branch 1090708106
Thu Feb 03 11:46:15 2022
Errors in file /dbprod/PROD/db/tech_st/12.1.0/admin/PROD_standbydb/diag/rdbms/prodmum/PROD/trace/PROD_m000_21700.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: ‘/dbprod/PROD/db/apps_st/data/log01b.dbf’
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Primary Database:
++++++++++++++++++++++++++++++++
SQL> select status,instance_name,database_role from v$database,v$instance;
STATUS INSTANCE_NAME DATABASE_ROLE
OPEN PROD PRIMARY
SQL> select group#,sum(bytes/1024/1024)”Size in MB” from v$log group by group#;
GROUP# Size in MB
1 1000
2 1000
SQL> select group#,sum(bytes/1024/1024)”Size in MB” from v$standby_log group by group#
GROUP # Size in MB
4 1000
5 1000
3 1000
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
146
STANDBY DATABASE
SQL> select status,instance_name,database_role from v$database,v$Instance;
STATUS INSTANCE_NAME DATABASE_ROLE
MOUNTED PROD PHYSICAL STANDBY
SQL> select group#, sum(bytes/1024/1024)”Size in MB” from v$log group by group#;
GROUP # Size in MB
1 1000
2 1000
SQL> select group#,sum(bytes/1024/1024)”Size in MB” from v$standby_log group by group#;
GROUP # Size in MB
3 1000
4 1000
5 1000
SQL> select group#,status from v$log;
GROUP# STATUS
2 INACTIVE
1 ACTIVE
1.SQL> alter system set standby_file_management=manual;
2.alter database recover managed standby dadatabase cancel;
3.SQL> select * from v$log;
4.SQL> select group# from v$standby_log;
5.
Once dropped, verify nothing is existing in ‘select group# from v$standby_log;’
Now create a new standby redo logfile,
will have to drop 3,4 and 4 drop
alter database add standby logfile group 3 ‘/dbprod/PROD/db/apps_st/data/log03as.dbf’ size 1000M
alter database add standby logfile group 4 ‘Location’ size 1000M;
alter database add standby logfile group 5 ‘Location’ size 1000M;
Always we recommend, we need to N+1 standby redo logfiles, here N is number of online redo logfile in primary database (each thread).
Once you create minimum 1 standb redo logfile, you drop and create online redo logfiles
Once you complete for standby and online redo logfile, then
SQL> alter system set standby_file_management=AUTO
Once restart the Stand by database
$ sqlplus / as sysdba
SQL> startup nomount;
SQL> alter database mount standby database;
Put the standby database into managed recovery mode
SQL> alter database recover managed standby database disconnect from session using current logfile;
http://Handling ORL and SRL (Resize) on Primary and Physical Standby in Data Guard Environment (Doc ID 1532566.1)