Timezone Displayed Incorretly in TOAD

Toad for Oracle
1

TIMESTAMPS are displayed with a strange, incorrect timezone in Toad for Oracle. It has a future offset of +59. So both the time and date are off. On the same PC, the timestamp is correct in SQL*Plus. So, only in Toad it is wrong.
Example:

SELECT SESSIONTIMEZONE, CURRENT_DATE, current_timestamp FROM DUAL;

-05:00	06/20/2023 9:59:36 AM	06/22/2023 8:59:36.182882 PM +59:00

But in SQL*Plus, it is correct ...

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Jun 20 09:06:33 2023
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.16.0.0.0
SQL> SELECT SESSIONTIMEZONE, CURRENT_DATE, current_timestamp FROM DUAL;

SESSIONTIMEZONE          CURRENT_D  CURRENT_TIMESTAMP
-----------------------  ---------- ---------------------------------------------------------------------------
-05:00                   20-JUN-23  20-JUN-23 09.06.57.432535 AM -05:00

This is happening when I query system tables (DBMS_SCHEDULER*), so I dont have the option to refactor table to use "local" timezone

2

This is a known issue when using Toad in no-client mode.

If you configure Toad to use an Oracle client as shown below, timestamps will be displayed as expected.

Note: this box is disabled when a connection is already open in Toad. You can only check/uncheck it when you have no open connections.

image
image718×567 21.3 KB