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.



תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - Version: 7.5.3 [16157] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3 [16157] Database: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא