Shulou(Shulou.com)06/01 Report--

The two jms queue,producer of Weblogic are OSB, which transfers logs to jms queue through the interface pipeline. Consumer is an Oracle DB.

There was no problem at first, but when the concurrency of OSB reached 15W a day, it was found that jms queue was seriously blocked and weblogic consumed a lot of memory. Database IO and CPU high

Through top activity and 10046, it is found that the query columns (with more than 100 million rows) in the table corresponding to consumer are not indexed.

All problems are resolved after creating the index

Top activity-session-dbms_system.set_ev do 10046

A large number of db file scattered read was found through trace, indicating that there are a large number of full table scans.

Discover the problem according to the SQL corresponding to top activity

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.