Appendix: Troubleshoot the RLV Store

The troubleshooting appendix includes a collection of symptoms, with information to further diagnose or solve the problem.

• RLV Store Out of Memory
  Problem: You receive the error message "RLV Store has run out of memory".
• Cannot Convert to Multiplex
  Problem: You receive the error message "Cannot convert database to multiplex. An RLV dbspace exists".
• Cannot Create RLV Dbspace in Multiplex
  Problem: You receive the error message "Create RLV dbspace not allowed in multiplex".
• RLV Dbspace Already Exists
  Problem: You receive the error message "RLV dbspace already exists. Cannot create more than one RLV dbspace".
• Cannot Make RLV Dbspace Read-Only
  Problem: You receive the error message "The RLV dbspace N cannot be made read only because it contains RLV enabled tables".
• Cannot Create Table in RLV Dbspace
  Problem: You receive the error message "Cannot create table N in an RLV dbspace".
• Cannot Enable Table for RLV Storage
  Problem: You receive an error message indicating that the table cannot be enabled for row-level versioning (RLV).
• Cannot Use Foreign Keys in RLV Enabled Table
  Problem: You receive the error message "The use of foreign keys in a RLV table is not supported".
• Cannot Use Index Type in RLV Enabled Table
  Problem: You either receive the error message "The index type 'TEXT' cannot be used with an RLV enabled table", or "The index type 'WD' cannot be used with an RLV enabled table".
• Merge Required Before Table Level Modification
  Problem: You receive the error message "Table N requires an RLV store merge before table-level modification".
• Cannot Perform Merge of RLV Store
  Problem: You receive an error message indicating that the RLV store cannot be merged with the IQ main store.
• RLV Store Merge Already in Progress
  Problem: You receive the error message "RLV store merge already in progress for table N".
• Cannot Open the Requested Object for Write in the Current Transaction
  Problem: You receive an error message indicating that the system cannot open the requested object for write in the current transaction, and that another user has the row locked.
• Transaction Seems to Hang
  Problem: Transaction appears to hang.
• Failed RLV Recovery
  You encounter a recovery problem such as Checksum error reading a page from disk, mismatched sequence number on head / tail of page, or OS exception reading a page from disk.