Toad gives ORA-00933 exception after correct a filter expression which has an error in it. It seems Toad doesn’t refresh the WHERE statement, the previous expression remains in the SELECT statement also.
My example was:
It was an ORA-00904 error, because there is no “allapota” column in the table
status=3 and
allapota=0
Here come the ORA-00933 exception, however the expression is valid
status=3 and
allapot=0 and
(teljesitesdatum >= date ‘2013-05-01’ OR kldatum >= date ‘2013-05-01’)
The generated SELECT statement was:
SELECT
…
FROM in_uzlkotes_v
Where
status=3 and
allapota=0
Where
status=3 and
allapot=0 and
(teljesitesdatum >= date ‘2013-05-01’ OR kldatum >= date ‘2013-05-01’)
I tried to reproduce this but it worked just fine for me. Maybe I am not understanding exactly what you did. Could you be more detailed in your steps to
reproduce the problem? Maybe a few screen shots? Thanks.
I send you the screenshots and create scripts offline.
This is also a problem in 11.6 GA 
Thanks, I can reproduce the problem now.
From: drbubo20 [mailto:bounce-urbantamas@beta.toadworld.com]
Sent: Thursday, May 16, 2013 3:59 PM
To: toadoraclebeta@beta.toadworld.com
Subject: RE: [Toad for Oracle - Beta Discussion Forum] Filter dataset
I send you the screenshots and create scripts offline.
Fixed for GA. I am not sure if there will be another beta or not at this point. One workaround is after you receive the 2nd error, click to another view on the LHS, then back to the view you were on. This is not a problem for tables, only views.
