SBL-DBC-00104: Error retrieving next record from the database.

Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.




Symptoms

Customer was running a batch job to deactivate workflows with following SQL:

SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')

This generates the following error in the EAIObjMgr log:

SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred

ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All

Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.

Running the SQL directly on the database returns 85 rows with no problems.



Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution


This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)

This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.














Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.




Symptoms

Customer was running a batch job to deactivate workflows with following SQL:

SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')

This generates the following error in the EAIObjMgr log:

SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred

ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All

Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.

Running the SQL directly on the database returns 85 rows with no problems.



Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution


This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)

This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.














Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.




Symptoms

Customer was running a batch job to deactivate workflows with following SQL:

SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')

This generates the following error in the EAIObjMgr log:

SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred

ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All

Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.

Running the SQL directly on the database returns 85 rows with no problems.



Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution


This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)

This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.


















Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.




Symptoms

Customer was running a batch job to deactivate workflows with following SQL:

SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')

This generates the following error in the EAIObjMgr log:

SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred

ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All

Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.

Running the SQL directly on the database returns 85 rows with no problems.



Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution


This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)

This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.


















Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.




Symptoms

Customer was running a batch job to deactivate workflows with following SQL:

SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')

This generates the following error in the EAIObjMgr log:

SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred

ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All

Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.

Running the SQL directly on the database returns 85 rows with no problems.



Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution


This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)

This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.


תגובות

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

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

Profile Attributes and Open UI

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

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

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

SBL-SVC-00150

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