there's no inherent mechanism -- you'd have to use a user-defined lock or a temporary table or even a SELECT FOR UPDATE on an appropriate row to prevent concurrent execution
what's the reason?
-- mcs
"Peter Jenny" <Pe*********@cedes.com> wrote in message news:c0**********@rex.ip-plus.net...
Hi NG
is it possible to protect a PL/SQL proc / func from running more than one instance simultaenously ?