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.