Bug 14143632 ora-30927 on active data guard
Adam Jarvis, January 26, 2017 - 11:54 pm UTC
Thank you so much for the response and the helpful information, I tried looking up this bug and more information about it but haven't been able to find much yet without the need of an Oracle provider code or something. I am going to try and get our DB team to reach out to Oracle for further assistance. Thanks again! Very quick reply !!
January 27, 2017 - 12:02 am UTC
There is a patch available, and the bug is fixed in 11.2.0.4
You could also try the following as a workaround
with blah as
( select a,b,c from ...)
becomes
with blah as
( select /*+ inline */ a,b,c from ...)
to avoid the temporary table load/creation - but no guarantees, because if a query cannot be inlined, you'll still get the error.
WITH clause inline view
Adam Jarvis, January 27, 2017 - 12:41 am UTC
That work around did force it to run as incline view vs being resolved as a Temp Table, however it took almost 16 Minutes to do so however forcing the same dataset to run as incline view on the other server (where this bug seems to not exist) only took 22 Seconds. Do you know if this bug also can cause overall low performance in general? Or does something specific set it off like DNS name change / Failing over from the other server to this one that is showing issues? Thank you for the work around, that is a neat trick I did not have any idea about!
January 30, 2017 - 7:53 pm UTC
INLINE is very much a *workaround* rather than a solution, because if a query cannot be inlined, then the hint wont take effect and you'd be back to the original error.
I think your best way forward would be to upgrade to 11.2.0.4 or get a patch for the bug.