PL/SQL Crashing
- Thread starter Sebastien
- Start date
Stew Stryker
Member³
Nope, but I'm not compiling anything over 1500 lines. Can you quantify "fairly large" for us?
Also, I only "add debug information when compiling" only when required, very sparingly.
Also, I only "add debug information when compiling" only when required, very sparingly.
Stew Stryker
Member³
Just compiled a package that has a 6000 line body without problem.
I just compiled a package body with 3138 lines, without problems.
Can you confirm that the size of the package is the problem? Perhaps by removing comments/whitespace/bits of code before trying to compile.
Also, there is this :
If your package A depends on package B, and package B is invalidated (because it depends on package C which was recompiled), then recompiling package A will try to recompile package B. Now if you do this at the exact same time someone else (or something else, like a job) does something that would cause package B to be recompiled, then you hit a deadlock. One of the two processes will time out, but that takes a few minutes.
Can you confirm that the size of the package is the problem? Perhaps by removing comments/whitespace/bits of code before trying to compile.
Also, there is this :
If your package A depends on package B, and package B is invalidated (because it depends on package C which was recompiled), then recompiling package A will try to recompile package B. Now if you do this at the exact same time someone else (or something else, like a job) does something that would cause package B to be recompiled, then you hit a deadlock. One of the two processes will time out, but that takes a few minutes.
Dezsoe Kados
Member³
I had similar problems with one of the beta releases
Disabling "recovery - save on time interval" made things better (Preferences/Files/Backup/Recovery/Save on time interval).
Disabling "recovery - save on time interval" made things better (Preferences/Files/Backup/Recovery/Save on time interval).
Claus Pedersen
Member³
If a session (for instance a 'normal' database user) is using a package in an un-comitted session, the package is also locked for compilation.
So sessions with long execution time before commit, can also cause this problem.
So sessions with long execution time before commit, can also cause this problem.
If you develop in an environment where there is a risk of compilation locks, you can enable the Program Window preference "Background compilation". Now all compilations occur in a background thread, and in a separate database session. You are now safe from locking the entire IDE, but have increased the chance that you "lock yourself", and you have increased the number of database connections.
Similar threads
- Discussion
