Hi John,
Sorry for the late response but I was really busy the last month.
I've checked your workaround with using direct connection, but unfortunately I'll still get the same error with "ORA-01805". I'm using the latest release of TOAD for Oracle.
I've used the following settings:
Hi Juergen,
Unfortunately, this is a problem in our 3rd party Oracle connectivity/access component. They have not been very responsive to this problem. 
I will raise it again with them.
All I can suggest, as a workaround, is don't include the timestamp column when you want to make edits in the grid. I do want to fix this but this workaround is all I can offer for now. In the Schema Browser, the easiest way is to just click "View/Edit Query", then remove the column that you don't want from the SQL. You can even Name it to save it for fast recall later.
-John
Hi!
Is there any update? I have this issue using Toad for Oracle Base (64-bit) 17.0.353.2906
Hi Denis.
I've been working with our 3rd party Oracle access component vendor on multiple timestamp problems. Progress has been slow and this is not resolved yet. But it hasn't been forgotten
-John
Hi John,
Nearing the end of the year I'd like to ask if there is any news on this issue?
As we use Oracle JDBC to connect with our Java application and it works there, what kind of components are you using? I'm also able to select the correct values within the SQL editor in TOAD.
So why is it that big issue to use a standarized SQL statement for the schema browser and maybe design a specialized column for your table view there for TS with TZR ?
Kind regards,
Juergen
Hi Juergen,
We have the week off at Quest. I just peeked in while turning on my PC for something else, but I have time to answer you...
Do you still have the ORA-01805 when editing other columns? Judging from my comments above, I think you can solve that by using Toad without an Oracle client, with this box unchecked (which is not the same as using the "Direct" tab). You can only check/uncheck that box when you don't have any connections made yet in Toad.
Regarding the editing of timestamps with TZR, that one is not fixed. I will open another case about it with our 3rd party vendor after the break. They did fix some other time zone problems recently, but not this one.
-John
Hi John,
Thank you for your quick answer!
I have a registry key for TNS_ADMIN with the location of tnsnames.ora, but TOAD will not use this. Must I create an additional environment variable for this to work?
Have happy holydays and a good and successfully start into 2025!
Kind regards,
Juergen
Hi Juergen
Use an environment variable. Toad will see that
Merry Christmas
John
Hi John,
Thank you! With the environment variable the connection works and the issue with the ORA-01805 then do not happen when edition non Timestamp fields anymore.
Then only the using and editing of region information instead of numeric time zone offset has to be fixed.
The region information ist essential for long ahead time timestamps.
Hi Juergen,
I'm glad that helps. I have raised the TZR issue again in the forum of our Oracle connectivity component.
-John
Looks like it finds TNS for me (Toad for Oracle Xpert Edition 24.2.275.4664) but has issues using the wallet:
connection error
NET: Cannot open file "C:\Program Files\Quest Software\Toad for Oracle 2024 R2"C:\app\product\instantclient\Network\admin"\cwallet.sso". The filename, directory name, or volume label syntax is incorrect
connection error>Items Checked
"C:\app\product\instantclient\network\admin\tnsnames.ora" was located
Probably because of the extra " after admin in the path as the path is correct otherwise not sure if that is a Toad issue (or Toad + our environment).
Is that path specified in your tnsnames.ora file, or in your sqlnet.ora file? Can you share these files with me? (It's ok if you remove all other tnsnames entries and change host name to XXX)
There are no references to wallets in tnsnames (only thing possibly related is (security=(ssl_server_dn_match=no))) but I found the following in sqlnet.ora
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY = "C:\app\product\instantclient\Network\admin")))
I can reproduce the problem with double-quotes around my wallet location in sqlnet.ora. This is a bug and it will be fixed in the next beta.
If I remove the double-quotes, I get a different error in version 24.2, but it works correctly in beta. Are you able to remove the double-quotes and try it in beta?
Good that you have solved it already, but I will have to wait until it is full released and pushed out in our organization.
Any update on the ORA-01805 issue John? We're using the edit data grid query workaround to allow users to modify records in data grids, but basically every table in our database has create/modify date attributes of type TIMESTAMP WITH TIME ZONE, so it's kind of tedious for them to edit the query every time they want to update something. We're using TOAD 11, which I acknowledge is very old, and doesn't allow users to save named data grid queries or connect without an Oracle client. This seems like a good opportunity to lobby my company to upgrade TOAD to the latest version, but I'd like to be sure this issue is resolved before I try that. Which release is targeted to receive this fix and when might we expect to see it? You mentioned this is a 3rd party vendor issue. I think this is something that used to work, and it seems to have broken at some point, possibly when we upgraded our Oracle client to 19c. Is that possible?
Hi Ben,
There are two problems here, and I am not sure which one you are referring to.
Are you using the TZR format and having problems with the timezone changing incorrectly when you edit, or is it just that the ORA-01805 error is thrown when you attempt to edit non-timestamp columns in any table that contains timestamp columns unless you exclude those columns from the SQL?
If the former, I can't give you a date as to when this will be fixed, I'm sorry.
If the latter, you can easily work around this in the latest version, 24.2, by using the option to NOT use an Oracle client (it's ok if you need to leave it installed for other applications).
Please don't just take my word for it though. Download a trial and test it for yourself. If you have problems with that, please let us know (in a separate thread - this one is getting too long!)
-John
Hi John,
The problem is the 2nd you describe - the ORA-01805 error is thrown when you attempt to edit non-timestamp columns in any table that contains timestamp columns unless you exclude those columns from the SQL. Sounds like a justification to upgrade TOAD.
