> Upgrade Guide > Performing Database Upgrade Tasks Manually

Upgrade Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Performing Database Upgrade Tasks Manually

This appendix describes how to perform various database upgrade tasks manually if you do not use the WebLogic Upgrade Wizard to perform upgrade from 8.1 SP4, SP5, or SP6.

Files associated with database upgrade are located in the following directories: 

WL_HOME\portal\upgrade\db
WL_HOME\common\p13n\upgrade\db

This appendix contains the following sections:

 

PointBase Name Changes

PointBase stores all data in .dbn files and all log information in .wal files. Database properties are stored in PointBase.ini files. Data files for WebLogic Portal are now named weblogic_eval.dbn and log files for WebLogic Portal are named weblogic_eval$1.wal. They were previously named workshop.dbn and workshop$1.wal, respectively.

 

Upgrading your Main WebLogic Portal Database

If you did not upgrade your main WebLogic Portal database using the WebLogic Upgrade Wizard, you can perform the upgrade manually as follows:

  1. Shut down WebLogic Server.
  2. Back up your database data as described by your database vendor.
  3. Edit the WL_HOME\portal\upgrade\db\upgrade_db.properties file for your database environment. Replace the @ symbols and the text between the symbols with the correct values for @DB_USER@, @DB_PASSWORD@, @DB_HOST@, @DB_PORT@, and @DB_NAME@.
    4. Note: For PointBase, follow the instructions in Upgrading PointBase Databases.
  4. Set files= as follows (this is the default):
    5. files=${env.WL_HOME}/common/p13n/db/${database}/jdbc_index/UPGRADE/jdbc.index,${env.WL_HOME}/portal/db/${database}/jdbc_index/UPGRADE/jdbc
    .index
    Note: If you are using SQL Server, and you applied the patch for CR244320 to your SQL Server database, do not use the above files= setting; instead set files= as follows: 
    files=${env.WL_HOME}/common/p13n/db/${database}/jdbc_index/UPGRADE/
    unicode/jdbc.index,${env.WL_HOME}/portal/db/${database}/jdbc_index/
    UPGRADE/unicode/jdbc.index
  5. Either:
    • Run upgrade_db.cmd/.sh

      • or

    • Set noexec=Y and SQLOutputFile=outputfile.sql, and manually run the output SQL file generated with this files= setting.
  6. Run upgrade_db_data.cmd/.sh to upgrade database data.
    7. Tip: To upgrade your user store, follow the instructions in Upgrading to the WebLogic Server SQL Authenticator on page B-4.
  7. Determine if patch # CR244936 has been applied. If this patch has been applied, manual upgrade of the main WebLogic Portal database is complete. This patch is described in BEA WebLogic Portal 8.1 Service Pack 5 Release Notes (http://edocs.beasys.com/wlp/docs81/relnotes/relnotes.html#1117746) as follows:

    8. CR237251 - If markup contains more than 4000 bytes, an attempt to store it in the database causes an error. If your database does not contain a PF_MARKUP_XML table that has been populated with data i.e. Select count(*) from PF_MARKUP_XML returns 0 rows) and the PF_MARKUP_DEFINITION table does not contain the BEGIN_XML and END_XML columns then this patch was not applied.

  8. If patch # CR244936 has not been applied, run the script:
    9. WL_HOME\portal\db\dbms_name\pf9_drop_columns.sql

 

Upgrading PointBase Databases

To upgrade a PointBase database manually:

  1. Shut down WebLogic Server and the PointBase Server.
  2. Copy the workshop.dbn and workshop$#.wal files from the 8.1 domain directory to the upgrade directory.
  3. Rename the workshop.dbn file to weblogic_eval.dbn. Rename the workshop$#.wal file weblogic_eval$#.wal.
  4. Run upgrade_db.cmd/.sh to process required WebLogic Portal database updates for PointBase.
  5. Run upgrade_db_data.cmd/.sh to upgrade database data.
  6. Copy the upgraded weblogic_eval.dbn and weblogic_eval$#.wal files back to the domain directory. The Upgrade Wizard will have updated the URL to reflect the database name change and will have modified the pointbase.ini file for the 5.1 version of PointBase used with WebLogic Portal 9.2.

 

Upgrading to the WebLogic Server SQL Authenticator

If you did not upgrade your user store using the WebLogic Upgrade Wizard during the domain upgrade process, you can perform a manual upgrade later. The script to upgrade from the WebLogic Portal-specific RDBMS Authenticator to the WebLogic SQL Authenticator is: 

WL_HOME\common\p13n\db\dbms_name\upgrade_fromdbmsauth_tosqlauth.sql

 

Upgrading Separate Behavior Tracking Databases

If you created a separate behavior tracking database in version 8.1, upgrade it as follows:

  1. Shut down WebLogic Server.
  2. Back up your database data as described by your database vendor.
  3. Edit the settings in the upgrade_db.properties for your behavior tracking database. Replace the @ symbols and the text between the symbols with the correct values for @DB_USER@, @DB_PASSWORD@, @DB_HOST@, @DB_PORT@, and @DB_NAME@.
  4. Modify the files= setting in the upgrade_db.properties file and set it to:
    5. files=${env.WL_HOME}/portal/db/${SQL_DIR}/jdbc_index/UPGRADE/BT/jdbc
    .index
  5. Either:
    • Run upgrade_db.cmd/.sh

      • or

    • Set noexec=Y and SQLOutputFile=outputfile.sql, and manually run the output SQL file generated with this files= setting.

 

Upgrading Additional Content Management Databases

The default content management database is upgraded automatically. If you created an additional content management database in 8.1, upgrade it as follows:

  1. Shut down WebLogic Server.
  2. Back up your database data as described by your database vendor.
  3. Update the settings in the upgrade_db.properties for your content management database. Replace the @ symbols and the text between the symbols with the correct values for @DB_USER@, @DB_PASSWORD@, @DB_HOST@, @DB_PORT@, and @DB_NAME@.
  4. Modify the files= setting in the upgrade_db.properties file and set it to:
    5. files=${env.WL_HOME}/portal/db/${SQL_DIR}/jdbc_index/UPGRADE/CM/jdbc
    .index
    Note: If you are using SQL Server and have already applied the patch for CR244320 to your SQL Server database, instead modify the files= setting in the upgrade_db.properties file to: 
    files=${env.WL_HOME}/portal/db/${SQL_DIR}/jdbc_index/UPGRADE/CM/unicode/jdbc.index
  5. Either:
    • Run upgrade_db.cmd/.sh

      • or

    • Set noexec=Y and SQLOutputFile=outputfile.sql, and manually run the output SQL file generated with this files= setting.

 

Dropping Deprecated RDBMS Authenticator Tables After Upgrade

After you have upgraded to the WebLogic Server SQL Authenticator, you can drop the tables associated with the WebLogic Portal RDBMS Authenticator using the following script: 

WL_HOME\common\p13n\db\dbms_name\dep9_drop_tables.sql

 

Dropping Deprecated Compoze Database Tables After Upgrade

After you have upgraded to version 9.2, you can drop the tables associated with Compoze/Collaboration using the following script: 

WL_HOME\portal\db\dbms_name\dep9_drop_tables.sql

  Back to Top       Previous  Next