Recent content by dennisd

We don't have an answer either. We are getting assistance from allaroundautomations now. To address your suggestions, I can use another company's debugger on the same package without problems, so that should cover #1 & #2. The package size isn't a problem. As I said earlier, I CAN run the...

How big is your package? - 3600 lines with whitespace and comments. Are there many comments? - No, there should be more, IMHO. Have you tried to recompile it? - Yes, with the debug info added. Compiles clean. Are there 2 cursors defined that have the same definition? (if yes, could you remove...

My DBA granted another role for the catalog. That allowed us to get into the procedure just once in several tries. We cannot figure out why this would be flaky and not allow us in each time. Ideas?

Yes, that's what I do. I go into the package and right click on the procedure/function and click test. It automatically brings up a test window as you described. I set my parmeters and tell it to step into the package. Thepackage steps through the global variables at the beginning of the package...

I am trying to run the debugger on my PACKAGE but it will only step through the declaration and setting of variables section. Once it gets to the end of the section and the line before the first procedure, it just runs to completion, even if I have breakpoints set in the first procedure. I CAN...

Did you ever get this resolved? I am having the same exact problem.