Arguments in DVM

Amid world cup fever with MOB (Men in Blue) finding mojo, here is my small piece on Data Validation Manager with constant Alt-Tab as SRT is on way for number 47.

One of the striking features of Data Validation Manager is the flexibility with which it allows to access fields in the underlying buscomp(Current Record) and child buscomp(All Records) in expressions. One can also pass arguments at run time to DVM which can be used in expression for evaluation.

We need to define arguments in the "Arguments" tab for the rule set.

This argument can be used in the expression just by appending the argument name with "&". Just like we use parameters in Data Map expressions.

This arguments should be passed in the workflow invoking the DVM as Property Set.

This allows us to pass multiple arguments to DVM at runtime which could be evaluated in the expression.

With my productivity going less than 50% just wishing all memorable cricket world cup...

SBL-DBC-00112: An error has occurred executing a query

Bug Attributes

---

Type	D - Documentation	Fixed in Product Version	-
Severity	2 - Severe Loss of Service	Product Version	1.0
Status	13 - Doc Bug (Response/Resolution)	Platform	289 - GENERIC (All Platforms)
Created	24-Nov-2009	Platform Version	NO DATA
Updated	09-Feb-2011	Base Bug	-
Database Version	N/A
Affects Platforms	Generic
Product Source	Oracle

Related Products

---

Line	Siebel	Family	Customer Relationship Management
Area	CRM - Enterprise Edition	Product	8962 - Siebel Documentation

Hdr: 10581921 N/A SIEBEL_DOC 1.0 LIF_SCI_GD PRODID-8962 PORTID-289
Abstract: [CR#12-1VMCEE7][FR#12-1VMCEET] LSG. SBL-DBC-00112, SBL-DAT-00175, & ORA-2396 ER

*** 05/06/10 03:39 pm ***
Summary: LSG. SBL-DBC-00112, SBL-DAT-00175, & ORA-2396 errors are thrown 
when initiating create accounts BS.
How to Reproduce: "'LS Pharma Account Contact Service¿ BS is invoked 
because of the BC User Prop ¿LS Pharma Targeting: Account Contact 
Relationship Enhancement¿ on Account and Contact BCs.

2) This user property is applicable only if customer is using Account-Contact 
functionality (for the Japanese market). Otherwise, you can just disable it. 
There are no issues with setting this user property to false.

3) This user property is creating a new db session in background when is 
active. Why this is happening?
*** 05/06/10 03:39 pm ***
*** 02/09/11 04:23 pm *** (CHG: Committed to Fix-> C -> NULL)

SBL-DBC-00111: An error has occurred writing to a record.

Applies to:

Siebel Consumer Goods - Version: 8.0.0.2 SIA [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue: Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

The OOTB Mass Sales Update button in Sales Value Planning Screen / CG SVP Category Baseline List Applet is causing strange numbers to come up (see attachment).

The error occurs due to the following insert:

UPDATE dbo.S_CG_CAT_BASELN SET
DB_LAST_UPD_SRC = ?,
DB_LAST_UPD = GETUTCDATE(),
LAST_UPD = ?,
LAST_UPD_BY = ?,
MODIFICATION_NUM = ?,
BASELN_SALES = ?
WHERE
ROW_ID = ? AND MODIFICATION_NUM = ?

0 : (00008)User
1 : (00038)2009-07-15 19:25:49
2 : (00012)1-4UOX
3 : (00010)25597
4 : (00032)1013324653189909
5 : (00016)1-18JLOD
6 : (00010)25596

SBL-DBC-00111: An error has occurred writing to a record. [Microsoft][SQL Native Client]Numeric value out of range

Cause

Cause Determination: Bug 10571878 - Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

Root Cause: Regression caused by 8.0.0.6 patch (which fixed the SVP drilldown issue).

Solution

Solution:

Install:

 8.0.0.6 20423 SBA QF0653
 8.0.0.9 Fix Pack

References

SVP, Sales Volume Planning, SBL-DBC-00111, Mass Update

Applies to:

Siebel Consumer Goods - Version: 8.0.0.2 SIA [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue: Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

The OOTB Mass Sales Update button in Sales Value Planning Screen / CG SVP Category Baseline List Applet is causing strange numbers to come up (see attachment).

The error occurs due to the following insert:

UPDATE dbo.S_CG_CAT_BASELN SET
DB_LAST_UPD_SRC = ?,
DB_LAST_UPD = GETUTCDATE(),
LAST_UPD = ?,
LAST_UPD_BY = ?,
MODIFICATION_NUM = ?,
BASELN_SALES = ?
WHERE
ROW_ID = ? AND MODIFICATION_NUM = ?

0 : (00008)User
1 : (00038)2009-07-15 19:25:49
2 : (00012)1-4UOX
3 : (00010)25597
4 : (00032)1013324653189909
5 : (00016)1-18JLOD
6 : (00010)25596

SBL-DBC-00111: An error has occurred writing to a record. [Microsoft][SQL Native Client]Numeric value out of range

Cause

Cause Determination: Bug 10571878 - Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

Root Cause: Regression caused by 8.0.0.6 patch (which fixed the SVP drilldown issue).

Solution

Solution:

Install:

 8.0.0.6 20423 SBA QF0653
 8.0.0.9 Fix Pack

References

SVP, Sales Volume Planning, SBL-DBC-00111, Mass Update

Applies to:

Siebel Consumer Goods - Version: 8.0.0.2 SIA [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue: Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

The OOTB Mass Sales Update button in Sales Value Planning Screen / CG SVP Category Baseline List Applet is causing strange numbers to come up (see attachment).

The error occurs due to the following insert:

UPDATE dbo.S_CG_CAT_BASELN SET
DB_LAST_UPD_SRC = ?,
DB_LAST_UPD = GETUTCDATE(),
LAST_UPD = ?,
LAST_UPD_BY = ?,
MODIFICATION_NUM = ?,
BASELN_SALES = ?
WHERE
ROW_ID = ? AND MODIFICATION_NUM = ?

0 : (00008)User
1 : (00038)2009-07-15 19:25:49
2 : (00012)1-4UOX
3 : (00010)25597
4 : (00032)1013324653189909
5 : (00016)1-18JLOD
6 : (00010)25596

SBL-DBC-00111: An error has occurred writing to a record. [Microsoft][SQL Native Client]Numeric value out of range

Cause

Cause Determination: Bug 10571878 - Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

Root Cause: Regression caused by 8.0.0.6 patch (which fixed the SVP drilldown issue).

Solution

Solution:

Install:

 8.0.0.6 20423 SBA QF0653
 8.0.0.9 Fix Pack

References

SVP, Sales Volume Planning, SBL-DBC-00111, Mass Update

Applies to:

Siebel Consumer Goods - Version: 8.0.0.2 SIA [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue: Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

The OOTB Mass Sales Update button in Sales Value Planning Screen / CG SVP Category Baseline List Applet is causing strange numbers to come up (see attachment).

The error occurs due to the following insert:

UPDATE dbo.S_CG_CAT_BASELN SET
DB_LAST_UPD_SRC = ?,
DB_LAST_UPD = GETUTCDATE(),
LAST_UPD = ?,
LAST_UPD_BY = ?,
MODIFICATION_NUM = ?,
BASELN_SALES = ?
WHERE
ROW_ID = ? AND MODIFICATION_NUM = ?

0 : (00008)User
1 : (00038)2009-07-15 19:25:49
2 : (00012)1-4UOX
3 : (00010)25597
4 : (00032)1013324653189909
5 : (00016)1-18JLOD
6 : (00010)25596

SBL-DBC-00111: An error has occurred writing to a record. [Microsoft][SQL Native Client]Numeric value out of range

Cause

Cause Determination: Bug 10571878 - Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

Root Cause: Regression caused by 8.0.0.6 patch (which fixed the SVP drilldown issue).

Solution

Solution:

Install:

 8.0.0.6 20423 SBA QF0653
 8.0.0.9 Fix Pack

References

SVP, Sales Volume Planning, SBL-DBC-00111, Mass Update

Applies to:

Siebel Consumer Goods - Version: 8.0.0.2 SIA [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue: Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

The OOTB Mass Sales Update button in Sales Value Planning Screen / CG SVP Category Baseline List Applet is causing strange numbers to come up (see attachment).

The error occurs due to the following insert:

UPDATE dbo.S_CG_CAT_BASELN SET
DB_LAST_UPD_SRC = ?,
DB_LAST_UPD = GETUTCDATE(),
LAST_UPD = ?,
LAST_UPD_BY = ?,
MODIFICATION_NUM = ?,
BASELN_SALES = ?
WHERE
ROW_ID = ? AND MODIFICATION_NUM = ?

0 : (00008)User
1 : (00038)2009-07-15 19:25:49
2 : (00012)1-4UOX
3 : (00010)25597
4 : (00032)1013324653189909
5 : (00016)1-18JLOD
6 : (00010)25596

SBL-DBC-00111: An error has occurred writing to a record. [Microsoft][SQL Native Client]Numeric value out of range

Cause

Cause Determination: Bug 10571878 - Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

Root Cause: Regression caused by 8.0.0.6 patch (which fixed the SVP drilldown issue).

Solution

Solution:

Install:

 8.0.0.6 20423 SBA QF0653
 8.0.0.9 Fix Pack

References

SVP, Sales Volume Planning, SBL-DBC-00111, Mass Update

Applies to:

Siebel Consumer Goods - Version: 8.0.0.2 SIA [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue: Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

The OOTB Mass Sales Update button in Sales Value Planning Screen / CG SVP Category Baseline List Applet is causing strange numbers to come up (see attachment).

The error occurs due to the following insert:

UPDATE dbo.S_CG_CAT_BASELN SET
DB_LAST_UPD_SRC = ?,
DB_LAST_UPD = GETUTCDATE(),
LAST_UPD = ?,
LAST_UPD_BY = ?,
MODIFICATION_NUM = ?,
BASELN_SALES = ?
WHERE
ROW_ID = ? AND MODIFICATION_NUM = ?

0 : (00008)User
1 : (00038)2009-07-15 19:25:49
2 : (00012)1-4UOX
3 : (00010)25597
4 : (00032)1013324653189909
5 : (00016)1-18JLOD
6 : (00010)25596

SBL-DBC-00111: An error has occurred writing to a record. [Microsoft][SQL Native Client]Numeric value out of range

Cause

Cause Determination: Bug 10571878 - Mass Sales Update button in SVP Screen causes the SBL-DBC-00111 and SQL Native Client]Numeric value out of range

Root Cause: Regression caused by 8.0.0.6 patch (which fixed the SVP drilldown issue).

Solution

Solution:

Install:

 8.0.0.6 20423 SBA QF0653
 8.0.0.9 Fix Pack

References

SVP, Sales Volume Planning, SBL-DBC-00111, Mass Update

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.

SBL-DBC-00108: An error has occurred preparing a Sql statement.

Applies to:

Siebel Tools - Version: 7.5.3 [100] to 8.1.1.2 - Release: V7 to V8
Information in this document applies to any platform.

Purpose

This document is intended to provide cause and corrective action information about Siebel
Error Message SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation

This error message can occur when a user navigates to a screen or view or executes a query in an applet. This error is generated when a SQL statement, usually a SELECT statement,
failed to be prepared against the database server.

In order to troubleshoot the error message it is important to review the error message returned by the database, which should be logged in the Siebel log files.
It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.


- Start by spooling the SQL, using the /s option, if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Document 475564.1 Using the /S Option to Examine the SQL Generated by Siebel Enterprise Application for more information.

- If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events for example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager? for more information.

- Refer to Document 475587.1 How Should Client Side Logging Be Set? for more information about setting up client side logging.


This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level. Below are some common causes:

1) Logical and Physical Schema are out of sync.

2) The SQL statement is missing a column name which can be further caused by:

  a) A field without a mapping to a physical column

  b)  A field with a Calculated Value but without the Calculated Flag value set to True

  c) A Link with properties Source Field or Destination Field defined with a calculated field

  d)  A Join Specification  with property Source Field defined with a calculated field

3) In version 7.7 when navigating to Opportunities Home view and try to search on the Contact field in the "Search" applet (Opportunity Home Search Virtual Form Applet)

4) If you encountered this error with ORA-00600

5) If you encountered this error with ORA-12570: TNS:packet reader failure

6) In version 8.0, when trying to schedule a route.

7) The components like Outbound Communications Manager and Workflow can lose their database connections intermittently due to networking issues or firewall time out connection between application server and the database.

8) There is a difference in the field type and length at the business component field definition versus the table column definition.

9) If you encountered this error with ORA-00942: table or view does not exist


Corrective Action

1) This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:

  a) Ensure that the user is connecting to the correct database

  b) Ensure that schema changes have been applied to the database.

i. Refer to Siebel Bookshelf version 7.7 (higher)> Configuring Siebel eBusiness Applications >   Configuring Tables and Columns > Applying Data Model Changes to the Server Database.

ii. Refer to Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Adding Custom Extensions to the Data Model

(1) Applying the Physical Schema Extensions to the Local Database

(2) Applying the Changes to the Server Database

2) Empty columns names are a result of a field in the business component not being correctly mapped. The name of the business component can be obtained from the log file when either client side logging or event component logging has been used. You might need to navigate to above the beginning of the SELECT statement in order to determine the name of the business component, for example:

ObjMgrBusCompLog Create 4 2003-12-22 16:01:27 Begin: construct BusComp 8d38658 "Internal Division"

Review the business component fields and joins to find the field definition causing the error and depending on the field or join, take appropriate action.


3) Bug 10479361 - "Error message when search on Contact from Opportunity Home page". It has been fixed in 7.8 version.

4) Contact Oracle Support to investigate the ORA-00600 message

5) Contact Oracle Support to investigate the error. It could be caused by SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file.

6) Bug 10566178 - "Invalid SQL statement generated when scheduling route". Further information can be found in Document 815515.1

7) Increase the firewall timeout or set OM-Model Cache Maximum parameter for the component (Outbound Communications Manager) to 0 (default is 10). Further information check Document 762888.1

8) This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. Document 476591.1 provides more information on this.

9) Ensure that the user has the privileges on the correspondent table or view.

Applies to:

Siebel CRM - Version: 8.1.1.1 [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

An error occurred while submitting a new order from Sales Order > Line Items applet in Siebel to AIA 2.5.



---
ObjMgrLog Error 1 000000044bf60a48:0 2010-05-21 15:57:41 (oracon.cpp (3211)) SBL-DBC-00108: An error has occurred preparing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
SQLParseAndExecute Execute 5 000000044bf60a48:0 2010-05-21 15:57:41 ORA-00942: table or view does not exist
----

Siebel version  use was 8.1.1.1 SIA [21111] with QF1102 related to ACR 474 and ACR 508 for supporting AIA 2.5.

Cause

From analysis of the log level 5 component log files, the cause of the error was traced down to missing tables/fields in the siebel schema . Due to this, the underlying SQL referencing those tables failed.

Solution

From the QF1102 install guide, it is seen that the QF introduces schema changes to the database for some existing tables. These schema changes need to applied in the underlying physical database by clicking "Apply/DDL" button in Siebel Tools.

While this seem to be done for the affected tables listed in the QF install guide, still the error was not  resolved. Apparently there could be some other table(s) for which the changes needed to be applied, however, this could not be determined in absence of further information.

Documentation Defect # 12-1YBWHXZ was raised requesting to provide further information if there could be other table (other than the ones listed in the QF install guide) for which DDLSync needs to be done

In this case, the issue was resolved by doing "Apply/DLL" for all existing tables in the siebel repository

Applies to:

Siebel Tools - Version: 7.5.3 [100] to 8.1.1.2 - Release: V7 to V8
Information in this document applies to any platform.

Purpose

This document is intended to provide cause and corrective action information about Siebel
Error Message SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation

This error message can occur when a user navigates to a screen or view or executes a query in an applet. This error is generated when a SQL statement, usually a SELECT statement,
failed to be prepared against the database server.

In order to troubleshoot the error message it is important to review the error message returned by the database, which should be logged in the Siebel log files.
It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.


- Start by spooling the SQL, using the /s option, if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Document 475564.1 Using the /S Option to Examine the SQL Generated by Siebel Enterprise Application for more information.

- If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events for example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager? for more information.

- Refer to Document 475587.1 How Should Client Side Logging Be Set? for more information about setting up client side logging.


This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level. Below are some common causes:

1) Logical and Physical Schema are out of sync.

2) The SQL statement is missing a column name which can be further caused by:

  a) A field without a mapping to a physical column

  b)  A field with a Calculated Value but without the Calculated Flag value set to True

  c) A Link with properties Source Field or Destination Field defined with a calculated field

  d)  A Join Specification  with property Source Field defined with a calculated field

3) In version 7.7 when navigating to Opportunities Home view and try to search on the Contact field in the "Search" applet (Opportunity Home Search Virtual Form Applet)

4) If you encountered this error with ORA-00600

5) If you encountered this error with ORA-12570: TNS:packet reader failure

6) In version 8.0, when trying to schedule a route.

7) The components like Outbound Communications Manager and Workflow can lose their database connections intermittently due to networking issues or firewall time out connection between application server and the database.

8) There is a difference in the field type and length at the business component field definition versus the table column definition.

9) If you encountered this error with ORA-00942: table or view does not exist


Corrective Action

1) This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:

  a) Ensure that the user is connecting to the correct database

  b) Ensure that schema changes have been applied to the database.

i. Refer to Siebel Bookshelf version 7.7 (higher)> Configuring Siebel eBusiness Applications >   Configuring Tables and Columns > Applying Data Model Changes to the Server Database.

ii. Refer to Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Adding Custom Extensions to the Data Model

(1) Applying the Physical Schema Extensions to the Local Database

(2) Applying the Changes to the Server Database

2) Empty columns names are a result of a field in the business component not being correctly mapped. The name of the business component can be obtained from the log file when either client side logging or event component logging has been used. You might need to navigate to above the beginning of the SELECT statement in order to determine the name of the business component, for example:

ObjMgrBusCompLog Create 4 2003-12-22 16:01:27 Begin: construct BusComp 8d38658 "Internal Division"

Review the business component fields and joins to find the field definition causing the error and depending on the field or join, take appropriate action.


3) Bug 10479361 - "Error message when search on Contact from Opportunity Home page". It has been fixed in 7.8 version.

4) Contact Oracle Support to investigate the ORA-00600 message

5) Contact Oracle Support to investigate the error. It could be caused by SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file.

6) Bug 10566178 - "Invalid SQL statement generated when scheduling route". Further information can be found in Document 815515.1

7) Increase the firewall timeout or set OM-Model Cache Maximum parameter for the component (Outbound Communications Manager) to 0 (default is 10). Further information check Document 762888.1

8) This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. Document 476591.1 provides more information on this.

9) Ensure that the user has the privileges on the correspondent table or view.

Applies to:

Siebel Tools - Version: 7.5.3 [100] to 8.1.1.2 - Release: V7 to V8
Information in this document applies to any platform.

Purpose

This document is intended to provide cause and corrective action information about Siebel
Error Message SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation

This error message can occur when a user navigates to a screen or view or executes a query in an applet. This error is generated when a SQL statement, usually a SELECT statement,
failed to be prepared against the database server.

In order to troubleshoot the error message it is important to review the error message returned by the database, which should be logged in the Siebel log files.
It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.


- Start by spooling the SQL, using the /s option, if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Document 475564.1 Using the /S Option to Examine the SQL Generated by Siebel Enterprise Application for more information.

- If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events for example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager? for more information.

- Refer to Document 475587.1 How Should Client Side Logging Be Set? for more information about setting up client side logging.


This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level. Below are some common causes:

1) Logical and Physical Schema are out of sync.

2) The SQL statement is missing a column name which can be further caused by:

  a) A field without a mapping to a physical column

  b)  A field with a Calculated Value but without the Calculated Flag value set to True

  c) A Link with properties Source Field or Destination Field defined with a calculated field

  d)  A Join Specification  with property Source Field defined with a calculated field

3) In version 7.7 when navigating to Opportunities Home view and try to search on the Contact field in the "Search" applet (Opportunity Home Search Virtual Form Applet)

4) If you encountered this error with ORA-00600

5) If you encountered this error with ORA-12570: TNS:packet reader failure

6) In version 8.0, when trying to schedule a route.

7) The components like Outbound Communications Manager and Workflow can lose their database connections intermittently due to networking issues or firewall time out connection between application server and the database.

8) There is a difference in the field type and length at the business component field definition versus the table column definition.

9) If you encountered this error with ORA-00942: table or view does not exist


Corrective Action

1) This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:

  a) Ensure that the user is connecting to the correct database

  b) Ensure that schema changes have been applied to the database.

i. Refer to Siebel Bookshelf version 7.7 (higher)> Configuring Siebel eBusiness Applications >   Configuring Tables and Columns > Applying Data Model Changes to the Server Database.

ii. Refer to Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Adding Custom Extensions to the Data Model

(1) Applying the Physical Schema Extensions to the Local Database

(2) Applying the Changes to the Server Database

2) Empty columns names are a result of a field in the business component not being correctly mapped. The name of the business component can be obtained from the log file when either client side logging or event component logging has been used. You might need to navigate to above the beginning of the SELECT statement in order to determine the name of the business component, for example:

ObjMgrBusCompLog Create 4 2003-12-22 16:01:27 Begin: construct BusComp 8d38658 "Internal Division"

Review the business component fields and joins to find the field definition causing the error and depending on the field or join, take appropriate action.


3) Bug 10479361 - "Error message when search on Contact from Opportunity Home page". It has been fixed in 7.8 version.

4) Contact Oracle Support to investigate the ORA-00600 message

5) Contact Oracle Support to investigate the error. It could be caused by SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file.

6) Bug 10566178 - "Invalid SQL statement generated when scheduling route". Further information can be found in Document 815515.1

7) Increase the firewall timeout or set OM-Model Cache Maximum parameter for the component (Outbound Communications Manager) to 0 (default is 10). Further information check Document 762888.1

8) This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. Document 476591.1 provides more information on this.

9) Ensure that the user has the privileges on the correspondent table or view.

Applies to:

Siebel Tools - Version: 7.5.3 [100] to 8.1.1.2 - Release: V7 to V8
Information in this document applies to any platform.

Purpose

This document is intended to provide cause and corrective action information about Siebel
Error Message SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation

This error message can occur when a user navigates to a screen or view or executes a query in an applet. This error is generated when a SQL statement, usually a SELECT statement,
failed to be prepared against the database server.

In order to troubleshoot the error message it is important to review the error message returned by the database, which should be logged in the Siebel log files.
It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.


- Start by spooling the SQL, using the /s option, if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Document 475564.1 Using the /S Option to Examine the SQL Generated by Siebel Enterprise Application for more information.

- If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events for example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager? for more information.

- Refer to Document 475587.1 How Should Client Side Logging Be Set? for more information about setting up client side logging.


This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level. Below are some common causes:

1) Logical and Physical Schema are out of sync.

2) The SQL statement is missing a column name which can be further caused by:

  a) A field without a mapping to a physical column

  b)  A field with a Calculated Value but without the Calculated Flag value set to True

  c) A Link with properties Source Field or Destination Field defined with a calculated field

  d)  A Join Specification  with property Source Field defined with a calculated field

3) In version 7.7 when navigating to Opportunities Home view and try to search on the Contact field in the "Search" applet (Opportunity Home Search Virtual Form Applet)

4) If you encountered this error with ORA-00600

5) If you encountered this error with ORA-12570: TNS:packet reader failure

6) In version 8.0, when trying to schedule a route.

7) The components like Outbound Communications Manager and Workflow can lose their database connections intermittently due to networking issues or firewall time out connection between application server and the database.

8) There is a difference in the field type and length at the business component field definition versus the table column definition.

9) If you encountered this error with ORA-00942: table or view does not exist


Corrective Action

1) This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:

  a) Ensure that the user is connecting to the correct database

  b) Ensure that schema changes have been applied to the database.

i. Refer to Siebel Bookshelf version 7.7 (higher)> Configuring Siebel eBusiness Applications >   Configuring Tables and Columns > Applying Data Model Changes to the Server Database.

ii. Refer to Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Adding Custom Extensions to the Data Model

(1) Applying the Physical Schema Extensions to the Local Database

(2) Applying the Changes to the Server Database

2) Empty columns names are a result of a field in the business component not being correctly mapped. The name of the business component can be obtained from the log file when either client side logging or event component logging has been used. You might need to navigate to above the beginning of the SELECT statement in order to determine the name of the business component, for example:

ObjMgrBusCompLog Create 4 2003-12-22 16:01:27 Begin: construct BusComp 8d38658 "Internal Division"

Review the business component fields and joins to find the field definition causing the error and depending on the field or join, take appropriate action.


3) Bug 10479361 - "Error message when search on Contact from Opportunity Home page". It has been fixed in 7.8 version.

4) Contact Oracle Support to investigate the ORA-00600 message

5) Contact Oracle Support to investigate the error. It could be caused by SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file.

6) Bug 10566178 - "Invalid SQL statement generated when scheduling route". Further information can be found in Document 815515.1

7) Increase the firewall timeout or set OM-Model Cache Maximum parameter for the component (Outbound Communications Manager) to 0 (default is 10). Further information check Document 762888.1

8) This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. Document 476591.1 provides more information on this.

9) Ensure that the user has the privileges on the correspondent table or view.

Applies to:

Siebel Tools - Version: 7.5.3 [100] to 8.1.1.2 - Release: V7 to V8
Information in this document applies to any platform.

Purpose

This document is intended to provide cause and corrective action information about Siebel
Error Message SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation

This error message can occur when a user navigates to a screen or view or executes a query in an applet. This error is generated when a SQL statement, usually a SELECT statement,
failed to be prepared against the database server.

In order to troubleshoot the error message it is important to review the error message returned by the database, which should be logged in the Siebel log files.
It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.


- Start by spooling the SQL, using the /s option, if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Document 475564.1 Using the /S Option to Examine the SQL Generated by Siebel Enterprise Application for more information.

- If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events for example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager? for more information.

- Refer to Document 475587.1 How Should Client Side Logging Be Set? for more information about setting up client side logging.


This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level. Below are some common causes:

1) Logical and Physical Schema are out of sync.

2) The SQL statement is missing a column name which can be further caused by:

  a) A field without a mapping to a physical column

  b)  A field with a Calculated Value but without the Calculated Flag value set to True

  c) A Link with properties Source Field or Destination Field defined with a calculated field

  d)  A Join Specification  with property Source Field defined with a calculated field

3) In version 7.7 when navigating to Opportunities Home view and try to search on the Contact field in the "Search" applet (Opportunity Home Search Virtual Form Applet)

4) If you encountered this error with ORA-00600

5) If you encountered this error with ORA-12570: TNS:packet reader failure

6) In version 8.0, when trying to schedule a route.

7) The components like Outbound Communications Manager and Workflow can lose their database connections intermittently due to networking issues or firewall time out connection between application server and the database.

8) There is a difference in the field type and length at the business component field definition versus the table column definition.

9) If you encountered this error with ORA-00942: table or view does not exist


Corrective Action

1) This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:

  a) Ensure that the user is connecting to the correct database

  b) Ensure that schema changes have been applied to the database.

i. Refer to Siebel Bookshelf version 7.7 (higher)> Configuring Siebel eBusiness Applications >   Configuring Tables and Columns > Applying Data Model Changes to the Server Database.

ii. Refer to Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Adding Custom Extensions to the Data Model

(1) Applying the Physical Schema Extensions to the Local Database

(2) Applying the Changes to the Server Database

2) Empty columns names are a result of a field in the business component not being correctly mapped. The name of the business component can be obtained from the log file when either client side logging or event component logging has been used. You might need to navigate to above the beginning of the SELECT statement in order to determine the name of the business component, for example:

ObjMgrBusCompLog Create 4 2003-12-22 16:01:27 Begin: construct BusComp 8d38658 "Internal Division"

Review the business component fields and joins to find the field definition causing the error and depending on the field or join, take appropriate action.


3) Bug 10479361 - "Error message when search on Contact from Opportunity Home page". It has been fixed in 7.8 version.

4) Contact Oracle Support to investigate the ORA-00600 message

5) Contact Oracle Support to investigate the error. It could be caused by SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file.

6) Bug 10566178 - "Invalid SQL statement generated when scheduling route". Further information can be found in Document 815515.1

7) Increase the firewall timeout or set OM-Model Cache Maximum parameter for the component (Outbound Communications Manager) to 0 (default is 10). Further information check Document 762888.1

8) This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. Document 476591.1 provides more information on this.

9) Ensure that the user has the privileges on the correspondent table or view.

Applies to:

Siebel Tools - Version: 7.5.3 [100] to 8.1.1.2 - Release: V7 to V8
Information in this document applies to any platform.

Purpose

This document is intended to provide cause and corrective action information about Siebel
Error Message SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Scope

This document is informational and intended for any user.

SBL-DBC-00108: An error has occurred preparing a Sql statement.Please continue or ask your systems administrator to check your application configuration if the problem persists.

Explanation

This error message can occur when a user navigates to a screen or view or executes a query in an applet. This error is generated when a SQL statement, usually a SELECT statement,
failed to be prepared against the database server.

In order to troubleshoot the error message it is important to review the error message returned by the database, which should be logged in the Siebel log files.
It is important to obtain the failing SQL statement as well but SQL statements are not logged unless SQL tracing is enabled.


- Start by spooling the SQL, using the /s option, if the error is reproducible in the dedicated client or mobile client. This spools all the SQL being generated by the application client to a log file and allows the SQL statement causing the error to be identified and reviewed. See Document 475564.1 Using the /S Option to Examine the SQL Generated by Siebel Enterprise Application for more information.

- If the error is reproducible only in the Siebel web client, you will need to raise the log levels for the different events for example, ObjMgrSqlLog for the Application Object Manager to capture the SQL statements. See Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager? for more information.

- Refer to Document 475587.1 How Should Client Side Logging Be Set? for more information about setting up client side logging.


This error message can be encountered for a variety of different reasons ranging from errors in the configuration of a business component to permissions on a table at the database level. Below are some common causes:

1) Logical and Physical Schema are out of sync.

2) The SQL statement is missing a column name which can be further caused by:

  a) A field without a mapping to a physical column

  b)  A field with a Calculated Value but without the Calculated Flag value set to True

  c) A Link with properties Source Field or Destination Field defined with a calculated field

  d)  A Join Specification  with property Source Field defined with a calculated field

3) In version 7.7 when navigating to Opportunities Home view and try to search on the Contact field in the "Search" applet (Opportunity Home Search Virtual Form Applet)

4) If you encountered this error with ORA-00600

5) If you encountered this error with ORA-12570: TNS:packet reader failure

6) In version 8.0, when trying to schedule a route.

7) The components like Outbound Communications Manager and Workflow can lose their database connections intermittently due to networking issues or firewall time out connection between application server and the database.

8) There is a difference in the field type and length at the business component field definition versus the table column definition.

9) If you encountered this error with ORA-00942: table or view does not exist


Corrective Action

1) This has occurred if the SQL statement refers to custom tables or custom extension columns which do not exist on the database the user is connecting to. To correct this:

  a) Ensure that the user is connecting to the correct database

  b) Ensure that schema changes have been applied to the database.

i. Refer to Siebel Bookshelf version 7.7 (higher)> Configuring Siebel eBusiness Applications >   Configuring Tables and Columns > Applying Data Model Changes to the Server Database.

ii. Refer to Siebel Bookshelf version 7.5.3 > Siebel Tools Reference > Adding Custom Extensions to the Data Model

(1) Applying the Physical Schema Extensions to the Local Database

(2) Applying the Changes to the Server Database

2) Empty columns names are a result of a field in the business component not being correctly mapped. The name of the business component can be obtained from the log file when either client side logging or event component logging has been used. You might need to navigate to above the beginning of the SELECT statement in order to determine the name of the business component, for example:

ObjMgrBusCompLog Create 4 2003-12-22 16:01:27 Begin: construct BusComp 8d38658 "Internal Division"

Review the business component fields and joins to find the field definition causing the error and depending on the field or join, take appropriate action.


3) Bug 10479361 - "Error message when search on Contact from Opportunity Home page". It has been fixed in 7.8 version.

4) Contact Oracle Support to investigate the ORA-00600 message

5) Contact Oracle Support to investigate the error. It could be caused by SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file.

6) Bug 10566178 - "Invalid SQL statement generated when scheduling route". Further information can be found in Document 815515.1

7) Increase the firewall timeout or set OM-Model Cache Maximum parameter for the component (Outbound Communications Manager) to 0 (default is 10). Further information check Document 762888.1

8) This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. Document 476591.1 provides more information on this.

9) Ensure that the user has the privileges on the correspondent table or view.

SBL-DBC-00107: An Oracle database error has occurred.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

EAI OM, Loyalty Engine Component Failure occur multiple times.

(oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

Cause

Siebel component shows error:





(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.








The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

Solution

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.





- Best option is to make more space available in the archive log destination (log_archive_dest_n).





- Increased frequency of log purges.
  Work with your DBA to address the above.





- Restart Siebel servers.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

EAI OM, Loyalty Engine Component Failure occur multiple times.

(oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

Cause

Siebel component shows error:





(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.








The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

Solution

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.





- Best option is to make more space available in the archive log destination (log_archive_dest_n).





- Increased frequency of log purges.
  Work with your DBA to address the above.





- Restart Siebel servers.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

EAI OM, Loyalty Engine Component Failure occur multiple times.

(oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

Cause

Siebel component shows error:





(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.








The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

Solution

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.





- Best option is to make more space available in the archive log destination (log_archive_dest_n).





- Increased frequency of log purges.
  Work with your DBA to address the above.





- Restart Siebel servers.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

EAI OM, Loyalty Engine Component Failure occur multiple times.

(oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

Cause

Siebel component shows error:





(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.








The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

Solution

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.





- Best option is to make more space available in the archive log destination (log_archive_dest_n).





- Increased frequency of log purges.
  Work with your DBA to address the above.





- Restart Siebel servers.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

EAI OM, Loyalty Engine Component Failure occur multiple times.

(oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

Cause

Siebel component shows error:





(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.








The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

Solution

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.





- Best option is to make more space available in the archive log destination (log_archive_dest_n).





- Increased frequency of log purges.
  Work with your DBA to address the above.





- Restart Siebel servers.

SBL-DBC-00106: An ODBC database error has occurred. Possibly the database name is invalid.

Bug Attributes

---

Type	B - Defect	Fixed in Product Version	0UNKNOWN
Severity	2 - Severe Loss of Service	Product Version	1.0
Status	30 - Additional Information Requested	Platform	289 - GENERIC (All Platforms)
Created	29-Jun-2007	Platform Version	NO DATA
Updated	12-Jan-2011	Base Bug	-
Database Version	9.2
Affects Platforms	Generic
Product Source	Oracle

Related Products

---

Line	Siebel	Family	Customer Relationship Management
Area	CRM - Enterprise Edition	Product	8981 - Siebel Apps - Service

Hdr: 10527107 9.2 ASGN_MGR 1.0 SER_PRO PRODID-8981 PORTID-289
Abstract: [CR#12-1K216WF][FR#12-1K216XJ] CANNOT INVOKE LOAD SPLITER ON DEDICATED WEB CLIEN

*** 08/13/07 10:06 am ***
Summary: Cannot invoke Load Spliter on dedicated web client
How to Reproduce: Invoking Load Spliter on dedicated client failed with:
SQLTraceAll SQLTraceAll 4 0 2007-05-16 09:12:33 No DNS found
ObjMgrBusServiceLog Error 1 0 2007-05-16 09:12:33 (loadspltrsvc.cpp (567)) 
SBL-DBC-00106: An ODBC database error has occurred. Possibly the database 
name is invalid.

However it works fine in web client.

How to reproduce:
- Import attached BS into the client or even Siebel Tools
- Invoke it from client (e.g. using Business Service Simulator)

You will the above error message.

See also log file attached.
*** 08/13/07 10:06 am ***
*** 08/13/07 10:02 am ***
*** 01/06/11 12:32 pm *** (CHG: Pri->2)

SBL-DBC-00105: An error has occurred executing a Sql statement.

Applies to:

Siebel Tools - Version: 7.7.2 [18325] to 8.1.1.3[21219]   [Release: to V8]
z*OBSOLETE: Microsoft Windows Server 2003


Product Release: V7 (Enterprise)


Version: 7.7.2.1 [18353]


Database: Oracle 9.2.0.6


Application Server OS: Microsoft Windows 2003 Server


Database Server OS: Sun Solaris 9





This document was previously published as Siebel SR 38-2849725171.





"" Checked for Relevance on 17-SEP-2010 ""

Symptoms

SBL-DBC-00105

Customer created an external view on SIEBVIEW schema (v$activity_follow_ups_ebc) in order to join two types of Activity rows (SQL UNION) - old ones that have no parent activity reference, and new ones that have this reference. The view is working fine from SQL Navigator, and there are no errors in any type of direct SQL Queries that customer made.

An EBC has been created based on this view to display the date in a List Applet that was inserted on Acitivity List view.

When customer opens this view, the following error occur:
"An error has occurred executing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)".

If customer changes the view, and select only the new group of records, the EBC is working fine and he can see records from GUI. But if he puts in the view only OLD records, he is getting this error.

Cause

The customer's view definition for the External Business Component (EBC) included a restriction on a date:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
... act.created > '17-Sep-2001' -- to eliminate activities created before Siebel roll-out
...

The view could be accessed successfully from a third party tool, but a select statement generated from the Siebel Application caused an SQL error.

Solution

As the date formatting depends on the session's NLS (National Language Support) settings, we suggested an adapted version that would work independent from the current NLS setting:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
act.created > (to_date('17.09.2001','DD.MM.YYYY'))

The customer changed the view definition accordingly and no more SQL errors occurred when accessing the EBC from the Siebel application.

Please note that the to_date function above and its syntax is specific to Oracle RDBMS.

Applies to:

Siebel Tools - Version: 8.0.0.2 [20412] and later   [Release: V8 and later ]
Siebel Tools - Version: 7.7.1 SIA [18306] to 8.0.0.2 [20412]   [Release: V7 to V8]
Siebel Tools - Version: 7.7.1 [18306] to 8.0.0.2 [20412]   [Release: V7 to V8]
Information in this document applies to any platform.

Symptoms

The customer created an External Business Component (EBC) based upon a database view on another application's tables (ERP - Oracle DB)

When querying the EBC using a simple Workflow Siebel Operation this resulted in the following warning message:

SBL-DBC-00105
--
ORA-24347: Warning of a NULL column in an aggregate function

which caused Siebel Error

SBL-DBC-00105

"An error has occurred executing a Sql statement.

Please continue or ask your systems administrator to check your application configuration if the problem persists."

then.

(Note that this behavior is generally independent from using a workflow or not for querying)

Cause

ORA-24347: Warning of a NULL column in an aggregate function

is a warning reported from the Oracle RDBMS when trying to use aggregation functions like SUM or AVG on records containing NULL values.

In this case, the customer's database view definition included a SUM:

create or replace view xx_ar_cust_ref_credit_sum_v as

select

addr.orig_system_reference orig_sys_ref_acct_id

...

 sum(credit_data.overall_credit_limit) overall_credit_limit,

 sum(credit_data.balance_due) balance_due
...

Solution

Changing the database view definition, using NVL to handle null values was suggested and confirmed to resolve this.

Please invoke Oracle Database Support or Consulting (billable) if you need assistance implementing this for your specific view definition.

Test your view definitions thoroughly before using them in a production environment to avoid database errors like this, and be aware that database views in EBCs cannot be used to update records (as the RDBMS will prevent updating records via database views).

http://www.dbasupport.com/forums/archive/index.php/t-17208.html

describes similar NULL value related errors and has examples using NVL - if this document should no longer exist

try searching for

ORA-24347 and NVL

on the Web.

References

NOTE:535155.1 - EBC generates ORA-24347 error


http://www.dbasupport.com/forums/archive/index.php/t-17208.html

Applies to:

Siebel System Software - Version: 7.7.2 [18325] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000


Product Release: V7 (Enterprise)


Version: 7.7.2.6 [18372]


Database: Oracle 9.2.0.6


Application Server OS: Microsoft Windows 2000 Advanced Server SP 3


Database Server OS: IBM AIX 5L 5.1





This document was previously published as Siebel SR 38-3205131191.

Symptoms

Customer reported the following:





We have come across an error in our Siebel production environment when running a query.


The error message is,





"An error has occurred executing a Sql statement.


Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)


ORA-00600: internal error code, arguments: [qkabix], [0], []. [], []... "





I have referenced on the My Oracle Support, the Siebel Error Message information on SBL-DBC-00105.


I did the spooling, found the SQL causing problems and then I ran the SQL in sqlplus. The SQL ran fine without error.





One thing I did try was changing the InsensitivityFactor to 1 rather than 2. And this did resolve the problem.





Is the case insensitivity factor a valid reason for this error we see?


Is there anything else I can do to confirm the cause of this problem?

Solution

For the benefit of other readers:



Customer encountered ORA-600 [qkabix]





1. Is the case insensitivity factor a valid reason for this error we see?


-- No. Setting InsensitivityFactor may not be a permanent solution.





2. Is there anything else I can do to confirm the cause of this problem?


The ORA-600 error with qkabix should appear in Oracle alert and/or trace files when the query ran and return with error.





For further information on ORA-600 [qkabix], please do a search in Oracle metalink using “ORA-600 [qkabix]”. This error is reported when Oracle fails with rowid-to-bitmap conversion when running a select statement with lots of joins and tables involved. Possible workaround is to set "_B_TREE_BITMAP_PLANS" = false.





_B_TREE_BITMAP_PLANS enables creation of interim bitmap representation for tables in a query with only binary index(es). Default value is FALSE in Oracle 8i and TRUE in Oracle 9i or later.





Siebel should work with _B_TREE_BITMAP_PLANS = FALSE with no issues since Siebel has been tested with Oracle 8i – prior version. This is supported so please feel free to set this to false.

Applies to:

Siebel Tools - 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: Oracle 9i


Application Server OS: Microsoft Windows 2000 Advanced Server SP 4


Database Server OS: Sun Solaris 8





This document was previously published as Siebel SR 38-1212395721.





""Checked for Relevance on 03-Dec-2010""

Symptoms

We have the business requirement to be able to search for all employees attached

to an activity without having to type "EXISTS" in the "Owned By" MVF. After setting the "Use

Primary Join" flag to "FALSE" for the Action/Employee MVL in BC Action, an SQL error occurs when

navigating to the Activities Screen.

Cause

The behavior described by the customer is reproducible using a standard Siebel environment. The steps are the following:





1. Using Siebel Tools set the 'Use Primary Join' property of the

'Employee' MVL to FALSE (Unchecked) in 'Action' BC. Compile the BC.





2. Launch Siebel Call Center application:


> The Home Page cannot be displayed and the following error occurs:


- - -


We detected an Error which may have occurred for one or more of the following reasons:





An error has occurred executing a Sql statement. Please continue or ask

your systems administrator to check your application configuration if

the problem persists.(SBL-DBC-00105)


- - -





NOTE: The Home page contains "My Activities" applet.





The same error occurs if we try to access any view in "Activities" screen.





By spooling the SQL we can see the cause of the error that the following SELECT statement:


- - -


SELECT


      ...


      T1.ACT_ALARM_FLG,


      T1.ACT_APPT_START_DT,


      T1.ACT_TODO_PLNSTRTDT,


      T1.ACT_TODO_PLNEND_DT,


      T1.ACT_APPT_REPT_FLG,


      T1.ACT_APPT_RPTEND_DT,


      T1.ACT_EVT_STAT_CD,


      T1.ACT_CAL_DISP_FLG,


      T1.ACT_TEMPLATE_FLG,


      T1.ACT_CAL_TYPE_CD,


      ...


   FROM


       SIEBEL.S_EVT_ACT T1


...


- - -





Indeed these columns do not exist in S_EVT_ACT table. They are

denormalized columns in S_ACT_EMP table. This table is the intersection

of link 'Action/Employee', the link used by the 'Employee' MVL.





Please note that a similar behavior is reproducible with other MVLs in

other BCs, e.g. 'Position' and 'Organization' MVLs in BC 'Account' and

'Contact' BCs. The same error will be encountered when accessing

"Accounts" or "Contacts" screen.





This behavior occurs because these MVLs are visibility MVLs. 'Employee'

MVL, for example, is involved in the visibility settings of 'Action' BC.

This one has indeed the following BusComp View Mode:


- - -


Name: Personal


Owner Type: Person


Visibility MVField: Owned By


Visibility MVLink: Employee


- - -



In fact setting Use Primary Join property to FALSE for visibility MVLs

is not supported. Visibility MVLs need to have a primary id defined and

primary join should be TRUE. The primary join has a special meaning for

visibility MVLs.





BUG 10474574 has been logged asking to document this

matter in Siebel Tools Reference and Object Types Reference guides.

Solution

The suggestion to achieve the customer's requirement is to create a new MVL based on the same link as the 'Employee' MVL and a MVF based on this MVL. This new MVL will have its 'Use Primary Join' set to FALSE and the new MVF will be used in the UI for the queries without the EXISTS operator.

References

BUG:10474574 - IT SHOULD BE DOCUMENTED THAT SET 'USE PRIMARY JOIN' TO FALSE FOR VISIBILITY MVLS IS NOT SUPPORTED

Applies to:

Siebel Tools - Version: 7.7.2 [18325] to 8.1.1.3[21219]   [Release: to V8]
z*OBSOLETE: Microsoft Windows Server 2003


Product Release: V7 (Enterprise)


Version: 7.7.2.1 [18353]


Database: Oracle 9.2.0.6


Application Server OS: Microsoft Windows 2003 Server


Database Server OS: Sun Solaris 9





This document was previously published as Siebel SR 38-2849725171.





"" Checked for Relevance on 17-SEP-2010 ""

Symptoms

SBL-DBC-00105

Customer created an external view on SIEBVIEW schema (v$activity_follow_ups_ebc) in order to join two types of Activity rows (SQL UNION) - old ones that have no parent activity reference, and new ones that have this reference. The view is working fine from SQL Navigator, and there are no errors in any type of direct SQL Queries that customer made.

An EBC has been created based on this view to display the date in a List Applet that was inserted on Acitivity List view.

When customer opens this view, the following error occur:
"An error has occurred executing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)".

If customer changes the view, and select only the new group of records, the EBC is working fine and he can see records from GUI. But if he puts in the view only OLD records, he is getting this error.

Cause

The customer's view definition for the External Business Component (EBC) included a restriction on a date:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
... act.created > '17-Sep-2001' -- to eliminate activities created before Siebel roll-out
...

The view could be accessed successfully from a third party tool, but a select statement generated from the Siebel Application caused an SQL error.

Solution

As the date formatting depends on the session's NLS (National Language Support) settings, we suggested an adapted version that would work independent from the current NLS setting:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
act.created > (to_date('17.09.2001','DD.MM.YYYY'))

The customer changed the view definition accordingly and no more SQL errors occurred when accessing the EBC from the Siebel application.

Please note that the to_date function above and its syntax is specific to Oracle RDBMS.

Applies to:

Siebel Tools - Version: 7.7.2 [18325] to 8.1.1.3[21219]   [Release: to V8]
z*OBSOLETE: Microsoft Windows Server 2003


Product Release: V7 (Enterprise)


Version: 7.7.2.1 [18353]


Database: Oracle 9.2.0.6


Application Server OS: Microsoft Windows 2003 Server


Database Server OS: Sun Solaris 9





This document was previously published as Siebel SR 38-2849725171.





"" Checked for Relevance on 17-SEP-2010 ""

Symptoms

SBL-DBC-00105

Customer created an external view on SIEBVIEW schema (v$activity_follow_ups_ebc) in order to join two types of Activity rows (SQL UNION) - old ones that have no parent activity reference, and new ones that have this reference. The view is working fine from SQL Navigator, and there are no errors in any type of direct SQL Queries that customer made.

An EBC has been created based on this view to display the date in a List Applet that was inserted on Acitivity List view.

When customer opens this view, the following error occur:
"An error has occurred executing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)".

If customer changes the view, and select only the new group of records, the EBC is working fine and he can see records from GUI. But if he puts in the view only OLD records, he is getting this error.

Cause

The customer's view definition for the External Business Component (EBC) included a restriction on a date:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
... act.created > '17-Sep-2001' -- to eliminate activities created before Siebel roll-out
...

The view could be accessed successfully from a third party tool, but a select statement generated from the Siebel Application caused an SQL error.

Solution

As the date formatting depends on the session's NLS (National Language Support) settings, we suggested an adapted version that would work independent from the current NLS setting:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
act.created > (to_date('17.09.2001','DD.MM.YYYY'))

The customer changed the view definition accordingly and no more SQL errors occurred when accessing the EBC from the Siebel application.

Please note that the to_date function above and its syntax is specific to Oracle RDBMS.