TOAD : Session Browser TOAD frozen

Toad for Oracle - Beta
1

I connected to database with user STATDSI, I launch Database / Monitor / Session Browser: TOAD is completely frozen. Nothing can be done anymore.

I use Oracle Database 19c patch 19.27 with sqlnet 19.26 X64 client.

TOAD 25.2 patch1 idem, ToadForOracle_Beta_x64_25.3.249.6951 idem.

The user:

CREATE USER STATDSI
IDENTIFIED BY STATDSI
DEFAULT TABLESPACE STATDSI_TRAVAIL
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;

-- 1 Role for STATDSI
GRANT RESOURCE TO STATDSI;
ALTER USER STATDSI DEFAULT ROLE ALL;

-- 3 System Privileges for STATDSI
GRANT CREATE SESSION TO STATDSI;
GRANT SELECT ANY TABLE TO STATDSI;
GRANT UNLIMITED TABLESPACE TO STATDSI;

3

ok, forget my prior reply, if you read it.

I just tried creating your user and then using it to open Session Browser.

Immediately, I get this dialog.

image
image544×109 4.79 KB

I think what has happened is that dialog is behind Toad for you.

To move that dialog to where you can see it, do an ALT+Spacebar on your keyboard, then M, then hold down your right or left arrow key on your keyboard. If this seems weird, try it first on a window that you can see. It doesn't have to be in Toad.

I am not sure why the dialog is not on top of Toad for you, but if you tell me about your monitor configuration, I'll try to reproduce the problem. Our source code seems correct, in that it specifies that this dialog should be on top of session browser.

I noticed that you granted SELECT ANY TABLE to that user. SELECT ANY TABLE is for non-sys/system tables. That is, tables created by others users in their own schemas. SELECT ANY DICTIONARY is the privilege you need for Oracle data dictionary views. I think that's what you meant to set up this user with.

4

When I launch TOAD directly via RDP (full screen), I can see the "Additional privileges required..." window, but if I click the Cancel button, TOAD remains frozen.
When I launch TOAD via Citrix, I don’t see the "Additional privileges required..." window, and TOAD remains frozen.

5

Does the "Alt+Spacebar, M, Arrow Key" trick work with Citrix?

I don't have a way to test Citrix.

6

With TOAD 25.2 patch 1, Yes the "Privileges" window appears, but with TOAD 25.3 beta, the window is not there. After clicking Cancel, TOAD freezes.

7

In my tests, the window appeared again after clicking cancel.

for you, it is likely behind Toad.

Please try the "Alt+Spacebar, M, Arrow Key" trick.

8

I can't find the window behind TOAD. I can't find the key combination to send Alt+Space via Citrix. I’ll see with grants.

9

I'll add some extra code to the next beta so we try a little harder to bring that window to the foreground when it is displayed. What we have now should be enough. I don't know why it is not.

Also, I'll make a change so that dialog is shown only once from Session Browser.

Please let me know if it's fixed next beta.

10

I use TOAD 25.3 25.3.297.7141 with a fresh install. with the user STATDSI, I launch Database / Monitor / Session Browser. I have to clic 3 times on Cancel button. And I can continue to use Toad.

image

With Citrix access, I think that this windows is behind TOAD, at the second Cancel, I have no access to reach Cancel button.

11

Hi Thierry,

Thanks for the update. Sorry you're still having problems.

I just tried the latest beta with STATDSI, and for me, when that dialog appears, I click cancel and the dialog does not come back unless I click the Refresh button (or the F5 key on my keyboard).

I added a "BringToFront" command when that dialog is shown, so I don't understand how it can ever be behind Toad. But I don't have Citrix to test with either. :frowning:

If you can get me a spool sql output, maybe I'll at least be able to determine why you are getting that dialog 3x.

To do that:

  1. Start Toad and make a connection but don't open Session Browser yet
  2. Go to main menu -> Database -> Spool SQL -> Spool to screen
  3. The Spool SQL panel appears at the bottom of Toad. All SQL executed within Toad will be shown there.
  4. Open the Session Browser and Cancel the dialog as needed
  5. Copy/paste the spool sql output here.

Thanks

12

I spool to file.

-- Session: STATDSI@TRDWX.WORLD
-- Timestamp: 16:43:30.035
Select * FROM V$SESSION WHERE 0=1;

-- Elapsed Time: 0,019 seconds
-- Rows fetched: 0

-- Session: STATDSI@TRDWX.WORLD
-- Timestamp: 16:43:30.054
with ps as
(select 1 as inst_id, sid, serial#, qcsid, qcserial#
from v$px_session
where qcserial# is not null)
Select PS.QCSID as parent_session_sid, PS.QCSERIAL# as parent_session_serial, PS.inst_id as parent_session_instid, rawtohex(s.SADDR) as SADDR, s.SID, s.SERIAL#, s.AUDSID, rawtohex(s.PADDR) as PADDR, s.USER#, s.USERNAME, s.COMMAND, s.OWNERID, s.TADDR, s.LOCKWAIT, s.STATUS, s.SERVER, s.SCHEMA#, s.SCHEMANAME, s.OSUSER, s.PROCESS, s.MACHINE, s.PORT, s.TERMINAL, UPPER(s.PROGRAM) PROGRAM, s.TYPE, s.SQL_ADDRESS, s.SQL_HASH_VALUE, s.SQL_ID, s.SQL_CHILD_NUMBER, s.SQL_EXEC_START, s.SQL_EXEC_ID, s.PREV_SQL_ADDR, s.PREV_HASH_VALUE, s.PREV_SQL_ID, s.PREV_CHILD_NUMBER, s.PREV_EXEC_START, s.PREV_EXEC_ID, s.PLSQL_ENTRY_OBJECT_ID, s.PLSQL_ENTRY_SUBPROGRAM_ID, s.PLSQL_OBJECT_ID, s.PLSQL_SUBPROGRAM_ID, s.MODULE, s.MODULE_HASH, substr(s.ACTION, 1, 64) as ACTION, s.ACTION_HASH, s.CLIENT_INFO, s.FIXED_TABLE_SEQUENCE, s.ROW_WAIT_OBJ#, s.ROW_WAIT_FILE#, s.ROW_WAIT_BLOCK#, s.ROW_WAIT_ROW#, s.TOP_LEVEL_CALL#, s.LOGON_TIME, s.LAST_CALL_ET, s.PDML_ENABLED, s.FAILOVER_TYPE, s.FAILOVER_METHOD, s.FAILED_OVER, s.RESOURCE_CONSUMER_GROUP, s.PDML_STATUS, s.PDDL_STATUS, s.PQ_STATUS, s.CURRENT_QUEUE_DURATION, s.CLIENT_IDENTIFIER, s.BLOCKING_SESSION_STATUS, s.BLOCKING_INSTANCE, s.BLOCKING_SESSION, s.FINAL_BLOCKING_SESSION_STATUS, s.FINAL_BLOCKING_INSTANCE, s.FINAL_BLOCKING_SESSION, s.SEQ#, s.EVENT#, s.EVENT, s.P1TEXT, s.P1, s.P1RAW, s.P2TEXT, s.P2, s.P2RAW, s.P3TEXT, s.P3, s.P3RAW, s.WAIT_CLASS_ID, s.WAIT_CLASS#, s.WAIT_CLASS, s.WAIT_TIME, s.SECONDS_IN_WAIT, s.STATE, s.WAIT_TIME_MICRO, s.TIME_REMAINING_MICRO, s.TIME_SINCE_LAST_WAIT_MICRO, s.SERVICE_NAME, s.SQL_TRACE, s.SQL_TRACE_WAITS, s.SQL_TRACE_BINDS, s.SQL_TRACE_PLAN_STATS, s.SES

13

Oh, I see. It looks like your user has been granted SELECT on V$SESSION but not V$PX_SESSION.

I'll fix that too. Thank you.

14

Update: This problem seems to be related to color schemes. See this post.