-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
[sqllab] use Oracle will occur exception "ORA-01036" #2534
Comments
Please fix the formatting |
Pretty sure that has nothing to do with Superset and just connectivity with Oracle. Find a connection string that work using only |
@mistercrunch , test.py:
result: |
@xrmx , |
Also in your
then do like what is around here: |
@mistercrunch , test.py test.py result |
I also encountered exactly the same problem, please help the big god to solve.@mistercrunch @xrmx |
Can you try adding |
@mistercrunch Thank you for the reply, I use the 0.17 version, no models folder, but you can modify models.py, I try, thanks again |
@mistercrunch I modified the original Now there is no question, thank you very much! |
@zhangsx9233 , I tried it according you, it's not ok, is there anything else to modify? modify result |
#2572 should help the original issue here, can you try my |
@mistercrunch , Thank you for the reply. I tried the superset 0.17.4 version, It's ok. but there is a little question, you shouldn't select a schema in the left schema drow-down box when excute sql. if you select a schema, you should modify the /superset/models/core.py as below, then it's ok. original It's very good for add the code in the next superset version, thanks again. |
I have the same error as @yixinyiyide , I also upgrade 0.17.4, but still the same thing, I can connect to oracle and I can see the data in a metric, but the SQL lab just won't work properly. Still the same issues.
BTW the connect string is:
|
The fix didn't make 1.7.4 but should be in the next version |
@Saber0517 , I solve this problem by upgrade to 0.17.4. you can try excute sql without select a schema in the left schema drow-down box, if it's ok, then modify the /superset/models/core.py as below. original |
@yixinyiyide Hi bro, thanks for your reply, but I still will wait for official solution |
Notice: this issue has been closed because it has been inactive for 370 days. Feel free to comment and request for this issue to be reopened. |
I have reproduced the issue with at least the latest released version of superset
"version": "0.17.0"
I have checked the issue tracker for the same issue and I haven't found one similar
SQL Lab: Oracle Error (cx_Oracle.DatabaseError) ORA-12505: TNS:listener does not currently know of SID given in connect descriptor #1761 is not solved
@xrmx @mistercrunch
Superset version
0.17.0
Expected results
SQL Lab can query from oracle source
Actual results
SQL Lab use oracle as source, don't connect
Problem decription
Oracle data souce for superset, config the oracle SQLAlchemy URI is "oracle://edw:XXXXXXXXXX@10.216.200.18:1522/orcl" ,
it to slice or dashboard is ok, but in SQL lab, it is not ok.
Steps to reproduce
edit database
SQLAlchemy URI : oracle://edw:XXXXXXXXXX@10.216.200.18:1522/orcl
Test Connection: Seems OK!
design slice
result: ok
SQL lab
query sql: SELECT * FROM WHERE edw.d_mstsc .
result: (cx_Oracle.DatabaseError) ORA-12505: TNS:listener does not currently know of SID given in connect descriptor.
The text was updated successfully, but these errors were encountered: