Our current guess is that Oracle experiments with potentially future builds in their sandboxes before they roll out changes in production and there is some low level change in their query engine that's now causing this error. Any help would be much appreciated!