CodePudding user response:
Just 50 largest connection if the connection pool, database backend is unlikely to reach 200 ~ 300 the number of connections, 11 g of background processes in general, just a few dozen, including 50 largest connection, to an almost, there may be some misunderstandings on set?Is the key to this such extreme cases, the foreground application have slow reaction, or cannot be used, if so, then you may need to adjust the number of connections, and greater may be the database design may not be able to cope with high concurrency, SQL or application needs to be optimized,
CodePudding user response:
Database connection half won't have a problem, is the basic program, see the program to open multiple connections, or connection not normally closed, you can test pressure testCodePudding user response:
select status, schemaname osuser, machine, the program from v $session
Look at the session is what contents
CodePudding user response:
Monitor on the web to see already deployed on the web database link has been capped 50, but from the database to see links are more than 300, then the web has been won't open the background has been submitted to the access database link fault, a few minutes database card deadCodePudding user response: