1Z0-052 · Question #194
Your database instance is currently configured to support 1,500 connections. The Web application that uses the database allows a large number of users to work with the database simultaneously. Some…
The correct answer is B. You would configure the database in shared server mode to use the connection pooling feature. Oracle shared server mode uses connection pooling so that many idle web users can share a limited pool of server processes, enabling the database to support far more simultaneous sessions.
Question
Your database instance is currently configured to support 1,500 connections. The Web application that uses the database allows a large number of users to work with the database simultaneously. Some users of the Web application do not interact with the server all the time. You want to increase the scalability by configuring the database instance to handle more connections. As a DBA, which configuration would you set to support more than 1,500 connections at a time?
Options
- AYou would configure more listeners for the database.
- BYou would configure the database in shared server mode to use the connection pooling feature.
- CYou would increase the value of the PGA_AGGREGATE_TARGET initialization parameter that assigns
- DYou would decrease the value of the PRIVATE_SGA resource limit in the profiles used by the users to
How the community answered
(29 responses)- A7% (2)
- B76% (22)
- C3% (1)
- D14% (4)
Why each option
Oracle shared server mode uses connection pooling so that many idle web users can share a limited pool of server processes, enabling the database to support far more simultaneous sessions.
Additional listeners only control how incoming network connections are routed and load-balanced across listener endpoints; they do not increase the number of server processes or total connections the instance can sustain.
In shared server mode, user sessions are decoupled from dedicated server processes via dispatchers and a pool of shared server processes; when a user session is idle, the server process is released back to the pool and can serve another session, allowing thousands of concurrent connections well beyond the 1,500 dedicated-server limit.
PGA_AGGREGATE_TARGET sets the aggregate memory target for PGA allocations used by server processes for sorting and hashing; it has no effect on the maximum number of concurrent connections.
Decreasing the PRIVATE_SGA resource limit in a user profile reduces the SGA memory a session can consume, but does not increase the instance's capacity to handle more connections.
Concept tested: Oracle shared server mode connection pooling scalability
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-processes.html
Topics
Community Discussion
No community discussion yet for this question.