Posted By: Pavlo To huge package too debug - 03/04/20 10:25 AM
Hello,

in our software we got a package which is used too read/write our standard interface to external software. It has become very large. Now we added some new procedures/functions in it. This caused the PL/SQL-Developer not too show debug information any longer for this package. In Debug all variables are shown as 'not available' If we remove some procedures (with its cursors) the values are shown again in debug. We presume it is caused by to many declared cursors. I hope you understand that we can't send our company software too you too test.
Is there a buffer used for cursors/varable which can be set higher?
Posted By: cct Re: To huge package too debug - 03/04/20 01:37 PM
I had a similar problem many years ago, in a package that did not use cursors.
The simple soltion was to split into smaller packages

Chris
Posted By: vlevi Re: To huge package too debug - 03/05/20 08:25 AM
I have the same problem before.
One of our packages cannot be debugged.
Strangely, this package can be debugged in Oracle 12.
Posted By: Pavlo Re: To huge package too debug - 02/18/22 07:30 AM
Hello,
We rearranged the Package and split it into three Packages (Tool, Read and Write) this is our work around.
© Allround Automations forums