Connection busy means it is probably running 'select *' on that table to get first n rows. Perhaps you have a large table with lot of empty space? that is the most likely scenario,. is that is the case? you can also see this by running 'select * from that_specific_table' in your worksheet, it will be some time before you will get results back.
When I ran the select * statement from the worksheet, the results appeared immediately. I actually can't reproduce the problem at this time. I don't know what cleared the error for the time being.
1 person found this helpful
Well it is likely that all the blocks needed for your db are in the db_cache now, hence instantaneous data back. if you can bounce the db and try again. However if there is a bug, then all bets are off. I have seen similar behavior on large tables with lot deleted rows on v3 and v4. it just could be your case too.
just to be complete. It has nothing to do with large tables. This is happening to me every day on many tables even on tables with constant data. This is a bug which was introduced in one of EA release of version 3 and it still seems not to be fixed.