GGS_DDL_SEQ on ADG env - weird (new) issue
Date: Tue, 30 Apr 2019 10:17:08 -0500
Message-ID: <CAP79kiRVC83jiSakKgaVu3rH9BMqBsOZc80ptgOvh3XCYaFzhg_at_mail.gmail.com>
env: 12.1.0.2
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-lReceived on Tue Apr 30 2019 - 17:17:08 CEST