Setting the webSphereDefaultIsolationLevel custom property (Microsoft SQL Server)
If your database type is Microsoft SQL Server, and you plan to connect to your source database as a JDBC data source in order to migrate the data, the database connection needs to be made at the correct isolation level. Before you start the WSRR upgrade, you must therefore ensure that the isolation level is set to the required value in the WebSphere Application Server administrative console.
Before you begin
About this task
- Specify full details of the source database, including authentication details.
- Specify the Java Naming and Directory Interface (JNDI) name of the JDBC data source for the database, if configured by your database administrator for alternative access. The JDBC data source can be set up either from the WebSphere Application Server administrative console of the target WSRR system, or by using the createSourceJDBCDatasource action of the upgrade command. For information about setting up a JDBC data source from the administrative console, see Configuring a data source using the administrative console.
If you are using the JNDI name to connect to an SQL Server source database, the isolation level, which is configured using the webSphereDefaultIsolationLevel custom property on the WSRR JDBC data source, must be set to a value of 2; that is, JDBC Read committed (or TRANSACTION_READ_COMMITTED).
Procedure
To set the isolation level from the WebSphere Application Server administrative console:
- Log in to the administrative console for your target WSRR system.
- Click .
- In the Data sources pane, click the name of the JDBC data source for the WSRR database.
- Under Additional Properties, click Custom properties.
- Locate, and then click the webSphereDefaultIsolationLevel property to access its details.
- In the Value field, enter a value of 2.
- Click Apply.
- Save your changes to the master configuration, and restart WebSphere Application Server.