oracle / oracle/python-oracledb
ValueError: None is not a valid TransactionPriority with version 26.0.0
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 451
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm using Robot Framework DatabaseLibrary with oracledb driver, oracledb was updated to 26.0.0 and it started getting this error.
Note that below analysis was done with Copilot.
Problem
When establishing a connection in thin mode (default) against a database version that does not support the new Transaction Priority feature (or when the server handshake returns None for transaction priority), oracledb.connect() fails with:
ValueError: None is not a valid TransactionPriority
Details
- What versions are you using?
26.0.0
Give your Oracle Database version, e.g.:
19.28 (should be applicable to 19c or older / pre-23.26.2)
Give your Oracle Client version (if you are using Thick mode):
I'm using thin mode
Python 3.11 Linux 64
-
Is it an error or a hang or a crash?
Error -
What error(s) or behavior you are seeing?
Traceback (most recent call last):
File ".../test.py", line 4, in <module>
conn = oracledb.connect(
File ".../oracledb/connection.py", line ..., in connect
...
ValueError: None is not a valid TransactionPriority
- Does your application call init_oracle_client()?
I'm using thin mode
This tells us whether you are using the python-oracledb Thin or Thick mode.
Thin mode
- Include a runnable Python script that shows the problem.
import oracledb
conn = oracledb.connect(
user="my_user",
password="my_password",
host="my_db_host",
port=1521,
service_name="my_service_name", # or sid="my_sid"
)
print("Connected:", conn.version)
conn.close()
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the oracledb.connect entry point and the connection.py location shown in the traceback. Reproduce the failure with the provided Python script in thin mode against the stated database versions, then verify that a server returning None for transaction priority can connect without raising ValueError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100