core/TESTRTS failed with bad Oper CPU Time in explain

[Dave Birdsall]

During gate tests for change https://review.trafodion.org/#/c/1716/, test core/TESTRTS failed because in an Explain plan, Oper CPU Time was reported as 3 for EX_TRAF_KEY_SELECT tcbs. The expected file shows 0 instead.

This failure did not occur during check jobs; instead the expected value of 0 occured.

I doubt this code change had anything to do with the failure; the code change is entirely in DDL logic, not in query plan costing. So I suspect an intermittent failure. Hence this case to record this suspicion.

[Dave Birdsall (dave-birdsall)]

The description is incorrect. The mismatching Oper CPU Time value was in a "display statistics for <query ID>" command, not an explain.

[Selvaganesan Govindarajan (selva-ganesan)]

Fixed. See https://review.trafodion.org/1756 for details