Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Debug .Net Stored Procedures - Extproc process is always shutdown after execution, cannot attach

GeorgDanglMay 27 2015 — edited May 27 2015

I'm unable to remote debug the extproc process for stored .Net procedures I created.

It actually looks like there are two instances of the extproc process on the machine:

1. extproc, this gets spawned when I start the according CLRAgent service, it is kept alive but does not seem to handle CLR processes

2. exproc, this process gets created when a CLR stored procedure is executed and then immediantly terminated after execution. I think this is the actual process I need to attach to, however, I can't since it's self shutting down...

I've tried with both settings for "RecreateAppDomain" in the registry, neithor 0 nor 1 will change the behaviour here.

Is there some other configuration I need to to?

Edit:

I found out that this is only true for requests that come through the ORDS service, if I execute a .Net stored procedure from SQLDeveloper, the extproc process stays alive.

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jun 24 2015
Added on May 27 2015
0 comments
611 views