You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Debug large proc/package

edited Oct 7, 2026 1:11AM in Database 2 comments

Hi Team,


We recently faced an issue after migrating an APEX application from DEV to UAT. The APEX page was not working as expected, and finally we found that the issue was related to the wallet location/path, which was different in DEV and UAT.


This made me think about the best way to troubleshoot such issues when a package/procedure has hundreds of lines of code.


We have two scenarios:


If we have backend database access:


If we can execute the procedure/package manually using SQL*Plus or SQL Developer, what is the best way to identify the exact line or section where the issue is occurring, without manually debugging all the lines?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!