SQL statements that run in parallel with NO_PARALLEL hints
(Doc ID 267330.1)
Last updated on MAY 09, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.6 and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Purpose
This document explains the common mistakes when you use a NO_PARALLEL/NO_PARALLEL_INDEX hints. It explains
why a query runs in parallel even though you use a NO_PARALLEL hint.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or
Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended
in any manner.
Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended
in any manner.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |