Forum Stats

  • 3,728,151 Users
  • 2,245,559 Discussions
  • 7,853,353 Comments

Discussions

Stored Procedures don't work

User_YEB0V
User_YEB0V Member Posts: 1 Green Ribbon

Hello, everyone! I stucked with porblem. When I try to compile any stored procedure in SQL Developer, my ScriptRunner Task works without break and that's all. It doesn't show any error. What should I do?


Answers

  • Günter
    Günter Member Posts: 99 Bronze Badge

    If your stored procedures are huge maybe a Java heap space problem ?

  • Billy Verreynne
    Billy Verreynne Member Posts: 28,175 Red Diamond

    Recompiling a stored proc requires an exclusive lock on the meta data object for the stored proc. Sessions using and executing a stored proc, or objects with dependencies on that stored proc, place a shared lock on the stored proc meta data object. This is to prevent runtime issues and errors to occur by changing the code of an in-use stored proc.

    Thus a recompile session call can wait for an extended time for obtaining an exclusive lock for changing the stored proc.

    thatJeffSmith-Oraclejnp1234L. Fernigrini
  • jflack
    jflack Member Posts: 1,449 Gold Badge

    So, if your database is busy, and your procedures are being used a lot, let me suggest that you use edition-based redefinition to make your changes.

Sign In or Register to comment.