Siebel Administration >  Siebel has errors- where can I start analysing?

Siebel has errors- where can I start analysing?

Very often we have errors in Siebel. Maybe an account has an error or an opportunity is in the wrong status.
How can we start debugging where Siebel has errors. I would suggest that we start with these SQls and steps.

1. Tables s_srm_data and s_srm_request have information about how this object (e.g. Opportunity or Account or Order or others)
was processed.

select sr.action_id, sr.COMPLETION_TEXT, sd.data_val , sr.resp_text
from
siebel.s_srm_request sr , siebel.s_srm_data sd
where sr.row_id = sd.par_id
and (sd.data_val like '%row_id of Account/order/opportunity%' or sr.resp_text like '%row_id of Account/order/opportunity%')
and status = 'ERROR';

2. s_srm_task_hist has information about log files, server names, process ids and task ids for crashes and disconnections
They do not have links to the object (e.g. an Account or sub account)

SET DEFINE OFF;
alter session set NLS_DATE_FORMAT='dd/mm/yyyy hh24:mi:ss'; -- this will show the hour , minute and seconds in time fields.

select created, last_upd, srvr_end_ts, SRVR_PROC_ID_VAL, SRVR_PRTTASK_IDVAL,
srvr_comp_name, srvr_error_msg,
srvr_host_name , srvr_logfile_name, srvr_task_type,srvr_user_name
from siebel.s_srm_task_hist where srvr_status in ('ERROR','error')
order by created desc;

3. Check the audit trail from the GUI of the object.

4. This SQL will show errors with BI Publisher reports.

select X.ROW_ID
,X.CREATED
,X.CREATED_BY
,X.NAME
,X.BOOKMARK_VAL
,X.STATUS_CD
,X.ERROR_CD
,X.ERROR_MSG
,X.QUERY_STRING
from SIEBEL.S_XMLP_REPOUTPT X
where X.STATUS_CD='Error'
and (X.QUERY_STRING is not null or X.BOOKMARK_VAL is not null);

5. s_escl_req is the table that processes Objects. If there are several rows in this table that are not automatically deleted,
that suggests that some component is not correctly working.

select * from siebel.s_escl_request;

the column bt_row_id is the row id of the object being processed. The column rule_id
is the row id of the Workflow policy that ius running.
It is possible that one or more rows in this table are creating the problem.
One Opportunity might have corrupt data and is blocking Siebel from processing other rows in this table.