SBL-DAT-60176: Unexpected end of stream '%1' at position %2.

Applies to:

Siebel Tools - Version: 8.1.1 [21112] - Release: V8

Information in this document applies to any platform.

Symptoms

When querying for certin audit trail records, application is throwing error.

-06-23 16:36:25 (sqllog.cpp (774)) SBL-DAT-60176: Unexpected end of stream '2*C14*NAME2*N161*AEG Mktg-Technical Writing - TUV Certification press release2*O132*AEG Mktg-Technical Writing - -' at position 115.
Error type2
=======
ObjMgrLog Error 1 0000ab6b4a11707b:0 2009-06-24 10:33:37 (sqllog.cpp (671)) SBL-DAT-60173: A number at position 3*C164*NAME11*PREV_ACT_ID16*TODO_PLAN_END_DT7*OPTY_ID13*APPT_START_DT7*TODO_CD6*X_AREA11*TODO_DUE_DT12*TARGET_OU_ID13*COMMENTS_LONG10*X_SUB_AREA8*LOC_DESC11*EVT_STAT_CD6*SRC_ID18*TODO_PLAN_START_DT11*OWNER_LOGIN3*O1630*NA-TEST WORKSHOP-Natick MA-2000*19*2008-11-21 16:00:000*19*2008-12-01 05:00:0015*Stage Execution18*Natick - Marketing0*0*0*0*0* 11*Not Started8*1-8H52OH19*2008-11-21 15:00:008*CSARKEES3*N160*0*0*0*0*0*0*0*0*0*0*0*0*0*0*0* is expected in the log stream '346'.

Customer already know the issue is due to corrupted data. Now they have a BS to correct the data. However this BS is not working because of the bad data- not moving to the next record.

Cause

because of the error, NextRecord not moving to the next record

Solution

Regarding scripting, igoring the bad record and continuing with the NextRecord, you could try using Try…Catch block inside the while loop.

while(isAuditRecord) {
// do something
try {
isAuditRecord = NextRecord();
}
catch(e) {
// skip broken record:
isAuditRecord = NextRecord();
}
}

Regarding information on the errors, no further information could be found out, Documentation Defect 12-1U0AX8T was created.

 

Thank you

References

BUG:12-1U0AX8T - QUERYING CERTAIN 'AUDIT TRAIL ITEMS' THROWING ERROR