Migration Application Assuming Unicode For Non-Unicode Target Database

(Doc ID 2382673.1)

Last updated on APRIL 04, 2018

Applies to:

Siebel CRM Call Center - Version 17.4 [IP2017] and later
Information in this document applies to any platform.


On : 17.4 [IP2017] System Admin, Data Migration

Migration Plan has been created and submitted for execution, but the execution was taking long time when executing Schema Service import.
By reviewing the ddlimport*.log file located under filesystem/migration/archive_id/log directory on the target environment it was found that every table was getting all columns being modified.
Below is a snippet of the ddlimport*.log file:

2018-04-03 13:43:56 ddlimp /R Y /u SIEBEL /p ***** /l \\SiebelFS\migration\88-CTY2A\log\ddlimport_39E3D4A97C62.log /f \\SiebelFS\migration\88-CTY2A\schema\ddlexport_39E3D4A1A3A3.ctl /Z Y /g SSE_ROLE /c OV_TEST_DSN /e y
2018-04-03 13:44:11 Reading existing schema...
2018-04-03 13:50:46 Read 0 tablespaces, 5383 tables and 26324 indexes from existing schema...
2018-04-03 13:50:46
2018-04-03 13:50:46 Running SQL statements against the database...
2018-04-03 13:50:47 Merging table CX_ABU_STATUS ...
2018-04-03 13:50:47 Modifying column ABU_STATUS ... 0.703s
2018-04-03 13:50:47 Modifying column BATCH_NUM ... 0.187s
2018-04-03 13:50:48 Modifying column CONFLICT_ID ... 0.203s
2018-04-03 13:50:48 Modifying column CREATED_BY ... 0.250s
2018-04-03 13:50:48 Modifying column DB_LAST_UPD_SRC ... 0.469s
2018-04-03 13:50:49 Modifying column LAST_UPD_BY ... 0.281s
2018-04-03 13:50:49 Modifying column NAME ... 0.375s
2018-04-03 13:50:49 Modifying column PAR_ABU_ID ... 0.125s
2018-04-03 13:50:49 Modifying column PAR_ROW_ID ... 0.281s
2018-04-03 13:50:50 Modifying column ROW_ID ... 0.313s
2018-04-03 13:50:50 Modifying column TYPE ... 0.484s

After reviewing the database columns that got modified it was noticed the column definitions were changed to Unicode, example: VARCHAR to NVARCHAR.

The migration application should not change the column definition to Unicode if the database is not Unicode.

The issue can be reproduced at will with the following steps:

1. Have two Siebel IP2017 environments ready for Migration Plan execution using SQL Server database non-Unicode Siebel schema
2. Login to Migration Application
3. Define Source and Target systems
4. Create a Migration Plan
5. Execute the Migration Plan


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms