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 to WebLogic Portal 10.3.
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:
If you did not upgrade your main WebLogic Portal database from 8.1, 9.2, or 10.0/10.2 to 10.3 using the WebLogic Upgrade Wizard, you can perform the upgrade manually. If you have a 9.2 GroupSpace database, you must also upgrade that database. See Upgrading a 9.2 GroupSpace Database for more information.
Perform the following steps to upgrade your WebLogic Portal database:
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 Upgrading 8.1, 9.2, or 10.0 PointBase Databases. |
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 or 8.1 to 10.3.)upgrade_db.cmd/.sh
.upgrade_db_data.cmd/.sh
script to upgrade database data.Tip: | To upgrade your user store, follow the instructions in Upgrading to the 10.3 WebLogic Server SQL Authenticator on page B-3. |
http://edocs.beasys.com/wlp/docs81/relnotes/relnotes.html#1117746
) 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.
<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:
weblogic.alternateTypesDirectory
to include the path to the deprecated provider: <WLPORTAL_HOME>/p13n/deprecated/lib/security
. 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:
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@
.upgrade_db.properties
file, modify and uncomment the files=
setting for your behavior tracking database. Follow the instructions in the upgrade_db.properties
file. 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:
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@
.upgrade_db.properties
file, modify and uncomment the files=
setting for your content management database. Follow the instructions in the upgrade_db.properties
file. upgrade_db.cmd/.sh
.
If you did not use the WebLogic Upgrade Wizard to upgrade your WebLogic Portal 9.2 GroupSpace repository database, you can manually upgrade it.
Perform the following steps to upgrade a GroupSpace database:
upgrade_db.properties
file, modify and uncomment the files=
setting for your GroupSpace database. Follow the instructions in the upgrade_db.properties
file. 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, you can drop the tables associated with Compoze/Collaboration using the following script:
<WLPORTAL_HOME
>\portal\db\
<DMBS>\dep9_drop_tables.sql