Search This Blog

SBL-DAT-00415: An internal error has occurred due to an invalid definition for id business component.

Applies to:

Siebel Tools - Version: 7.5.3 [16157] to[21219] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

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

"" Checked for Relevance on 09/11/2010 ""


We have a problem inserting the record through Application or locking the project through Tools we get Error.

Updating inserting and deleting is not happening through the Application. It is working through Query Analyzer.

Our Application DBA has checked the SSE_ROLE permissions and looks good for all users.

Attached the Screen-Print.

We have worked with our DBA’s and noticed the application try to write the Record but Rollback the transaction.

We need your assistance to fix the issue.


Customer’s Siebel Application started behavior as Read only. User was able to login and navigate within the application but users could not Insert, Update and delete records.

Siebel Application 7.5.3 [16157] was using MS SQL server database. The database hosted 7 instances of Siebel Application database and for all of this database user experienced read only behavior

When user tried to update records on UI the experienced following messages

a) An error has occurred writing a record.

Please contact or ask your system administrator to check your application configuration if the problem ppresists . (SBL-DBC-00111)”


b) “An internal error has occurred due to an invalid definition for id business component.

Please ask your system administrator to check your application configuration.(SBL-DAT-00415)”


This issue was resolved with the help of MS Server DBA and root case was that DB instance level options ANSI_PADDINF and NOCOUNT were enabled. After DBA disabled them issue was resolved.

Siebel Software Support

Keywords : Readonly , Read-only , No-Insert , No-Delete , No-Update

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i

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


SBL-DAT-00415, SBL-DBC-00108

I've installed a basic Standard system at 7.7.2

It comprises a Gateway, Siebel Server. Database and Web Server.

The install was uneventful with no apparent errors in the logs. However when I logged on the system via a thick client to enter the system key I got the following error.

"Error reinit license key".

I logged on using Siebel Tools which accepted the license key.

When I log onto the system I get a variety of errors, attached some screenprints. All these errors seem to point to a database problem. I've gone through the database install logs and can find nothing obvious. I have reinstalled the database and am getting the same problems again.

What is interesting is the screenprint of the problem within System Preferences. When attempting to alter UTC the error appears to think the field is a Month field ?

Variety of error messages from the database including

An error has occurred getting a new row id for the new record.
Data value out of range

There is nothing obvious in either the Siebel logging or the Oracle logging.

I've checked Supportweb for the variety of messages and have been unable to find anything that fits.

Please advise ?

Many thanks


Message 1


The following errors appeared while creating/modifying user:

ORA-25137: ORA-25137 Data value out of range

The following errors appeared while modifying the Universal Time Coordinated to FALSE:

ORA-01843: not a valid month
while updating the UTC on preferences


Customer resolved this issue by adjusting the SqlStyle of the .cfg file. It was set to db2, while their database is Oracle. Setting it to Oracle resolved the issue.

Thank you.

- Siebel Technical Support -

Applies to:

Product Release: V7 (MidMarket)
Version: 7.5.3 [16157] MME
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: IBM AIX 4.3.3

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



I was asked to submit a new SR after submitting an SR when the 7.5.3 Repository Update failed.

Basically, this was a prior failed implementation, and I was brought in to clean it up and help this client get into production.

Recently, as part of a corporate initiative, the Siebel database was relocated to an IMB Regattat machine, and upgraded from Oracle 8.1.7 to Oracle 9.2.

I will confirm these exact actions with the DBA, but I believe that he created a new table space on the new database server, and then bulk copied the entire 8.17 db into the new 9.2 db.

Now the application will not work correctly, and throws out the following errors depending on the action performed:

and others.

How do I troubleshoot this issue and what are the possible resolutions?

Currently, our entire development effort has come to a halt, as well as the 7.5.3 Maintenance Release installation process.



Message 1

For the benefit of other users:


In the Support Database Server Platforms section of the Siebel System Requirements and Supported Platforms document, it is not clear exactly how to configure the Oracle environment.

On Page 7-4, the Vendor is Oracle 9i Enterprise Server, Version is, there is a footnote in the Code Page column stating that customers should move AL32UTF8 as soon as possible.

So, according to the documentation, the new Oracle environment was setup with AL32UTF8 as the NLS_CHARACTERSET. For some reason, Oracle suggested using AL16UTF16 for NLS_NCHAR_CHARACTERSET, which the DBA has set. The application can startup, log in, query, etc, but cannot add or delete records.

So I guess our questions are:

Which code page should be used in order to successfully apply the Maintenance Releases required to take the application from v7.5.2.200 running on Oracle 8.1.7, to v. running on Oracle


Regarding your questions about the Oracle character set -- switching from WE8MSWIN1252 to AL32UTF8 is not recommended and not supported. AL32UTF8 is a Unicode character set, while WE8MSWIN1252 is non-Unicode -- the Unicode database objects for the Siebel Database are created differently than the non-Unicode database objects, so changing from non-Unicode to Unicode requires a complete reinstallation and recreation of the database objects.


Message 2

Resolution page 2:

The note you found in the Siebel System Requirements and Supported Platforms document regarding the AL32UTF8 character set is meant for customers who have a Unicode installation on the UTF8 character set. Oracle is phasing out the UTF8 character set and recommends that all Unicode customers move to AL32UTF8.

WE8MSWIN1252 is still a supported character set for Oracle 9i. Our recommendation is to return the database to the WE8MSWIN1252 character set. It may be necessary to re-export and re-import the data from your Oracle 8i database, because some of the data may have been converted when imported into the Unicode database on Oracle 9i, and you may experience data corruption if you just change the character set back without re-exporting and re-importing the data.

Regarding the NLS_NCHAR_CHARACTERSET value -- this is a database parameter which does not affect Siebel in any way. The parameter which affects Siebel is the NLS_CHARACTERSET parameter.

After the databse was rebuilt with the proper characterset, everything seems to be working correctly.


Thank you,
Siebel Technical Support

No comments:

Post a Comment