Re: dgmgrl hangs for 40minutes with switchover command

You may already know this but I'll throw it out there anyway. There is a file in same directory as alert log named drc<SID>.log (or similar).
This gives detailed information about what dataguard is doing.

On 25 March 2017 at 03:35, Martin Berger <martin.a.berger_at_gmail.com> wrote:

> Have you set
> log apply delay (DelayMins)
> <http://laurentschneider.com/wordpress/2013/12/changing-the-log-apply-delay-delaymins.html>
> Somewhere?
>
> I'm not sure if this is an issue in 11.2 (my memory tells me 12.1 has
> these issues)
> But it's worth a check.
>
> Hth,
> berx
>
> ^∆x
>
> On 24 Mar 2017 16:40, "GG" <grzegorzof_at_interia.pl> wrote:
>
>> Hi,
>> looks like funny friday just have started for production switchover.
>>
>> We are on 11.2.0.3 with latest psu and after
>> dgmgrl sys/pass_at_primary
>>
>> switchover to standby
>>
>>
>> the switchover command hangs for 40minutes .
>> For primary database_role is primary for standby database_role is standby
>> and nothing is going on , except normal redo apply (no gap showed) .
>>
>> in primary alert log though:
>> "
>> Fri Mar 24 15:21:27 2017
>> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION
>> SHUTDOWN
>> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY [Process Id:
>> 28654] (DB_NAME)
>> Fri Mar 24 15:21:28 2017
>> LGWR: Standby redo logfile selected to archive thread 1 sequence 70230
>> LGWR: Standby redo logfile selected for thread 1 sequence 70230 for
>> destination LOG_ARCHIVE_DEST_2
>> Thread 1 advanced to log sequence 70230 (LGWR switch)
>> Current log# 5 seq# 70230 mem# 0: /u04/oradata/DB_NAME/redo05a.log
>> Current log# 5 seq# 70230 mem# 1: /u04/oradata/DB_NAME/redo05b.log
>> Fri Mar 24 15:21:28 2017
>> Stopping background process CJQ0
>> Fri Mar 24 15:21:28 2017
>> Archived Log entry 139667 added for thread 1 sequence 70229 ID 0xa380a3ed
>> dest 1:
>> "
>> Part of alert log standby:
>> "
>> Fri Mar 24 15:11:51 2017
>> Archived Log entry 139214 added for thread 1 sequence 70228 ID 0xa380a3ed
>> dest 1:
>> Archived Log entry 139215 added for thread 1 sequence 70228 ID 0xa380a3ed
>> dest 3:
>> Fri Mar 24 15:21:28 2017
>> RFS[166]: Selected log 8 for thread 1 sequence 70230 dbid -1555432873
>> branch 842634839
>> Fri Mar 24 15:21:28 2017
>> Archived Log entry 139216 added for thread 1 sequence 70229 ID 0xa380a3ed
>> dest 1:
>> Archived Log entry 139217 added for thread 1 sequence 70229 ID 0xa380a3ed
>> dest 3:
>> Fri Mar 24 15:21:28 2017
>> Media Recovery Waiting for thread 1 sequence 70230 (in transit)
>> Recovery of Online Redo Log: Thread 1 Group 8 Seq 70230 Reading mem 0
>> Mem# 0: /u04/oradata/DB_NAME/DB_NAME_srl1.f
>>
>>
>> dgmgrl shows:
>> DGMGRL> show configuration
>>
>> Configuration - DB_NAME
>>
>> Protection Mode: MaxAvailability
>> Databases:
>> DB_NAME_L1 - Primary database
>> DB_NAME_L2 - Physical standby database
>>
>> Fast-Start Failover: DISABLED
>>
>> Configuration Status:
>> ORA-16534: switchover, failover or convert operation in progress
>> DGM-17017: unable to determine configuration status
>>
>>
>>
>>
>> Session stats on primary shows one session related to dgmgrl
>> which is waiting for ' wait for unread message on broadcast channel'
>>
>> bcd8d2qdv1kcy 1 SYS dgmgrl_at_pimlu-db001 (TNS V1-V3) WAITING wait for
>> unread message on broadcast cha
>>
>> with SQL text like below :
>> ----------
>> SQL_TEXT
>> -----------------------------------------------------------------------------------
>>
>> BEGIN dbms_drs.do_control_raw(:indoc, utdoc, :rid, ieceno, :context, 1);
>> END;
>>
>>
>>
>> We've opened sever 1 but Support did not touch it yet .
>>
>> I've found some bugs related closely to this which suggests :
>> 1. restart primary
>> or
>> 2 kill rsm0 process .
>>
>> Any suggestions greatly appreciated .
>> Regards .
>> GG
>>
>>
>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>>

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