How can I see the actual error after submitting the procedure (Ctrl+K)?

I'm going to post my own example here.

Version info:

DataGrip 2026.1.2

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.30.0.0.0

Background:

When composing an Oracle procedure, DataGrip will highlight some errors, but not necessarily all. For example, it can't highlight ORA-01031 (insufficient privileges) if it doesn't know about the privileges.

In a case where the proc looks fine to DataGrip but has errors like these, compiling it will result in output like this:

• Green checkmark in query console.
• Oracle errors in output console.
• Red underline in db explorer due to object state (invalid)
• No errors highlighted in code in query console.

When I open the procedure directly, there are also no errors highlighted:

My understanding of this scenario is that basically DataGrip is not aware of the errors either because the errors don't fall in the scope of detection, or it doesn't have enough introspection info. 

However, Oracle provides detailed error info in its catalogs.

I would like to see DataGrip use this info to highlight errors within the editor. It would make DataGrip much more useful as an Oracle IDE.

It's not so much that it's missing, but it would be nice if the IDE was able to retrieve the compile errors from the database and highlight them in the editor, so this is really more of a feature request. I still keep Oracle's SQL Developer around to work on more complex procedures, because it does provide this function, like so:

In this example, SQL Developer also did not highlight my error while I was composing, because it was either unaware of the error or didn't check for it. But once I saved/compiled, it introspected the errors and then displayed them.

And the basic idea is that regardless of what the IDE is or isn't able to detect based on syntax checking and introspection data, Oracle's error data itself could be directly introspected from the database (from SYS.USER_ERRORS), and those errors could theoretically be highlighted within the IDE. And I should mention that with a feature like this, it would be important to actually retrieve the info from the database instead of relying on the errors returned when saving the procedure, so that the error info could be available even when you're just viewing the procedure, and not just after saving it.

Thanks for taking the time to read this.

I apologize for my delayed response.

I will describe the case I mentioned:

Here, I already had a valid stored procedure. 

During the coding process, some lines might have been missing, causing errors that I was not aware of, or there might have been some invalid syntax (like below, variable b_loi VARCHAR2(200) now change to b_loi VARCHAR2) .

 However, when I used Submit (using Ctrl + K with the default setting), my code was still submitted without showing any errors. As a result, I did not realize there was an issue until I executed the query below, and only then did I discover the error.

 

My version info:

DataGrip 2026.1.2

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.17.0.0.0

Thanks, and yes I see that now. I will just follow that issue.