Problem with 2025r1 with Data Guard Standby

Toad for Oracle & DevOps Toolkit
1

This new version of Toad has reverted to an older version's behavior when connecting to a Data Guard standby database that is only mounted. 2025r1 is presenting error dialogs twice when making such connections with the following Oracle error:

ORA-01219: database or pluggable database not open: queries allowed on fixed tables or views only

These dialogs are suppressed in 17.0.

When executing SQL in Editor, an error dialog with the following error always appears when hitting F9:

ORA-01435: user does not exist

The above error appears once when the query of a dynamic view is made but then the output is displayed after closing the dialog. It appears twice when hitting F5, and then the queries are not run. After that, F5 appears to be broken even in a new tab until a new Editor is opened where the cycle repeats. F9 still works (still with the transient error) after F5 breaks an Editor.

These are SYSDBA sessions. Toad is being run on a Windows Server 2016 VDI which has been used with Toad for several years now without issue.

I would like to return Toad's behavior to what it did in version 17.0, which is the previous version we have used in our VDIs. (We still have it installed.)

I would greatly appreciate any help you folks could provide as I have been looking forward to getting this version into the VDI. But, this is a deal-breaker for us so that we will have to go on using 17.0.

I cannot try this outside the VDI because none of the databases that are accessible directly from my Windows 10 workstation are running in Data Guard.

Cheers,
Russ

2

Thanks Russ.

I can reproduce this....luckily with just a plain old database that's mounted and not opened, so I don't have to mess with data guard.

I will take care of it for Toad version 2025R2 which is due out next month.

This was inadvertently broken when we added support for Oracle 23's VECTOR datatype.

3

Thank you so much John. I had been looking forward to 25.1 as the version of Toad we would offer in all our environments, but we had to hold off on that. I look forward to the .2 release.

I could not have done the plain mounted thing because we cannot close any of the local databases.

Thanks,
Russ

4

Well, I'm sorry I broke it. It was definitely me.

I have to say, your timing is very good. If you had reported this a week later, it would have been too late to fix for 2025R2.

It will be fixed in Monday's beta, so if you can use that, you:

a) won't have to wait as long, and
b) can double-check my work

-John

1 Like
5

We are not usually allowed to use betas, but I may be able to get one in provisionally.

Cheers,
Russ