The algorithm determines the connection request processing for
the multi data source.

You can specify one of the following algorithm types:

Failover

Connection requests are sent to the first data source in the
list; if the request fails, the request is sent to the next data
source in the list, and so forth. The process is repeated until a
valid connection is obtained, or until the end of the list is
reached, in which case an exception is thrown.

Load balancing

The multi data source distributes connection requests evenly to
its member data sources. With this algorithm, the multi data source
also provides failover processing. That is, if a request fails, the
multi data source sends the request to the next data source in the
list until a valid connection is obtained, or until the end of the
list is reached, in which case an exception is thrown.

Enables multiple rows to be "prefetched" (that is, sent from the
server to the client) in one server access.

When an external client accesses a database using JDBC through
WebLogic Server, row prefetching improves performance by fetching
multiple rows from the server to the client in one server access.
WebLogic Server ignores this setting and does not use row
prefetching when the client and WebLogic Server are in the same
JVM.

If row prefetching is enabled, specifies the number of result
set rows to prefetch for a client.

The optimal prefetch size depends on the particulars of the
query. In general, increasing this number will increase
performance, until a particular value is reached. At that point
further increases do not result in any significant performance
increase. Very rarely will increased performance result from
exceeding 100 rows. The default value should be reasonable for most
situations.