Check to see whether you have an object named the same as the owner of the procedure. When this is the case, Oracle thinks that the user name in the anonymous block is actually the object name. We recommend either renaming the problematic object or manually removing the user name from the anonymous block in the Set Parameters window.
Related Articles
Quest® Toad® Data Point 5.6 supports Snowflake
On December 6, Quest® announced the general availability of Toad® Data Point 5.6 with native support for Snowflake. This makes a significant contribution to the plethora of other platforms that Toad D...
An Easy Way to Sync Data Without Sinking in Queries
We have all been there. We start making changes to data inside a table either manually or by running one or a series of queries, only to find out that we messed part of it up. We know we have our orig...
How to Rock Using BPMN
Why BPMN? As you know, a requirements document us not just about new functionality. I'm sure you're familiar with non-functional requirements like performance and usability; however, there's another k...