The procedure may exist in that schema but you may not have privileges to execute it, or you may have privileges through a role that isn't enabled Could be parameters. If the procedure expects two parameters (or is a function) then trying to call it with one can get a "Doesn't exist" error when it really means "There isn't one I can call with just one parameter Final option is if you have a package in your schema with the same name as the other schema. Can happen with something generic like 'UTILS'.
If you ask Oracle to execute UTILS. PROC and you have a UTILS package, then it will look in the package and throw an error if it doesn't find it, even if there is a UTILS schema with a procedure PROC Edited to add In that case, I'm leaning towards a parameters issue The example here seems to use? As the parameter placeholder.
The procedure may exist in that schema but you may not have privileges to execute it, or you may have privileges through a role that isn't enabled. Could be parameters. If the procedure expects two parameters (or is a function) then trying to call it with one can get a "Doesn't exist" error when it really means "There isn't one I can call with just one parameter".
Final option is if you have a package in your schema with the same name as the other schema. Can happen with something generic like 'UTILS'. If you ask Oracle to execute UTILS.
PROC and you have a UTILS package, then it will look in the package and throw an error if it doesn't find it, even if there is a UTILS schema with a procedure PROC. Edited to add In that case, I'm leaning towards a parameters issue The example here seems to use? As the parameter placeholder.
I can do "exec schem1. My_sproc(:p1)" in sqldeveloper without any errors so this should not be a privileges thing (by using the same login). And there are no packages involved in this.
– Niner Jul 27 '10 at 2:49.
I could be mistaken here, but I thought that Nbernate requires all UDFs/SPROCS to be prefixed with "dbo"; does {call dbo. Schema2. My_sproc (:p1)} work?
The procedure may exist in that schema but you may not have privileges to execute it, or you may have privileges through a role that isn't enabled. Could be parameters. If the procedure expects two parameters (or is a function) then trying to call it with one can get a "Doesn't exist" error when it really means "There isn't one I can call with just one parameter".
Final option is if you have a package in your schema with the same name as the other schema. Can happen with something generic like 'UTILS'. If you ask Oracle to execute UTILS.
PROC and you have a UTILS package, then it will look in the package and throw an error if it doesn't find it, even if there is a UTILS schema with a procedure PROC. The example here seems to use? As the parameter placeholder.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.