Priority: L3 - Default
Affects Version/s: None
Fix Version/s: None
Steps to do:
1) Replace all keys with composite keys e.g. MY_KEY_ -> (MY_KEY_, 0)
2) Set up an Oracle Database and check, if all test are running flawlessly
Assuming one has column index on ( x ) and one uses WHERE x IS NULL, then Oracle does not use an index. The reason is that Oracle indexes do not contain values for rows with a NULL index key. The issue is described in depth at this blog and this forum thread.
In order to fix that issue keys at the index creation should be containing a composite index e.g. USER_ID_ should be replaced by (USER_ID_, 0). For the Tenant ID this issue is treated on CAM-6680. However, this problem might also occur on other indexes. Therefore, all indexes should consist of composite indexes. That could avoid full table scans for queries where the other predicates do not require a full table scan (e.g. because they are indexed themselves).
The files to be adjusted can be found here.