Recent content by joel

I think I find the issue in our shop... when right clicking on the package in question, the check box appeared next to the "Add Debug Information" line, so I didn't think I needed to "re-add" it. However, without repeating the "Add Debug Information" step, we were hung up as indicated in this...

We are a debugger issue with 11g RAC as well -- we are unable to step into the program.

I am still after my DBA... it only gives us problems on one DB, the other 7 are fine. It would be nice to track down the parameter that is reponsible for the error and increase the allowable size.... that seems like the ultimate solution.

Hello, I understand the message "Program too large" when compling is a database issue, and not a PL/SQL Developer issue. However, I have the "large" package excluded from adding debug info in Preferences - Debugger, in the "Never add debug info for objects" section. This works well, except...

6.0.3.893 1.22130 -- thanks.

I am experiencing a problem with the Preference Sets -- I would like to configure the key configuration based on the database that I am on (to prevent accidentally compiling on the live system). I followed the instructions in the help section, creating a new personal preference , then defining...

The new version is posted the same place where you downloaded v 6.0 registered from.

as per marco: It will be fixed for 6.0.1, which is planned for next week.

Hello, I have been evaluating v. 6.0, and am having a problem with the safe compilation option. In package A, I reference a constant in package B. The constant in package B also shares the name of another package in the same schema, but I reference explicitly (var := pkg_b.constant). When...