TOAD 13 Query Standby v$ Unusual Error

I use TOAD to connect to physical standby databases to query dynamic performance views specific to standby operation. I have done this for years using previous versions but now with TOAD 13, I get the following error with each query of a v$ view:

ORA-01435: user does not exist

After hitting OK, the data is returned successfully. There is no indication what user it is looking for. I am connecting with my own account as sysdba which is properly granted IAW standard practices. This error did not occur in previous versions. It is only an annoyance since the query returns data after hitting OK.

TOAD version is x64
Database version is x64 on Solaris 10 SPARC 64bit
Oracle Client version is 11.2 x64 on Windows 10 x64


turn on spool SQL to see if Toad is running any query in the background and erroring on that.

It is performing a set schema before the query:

alter session set current_schema = “<my user>”;

I am logged in “as sysdba” which, of course, sets my schema to SYS, and the first thing TOAD attempts with each query is a set schema to my own user. The set schema is producing an ora-01435 error, “user does not exist”. The user appears to not exist, of course, because the database is only mounted and not open, so the user$ table cannot be referenced for set schema operations. Logging in normally when the database is open does not produce this result because TOAD does not attempt a set schema with each query. If it did, the SYS tables are now visible so that the operation would work if TOAD attempted it.


Thanks for the details. I’ll log it. We should be able to do prevent that. I’ll let you know when it’s fixed.

This should be fixed next beta.