Re: CRS/RAC external-procedure handling

From: Dan Norris <>
Date: Thu, 7 Feb 2008 21:31:00 -0800 (PST)
Message-ID: <>

I haven't done this before, but it should be possible. I think that if you review the whitepaper and instructions on setting up a single-instance database to be managed by Clusterware, that may help. In there, you'll see some "special" setup steps using crs_setperm to set the ownership of a resource (the application VIP) to be a different user (root). I think the same could be done with an alternate listener resource and some other unprivileged user. In that same whitepaper, you'll see instructions on how to set up a listener resource manually which will also be helpful. If you combine the two sets of commands--I think there may be a solution to your issue therein.

The whitepaper is on OTN under the RAC or Clusterware sections. Email me if you don't find it.


  • Original Message ---- From: Greg Norris <> To: ORACLE-L <> Sent: Thursday, February 7, 2008 8:44:29 PM Subject: CRS/RAC external-procedure handling

We're planning to migrate an existing application which requires an external procedure into a recently-created RAC environment on Solaris 10. At this point we've created a separate IPC-only listener on each node to handle extproc calls, and have validated that it allows us to invoke the procedure successfully.

The next thing we'd like to do is get the extproc listener running as a limited OS user, rather than under the oracle account. Can anyone tell me if this is possible when the listener is managed through CRS? We don't mind writing a few scripts, if necessary, but would prefer not to duplicate the CRS monitoring/restart infrastructure.

My apologies if this is rather basic... I'll happily accept a pointer to the FM to R. :) We're still a bit new to the whole CRS/RAC environment, and it's entirely possible that I simply don't know where to look.


"I'm too sexy for my code." - Awk Sed Fred.

Received on Thu Feb 07 2008 - 23:31:00 CST

Original text of this message