OBIEE 11G - Agent Diagnostic (log)

> Reporting and Data Access Tools > Oracle Business Intelligence (OBIEE/Siebel Analytics)

1 - About

How to diagnostic a failed agent in 11G.

3 - Steps

3.1 - Get the job Id

You can get the job id from the Job Manager or from the bi_platform schema.

From the bi_platform schema.

SET define off;
SELECT * FROM
(
  SELECT 
    job.job_id AS job_id,
    (SELECT job_param  FROM s_nq_job_param WHERE script_type = 'iBot' AND relative_order = 1 AND job_id = job.job_id) AS job_path, 
    'Agent-'|| job.job_id || '-' || last_instance.instance_id || '.*' AS log_pattern,
    job.name AS job_name,
    last_instance.instance_id,
    last_instance.begin_ts,
    last_instance.end_ts,
    round((last_instance.end_ts - last_instance.begin_ts)*24*60,2) AS instance_duration_min,
    last_instance.exit_code
  FROM s_nq_job job LEFT OUTER JOIN
  (SELECT * FROM (
      SELECT ROW_NUMBER() OVER (partition BY job_id ORDER BY instance_id DESC) AS ROW_NUMBER, instance.* FROM s_nq_instance instance
    )
    WHERE ROW_NUMBER = 1 ) last_instance ON last_instance.job_id = job.job_id
)
WHERE 
job_path LIKE '/shared/%'
ORDER BY job_path;
Advertising

3.2 - Get the logs of failed agents

  • The agent error and debug log files are written as separate files for each agent instance that fails to execute. Actually, there is an enhancement bug to get more info: REQUEST ADDITIONAL LOGGING FOR AGENTS (bug 21171594)
  • The presence of an error log does not necessarily mean that an agent failed completely. For example, suppose an agent delivers content to multiple e-mail addresses. If some addresses are invalid or the mail server is down, then an error log is generated for the agent.

The location for agent log files is specified in the instanceconfig.xml file for the Oracle BI Scheduler. Normally, fmw_home/instances/instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1

The log file name has the following format:

Agent-JobID-InstanceID.xxx

where:

  • Agent is the prefix for all agent log files.
  • JobID is the Oracle BI Scheduler job identifier for the agent.
  • InstanceID is the Oracle BI Scheduler instance identifier for the agent.
  • xxx is the file extension:
    • .err for agent error log files.
    • .log for debug log files.

3.3 - Verify the run of the analytics

SELECT
  saw_src_path,
  ROW_COUNT,
  ROUND((CAST(acct.end_ts AS DATE)-CAST(acct.start_ts AS DATE))*24,2) AS duration_hour,
  acct.*
FROM
  s_nq_acct acct
WHERE
  saw_src_path LIKE
  '/path'
AND start_dt  > sysdate - 1
-- AND user_name = 'agent user'
ORDER BY
  start_ts DESC;

4 - What if the (mail) agent is successful

To get more information, you can:

  • Check the log of the mail server
  • Check the mail of the recipient.
  • Add another recipient.
  • Add a channel to dump the file to the local file system. It will show (/ or not) that the agents has run successfully, if you get the content on the local file system.
  • Check the mailbox of the Sender

Advertising

5 - Documentation / Reference