When comparing a single object in a 19.0 DB I get the error message "-904 Table or view not found" since the last beta and the combo box "Object Type" remains empty. But in a 12.2 DB it still works.

Thanks Stefan, I see that. Will fix.

The problem is only half solved, the error message no longer appears if version 19 is addressed on the source side, but still on the target side

And if something like this is done in the Object Compare, why is the schema of the source always automatically selected at the target, although another, open connection is selected. It would be better to always choose the logon schema.

Hi Stefan, I see. There was actually a 2nd error in there. We can't query against SYS.ALL_JOBS, it has to be just ALL_JOBS due to some Oracle weirdness. This will be fixed in the next beta. Regarding the selection of the target schema, the idea is that the source and target objects are likely …

SQL-Error when comparing a single object

Toad for Oracle - Beta

JohnDorlon April 2, 2020, 6:11pm 7

This is fixed in the beta 14.0.0.248

Topic		Replies	Views
the compared results show 0 objects exist between different pdb(like source pdb1, target pdb2) and same schema(c##test1) Toad for Oracle & DevOps Toolkit	2	863	October 20, 2017
Comparing Schemas does not work properly Toad for Oracle & DevOps Toolkit	8	1039	August 30, 2010
Beta Released (12.9.0.26) Toad for Oracle - Beta	0	686	February 10, 2016
problem with Database - Compare Schemas Toad for Oracle & DevOps Toolkit	0	291	February 11, 2013
Object compare defaults and display Toad for Oracle - Beta	1	784	December 15, 2017

SQL-Error when comparing a single object

Related topics