Datagrip hangs introspecting oracle schema Follow
My Oracle 11g XE database runs in docker. I created a new schema (OE which is a sample schema of Oracle). But, DataGrip hangs forever with "Introspecting database: major object names".
P.S. DataGrip can introspect schemas that were in database by default.
Build #DB-172.4155.28, built on September 6, 2017
Licensed to Rustam Ibragimov
Subscription is active until November 1, 2017
For educational use only.
JRE: 1.8.0_152-release-915-b11 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.6
Please sign in to leave a comment.
I have the same issue as Rustam. I'm able to perform normal selects to the tables in my schema, but IDEA is not able to retrieve the names of the schema objects, and the table/column names are not available for auto-completion. Using a completely different client (DbVisualizer), I'm able to browse the schema objects using the same user credentials, so I don't believe I have a problem with permissions or port mappings.
Here's my IDEA info:
When I create a connection to my Oracle 11g XE running in Docker, I get the same progress task that Rustam reported, stating: "Introspecting database: Major object names". The idea.log has the following at this point:
After waiting for >10 minutes with no change in progress, I stopped the introspection task, but this had no effect. Next, I deleted the connection. After deleting the connection, the idea.log shows the following...
Can you attach any IDE logs? In case, if there are some freeze log it would be great to get'em too.
Could you email zipped IDE log folder to me firstname.lastname@example.org?
I have had an issue too with the introspection hanging - particularly while trying to get synonyms on two schemas + public. When it did complete, it would take hours.
The issue appears to be with the SQL used to obtain the synonyms. There is an IN clause specifying the schemas. When there is only one schema specified, the query takes seconds to execute. When there are two or more, the required time to execute increases exponentially. Changing the query to use a UNION (or UNION ALL) - one select for each schema - brings the execution time back down to seconds (or minutes).
I am using IDEA 2019 and IDEA 2020.
(With Oracle as our DBMS)