Thinking Out Loud

May 29, 2015

Warning: standby redo logs not configured for thread – BUG

Filed under: 12c,Dataguard,oracle — mdinh @ 12:12 am

Surprise to find the following error for single instance Data Guard environment:

    Warning: standby redo logs not configured for thread 3 on boston

 

This will be fixed with an upcoming patch for the existing issue in Oracle Database 12.1.0.1.0 – good reason to stay up to date on patching?

Also, the number of Standby Redo Log Groups do not match since thread = 1 is being used.

Not *ALL* SRL have thread 1 assigned – not sure if this is a bug as well.

[oracle@host01 trace]$ dgmgrl /

DGMGRL for Linux: Version 12.1.0.1.0 - 64bit Production

Copyright (c) 2000, 2012, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected as SYSDG.
DGMGRL> validate database boston

  Database Role:    Primary database

  Ready for Switchover:  Yes

  Flashback Database Status:
    boston:  Off

DGMGRL> validate database london

  Database Role:     Physical standby database
  Primary Database:  boston

  Ready for Switchover:  Yes
  Ready for Failover:    Yes (Primary Running)

  Flashback Database Status:
    boston:  Off
    london:  Off

  Current Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (boston)                 (london)                 
    1         3                        2                        

  Future Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (london)                 (boston)                 
    1         3                        0                        
    Warning: standby redo logs not configured for thread 3 on boston

DGMGRL> validate database london2

  Database Role:     Logical standby database
  Primary Database:  boston

  Ready for Switchover:  Yes
  Ready for Failover:    Yes (Primary Running)
    Warning: Physical and snapshot standby databases will
    be disabled if a role change is performed to this database

  Flashback Database Status:
    boston:   Off
    london2:  Off

  Current Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (boston)                 (london2)                
    1         3                        2                        

  Future Log File Groups Configuration:
    Thread #  Online Redo Log Groups   Standby Redo Log Groups  
              (london2)                (boston)                 
    1         3                        0                        
    Warning: standby redo logs not configured for thread 3 on boston

DGMGRL> 
HOST01:(SYS@boston):PRIMARY> select group#,thread#,sequence#,bytes,used,status from v$standby_log;

    GROUP#    THREAD#  SEQUENCE#      BYTES       USED STATUS
---------- ---------- ---------- ---------- ---------- ----------
         4          0          0   52428800          0 UNASSIGNED
         5          0          0   52428800          0 UNASSIGNED
         6          0          0   52428800          0 UNASSIGNED
         7          0          0   52428800          0 UNASSIGNED

HOST01:(SYS@boston):PRIMARY> select count(*) from v$standby_log where thread#=1;

  COUNT(*)
----------
         0

HOST01:(SYS@boston):PRIMARY> 
HOST03:(SYS@london2):LOGICAL STANDBY> select group#,thread#,sequence#,bytes,used,status from v$standby_log;

    GROUP#    THREAD#  SEQUENCE#      BYTES       USED STATUS
---------- ---------- ---------- ---------- ---------- ----------
         4          1         67   52428800    4803072 ACTIVE
         5          1          0   52428800          0 UNASSIGNED
         6          0          0   52428800          0 UNASSIGNED
         7          0          0   52428800          0 UNASSIGNED

HOST03:(SYS@london2):LOGICAL STANDBY> select count(*) from v$standby_log where thread#=1;

  COUNT(*)
----------
         2

HOST03:(SYS@london2):LOGICAL STANDBY> 
HOST03:(SYS@london):PHYSICAL STANDBY> select group#,thread#,sequence#,bytes,used,status from v$standby_log;

    GROUP#    THREAD#  SEQUENCE#      BYTES       USED STATUS
---------- ---------- ---------- ---------- ---------- ----------
         4          1         67   52428800    4816896 ACTIVE
         5          1          0   52428800          0 UNASSIGNED
         6          0          0   52428800          0 UNASSIGNED
         7          0          0   52428800          0 UNASSIGNED

HOST03:(SYS@london):PHYSICAL STANDBY> select count(*) from v$standby_log where thread#=1;

  COUNT(*)
----------
         2

HOST03:(SYS@london):PHYSICAL STANDBY> 
Advertisements

4 Comments »

  1. Funny, yesterday I corrected this at a client of mine.
    For information, Metalink notes:
    – Warning: standby redo logs not configured for thread on (Doc ID 1956103.1)
    – Bug 14674237 – VALIDATE DATABASE from BROKER incorrectly reports on standby redo log files (Doc ID 14674237.8)

    talk about it. The solution is (verified yesterday, it works):
    Drop and recreate the SRL with a valid thread# to avoid the warning.
    ALTER DATABASE DROP STANDBY LOGFILE GROUP #;
    ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 SIZE ;

    Cheers,
    Miguel Anjo

    Comment by Miguel Anjo — May 29, 2015 @ 3:21 pm | Reply

  2. […] Warning: standby redo logs not configured for thread – BUG […]

    Pingback by Log Buffer #425: A Carnival of the Vanities for DBAs | InsideMySQL — May 30, 2015 @ 7:00 am | Reply

  3. […] Warning: standby redo logs not configured for thread – BUG […]

    Pingback by Log Buffer #425: A Carnival of the Vanities for DBAs | MySQL — June 1, 2015 @ 7:55 am | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: