RE: GGS_DDL_SEQ on ADG env - weird (new) issue

From: Reen, Elizabeth <"Reen,>
Date: Tue, 30 Apr 2019 15:50:43 +0000
Message-ID: <7fbf566585b24c60bbeada360625f35d_at_imcnam.ssmb.com>

                That looks like a golden gate sql.  Are you running Active dataguard? Or GG on your DR instance?

Liz

From: [External] oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of [External] Chris Taylor Sent: Tuesday, April 30, 2019 11:17 AM
To: ORACLE-L <oracle-l_at_freelists.org> Subject: GGS_DDL_SEQ on ADG env - weird (new) issue

env: 12.1.0.2<https://urldefense.proofpoint.com/v2/url?u=http-3A__12.1.0.2&d=DwQFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=yWMFosURAngbt8VLeJtKLVJGefQxustAZ9UxecV7xpc&m=kEJKNCTOpH2CKJA-RlIsbliE0IhRX_WW6pXyWTAO86k&s=lVC0ROqsXZZI--eaVjJq17TwvllRXZs9a-vrwd1FX8g&e=>

So I've got a weird issue and seems related to this doc:

ORA-00604 And ORA-16000 In ADG Due to the Internal Updates for Sequence GGS_DDL_SEQ (Doc ID 2503143.1)

BACKGROUND:

---

 On Friday & today our standby threw an error like this:

ORA-00600: internal error code, arguments: [6817], [110546404], [], [], [], [], [], [], [], [], [], []

6817 related to global sequence problem.

The incident file shows this:
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0) [TOC00003]
----- Current SQL Statement for this session (sql_id=gj5cb8uz35v3h) ----- SELECT "GGATE" . "GGS_DDL_SEQ" .NEXTVAL FROM DUAL The workaround in the support document talks about disabling the trigger which I don't really want to do on the primary.

Would it be reasonable to disable the trigger the on standby for this? Seems like it should be disabled on the standby anyway (or ignored) but doesn't seem to be happening.

I'm thinking about coming up with a solution to disable the trigger on the standby unless that doesn't make sense?

Chris

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

Received on Tue Apr 30 2019 - 17:50:43 CEST