-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
cx_Oracle.DatabaseError: ORA-00942: table or view does not exist #5784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Milestone
Comments
Note that this bug is reported in #5783 |
Mike Bayer has proposed a fix for this issue in the master branch: Gracefully degrade on v$transaction not readable https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/2421 |
Mike Bayer has proposed a fix for this issue in the rel_1_3 branch: Gracefully degrade on v$transaction not readable https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/2422 |
sqlalchemy-bot
pushed a commit
that referenced
this issue
Dec 18, 2020
Fixed regression which occured due to [ticket:5755] which implemented isolation level support for Oracle. It has been reported that many Oracle accounts don't actually have permission to query the ``v$transaction`` view so this feature has been altered to gracefully fallback when it fails upon database connect, where the dialect will assume "READ COMMITTED" is the default isolation level as was the case prior to SQLAlchemy 1.3.21. However, explicit use of the :meth:`_engine.Connection.get_isolation_level` method must now necessarily raise an exception, as Oracle databases with this restriction explicitly disallow the user from reading the current isolation level. Fixes: #5784 Change-Id: Iefc82928744f3c944c18ae8000eb3c9e52e523bc (cherry picked from commit 566f1b5)
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
After upgrading from
1.3.20
to1.3.21
I get the following exception upon establishing a connection:cx_Oracle.DatabaseError: ORA-00942: table or view does not exist
Expected behavior
No exception, as in the previous version.
To Reproduce
Error
Versions.
The text was updated successfully, but these errors were encountered: