In this Document
This issue possibly occurs following an upgrade from a prior database release.
This is due to internal bug:
1. The bug is fixed in 21.1
2. Apply Patch 31440426
3. Or use following workaround:
Set _OPTIMIZER_COST_BASED_TRANSFORMATION to OFF.
Set _FIX_CONTROL to '22559379:0'.
at the session level.