SBL-DBC-00111: An error has occurred writing to a record.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
This error message can occur when a SQL statement, usually the UPDATE, INSERT, or DELETE statement, was not executed successfully against the database server. In order to troubleshoot the error and get to the root of the behavior, it is important to review the SQL statement that is causing the error. Below are the different ways to capture the SQL statement:
1. Start by spooling the SQL, using the /s option, to determine 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 Technical Note 91 for more information.
2. 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 FAQ 2116 for more information.
3. Refer to FAQ 1322 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. It may be related to a database specific defect. The database may not contain the latest patchset.
2. If you are using DB2 for your server database, check if the following error is generated after the SBL-DBC-00111 error in the log file created with tracing set on the client:
[IBM][CLI Driver][DB2/SUN] SQL0101N The statement is too long or too complex.
This error may occur when you create a new record and undo the record. This SQL0101N error is a DB2 specific error with the length of the SQL query. Although the sql is generated by the Siebel application, the limitation is coming from the DB2 database.
3. This error arises when there is discrepancy between the logical schema in the Siebel repository and physical schema in the actual database. There may be a difference in the field type and length at the business component field definition versus the table column definition.
4. A common cause is when deep copying a business component with Multi-Value Links (MVL) having No Copy set to False.
5. When you right-click and select Columns Displayed in the Quotes > Attachments view for a newly created attachment without entering any information for the new attachment, this error will appear instead of the error, “Name is a required field”.
6. When merging Account records from Site Map > Administration > Data Quality > Duplicate Account applet, this error may occur. The cause is if the source field of a join is a system field.
7. The database column length may not be sufficient to store a value of the field or the field value’s text length exceeds the supported database column length. The length of the Name field on a Dynamic Hierarchy is 30 and the GenerateHierarchy method defaults the User Id + time stamp into the Name field. The time stamp, including any spaces is 22, thus the user Id is not supposed to be longer than 8 characters. If you are updating a column of type DTYPE_CURRENCY with more than 22 digits, this may also occur.
Corrective Action
1. If you are encountering the “ORA-01843: not a valid month” error following this error message, this is an Oracle database defect 3138618, which has been fixed in the patchset 9.2.0.6.
If you are encountering the “ORA-02248: invalid option for ALTER SESSION” error following this error message, an option was used with ALTER SESSION that was not supported by the version of database used.
2. If the SQL0101N error occurs using the vanilla srf and only when connected to your server database, check if triggers are active in your server database. If triggers are active in your server database, more memory is needed by DB2 to process the statement because the trigger is effectively executed with the statement.
Ensure that the STMTHEAP is set to the value recommended by Siebel Bookshelf > Siebel Server Installation Guide for UNIX > Creating the DB2 Universal Database for Windows and UNIX > DB2 Database Configuration Guidelines. The suggested setting is at least 8192. You may need to continue increasing the STMTHEAP size up to 40960 to accommodate having triggers active in the server database.
3. 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.
If there is a difference in the field type and length at the business component field definition versus the table column definition, refer to Technical Note 345.
4. Keep the No Copy property of the MVL to TRUE.
No comments :