SYMPTOM:
Reports containing cross joins are still run against the database despite the VLDB property "Cartesian join warning" set to cancel reports containing cross joins. The subquery is seen in a subquery generated by an explicit or implicit relationship filter.
CAUSE:
The check for whether cross joins are involved/necessary for the report does not evaluate the logic for relationship filter subqueries. This is a known issue in Strategy.
ACTION:
This issue was reviewed by our Technology team for feasibility and will not be scoped for a code fix in any upcoming Strategy release.
WORKAROUND:
This happens when the cross join is included in a subquery expression. If the "sub query type" VLDB property is changed to use temporary tables then the reports are appropriately canceled.
The Strategy Internal Reference Number for the issue discussed in this technical note is DE24791
