My Oracle Support Banner

ORA-600[KGL-heap-size-exceeded] And Concurrency Issues After Failure To Compile An Invalid AFTER ALTER ON DATABASE Trigger With Query Rewrite Enabled And Materialized Views (Doc ID 2385185.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

In a database that has an AFTER ALTER ON DATABASE trigger enabled, if this trigger becomes invalid and cannot be recompiled, and the database has materialized views (mviews) with queries that rewrite to them, then a number of symptoms can occur:

Call stack for ORA-600[KGL-heap-size-exceeded]

kglLargeHeapWarning <- kglHeapAllocCbk <- kghalp <- qsmqsmr <- kqlobjlod <- kqllod_new
<- kqlCallback <- kqllod <- kglobld <- kglobpn <- kglpim <- kglpin <- kglgob <- qsmqgso
<- kkqsLoadKglSummary <- kkqsGetSum <- kkqslsum <- kkqspsum <- kkqsedrv <- kkqsrqb
<- kkqsRewriteCurrentQB <- kkqscqb <- kkqsptq <- kkqsptqur <- kkqsrdrv <- kkqdrv <- opiSem
<- opiDeferredSem <- opitca <- kksFullTypeCheck <- rpiswu2 <- kksSetBindType <- kksfbc
<- opiexe <- opipls <- opiodr <- rpidrus <- skgmstack <- rpidru <- rpiswu2 <- rpidrv

  

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.