Flashes (Alerts)
Abstract
The Region Move tool is agnostic to the Process Engine (PE) and Content Platform Engine (CPE) software. So when performing a region move operation, customers must use the latest version of Region Move. Using an old version of Region Move tool from the shipped media may result in migration issues already resolved by current version of the tool.
Content
In order to avoid the migration issues already resolved by current version of the tool, the latest Region Move tool version must always be used as specified in the Technical Notice - https://www-01.ibm.com/support/docview.wss?uid=swg27036552. The latest version of Region Move tool will work with all CPE 5.x releases.
Here are a few known issues using Region Move tool shipped with the CPE 5.2.1 GA media.
The following known issues are particular for ORACLE:
1. For the string fields, the CREATE TABLE in the destination database contains the VARCHAR2(size) - missing CHAR keyword. In this case, the 200 size length will be treated as BYTE instead of CHAR. As a result, the string will accommodate less characters than expected, particularly with multi-byte characters.
2. For the NUMBER type fields, the CREATE TABLE in the destination database contains the NUMBER type fields without the precision information. Without this precision information, the Oracle CREATE TABLE statement will throw an exception, "expects a non-zero size (i.e. from 1-38 to be a valid one)".
The older Region Move tool will create the table VWOBJECT (for instance) with the following Data Definition Language (DDL):
CREATE TABLE <schema>.VWOBJECT
(
F_BLOB BLOB,
F_OBJNAME VARCHAR2(200 BYTE) NOT NULL,
F_OBJINT NUMBER NOT NULL,
F_FLAGS NUMBER NOT NULL
)
The newer version of the tool will create table VWOBJECT with correct schema information as the following:
CREATE TABLE <schema>.VWOBJECT
(
F_BLOB BLOB,
F_OBJNAME VARCHAR2(200 CHAR) NOT NULL,
F_OBJINT NUMBER(10) NOT NULL,
F_FLAGS NUMBER(10) NOT NULL
)
The following known issues are particular for ORACLE:
1. For the string fields, the CREATE TABLE in the destination database contains the VARCHAR2(size) - missing CHAR keyword. In this case, the 200 size length will be treated as BYTE instead of CHAR. As a result, the string will accommodate less characters than expected, particularly with multi-byte characters.
2. For the NUMBER type fields, the CREATE TABLE in the destination database contains the NUMBER type fields without the precision information. Without this precision information, the Oracle CREATE TABLE statement will throw an exception, "expects a non-zero size (i.e. from 1-38 to be a valid one)".
The older Region Move tool will create the table VWOBJECT (for instance) with the following Data Definition Language (DDL):
CREATE TABLE <schema>.VWOBJECT
(
F_BLOB BLOB,
F_OBJNAME VARCHAR2(200 BYTE) NOT NULL,
F_OBJINT NUMBER NOT NULL,
F_FLAGS NUMBER NOT NULL
)
The newer version of the tool will create table VWOBJECT with correct schema information as the following:
CREATE TABLE <schema>.VWOBJECT
(
F_BLOB BLOB,
F_OBJNAME VARCHAR2(200 CHAR) NOT NULL,
F_OBJINT NUMBER(10) NOT NULL,
F_FLAGS NUMBER(10) NOT NULL
)
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Component":"Tools","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.5.x;5.2.1;5.2.0;5.1.0;5.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
26 September 2022
UID
ibm10960045