Configuring Multi Data Sources with Oracle RAC

4-6 Oracle Fusion Middleware High Availability Guide sqlplus as sysdba 2. Grant select on sys.dba_pending_transactions to the appropriate_user. 3. Grant force any transaction to the appropriate_user.

4.1.3 Configuring Multi Data Sources with Oracle RAC

Oracle Middleware 11g components support only multi data source configuration for Oracle RAC. You can configure multi data sources using the following: ■ Oracle Fusion Middleware Configuration Wizard during WebLogic Server domain creation ■ Oracle Universal Installer Java EE component configuration for Identity Management or Oracle Portal, Forms, Reports, and Discoverer. ■ Oracle WebLogic Server Administration Console ■ WLST Commands Multi data sources support load balancing for both XA and non-XA data sources. This applies to all Oracle database versions Oracle Fusion Middleware components support. Multi data sources encapsulate individual data sources that pool connections to specific instances of Oracle RAC. For multi data sources created manually, or modified after initial configuration, Oracle strongly recommends the following XA and Non-XA data source property values for optimal high availability behavior. If your environment so demands, changes to these should be done after careful consideration and testing: For the individual data sources, Oracle recommends the following for high availability environments. Any other parameters should be set according to application requirements. Note: These privileges should be granted to the owner of the soainfra schema, as determined by the RCU operations. Table 4–1 Recommended Multi Data Source Configuration Property Name Value test-frequency-seconds 5 algorithm-type Load-Balancing Table 4–2 XA Data Source Configuration Property Name Value Driver oracle.jdbc.xa.client.OracleXADataSource Property command property nameoracle.net.CONNECT_ TIMEOUTname value10000value property initial-capacity connection-creation-retry-frequency-seconds 10 Considerations for High Availability Oracle Database Access 4-7 For examples of recommended multi data sources, see Appendix B, Recommended Multi Data Sources. Increasing Transaction Timeout for XA Data Sources If you see WARNING messages in the server logs that include the following exception: javax.transaction.SystemException: Timeout during commit processing [ javax.transaction.SystemException: Timeout during commit processing This may indicate the XA timeout value you have in your setup must be increased. XA timeout can be increased for individual data sources when these warnings appear. To increase this setting, use Oracle WebLogic Server Administration Console: 1. Access the data source configuration.

2. Select the Transaction tab.

3. Set XA Transaction Timeout to a larger value, for example, 300.

test-frequency-seconds 300 test-connections-on-reserve true test-table-name SQL SELECT 1 FROM DUAL seconds-to-trust-an-idle-pool-connection 0 global-transactions-protocol TwoPhaseCommit keep-xa-conn-till-tx-complete true xa-retry-duration-seconds 300 xa-retry-interval-seconds 60 Table 4–3 Non-XA Data Source Configuration Property Name Value Driver oracle.jdbc.OracleDriver Property to set property nameoracle.net.CONNECT_TIMEOUTname value10000value property initial-capacity connection-creation-retry-frequency -seconds 10 test-frequency-seconds 300 test-connections-on-reserve true test-table-name SQL SELECT 1 FROM DUAL seconds-to-trust-an-idle-pool-conne ction global-transactions-protocol None Table 4–2 Cont. XA Data Source Configuration Property Name Value 4-8 Oracle Fusion Middleware High Availability Guide

4. Select the Set XA Transaction Timeout checkbox. You must select this checkbox for

the new XA transaction timeout value to take effect.

5. Click Save.

Repeat this configuration for all individual data sources of an XA multi data source.

4.1.4 Oracle RAC Failover with WebLogic Server