Issue Information
| Issue Number | 701508a |
| Issue | When parallel DML (PDML) is performed on a table containing both indexes that include encrypt columns and indexes with the multi-index maintenance feature enabled, the indexes with the multi-index maintenance feature enabled become corrupted. When INSERT is executed, the keys of new rows are not reflected in the indexes, and when DELETE is executed, the keys of deleted rows remain in the indexes. The row count matches, but the DML itself is processed as successful. On tables containing only encrypt column indexes, PDML DELETE and UPDATE fail with an internal error. |
| Cause | During PDML execution, the order in which subqueries for each index are processed in the index maintenance logic does not match the actual execution order, which can result in missing or duplicate key values. In addition, on tables containing only encrypted column indexes, index maintenance is attempted even though no subquery is generated, resulting in an internal error. |
| Solutions | PE IDXM is modified not to count empty subquery positions and to process only subqueries with use_multi index applied sequentially. In addition, when there is no DML with use_multi index applied, PDML is disabled and the operation is performed serially. PE IDXM is also modified to be applied to MERGE statements with an insert clause even when the update clause does not modify index columns. Previously, when executed without PE IDXM, the index keys in the insert clause could be omitted. |
| Occurrence Date | 26.10.05. |
| Version Requiring the Patch | 7FS02PS |
Patch Information
| Patch Name | FS02PS_701508a |
| Major Version | 7 |
| Minor Version | FS02PS |
| Version Title | Fix for an issue where use_multi indexes were corrupted in PDML on tables with mixed encrypt column indexes |
| Available for Deployment | 26.11.09. |
| Compatibility | • TAC rolling patch: Available • TSC rolling patch: Available • Backup data compatibility: Available • Protocol compatibility: Available • Data format compatibility: Available |
| AP Impact | • Plan change: Yes • Result value change: No • SQL syntax change: No • System object change: No • Existing feature change: No |
| Parameters | - |
| Workaround | - |