OK, I get it, Oracle consults DUAL in the drop process. And don't go messing up a database of any importance. But it is odd how the fact that I was succeeding to mess things up was hidden from me. Yes it told me that I had inserted the row, but then it didn't display it with a select. It was an interesting bit of play.

10 comments:

I had a DBA in the 90's in an Oracle V6 database run the data dictionary catalog script by accident a second time. The catalog script created the DUAL table and inserted one row into it. The create failed, but the insert succeeded. We ended up with two rows in the DUAL table. Our applications were all SQL*Forms V2. The logic for each trigger step in the forms was SELECT ... FROM DUAL branch on success or branch on failure. You talk about getting a lot calls from users all at once.

Very helpful post you have provided here. I have not faced this problem so far but after knowing the problem and its recommended solution I will remember this point and take care of it. Thanks for sharing it.sap upgrade evaluation