DB2 Script Error on Upgrade
If you are upgrading from 4.7 to 5.6, and you use the js-upgrade-samedb.bat/sh script, it is possible to get an error related to an inadequate PAGESIZE setting. The recommended minimal PAGESIZE setting for both 4.7 and 5.0 is 16384. If the PAGESIZE setting is less than this you can get an error such as the following:
com.ibm.db2.jcc.am.SqlException:
DB2 SQL Error: SQLCODE=-670,SQLSTATE=54010, SQLERRMC=4005;
or
com.ibm.db2.jcc.am.SqlSyntaxErrorException:
DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=8192;DB2ADMIN,
DRIVER=4.11.77
If you get this error, recreate your 4.5 database using a command such as the following:
CREATE DATABASE JSPRSRVR USING CODESET UTF-8 TERRITORY US PAGESIZE 16384
This may require reloading your database from your database backup and rerunning the upgrade procedure after PAGESIZE has been changed.
Include Audit Events on Upgrade
If you have auditing enabled and you run upgrade using js-upgrade-newdb.bat/sh, audit events are not imported by default. To import audit events, you need to run an additional command after the after the js-upgrade-newdb script completes. To do this, change to the buildomatic directory:
cd <js-install>/buildomatic
Then run one of the following commands (for example):
js-import.bat --input-zip=js-my-export-all.zip --include-audit-events (Windows)
js-import.sh --input-zip=js-my-export-all.zip --include-audit-events (Linux)
or
ant import -DimportFile=js-my-export-all.zip -DimportArgs="--include-audit-events"
These commands reimport all resources from the specified export file. Existing resources will not be overwritten and the audit event will be added.
When using either import utility, the server must be stopped to avoid issues with caches, configuration, and security. |
Recommended Comments
There are no comments to display.