ORA-00942 Without Compatibility Issue?

[847396730]

Hello!  I have a 10.2 client trying to connect to a 10.2 Oracle geodatabase.  The error received is:

Release of GeoDatabase invalid or out of date. ORA-00942: table/view doesn't exist.

I understand, from online resources, that this is a common error with compatibility issues.  But both client and gdb here are on 10.2. 

I strongly suspect privilege issues, but cannot currently prove or disprove this theory.  I also have a second 10.2 Oracle geodatabase to which this user can connect with no trouble at all.

What should I be looking for?  I cannot ask the DBA to grant frivolous privileges, so SELECT ANY and EXECUTE DBMS* are not an option.  The documentation shows CREATE SESSION is all that a read-only user requires, but there must be more that I'm missing.

One added bit of info: the user can create a Query Layer (10.0) and an ArcSDE Connection File (10.2).  The error is only thrown when attempting a direct connect.

Thank you!

[MarcoBoeringa]

But here's the twist: the SDE user can connect to the production database via any method. Again, this was not true last I posted; something IT changed during this process made it so.

So, again, I am left to strongly suspect permissions as the root issue.  I will post when the resolution appears.

If the SDE user can access the same database from exactly the same client PC, and access the full (ArcMap) geodatabase functionality without issues, than I think you are right and we can exclude an issue with the ArcSDE Repository, and also a possible misconfiguration of the database client on the client PC.

The permission track you are on sounds right, especially in the light of all the other issues related to permissions and roles you highlighted in your last post.

You may find this Help page useful to track down the issue:

User privileges for geodatabases in Oracle

[847396730]

Thank you, both for the thoughtful response and the link.  I examined the link's content when this issue first arose, and our permissions all adhere to its documentation.  Either the documentation is incomplete, or my IT division has done something which negates the granted permission.  If I ever figure out which, I will update.  So far, I am leaning toward the latter...