Help - Search - Members - Calendar
Full Version: Same stored procedure but different behaviour in two environments.
Oracle DBA Forums > Oracle > Oracle Forum
harryp
Background information - one test environment, one production environment. Test & Prod both have the same data model, users and roles.

A change was made to an existing stored procedure, applied to test environment for testing, all worked then promoted to production. In production, users are not able to see the changes and it still works in production as though no changes have been applied to stored procedure.

The DBA has checked, the procedure in production does contain the changes, it is the same as the one in test. It has the correct private synonym, execute rights on the procedure for the relevant role. Users are assigned to the relevant roles in prod as they are in test.

Does anyone know what could be the cause or what else I could be checking for?

Thanks
Brian Carr
Execute the stored procedure from SQL Plus and see if its behaving the same. This will rule out your Application, Web caching, etc.

JGarmany
You might want to insure that you promoted it to production correctly, correct schema, grants etc. If the application can't see it there may be a grant missing.
burleson
Hi,

>> In production, users are not able to see the changes and it still works in production as though no changes have been applied to stored procedure.

If the propcedured are pinned with dbms_shared_pool.keep, I woyld unkeep them and re-keep them.

http://www.dba-oracle.com/t_dbms_shared_pool_keep.htm

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.