DDLSYNC (ddldict & ddlimp) on a Unicode DB creates VARCHAR2 columns as BYTE while they need to be CHAR
(Doc ID 1543446.1)
Last updated on AUGUST 17, 2022
Applies to:
Siebel CRM - Version 8.2.2 SIA[22320] and laterInformation in this document applies to any platform.
Symptoms
Running DDLSync on a text column, for example:
EIM_PAYMENT.X_NOM_PIECE
with Text 2000 in the Siebel repository
creates this column as VARCHAR2(2000 Byte)
on a unicode DB
(with NLS_LENGTH_SEMANTICS set to CHAR, but this is irrelevant for the creation by the Siebel utilities)
rather than
VARCHAR2(2000 CHAR)
Changes
Run DDLSync on a text column
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |