Print Thread
To huge package too debug
#61201 03/04/20 10:25 AM
Joined: May 2007
Posts: 19
Bremen, Germany
P
Pavlo Offline OP
Member
OP Offline
Member
P
Joined: May 2007
Posts: 19
Bremen, Germany
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?

Re: To huge package too debug
Pavlo #61202 03/04/20 01:37 PM
Joined: Jan 2015
Posts: 89
Cambridge, UK
C
cct Offline
Member
Offline
Member
C
Joined: Jan 2015
Posts: 89
Cambridge, UK
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

Re: To huge package too debug
cct #61207 03/05/20 08:25 AM
Joined: Mar 2004
Posts: 166
V
Member
Offline
Member
V
Joined: Mar 2004
Posts: 166
I have the same problem before.
One of our packages cannot be debugged.
Strangely, this package can be debugged in Oracle 12.

Re: To huge package too debug
Pavlo #63348 02/18/22 07:30 AM
Joined: May 2007
Posts: 19
Bremen, Germany
P
Pavlo Offline OP
Member
OP Offline
Member
P
Joined: May 2007
Posts: 19
Bremen, Germany
Hello,
We rearranged the Package and split it into three Packages (Tool, Read and Write) this is our work around.


Moderated by  support 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.4
(Release build 20200307)
Responsive Width:

PHP: 7.1.33 Page Time: 0.031s Queries: 15 (0.008s) Memory: 2.5083 MB (Peak: 3.0380 MB) Data Comp: Off Server Time: 2024-05-02 02:59:30 UTC
Valid HTML 5 and Valid CSS