This blog post is designed to help you if you receive the “SQL Developer Connection Busy” error code.
Recommended
Why is my tmsconnection busy with results for another command?
If FetchAll = False, executing such requests will fill the current session. To avoid blocking, OLEDB creates additional appointments, which can cause the “Connection is usually busy with results for one team” error. To solve the problem in this case, you need to set our TMSConnection.Options.MultipleActiveResultSets property to True.
So you are a self-employed person making an effort and you are clicking on your successful Oracle Database IDE. Are you getting what you asked for? Not! Instead, you will be rewarded for interfering with this confusing and annoying message.