Toad for Oracle 2026 R1 Session Browser windows opening or refreshing Sessions tab takes too long

Hi,

I am using Toad for Oracle 2026 R1 DBA Suite. Session browser window is painful while opening it or refreshing Sessions tab when it is opened already. When I spool SQL while refreshing the Sessions tab, I saw it trying to get all objects from dba_objects with object_id in clause for thousands of objects and it blocks UI and takes too long to respond. With same Toad version and same database, my friend does not observe this problem. And also I do not see such this behavior for different database with same Toad version. What can cause this?

Thanks.

Toad for Oracle DBA Edition (64-bit)
Add-Ons: DB Admin Module
26.1.193.8012

Captured query:

-- Timestamp: 11:01:44.876
select object_id, owner, object_name, object_type
from sys.dba_objects
where object_id in (1073072,1089455,1053303,1073072,1073072,1073072,3571172,1088928,2509219,3580301,3336554,93160,93199,93160,1073072,193453,93160,93160,1073072,……….

-- ORA-01795: maximum number of expressions in a list is 1000
Help: ORA-01795 - Database Error Messages

That is something that I added recently.

When the main sessions grid is loading, Toad gets the Object ID's from the ROW_WAIT_OBJ# field. These represent objects with Locks.

Immediately after that, we put them in the SQL that you are seeing to determine the names of those objects. I didn't expect so many. I see in the small sample that you provided, that some of the same numbers are being repeated, so I need to at a minimum, weed out the duplicated, but also keep it below 1000...

To get around it, choose one of the filters in this dropdown so that the Session Browser does not show so many rows. You might want to see what your coworker has enabled here.

I will fix this for next beta.

Hi John,

Yes, they are duplicated. There are 15K object ids but 621 distinct object id there are.

Until it is fixed, I think I will use previous version.

Thank you.

Next beta, that SQL won't run at all unless you make the "Lock Info" column visible, or hover your mouse over a lock or circle/slash icon. And even then we will run the SQL only for the object ID that needs to be shown....AND we'll remember the object name for each object ID as long as Session Browser is open on that connection. So it will only query for any particular object id once. It should be much faster.

That sounds good.

By the way, is it possible to set a custom filter for Session Browser at opening?

Until it is fixed, may be this kind of custom filter or “STATUS - ACTIVE“ filter can be set while opening Session Browser. Is there any option to make this happen?

Yes, look at my screen shot - whichever filter you choose there will be used by default until you choose something different.

Yes it works! Thank you John

You're welcome. Are you referring to the beta released yesterday (which you can get here) or choosing a filter?

Hi John,

I meant choosing custom filter but I have just tested newly release beta, same problem seems to continue.

I just tested this in the beta and confirmed that we aren't running that SQL at all anymore, unless one of these happens
a) you hover your mouse over a lock or circle/slash icon
b) The 'lock details' column is visible in the main grid, and it contains data

But...even if we run the SQL now, it will be of the form:

select owner, object_name, object_type
from sys.DBA_OBJECTS
where object_id = :ObjID;

...with no 'In' list, so the prior error should not happen anymore. The query above only runs once as each object name is displayed for the first time. After that it is cached.

The beta version is intended to be installed as a separate product, not to replace your official Toad version. The beta version will have the word BETA in the title bar like this

If you are still seeing an error in beta, can you do the following for me?

  1. Close Session Browser
  2. In the main menu, click Database -> Spool SQL -> Spool to screen
  3. Open Session Browser so error happens again
  4. Post the spool sql output or email it to john.dorlon@quest.com if you don't want to post it here.

Thanks

Incase anyone else is following this, Samet had over 20,000 sessions in his database. The query to dba_objects was one problem, and another was that the Session Browser took several minutes to load or refresh if one of the columns in the Session Browser was sorted. You can CTRL+Click on a column header to remove the sort. This helps a lot but it still takes about 20 seconds to load 30,000 sessions (this is what I was testing with)

Both problems will be fixed in Monday's beta (to be released 6-April-2026). After the changes, Session Browser can load 30,000 sessions in about 10 seconds, with or without column header sorting.

Hi John,

I have tested the last beta(26.2.93.8391), it works well.

Thank you for your support and quick solution.

Regards

Hi Samet,

You're welcome. Thanks for reporting the problem and following up.

-John