Oracle PL/SQL How to resolve Unable to resolve column 'COLUMNa_NAME' or to not show the error?


Hi, 'im new in Datagrip and PLSQL programming in general (and programming in general too)

I'm writing some code in plsql for an apex application and i get some error in my code even if it runs ok.

The problem is that some columns are not resolved for the IDE, take this example:

Here DataGrip could not find p.line_number and p.COL006 and COL008. p are  wwv_flow_t_parser_row objects that has not been declared in the Declaration section of the procedure.

So i had declared it in the declare section of the procedure (the outermost one in the procedure realm) but the error keep showing.

If i declare the p object it in the declaration section after the loop statement:

errors are gone and the ide is happy again.

So, i'm asking as im still learning:

1) Is correct to declare the p object to get the errors away (the procedure work the same way)

2) Is correct to have to declare them inside the loop and not in the main delcaration section of the procedure to get the errors away?



Could you please provide full procedure code for investigation?



Upload id: 2023_06_22_23hp5eEwZapxL1KgXNmRmW (file: XXX_ V3.sql)

DataGrip 2023.1.2
Build #DB-231.9011.35, built on May 16, 2023
Subscription is active until January 11, 2024.
Runtime version: 17.0.6+10-b829.9 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 8
Non-Bundled Plugins:
    bundled-datagrip-help (231.9011.35)
    Key Promoter X (2023.1.0)




We need WWV_FLOW_T_PARSER_ROW type and apex_data_parser.parse function as well.



Done! Thank you!

Upload id: 2023_06_22_2AuEJ9ZYCoybGuqg5JHq4A (files: apex_data_parse.sql, wwv_flow_t_parser_row.sql)


Thanks for sending these.

I've reviewed the procedure, and it seems like an issue related more to how objects are resolved in IDE, rather than the variable scopes or anything that could be related to the syntax. This has been reported here.

Please follow to stay updated on the progress.


Thanks a lot! i will follow the other thread .I must admit that seeing the DBE-3380 is 7 year old and planned for the 2020.x version and still unresolved, i have a little faith that it will be resolved :) 

EDIT: Sorry i don't know what happened but i get redirected to the wrong ticket! i see the correct one DBE-18426 Object variable highlighted as unresolved if declared in the beginning of procedure in Oracle

I've subscribed to it.

have a nice day



Please sign in to leave a comment.