SBL-DAT-60171: End of the log stream is reached.

Applies to:

Siebel Tools - Version: 8.0 SIA [20405] to 8.1.1 [21112] - Release: V8 to V8
Information in this document applies to any platform.

Symptoms

On accessing Audit Trail records or navigating through Audit Trail records receiving error: SBL-DAT-60171: End of the log stream is reached.

Following error  has been found in the log file:
ObjMgrLog Error 1 000000064a136020:0 2009-05-20 10:17:49 (sqllog.cpp (671)) SBL-DAT-60171: End of the log stream is reached.

It is occurring when the Method GetAuditTrail of the Business Service CIS General Tools  which is called via a shell script is accessed.

Cause

Bug 12-1NSKPEZ (Audit Trail Error in log fiels in 8.0) has been raised to report the issue. It seems related to database since it is coming from "sqllog.cpp".

Solution

The Change Request is still under investigation. If the error does not harm or stop any functionality, the error can be ignored as per Change Request comments. 

Applies to:

Siebel CRM - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

OM logs show following errors prior to crash:

(sqllog.cpp (671)) SBL-DAT-60171: End of the log stream is reached.ObjMgrLog Error 1
(sqllog.cpp (671)) SBL-DAT-60171: End of the log stream is reached.DBCLog DBCLogError 1

Oracle RAC is failing over...DBCLog DBCLogError 1
Failover type is SELECTDBCLog DBCLogError 1
Oracle RAC failover ended successfullyDBCLog DBCLogError 1
Oracle RAC is failing over...DBCLog DBCLogError 1
Failover type is SELECTDBCLog DBCLogError 1
Oracle RAC failover ended successfully


- crash.txt shows crash on Oracle client dlls when OM task tries to re login on the killed DB session.

- CALL STACK -
kernel32 RaiseException()
orageneric11 slcra()
orageneric11 skgdbgcra()
orageneric11 kpeDbgCrash()
OraClient11 xaolog()
OraClient11 kpufhndl()
OraClient11 OCIHandleFree()
OCI OCIHandleFree()
sscdo90 CSSOraSqlCursor::~CSSOraSqlCursor()
sscdo90 SSASqlObjLogon() +0x1c5
sscfdm CSSLockSqlCursor::~CSSLockSqlCursor()
sscfdm CSSDbConn::BeginTransaction()
sscfdm CSSLockSqlCursor::Delete()
sscfdm CSSDbConn::CacheSqlCursor()
sscfdm CSSDbConn::CachePendingCursors()
sscfdm CSSLockDbConn::Unlock()
sscfdm CSSDbLock::~CSSDbLock()
sscfdm CSSSqlCursor::NextRecord()
sscfdm CSSSqlObj::AddListRow()
sscfdm CSSSqlObj::NextRecord()
sscfom CSSBusComp::SqlNextRecord()
sscfom CSSBusComp::Home()
SSCASWBC CSSSWEFrame::ExecuteQuery(


- FDR shows the the thread crashes when trying to do "Sql Cursor Destruction"


FdrSub_FDR_CRASH ** CRASHING THREAD **
FdrSub_FDR_CRASH ** CRASHING THREAD **
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_FDR_CRASH ** CRASHING THREAD **

Changes

Customer developed new Script that kills session for long running SQL:

select 'REM SID: '||a.sid||' SERIAL#: '||a.serial#||' SQL ID: '||b.sql_id||chr(10)||' /*+ '||sql_fulltext||' */' from v\$session a, v\$sql b where b.address = a.sql_add
ress and program = 'siebmtshmw.exe' and command = 3 and status = 'ACTIVE' and last_call_et >= 300 and username = 'SADMIN';

select 'alter system kill session '||''''||sid||','||serial#||''''||';' from v\$session where program = 'siebmtshmw.exe' and command = 3 and status = 'ACTIVE' and last_c
all_et >= 300 and username = 'SADMIN';

Cause

When Kill SQL script runs for a specific DB session the OM task seems to treat this as RAC failure and OM tries to relogin and continue SQL execution when the crash occurs on the Oracle client dlls.

Solution

Hence suggesting turning off Kill SQL script.
Monitor the OM logs for next two hours and confirm if there are still these "RAC failure..." errors reported.

This resolved the RAC failure errors and OM crashes.

Applies to:

Siebel Tools - Version: 8.1.1.3[21219] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Created a new calculated field for audit trail applets and when querying on this field an error(SBL-DAT-00471) is returned.

Cause

Calculated value used: LookupValue('CT_AUDIT_CAPTION', [Field]).
This query fails in Audit Trail context because Audit Trail Item 2 is a VBC.

Solution

As a workaround, display the translated and the original field names side by side so when the users want to query for a specific field they can use the original field name for this query.

The following script can be used to stop querying on certain fields:


function BusComp_Query ()
{
/*------------
Description: Added to stop querying on certain field, user props only stop wildcard queries
------------*/
try
{
var sSearchQuery = this.GetSearchExpr();

if(sSearchQuery.indexOf("CT Field Caption") != "-1")
{
TheApplication().RaiseErrorText("Querying on 'Field' is currently not possible. Please query on 'BC Field' which is available from Columns Displayed.");

}
}
catch(e)
{
throw e;

}
}

References

BUG:12-1NSKPEZ - AUDIT TRAIL ERROR IN LOG FIELS IN 8.0
NOTE:985883.1 - Navigating through Audit Trail Records throw Error SBL-DAT-60171 (End of the log stream is reached)
NOTE:477101.1 - Can you translate the field names displayed in an Audit Trail Item list applet?
NOTE:728852.1 - Error querying the Id field from the 'Audit Trail Item 2' BC
NOTE:820735.1 - Property "Disable Search" on Business Component Field
NOTE:780618.1 - Disable Search User Prop returns error msg with BusComp Field name and not U