You are on page 1of 2

8/10/2021 Document Display

Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

ORA-600[Mal0-Size-Too-Large] [bfo_qeeOpn: qkexrXformOpn_InitOpn] at function kksmal0


(Doc ID 1379664.1)

In this Document

Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]


Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later


Oracle Database Cloud Exadata Service - Version N/A and later

Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

SYMPTOMS

1.  The following error is being reported in the alert.log:

ORA-00600: internal error code, arguments: [mal0-size-too-large], [bfo_qeeOpn: qkexrXformOpn_InitOpn], [], [], [], [],
[], [], [], [], [], []

2.  The call stack in the trace file will resemble the following:

skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp <- ksfdmp <- dbgexPhaseII <- dbgexProcessError <-
dbgeExecuteForError <- dbgePostErrorKGE <- 1346 <- dbkePostKGE_kgsf <- kgeadse <- kgerinv_internal <- kgerinv <-
kgeasnmierr <- kksmal0 <- kksmal <- qkexrXformOpn <- qkxrXformRwo <- qerocAllocate <- qknDoRwsAllocate <- 131 <-
qkaTraverseQknDesce <- ndents <- qkaTraverseQkn <- qkadrv2Post <- qkadrv2 <- opitca <- kksFullTypeCheck <-
rpiswu2 <- kksLoadChild <- kxsGetRuntimeLock <- kksfbc <- kkspsc0 <- kksParseCursor <- opiosq0 <- kpooprx <-kpoal8
<- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main <-
libc_start_main <- start

Note a call to the function "kksmal0" in the above stack.


3) Database is of multibyte character set such as AL32UTF8 is used


4) The parameter NLS_LENGTH_SEMANTICS = CHAR

5) Pipe-lined table function returning CHAR/VARCHAR2 as object's "attributes"


                   --> if it returns a scalar value then see bug4568610

6) length of the character is greater than 32767 bytes,

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=17xl0hlc3z_52#CAUSE 1/2
8/10/2021 Document Display

i.e  internally

8192 on AL32UTF8 ( * 4)
10923 on UTF8 ( * 3)
16384 on JA16SJIS ( * 2)

CHANGES

CAUSE

The above symptoms matches to the Bug 12851443: ORA-600 [MAL0-SIZE-TOO-LARGE] [BFO_QEEOPN:
QKEXRXFORMOPN_INITOPN]

SOLUTION

Any one of the following solutions will help in resolving the problem:

1. Use the available workaround

-Change the table function to ensure it does not exceed the limits.
-VARCHAR2(8191) character on AL32UTF8 case within 1/4 of 32767
bytes.
-Explicitly use BYTE length such as VARCHAR2(32767 BYTE)

- OR-

2. Download the Patch 12851443 from MOS and apply the Patch 12851443 if available for your current release and platform (
OR )

- OR -

3. Upgrade to the fixed future release of 12.1 when available

REFERENCES

BUG:12851443 - ORA-600 [MAL0-SIZE-TOO-LARGE] [BFO_QEEOPN: QKEXRXFORMOPN_INITOPN]


BUG:4568610 - PROBLEM WITH PIPELINE AND VARCHAR2 LONGER THAN 8191 CHARS ORA-600

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=17xl0hlc3z_52#CAUSE 2/2

You might also like