-
Notifications
You must be signed in to change notification settings - Fork 162
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
Error Msg = ORA-00932: inconsistent datatypes: expected - got CLOB #488
Comments
oracle.properties
|
By the way, how can i use metadata file,i got file by extract-db-metadata, and remove columns which datatype is CLOB in oracle_metadata.json, then i tried
it seems doesn't work, the columns i removed from metadata file still exists in oracle_ontology.ttl and oracle_mapping.obda. What should i do, and how to use it correctly,Thank for your help. |
Hi @hpstory, thanks for reporting this issue. Your last test showed that the serialized DB metadata is not taken into account by the boostrapper, I will create an issue for that. The DISTINCT in the SQL queries are most likely due to the absence of primary keys in some tables. Unfortunately at the moment, we don't have a way to ignore some tables or schemas when doing boostrapping, but there is an issue tracking this feature request (#471). A common trick for avoiding this issue seems to be casting the CLOB into a VARCHAR (using TO_CHAR) in the presence of a DISTINCT. This only works if the string is not too large (4000 characters seem to be the limit). This in principle could be implemented. |
@bcogrel Thank you for your reply, I'm going to replace the contents in output files by code to avoid this issue, look forward to the follow-up progress. |
Description
i try to generate RDF data out of oracle use following commands, but got error in command 3.
because some columns in table which data type is CLOB and get sql syntax error like
Data type cannot be modified. Are there any other ways to deal with CLOB data type, or remove distinct(will it cause other errors?)
Thank for your help.
Actual behavior: [What actually happens]
The following is the error log
Versions
ontop version 4.1.1
The text was updated successfully, but these errors were encountered: