If a table is enabled for RLV storage, you can still issue table-level snapshot
versioning DML statements against it. The DML engine recognizes table-level and row-level
versioned transactions, and manages the locks accordingly.
When a transaction issues a table-level snapshot versioning DML statement against an
RLV-enabled table:
- In-memory data is merged into the IQ main store portion of the table
- The write-intent lock releases
- The table-level DML statement proceeds
Once the transaction completes, the next connection issuing a DML statement in a
row-level snapshot-versioned transaction causes the RLV portion of the table to be
recreated in memory. Until the current transaction issuing the table-level snapshot
versioning DML statement completes, row-level snapshot versioned transactions either
block, or fail.
Note: If a table is enabled for RLV storage, the LOCK TABLE statement
cannot be used.