Help: How should I live with 'literal' application

From: <emdproduction_at_hotmail.com>
Date: 8 Dec 2006 18:20:54 -0800
Message-ID: <1165630854.538077.232230@73g2000cwn.googlegroups.com>

Dear Group,

I have a Oracle 9206 database.

Our application is a third party software. For a recently new added module, it uses a lot of hard coded 'literal' value in their SQL statement. (It sucks, I know). This new module puts a lot of stress on our database, slow the database down on very large scale. Asking the vendor to change their code is not an option. My only choice is to live the best out of it.

While I am doing some research, this cursor_sharing seems to be able to solve our problem. But I also noticed some poster was complaining that after setting cursor_sharing = similar, a lot of their execution plan changed, and a lot of weird things happened.

What I have is a mission critical database, I do not have the luxury of setting "cursor_sharing = similar" and testing.

I would like your comment on this situation and any suggestion on the instance tuning to accomdate this memory hungry application will be highly appreciated. Received on Fri Dec 08 2006 - 20:20:54 CST