Skip to content
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

Row validation of Oracle LOB columns causes ORA-00932 exception #1364

Open
nj1973 opened this issue Dec 4, 2024 · 0 comments
Open

Row validation of Oracle LOB columns causes ORA-00932 exception #1364

nj1973 opened this issue Dec 4, 2024 · 0 comments
Labels
priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@nj1973
Copy link
Contributor

nj1973 commented Dec 4, 2024

Examples:

data-validation validate row -sc=ora -tc=pg -tbls=pso_data_validator.dvt_ora2pg_types --concat="id,col_clob"
...
sqlalchemy.exc.DatabaseError: (cx_Oracle.DatabaseError) ORA-00932: inconsistent datatypes: expected CLOB got CHAR

data-validation validate row -sc=ora -tc=pg -tbls=pso_data_validator.dvt_ora2pg_types --concat="id,col_blob"
...
sqlalchemy.exc.DatabaseError: (cx_Oracle.DatabaseError) ORA-00932: inconsistent datatypes: expected - got BLOB

Same issue for col_nclob, col_json, col_jsonb.

We need to decide how these columns are best validated. For aggregations we use the length, perhaps we do the same for row validations?

We'll need the raw Oracle data types to differentiate between CLOB vs VARCHAR and BLOB vs RAW.

Search for "issue-1364" in test_oracle.py to enable test columns.

@helensilva14 helensilva14 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) labels Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants