Today, I’ve encountered an interesting bug for what I believe it’s related to TEMP TABLE TRANSFORMATION operation.
I was able to reproduce this on 188.8.131.52, 184.108.40.206 and 220.127.116.11, but not on 18.104.22.168 (looks like it’s been fixed).
I didn’t find any related MOS note/bug regarding this issue, if you’re aware of any please let me know.
Let’s observe the following statement.
During statement execution if you press CTRL-C on the keyboard to stop (break) the execution it it will report “ORA-01013: user requested cancel of current operation”, which is fine. However, the bug is that this error is written in the alert.log and trace file is generated.
This should happen for every error if one occurs during execution of the query.
The problem looks like to be at TEMP TABLE TRANSFORMATION operation. Probably it’s some code defect where an exception is missing and every error is traced. Note, the error has to occur during query execution, not fetching phase.
In my case, the monitoring system raised an alert for “ORA-01722: invalid number” in the alert.log file.