Transfer Oracle manually

 

+
Search Tips   |   Advanced Search

 

You are here

  1. Planning for Oracle
  2. Installing Oracle
  3. Creating databases and users for Oracle
  4. Transferring Oracle manually (Current task) or Transferring between databases manually
  5. Verifying database connections

 

Before you begin

Before configuring databases, ensure that the following prerequisites are met:

  • Supported database software is installed.
  • Databases and users are correctly setup for use by IBM WebSphere Portal.

The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, we can use the configuration wizard, a graphical user interface, to transfer data to another supported database.

A configuration template might exist to support these instructions. Refer to the directory...

portal_server_root/config/helpers

...for available configuration templates. Use the configuration template to update...

wpconfig.properties
wpconfig_dbdomain.properties
wpconfig_dbtype.properties

...as described in Websphere Portal v6 Configuration program.

 

Steps for transferring data to another supported database

Follow these steps to transfer WebSphere Portal and Member Manager databases to Oracle Enterprise Edition.

When doing a single database, single user, and multi schema database transfer to Oracle, there can be only one user for each domain...

  • release
  • community
  • customization
  • JCR
  • Feedback
  • LikeMinds
  • WMM

...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.

  1. Locate the following files and create a backup copy of each before changing any values:

  2. Edit the properties files and enter the values that are appropriate for the environment.

    The WebSphere Portal database can be used to hold information for applications such as...

    In this case, the user should have similar naming conventions for property values such as...

    • release.DbName
    • jcr.DbName
    • feedback.DbName
    • likeminds.DbName

    For example...

    • releaseDbName=wpsdb
    • jcr.DbName=jcrdb
    • feedback.DbName=fdbkdb
    • likeminds.DbName=lkmddb

    Do not change any settings other than those that are specified in these steps.

    If you are using a remote database, enter the values for the remote server.

    Use / instead of \ for all platforms.

    There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.

    Depending on which database domain has to be configured, dbdomain may need to be replaced by:

    • release
    • customization
    • community
    • jcr
    • feedback
    • likeminds
    • wmm

    Update the following properties in the file wpconfig_dbdomain.properties.

    Database domain properties
    Property Value
    dbdomain.DbType Type of database used to store information for WebSphere Portal.

    Value type: Alphanumeric text string

    Recommended: oracle

    dbdomain.DbName Name of the WebSphere Portal domain database and schema.

    This value is also the database element in the dbdomain.DbUrl property.

    This value should match the 'ORACLE_SID'.

    Value type: Alphanumeric text string

    If you change the name of the WebSphere Portal data source due to a database migration, manually update this property in...

    portal_server_root/config/wpconfig_dbdomain.properties

    ...to maintain the proper resource reference mapping.

    Default value for all domains: wpsdb

    dbdomain.DbUrl The database URL used to access the WebSphere Portal database with JDBC. The value must conform to standard JDBC URL syntax.

    The hostname is the name of the remote server and port is the port where the database instance is listening.

    The database element of this value should match the value of dbdomain.DbName.

    Value type: Alphanumeric text string, conforming to standard JDBC URL syntax

    Recommended value for all domains:

    jdbc:oracle:thin:@YourDatabaseServer:1521:wpsdb

    dbdomain.DbUser The user ID for the database administrator.

    Value type: Alphanumeric text string

    Default:

    Release db2admin
    Community db2admin
    Customization db2admin
    JCR db2admin
    WMM db2admin
    Feedback db2admin
    LikeMinds db2admin

    Recommended: wpsdbusr

    If the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property, otherwise, this value must be set to FEEDBACK, which corresponds to the user FEEDBACK in the database.

    dbdomain.DbPassword

    The password for the database administrator.

    A value must be set for this property; it cannot be empty.

    Value type: Alphanumeric text string

    Default value for all domains:

    ReplaceWithYourDbAdminPwd
    dbdomain.DataSourceName

    The name of the data store that WebSphere Portal uses to communicate with its databases.

    If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains.

    The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName.

    Value type: Alphanumeric text string

    Default values:

    Release wpsdbDS
    Community wpsdbDS
    Customization wpsdbDS
    JCR JCRDS
    WMM wpsdbDS
    Feedback feedback5
    LikeMinds lmdbDS

    Update the following properties in the file wpconfig_dbtype.properties.

    Database type properties
    Property Value
    DbSafeMode If set to true, database-specific tasks, such as create, modify, drop, will not be performed.

    Use if a pre-configured database from a previous installation already exists.

    If set to false, the database will be updated and the pre-existing database configuration will be overwritten.

    Recommended: false

    Default: false

    oracle.DbDriver The name of class that SqlProcessor will use to import SQL files.

    Recommended:

    oracle.jdbc.driver.OracleDriver
    oracle.JdbcProviderName

    The name of the JDBC provider that WebSphere Portal uses to communicate with its databases.

    Recommended:

    wpdbJDBC_oracle

    Default:

    wpdbJDBC_cloudscape
    oracle.DbLibrary The directory and name of the.zip or.jar file that contains the JDBC driver class.

    Recommended:

    Portal_Server_root/oracleJDBCyu/lib/jar

    In UNIX environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.

    Default:

    D:/oracleJDBC/ojdbc14.jar

    Update the following properties in the file wpconfig.properties.

    WebSphere Application Server properties
    Property Description
    WasPassword

    The password for WebSphere Application Server security authentication.

    If a value is specified for WasPassword, a value must also be specified for WasUserid. If WasPassword is left blank, WasUserid must also be left blank.

    Value type: Alphanumeric text string

    Recommended: Set this value according to your own environment.

    Default: ReplaceWithYourWASUserPwd

  3. Save the file.

  4. cd to portal_server_root/config.

  5. Validate configuration properties...

  6. Stop both server1 and the WebSphere Portal server.

    • UNIX

      ./stopServer.sh server1 -user admin_userid -password admin_password

    • i5/OS:

      stopServer -profileName profile_root -user admin_userid -password admin_password

  7. Enter the following command:

    • UNIX:

      ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password

    • i5/OS:

      stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password

  8. To transfer the database, perform this step:

    1. Run the configuration task. 

      ./WPSconfig.sh database-transfer \
    -Drelease.DbPassword=password \
    -Dcustomization.DbPassword=password \
    -Dcommunity.DbPassword=password \
    -Djcr.DbPassword=password \
    -Dwmm.DbPassword=password \
    -Dfeedback.DbPassword=password \
    -Dlikeminds.DbPassword=password

    2. After running this task, a message indicating success should result. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig_dbdomain.properties file, and then repeat this step.

  9. After transferring the database tables, execute the dbms_stats.gather_schema_stats command to avoid slow database response. Example:

    SQL> execute dbms_stats.gather_schema_stats(ownname=> 'icmadmin', cascade=> TRUE);

  10. Change to the directory...

    was_profile_root/bin

  11. Restart the server:

    startServer WebSphere_Portal

 

Next steps

You have completed this step. Continue to the next step:

 

Parent topic:

Transfer all domains