Oracle® Fusion Middleware Upgrade Guide for Oracle WebLogic Portal 10g Release 3 (10.3.2) Part Number E14253-01 |
|
|
View PDF |
This appendix describes how to perform database upgrade tasks manually if you do not use the WebLogic Upgrade Wizard to upgrade from 8.1, 9.2, or 10.0/10.2/10.3 to WebLogic Portal 10.3.2.
See the README.txt
file and the upgrade_db.properties
file in the <
WLPORTAL_HOME>\common\lib\upgrade\db
directory for detailed information about the files used in the upgrade and specific upgrade steps.
This appendix contains the following sections:
Section B.1, "Upgrading your Main WebLogic Portal 8.1, 9.2, or 10.0/10.2/10.3 Database"
Section B.2, "Upgrading 8.1, 9.2, or 10.0 PointBase Databases"
Section B.3, "Upgrading to the 10.3.2 WebLogic Server SQL Authenticator"
Section B.4, "Upgrading Separate 8.1 Behavior Tracking Databases"
Section B.5, "Upgrading Additional 8.1, 9.2, or 10.0 Content Management Databases"
Section B.6, "Dropping Deprecated RDBMS Authenticator Tables After Upgrade"
Section B.7, "Dropping Deprecated Compoze Database Tables After Upgrade"
If you did not upgrade your main WebLogic Portal database from 8.1, 9.2, or 10.0/10.2/10.3 to 10.2.3 using the WebLogic Upgrade Wizard, you can perform the upgrade manually.
Note:
As part of the upgrade process, the DDL automatically creates the RDBMS Security Store tables in the schema for which the p13nDatasource is configured. If a portal domain administrator wishes to use or configure a database schema other than the schema for which the p13nDatasource is configured, he or she must manually run the following script to create the RDBMS Security Store tables for that schema:<WLPORTAL_HOME>/p13n/db/<database_vendor>/rdbms_security_store_create_tables.sql
For more information on the RDBMS Security Store tables, see "RDBMS Security Store Tables" in the Oracle Fusion Middleware Database Administration Guide for Oracle WebLogic Portal.
Perform the following steps to upgrade your WebLogic Portal database:
Shut down WebLogic Server.
Back up your database data as described by your database vendor.
Edit the <
WLPORTAL_HOME>\common\lib\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@
.
Note:
For PointBase, follow the instructions in Section B.2, "Upgrading 8.1, 9.2, or 10.0 PointBase Databases."In the upgrade_db.properties
file, modify and uncomment the files=
setting for your portal database. Follow the instructions in the upgrade_db.properties
file for your specific type of upgrade (9.2 to 10.3.2 or 8.1 to 10.3.2.)
Run the following script: upgrade_db.cmd/.sh
.
If you are upgrading from 8.1 to 10.3.2, run the upgrade_db_data.cmd/.sh
script to upgrade database data.
Note:
To upgrade your user store, follow the instructions in Section B.3, "Upgrading to the 10.3.2 WebLogic Server SQL Authenticator."If you are upgrading a main WebLogic Portal database from 8.1 SP4, SP5, or SP6, determine if patch # CR244936 was applied. If this patch was applied, manual upgrade of the main WebLogic Portal database is complete. This patch is described in WebLogic Portal 8.1 SP5 Release Notes (http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/relnotes/index.html
) as follows:
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 (for example, 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.
If you are upgrading a main WebLogic Portal database from 8.1 SP4, SP5, or SP6 and patch # CR244936 has not been applied, run the following script against your database:
<WLPORTAL_HOME>\portal\db\<DBMS>\pf9_drop_columns.sql
To manually upgrade your PointBase database from 8.1, 9.2, or 10.0, you must first run the WebLogic Upgrade Wizard to perform a domain upgrade, and select No to skip the database upgrade. You must also copy the database files themselves (weblogic_eval.dbn
and weblogic_eval$#.wal
) into the <WLPORTAL_HOME>
\common\upgrade\db
directory and then copy them back to the domain directory.
See the README.txt
file for the specific steps to manually upgrade your PointBase database.
The RDBMS Authenticator was supported in 8.1, but was deprecated in Portal 9.2 and all later releases. The RDBMS Authenticator was replaced by the SQL Authenticator.
To enable support in the Upgrade Wizard for upgrading a domain with an RDBMS Authenticator, a manual step is required. Perform the following workaround before you upgrade from an 8.1 RDBMS Authenticator to Portal 10.3.2:
Update your setDomainEnv.cmd/sh variable weblogic.alternateTypesDirectory
to include the path to the deprecated provider: <WLPORTAL_HOME>/p13n/deprecated/lib/security
.
Run the Upgrade Wizard to perform the upgrade. The Upgrade Wizard also removes references to the deprecated RDBMS Authenticator from the domain's config.xml
file.
Tip:
If you did not upgrade your user store during the domain upgrade process, you can perform a manual upgrade later. Use the following script to upgrade from the WebLogic Portal-specific RDBMS Authenticator to the WebLogic SQL Authenticator: <WLPORTAL_HOME>\p13n\db\<DBMS>\ upgrade_fromdbmsauth_tosqlauth.sql.If you created a separate behavior tracking database in 8.1, you can upgrade it manually.
Perform the following steps to upgrade a separate behavior tracking database:
Shut down WebLogic Server.
Back up your database data as described by your database vendor.
Edit the settings in the upgrade_db.properties
file 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@
.
In the upgrade_db.properties
file, modify and uncomment the files=
setting for your behavior tracking database. Follow the instructions in the upgrade_db.properties
file.
Run the following script: upgrade_db.cmd/.sh
.
The default content management database is upgraded automatically. If you created an additional content management database in 8.1, 9.2, or 10.0, you can upgrade it manually.
Perform the following steps to upgrade an additional Content Management database:
Shut down WebLogic Server.
Back up your database data as described by your database vendor.
Update the settings in the upgrade_db.properties
file 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@
.
In the upgrade_db.properties
file, modify and uncomment the files=
setting for your content management database. Follow the instructions in the upgrade_db.properties
file.
Run the following script: upgrade_db.cmd/.sh
.
After you upgrade to the WebLogic Server SQL Authenticator, you can drop the tables associated with the WebLogic Portal RDBMS Authenticator using the following script:
<WLPORTAL_HOME>\p13n\db\<DMBS>\dep9_drop_tables.sql
After you upgrade to WebLogic Portal 10.3.2, you can drop the tables associated with Compoze/Collaboration using the following script:
<WLPORTAL_HOME>\portal\db\<DMBS>\dep9_drop_tables.sql