Tuning Data Source Connection Pools 10-13
When wrapping is disabled the wrap-types element is false, the following data types are not wrapped:
■
Array
■
Blob
■
Clob
■
NClob
■
Ref
■
SQLXML
■
Struct
■
ParameterMetaData
– No connection testing performed.
■
ResultSetMetaData
– No connection testing performed.
– No result set testing performed.
– No JDBC MT profiling performed.
10.9.1 How to Disable Wrapping
You can use the Administration Console and WLST to disable data type wrapping.
10.9.1.1 Disable Wrapping using the Administration Console
To disable wrapping of JDBC data type objects:
1.
If you have not already done so, in the Change Center of the Administration Console, click Lock Edit.
2. In the Domain Structure tree, expand Services, then select Data Sources.
3.
On the Summary of Data Sources page, click the data source name.
4. Select the Configuration: Connection Pool tab.
5. Scroll down and click Advanced to show the advanced connection pool options.
6. In Wrap Data Types, deselect the checkbox to disable wrapping.
7.
Click Save.
8.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
This change does not take effect immediately—it requires that the data source be redeployed or the server be restarted.
10.9.1.2 Disable Wrapping using WLST
The following is a WLST code snippet to disable data type wrapping: . . .
jdbcSR = createdsname,JDBCSystemResource; theJDBCResource = jdbcSR.getJDBCResource;
poolParams = theJDBCResource.getJDBCConnectionPoolParams; poolParams.setWrapTypesfalse;
. . .
10-14 Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server
This change does not take effect immediately—it requires that the data source be redeployed or the server be restarted.
11
Using WebLogic Server with Oracle RAC 11-1
11
Using WebLogic Server with Oracle RAC
Oracle WebLogic Server provides strong support for Oracle Real Application Clusters RAC features in Oracle Database 11g, minimizing database access time while
allowing transparent access to rich pooling management functions that maximizes both connection performance and availability.
The following sections describe the requirements and configuration tasks for using Oracle Real Application Clusters with WebLogic Server:
■
Section 11.1, Overview of Oracle Real Application Clusters
■
Section 11.2, Software Requirements
■
Section 11.3, JDBC Driver Requirements
■
Section 11.4, Hardware Requirements
■
Section 11.5, Configuration Options in WebLogic Server with Oracle RAC Both Oracle RAC and WebLogic Server are complex systems. To use them together
requires specific configuration on both systems, as well as clustering software and a shared storage solution. This document describes the configuration required at a high
level. For more details about configuring Oracle RAC, your clustering software, your operating system, and your storage solution, see the documentation from the
respective vendors.
11.1 Overview of Oracle Real Application Clusters
Oracle Real Application Clusters Oracle RAC is a software component you can add to a high-availability solution that enables users on multiple machines to access a
single database with increased performance. Oracle RAC comprises two or more Oracle database instances running on two or more clustered machines and accessing a
shared storage device via cluster technology. To support this architecture, the machines that host the database instances are linked by a high-speed interconnect to form the
cluster. The interconnect is a physical network used as a means of communication between the nodes of the cluster. Cluster functionality is provided by the operating
system or compatible third party clustering software.
An Oracle RAC installation appears like a single standard Oracle database and is maintained using the same tools and practices. All the nodes in the cluster execute
transactions against the same database and Oracle RAC coordinates each nodes access to the shared data to maintain consistency and ensure integrity. You can add nodes to
the cluster easily and there is no need to partition data when you add them. This means that you can horizontally scale the database tier as usage and demand grows by
adding Oracle RAC nodes, storage, or both.
