ORA-04030 (initSubHeap:qk,travElemP:qkspmTravCreate) from SELECT or EXPLAIN PLAN statement
(Doc ID 1330496.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Server - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
Running a SELECT or EXPLAIN PLAN statement, you consistently get the error :
The SELECT statement is same as or similar to :
OBJECT_NAME || ' COMPILE' COMANDO
WHERE OWNER = 'SCOTT' AND OBJECT_NAME IN
WHERE OWNER LIKE 'SCOTT' AND REFERENCED_NAME IN
(SELECT DISTINCT (TABLE_NAME)
WHERE TABLE_OWNER LIKE 'SCOTT' AND TABLE_NAME IN
(SELECT DISTINCT NAME
FROM ALL_PART_KEY_COLUMNS C
WHERE OWNER = 'SCOTT' AND C.COLUMN_NAME NOT LIKE 'COD%'))
AND REFERENCED_OWNER = 'SCOTT') AND STATUS = 'INVALID'
AND OBJECT_TYPE IN ('VIEW', 'PROCEDURE', 'FUNCTION', 'PACKAGE')
Setting _optimizer_reuse_cost_annotations to FALSE or _push_join_predicate to FALSE does NOT avoid the ORA-4030
No changes made to the environment.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|