The following applies only while performing a RAC two-stage rolling patch from 23.6 or 23.7 to 23.8 and above.

Just as in 23.6 and 23.7, explicit vector storage format usage in PL/SQL will raise a compile time error. Neither the constructor nor the type accept a storage format argument. The constructor always defaults to dense and vector variables may contain vectors with either storage format (as passed in via SQL or elsewhere).

Column references (such as %type, %rowtype, and static cursors) to dense vectors will also be unchanged during the patch. These will create flexible storage format vectors. Usage of sparse column references in PL/SQL will now raise a PLS-850, feature not supported, during a 2-stage RAC roll.

Once the patch is enabled, the PL/SQL compiler behaves normally. The vector constructor and type support the storage format argument. Vector variables adhere to the storage format constraints, whether declared explicitly or inherited from SQL. Errors are raised upon assignment if the vector fails the storage format constraint check, as they are for dimension count and dimension format.

Workaround

Use EXECUTE IMMEDIATE or another dynamic reference to query a sparse column.