My Oracle Support Banner

Wrong Results in Parallel When Joining Views Containing ORDER BY or GROUP BY on the Join Columns (Doc ID 1296516.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Oracle Database - Enterprise Edition - Version to [Release 10.2]
Information in this document applies to any platform.


A CTAS and/or underlying query returned a different number of rows (fewer) each time the SQL was run.   That is, even the wrong number of rows changed with each execution.  The correct results were returned when run serially. 

ksedst1 <- ksedst <- dbkedDefDump <- dbgexPhaseII <- dbgexProcessError
<- dbgePostErrorKGE <- 1320 <- dbkePostKGE_kgsf <- kgeade <- kgeriv_int
<- kgeasi <- kxfqenq <- qertqoRop <- kdstf00001010000km <- kdsttgr
<- qertbFetch <- rwsfcd <- qertqoFetch <- qerpx_resume <- qerpxFetch
<- rwsfcd <- qerltFetch <- ctcdrv <- opiexe <- opiosq0
<- kpooprx <- kpoal8 <- opiodr <- ttcpip <- opitsk
<- opiino <- opiodr <- opidrv <- sou2o <- opimai_real
<- ssthrdmain <- main <- star

Note: Running a sqltxtract on the wrong-results query will assist with diagnosis, as in a single step, it captures the execution plan, predicates, and DDL for all objects involved.  Please refer to  <Document 215187.1> "SQLT (SQLTXPLAIN) - Tool that helps to diagnose SQL statements performing poorly" to create the necessary schema.  Once installed, you can use the following steps to run a sqltxtract:
• # cd sqlt/run
• # sqlplus [apps user]/[apps pwd]
• SQL> start sqltxtract.sql [sql_id for one SQL]


Update from patch set to the patch set.


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

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

In this Document

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