Search Tips   |   Advanced Search

AIX stand-alone: Configure Portal to use Oracle or Oracle RAC


By default, open_cursors is set to 1500. You may need to increase this value based on the table count in the Java Content Repository schema.

With Oracle RAC, WebSphere Portal server must explicitly connect to one RAC node during database transfer. Specify the information of one Oracle RAC node as if it is the only database server.

For example, the Oracle database URL should look like the following:

When database transfer is completed, the WebSphere Portal server will be configured to use this single database server.

When doing a single database, single user, and multi schema database transfer, there can be only one user for each domain (release, community, customization, JCR, Feedback, and LikeMinds), and the schema for each database must be different. The user must be a superuser or DBA and must have authority over all other schemas for the transfer to work.

Configure Portal to use Oracle or Oracle RAC

  1. cd WP_PROFILE/ConfigEngine

  2. Validate configuration properties...

      ./ConfigEngine.sh validate-database -DWasPassword=foo

    Add -DTransferDomainList to the validating task to specify the domains to validate; for example...


    To validate all domains, do not specify this parameter.

  3. cd WP_PROFILE/bin

  4. Stop the WebSphere_Portal server:

      ./stopServer.sh WebSphere_Portal -username wpadmin -password foo

  5. Transfer the database:

    Important: Do not execute the database-transfer task as a background process. This might cause the task to stall.

    1. cd WP_PROFILE/ConfigEngine

      ./ConfigEngine.sh database-transfer -DWasPassword=foo

      We can include only the domains to transfer.

      For example, to transfer only the JCR domain...

        ./ConfigEngine.sh database-transfer -DTransferDomainList=jcr -DWasPassword=foo

    2. Log output is written to:


      If the configuration fails, verify the values in the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files and then repeat this step.

  6. If dbdomain.DbRuntimeUser is set that user must have sufficient database user privileges:

    1. To manually grant database user privileges:

      1. Copy the appropriate template files to a work directory:

          createRuntimeRoleForDifferentSchema.sql Name of DB user and schema name are not the same
          createRuntimeRoleForSameSchema.sql Name of DB user and schema name are the same

        Files are in the following directories, where dbms is the database management system, and domain represents the database domains we are configuring (release, customization, community, jcr, feedback, and likeminds):


        For the JCR database domain, copy grantPermissionsToRuntimeRoleStatic.sql from the following directory:


      2. Replace all placeholder values with the values as defined in wkplc_dbdomain.properties. Placeholder values are surrounded by the character @.

      3. Execute the SQL statements.

    2. Grant database user privileges:

      1. Ensure the database administrator user ID is specified for domain.DBA.DbUser in...


        For example...


          ./ConfigEngine.sh grant-runtime-db-user-privileges -DTransferDomainList=release,customization,community,etc...

        You only need to add -DTransferDomainList when granting privileges across specific domains.

  7. After transferring the database tables, to avoid slow database response, start sqlplus, log in to the jcr.DbName database as the jcr.DbUser, and then run...
    SQL> execute dbms_stats.gather_schema_stats(ownname=> 'jcr.DbUser', cascade=> TRUE);
    SQL > commit;
    Exit sqlplus

    Reference wkplc_dbdomain.properties for jcrDbName and jcr.DbUser values.

  8. cd WP_PROFILE/bin
  9. Start the WebSphere Portal server.

  10. (Oracle RAC only) Manually specify an RAC datasource URL in the WAS console. The URL should look like the following:


If you have additional nodes already configured, compare the following file on all nodes with the file from the primary node. Ensure all instances of the file are identical:

If the files are not identical, copy icm.properties from the primary node on which you ran the database-transfer task to the node.

  1. Stop the portal server on the secondary nodes.

  2. Copy


    from the primary node and replace icm.properties on the secondary nodes.

  3. Start the portal server on the secondary nodes.

Parent: AIX stand-alone: Set up Oracle or Oracle RAC database
Previous: AIX stand-alone: Set up Oracle or Oracle RAC automatically or manually
Next: AIX stand-alone: Change Oracle or Oracle RAC driver types