|
|
|
|
| Re: Flushing Shared Pool [message #294838 is a reply to message #294827] |
Sat, 19 January 2008 23:53   |
mkbhati
Messages: 93
Registered: February 2007
Location: Mumbai
|
Member |
|
|
Often in oracle world we face certain kind of situation where flushing the shared pool remains only solution. Three times I faced such situations. The application was executing a very large number of dynamically generated SQL statements. the statements were almost identical & differing with only where userid='xxx' or some thing little different
Regards
Manjit Kumar [mkbhati]
|
|
|
|
|
|
| Re: Flushing Shared Pool [message #294887 is a reply to message #294838] |
Sun, 20 January 2008 07:56 |
pablolee
Messages: 2882
Registered: May 2007
Location: Scotland
|
Senior Member |
|
|
| mkbhati wrote on Sun, 20 January 2008 05:53 |
Often in oracle world we face certain kind of situation where flushing the shared pool remains only solution. Three times I faced such situations. The application was executing a very large number of dynamically generated SQL statements. the statements were almost identical & differing with only where userid='xxx' or some thing little different
Regards
Manjit Kumar [mkbhati]
|
Your issue is that you are not using bind variables. Flushing the shared pool is not a solution, re-writing your code to use bind variables is.
[Updated on: Sun, 20 January 2008 07:56] Report message to a moderator |
|
|
|
|
|
| Re: Flushing Shared Pool [message #294927 is a reply to message #294827] |
Sun, 20 January 2008 22:21 |
mkbhati
Messages: 93
Registered: February 2007
Location: Mumbai
|
Member |
|
|
Yes pablolee you are right, the correct solution is to use bind variables. But very often dba's are faced with poorly written application code hijacking Oracle resources & developers claiming that their code is absolutely legal & oracle supports it. Often developers are adamant enough to change their code and blame it on DBA for not handling the server properly. There is a difference between a DBA's perspective & a Developers perspective. Both see oracle from different perspective. This is root of many problems in oracle world. There are many things is oracle world which are legal and permitted but not advisable from performance point of view. The developers which are entry level guys in most cases fails to understand this point and continue to code with bad coding practices. There oracle comes to rescue by providing dba with unconventional facilities of flushing shared pool / buffer cache e.t.c. .
Regards
Manjit Kumar [mkbhati]
|
|
|
|
| Re: Flushing Shared Pool [message #294935 is a reply to message #294924] |
Sun, 20 January 2008 23:20 |
 |
Michel Cadot
Messages: 68684
Registered: March 2007
Location: Nanterre, France, http://...
|
Senior Member
Account Moderator |
|
|
pablolee explained what I meant.
If you are forced to often flush the shared pool then you don't have an Oracle application.
@mkbhati, it is not because you are a feature that you have to use it. You are wrong, Oracle did not provide flushing the shared pool facility for this, he did because in a very ancient version it was useful, it is not now.
If a DBA accepts to do this, he does not make his job. The only answer to this kind of application is: "he does not work". Full stop. He should never mention flushing something.
Regards
Michel
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
