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

Hello All,

Recently i faced an issue where in a view was not loading and error "SBL-DBC-00104: Error retrieving next record from the database" was appearing.
In detailed log also not much of the information was given ,
"SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0000a9f7572e1aa8:0 2016-08-25 18:03:38 ORA-24345: A Truncation or null fetch error occurred"

after some debugging i narrowed down the scenarios where this type of error could occur.

• Some wrong query is being run in back end, which is not fetching any record.
• Some wrong or Null value is there in any column which is causing the Select selection which is generated at view load time to fail
• Some columns attribute is being wrongly defined i.e. Length of column is Different then what is maximum declared at table level.
• Some existing column is mistakenly used again

if found below articles very helpful to make me sure that i was in the right direction.(thank you respective authors for such nice articles)

http://www.error-codes.info/2011/02/sbl-dbc-00104-error-retrieving-next.html

http://crmcog.com/error-retrieving-next-record-in-siebel/


http://siebelmantra.blogspot.qa/2009/01/error-retrieving-next-record-from.html

i further debugged and the root cause in my case was ,

Some existing column is mistakenly used again

in the course of development we used a already used extension column to store some custom value and this column was appearing in the select statement of view load, there was some conflict because of this and it resulted in error.

After changing the column to a new one and clearing any previous value in the columns solved my issue.

so to summaries,

• whenever using any existing extension column make sure its not already used
• always make sure length property of column and BC level are same
• In any error situation the best approach is to first generate Spool and read the Select statement that is failing, most of the issue can be resolved by debugging this SQL statement.

Related Error : "SBL-DBC-00105: An error has occurred executing a Sql statement" ,caused by difference in Physical Schema and Logical Schema, can be removed after Applying DDL from Siebel Tools to the changed/modified table.

Hope it was helpful..