Solaris clustered server: Changing Oracle or Oracle RAC driver types

IBM® WebSphere® Portal requires the use of either Oracle JDBC Type 4 drivers or JDBC OCI Type 2 drivers when connecting to Oracle or Oracle RAC. You may need to change driver types after a migration. Direct migration from a previous installation of WebSphere Portal using JDBC Type 4 drivers to an installation using JDBC OCI Type 2 drivers is not supported. To migrate from a previous version of WebSphere Portal using JDBC Type 4 drivers, the target system must use JDBC Type 4 drivers. Once migration is complete, you can continue using JDBC Type 4 drivers or change the driver type to JDBC OCI Type 2 drivers as appropriate.

Before you begin

Before you begin, ensure that the following conditions are met:

You have completed one of the following goals:
- You have successfully transferred your data to Oracle or Oracle RAC using the database-transfer configuration task.
- The WebSphere Portal migration has been successfully transferred to Oracle or Oracle RAC using the Type 4 JDBC driver.

The files wkplc_dbdomain.properties and wkplc_dbtype.properties have been modified to set the correct values for the Oracle drivers that you are switching to:

Note: The value for service_name in the database URL is the same value used for the service name value in the tnsnames.ora file on your Oracle database.

In the file wkplc_dbdomain.properties set each domain.DbUrl property using the following formats:

Note: The value for service_name in the database URL is the same value used for the service name value in the tnsnames.ora file on your Oracle database.

Table 1. Format for `domain`.DbUrl
Database	Format for `domain`.DbUrl
Oracle (JDBC OCI Type 2)	`jdbc:oracle:oci:@//YourDatabaseServer:1521/service_name`
Oracle (JDBC Type 4)	`jdbc:oracle:thin:@YourDatabaseServer:1521:service_name`
Oracle RAC (JDBC OCI Type 2)	`jdbc:oracle:oci:@//NODE_HOSTNAME:1521/NODE_INSTANCENAME`
Oracle RAC (JDBC Type 4)	`jdbc:oracle:thin:@NODE_HOSTNAME:1521:NODE_INSTANCENAME`

Prerequisites: Solaris clustered server: Installing Oracle or Oracle RAC; Solaris clustered server: Modifying Oracle or Oracle RAC database properties; Solaris clustered server: Creating Oracle or Oracle RAC databases; Solaris clustered server: Setting up Oracle or Oracle RAC automatically or manually; Solaris clustered server: Configuring Portal to use Oracle or Oracle RAC

Procedure

Open a command prompt and change to the directory wp_profile_root/ConfigEngine.
Enter the ./ConfigEngine.sh validate-database command to validate configuration properties.
From the same command prompt as the previous steps, change to the directory wp_profile_root/bin.
Stop the WebSphere_Portal server:
- ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
Change to the directory wp_profile_root/ConfigEngine.

To change from one supported driver to the other, run the following task to connect the database, including only the domains that require the switch.

./ConfigEngine.sh connect-database -Drelease.DbPassword=password
 -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password
 -Djcr.DbPassword=password -Dfeedback.DbPassword=password
 -Dlikeminds.DbPassword=password
-DWasPassword=password

Change to the directory wp_profile_root/bin.
Start the WebSphere Portal server. See Starting and stopping servers, deployment managers, and node agents for instructions.