Search This Blog

SBL-DBC-00110: The characters: '%1' that are being inserted into column '%2', are not compatible with the Server Database Charset.

Applies to:

Siebel Tools - Version: 8.0.0.4 [20417] and later   [Release: V8 and later ]
Information in this document applies to any platform.


Symptoms

Situation: An External Business Component (EBC) is configured to connect to an external database that uses a Turkish character set.

Observed behavior: Inserting data containing Turkish characters into the EBC triggers an error message:



"The characters: '' that are being inserted into column '', are not compatible with the Server Database Charset. (SBL-DBC-00110)."

Cause

An EBC needs an instance of tables S_APP_VER and S_SYS_PREF in the external database in order to determine the character encoding to be used. These tables hold records to identify the encoding and the code page used by the external database.

As a background information, Siebel applications use the column UNICD_DATATYPS_FLG of table S_APP_VER to see if the database is a unicode database or not. Also, the system preference 'Enterprise DB Server Code Page' (SELECT VAL FROM S_SYS_PREF WHERE SYS_PREF_CD='Enterprise DB Server Code Page') needs to have the correct setting.

A Bug has already been raised to request documenting this in Siebel Bookshelf:

Bug 10548151: EBC with non-ENU data needs S_APP_VER and S_SYS_PREF

Another Bug has already been raised to request that EBC's shall read this information from within the Siebel database, to avoid having to add S_APP_VER and S_SYS_PREF to the external database:

Bug 10548153: Control EBC's code page info inside Siebel database

Solution

1. In Tools, export the table schemas of S_APP_VER and S_SYS_PREF into a .ddl file. (Use the "Apply/Generate DDL" button for this purpose).

2. Use the DDL file to create these two tables in the external database.

3. Insert a new row into S_APP_VER in the external database with column UNICD_DATATYPS_FLG set to the appropriate value:

'Y' if the database uses Unicode with UTF16 encoding
'8' if the database uses Unicode with UTF8 encoding
'N' if the database uses a non-Unicode encoding

4. Add a new row into S_SYS_PREF of the external database and set these columns:
SYS_PREF_CD = 'Enterprise DB Server Code Page'
VAL = <code page>

For VAL, the values utf-8, utf-16, cp1252, and cp932 are allowed in a production system.



Please note that none of these schema changes, inserts or updates are applied to the Siebel database; only the external database receives these changes. Updating the Siebel database through direct SQL is not supported.









Applies to:

Siebel Tools - Version: 8.0.0.4 [20417] and later   [Release: V8 and later ]
Information in this document applies to any platform.


Symptoms

Situation: An External Business Component (EBC) is configured to connect to an external database that uses a Turkish character set.

Observed behavior: Inserting data containing Turkish characters into the EBC triggers an error message:



"The characters: '' that are being inserted into column '', are not compatible with the Server Database Charset. (SBL-DBC-00110)."

Cause

An EBC needs an instance of tables S_APP_VER and S_SYS_PREF in the external database in order to determine the character encoding to be used. These tables hold records to identify the encoding and the code page used by the external database.

As a background information, Siebel applications use the column UNICD_DATATYPS_FLG of table S_APP_VER to see if the database is a unicode database or not. Also, the system preference 'Enterprise DB Server Code Page' (SELECT VAL FROM S_SYS_PREF WHERE SYS_PREF_CD='Enterprise DB Server Code Page') needs to have the correct setting.

A Bug has already been raised to request documenting this in Siebel Bookshelf:

Bug 10548151: EBC with non-ENU data needs S_APP_VER and S_SYS_PREF

Another Bug has already been raised to request that EBC's shall read this information from within the Siebel database, to avoid having to add S_APP_VER and S_SYS_PREF to the external database:

Bug 10548153: Control EBC's code page info inside Siebel database

Solution

1. In Tools, export the table schemas of S_APP_VER and S_SYS_PREF into a .ddl file. (Use the "Apply/Generate DDL" button for this purpose).

2. Use the DDL file to create these two tables in the external database.

3. Insert a new row into S_APP_VER in the external database with column UNICD_DATATYPS_FLG set to the appropriate value:

'Y' if the database uses Unicode with UTF16 encoding
'8' if the database uses Unicode with UTF8 encoding
'N' if the database uses a non-Unicode encoding

4. Add a new row into S_SYS_PREF of the external database and set these columns:
SYS_PREF_CD = 'Enterprise DB Server Code Page'
VAL = <code page>

For VAL, the values utf-8, utf-16, cp1252, and cp932 are allowed in a production system.



Please note that none of these schema changes, inserts or updates are applied to the Siebel database; only the external database receives these changes. Updating the Siebel database through direct SQL is not supported.










Applies to:

Siebel Tools - Version: 8.0.0.4 [20417] and later   [Release: V8 and later ]
Information in this document applies to any platform.


Symptoms

Situation: An External Business Component (EBC) is configured to connect to an external database that uses a Turkish character set.

Observed behavior: Inserting data containing Turkish characters into the EBC triggers an error message:



"The characters: '' that are being inserted into column '', are not compatible with the Server Database Charset. (SBL-DBC-00110)."

Cause

An EBC needs an instance of tables S_APP_VER and S_SYS_PREF in the external database in order to determine the character encoding to be used. These tables hold records to identify the encoding and the code page used by the external database.

As a background information, Siebel applications use the column UNICD_DATATYPS_FLG of table S_APP_VER to see if the database is a unicode database or not. Also, the system preference 'Enterprise DB Server Code Page' (SELECT VAL FROM S_SYS_PREF WHERE SYS_PREF_CD='Enterprise DB Server Code Page') needs to have the correct setting.

A Bug has already been raised to request documenting this in Siebel Bookshelf:

Bug 10548151: EBC with non-ENU data needs S_APP_VER and S_SYS_PREF

Another Bug has already been raised to request that EBC's shall read this information from within the Siebel database, to avoid having to add S_APP_VER and S_SYS_PREF to the external database:

Bug 10548153: Control EBC's code page info inside Siebel database

Solution

1. In Tools, export the table schemas of S_APP_VER and S_SYS_PREF into a .ddl file. (Use the "Apply/Generate DDL" button for this purpose).

2. Use the DDL file to create these two tables in the external database.

3. Insert a new row into S_APP_VER in the external database with column UNICD_DATATYPS_FLG set to the appropriate value:

'Y' if the database uses Unicode with UTF16 encoding
'8' if the database uses Unicode with UTF8 encoding
'N' if the database uses a non-Unicode encoding

4. Add a new row into S_SYS_PREF of the external database and set these columns:
SYS_PREF_CD = 'Enterprise DB Server Code Page'
VAL = <code page>

For VAL, the values utf-8, utf-16, cp1252, and cp932 are allowed in a production system.



Please note that none of these schema changes, inserts or updates are applied to the Siebel database; only the external database receives these changes. Updating the Siebel database through direct SQL is not supported.










Applies to:

Siebel Tools - Version: 8.0.0.4 [20417] and later   [Release: V8 and later ]
Information in this document applies to any platform.


Symptoms

Situation: An External Business Component (EBC) is configured to connect to an external database that uses a Turkish character set.

Observed behavior: Inserting data containing Turkish characters into the EBC triggers an error message:



"The characters: '' that are being inserted into column '', are not compatible with the Server Database Charset. (SBL-DBC-00110)."

Cause

An EBC needs an instance of tables S_APP_VER and S_SYS_PREF in the external database in order to determine the character encoding to be used. These tables hold records to identify the encoding and the code page used by the external database.

As a background information, Siebel applications use the column UNICD_DATATYPS_FLG of table S_APP_VER to see if the database is a unicode database or not. Also, the system preference 'Enterprise DB Server Code Page' (SELECT VAL FROM S_SYS_PREF WHERE SYS_PREF_CD='Enterprise DB Server Code Page') needs to have the correct setting.

A Bug has already been raised to request documenting this in Siebel Bookshelf:

Bug 10548151: EBC with non-ENU data needs S_APP_VER and S_SYS_PREF

Another Bug has already been raised to request that EBC's shall read this information from within the Siebel database, to avoid having to add S_APP_VER and S_SYS_PREF to the external database:

Bug 10548153: Control EBC's code page info inside Siebel database

Solution

1. In Tools, export the table schemas of S_APP_VER and S_SYS_PREF into a .ddl file. (Use the "Apply/Generate DDL" button for this purpose).

2. Use the DDL file to create these two tables in the external database.

3. Insert a new row into S_APP_VER in the external database with column UNICD_DATATYPS_FLG set to the appropriate value:

'Y' if the database uses Unicode with UTF16 encoding
'8' if the database uses Unicode with UTF8 encoding
'N' if the database uses a non-Unicode encoding

4. Add a new row into S_SYS_PREF of the external database and set these columns:
SYS_PREF_CD = 'Enterprise DB Server Code Page'
VAL = <code page>

For VAL, the values utf-8, utf-16, cp1252, and cp932 are allowed in a production system.



Please note that none of these schema changes, inserts or updates are applied to the Siebel database; only the external database receives these changes. Updating the Siebel database through direct SQL is not supported.










Applies to:

Siebel Tools - Version: 8.0.0.4 [20417] and later   [Release: V8 and later ]
Information in this document applies to any platform.


Symptoms

Situation: An External Business Component (EBC) is configured to connect to an external database that uses a Turkish character set.

Observed behavior: Inserting data containing Turkish characters into the EBC triggers an error message:



"The characters: '' that are being inserted into column '', are not compatible with the Server Database Charset. (SBL-DBC-00110)."

Cause

An EBC needs an instance of tables S_APP_VER and S_SYS_PREF in the external database in order to determine the character encoding to be used. These tables hold records to identify the encoding and the code page used by the external database.

As a background information, Siebel applications use the column UNICD_DATATYPS_FLG of table S_APP_VER to see if the database is a unicode database or not. Also, the system preference 'Enterprise DB Server Code Page' (SELECT VAL FROM S_SYS_PREF WHERE SYS_PREF_CD='Enterprise DB Server Code Page') needs to have the correct setting.

A Bug has already been raised to request documenting this in Siebel Bookshelf:

Bug 10548151: EBC with non-ENU data needs S_APP_VER and S_SYS_PREF

Another Bug has already been raised to request that EBC's shall read this information from within the Siebel database, to avoid having to add S_APP_VER and S_SYS_PREF to the external database:

Bug 10548153: Control EBC's code page info inside Siebel database

Solution

1. In Tools, export the table schemas of S_APP_VER and S_SYS_PREF into a .ddl file. (Use the "Apply/Generate DDL" button for this purpose).

2. Use the DDL file to create these two tables in the external database.

3. Insert a new row into S_APP_VER in the external database with column UNICD_DATATYPS_FLG set to the appropriate value:

'Y' if the database uses Unicode with UTF16 encoding
'8' if the database uses Unicode with UTF8 encoding
'N' if the database uses a non-Unicode encoding

4. Add a new row into S_SYS_PREF of the external database and set these columns:
SYS_PREF_CD = 'Enterprise DB Server Code Page'
VAL = <code page>

For VAL, the values utf-8, utf-16, cp1252, and cp932 are allowed in a production system.



Please note that none of these schema changes, inserts or updates are applied to the Siebel database; only the external database receives these changes. Updating the Siebel database through direct SQL is not supported.











Applies to:

Siebel Tools - Version: 8.0.0.4 [20417] and later   [Release: V8 and later ]
Information in this document applies to any platform.


Symptoms

Situation: An External Business Component (EBC) is configured to connect to an external database that uses a Turkish character set.

Observed behavior: Inserting data containing Turkish characters into the EBC triggers an error message:



"The characters: '' that are being inserted into column '', are not compatible with the Server Database Charset. (SBL-DBC-00110)."

Cause

An EBC needs an instance of tables S_APP_VER and S_SYS_PREF in the external database in order to determine the character encoding to be used. These tables hold records to identify the encoding and the code page used by the external database.

As a background information, Siebel applications use the column UNICD_DATATYPS_FLG of table S_APP_VER to see if the database is a unicode database or not. Also, the system preference 'Enterprise DB Server Code Page' (SELECT VAL FROM S_SYS_PREF WHERE SYS_PREF_CD='Enterprise DB Server Code Page') needs to have the correct setting.

A Bug has already been raised to request documenting this in Siebel Bookshelf:

Bug 10548151: EBC with non-ENU data needs S_APP_VER and S_SYS_PREF

Another Bug has already been raised to request that EBC's shall read this information from within the Siebel database, to avoid having to add S_APP_VER and S_SYS_PREF to the external database:

Bug 10548153: Control EBC's code page info inside Siebel database

Solution

1. In Tools, export the table schemas of S_APP_VER and S_SYS_PREF into a .ddl file. (Use the "Apply/Generate DDL" button for this purpose).

2. Use the DDL file to create these two tables in the external database.

3. Insert a new row into S_APP_VER in the external database with column UNICD_DATATYPS_FLG set to the appropriate value:

'Y' if the database uses Unicode with UTF16 encoding
'8' if the database uses Unicode with UTF8 encoding
'N' if the database uses a non-Unicode encoding

4. Add a new row into S_SYS_PREF of the external database and set these columns:
SYS_PREF_CD = 'Enterprise DB Server Code Page'
VAL = <code page>

For VAL, the values utf-8, utf-16, cp1252, and cp932 are allowed in a production system.



Please note that none of these schema changes, inserts or updates are applied to the Siebel database; only the external database receives these changes. Updating the Siebel database through direct SQL is not supported.


No comments:

Post a Comment

Subscribe to: Post Comments (Atom)