Re: Some weird phenomenons on oracle data guard physical standby on 11g?

Hi Howard and Andy :-),

The Oracle Data Guard with Primary and Physical Standby are working well, physical standby database is real time apply redo from the primary as well as the redo log files and standby redo log files have the same size 512m whatever on primary and physical standby.

BTW it could not change CLEARING and CURRENT to UNUSED even if I clear and drop firstly and re-add it secondly but for a while it become CLEARING or CURRENT. Even if I don't understand why only switch between 2 number of standby redo log files although having 11 number of standby redo log files on physical standby database, and the 10 number of redo log files have been switched amongst them on primary database.

Best Regards
Quanwen Zhao

Andy Sayer <andysayer_at_gmail.com> 于2023年6月1日周四 22:01写道：

> Running 11g on production is a weird phenomenon.
>
> The important thing to know is if dataguard is working? Is it supposed to
> be real time apply? Is it real time applying?
>
> What you’ve said doesn’t raise any alarm bells with me.
>
> Thanks,
> Andy
>
> On Thu, Jun 1, 2023 at 6:31 AM, Howard Latham <howard.latham_at_gmail.com>
> wrote:
>
>> Are they part of the dB. ? Are they the same size?
>>
>> On Thu, 1 Jun 2023, 14:15 Quanwen Zhao, <quanwenzhao_at_gmail.com> wrote:
>>
>>> Hello my oracle friends :-),
>>>
>>> I've found out some weird phenomenons on oracle data guard physical
>>> standby on 11g of production system on my customer.
>>>
>>> - The status are all showing *CLEARING* on 9 number of redo log
>>> files and the status is *CURRENT* on another redo log file (*the
>>> group number is from 11 to 20*).
>>>
>>>
>>> - The total *11* number of standby redo log files (*the group number
>>> is from 21 to 31*) have always switched (*the status is from
>>> UNASSIGNED to ACTIVE*) on only between *21* and *22* and the rest of
>>> 23 - 31 seem to not have been their turn forever. I've observed it from
>>> alert log.
>>>
>>> Those two number of descriptions above is normal? At the same time I've
>>> glanced at Oracle 19c Data Guard Physical Standby, the status are always
>>> *UNUSED* (never showing CLEARING and CURRENT) on redo log files, 11g
>>> and 19c has a different action?
>>>
>>> Any ideas for this? Thanks in advance!
>>>
>>> Best Regards
>>> Quanwen Zhao
>>>
>>

--
http://www.freelists.org/webpage/oracle-l