Corrupt Statement In Shared Pool???

Recently, we had a production issue in a 7.3.4.4 instance (uptime about 5 months) where a specific SQL statement would "hang" from a PowerBuilder application. The SQL statement run from SQLPlus without problems. The same SQL statement from could be executed in TOAD or SQL Navigator. Digging further, it was determined that the PB application uses bind variables, which may contribute to the SQL statement hanging.

The application team wanted the database bounced, but several hundred users were connected and about 20 active. I did flush the shared pool, following the "impacted" users disconnecting. Still, the PB application was hanging.

Well, after decision makers approved the instance bounce, the application team is claiming success in solving the problem. For me, that just proves that the symptom may have been temporarily solved. I am certain it will return again.

Has anyone experienced an issue like I describe?

Is there any documentation regarding an Oracle bug?

Can the shared_pool become corrupt? If so, how can we monitor it? Does PowerBuilder have any documentation regarding this type of a problem?

I'm really looking to find the root cause of this problem, rather than solve by "bouncing" instance.

Steve Siebenaler
Cincinnati, Ohio Received on Mon Feb 17 2003 - 18:53:27 CST