LoyEngineBatch Component Remains In "Not Online " State as Table Owner Is Not Included In The SQL (Doc ID 2261377.1)

Last updated on MAY 02, 2017

Applies to:

Siebel Loyalty Engine - Version 16.10 [IP2016] to 16.10 [IP2016] [Release V16]
Information in this document applies to any platform.

Symptoms

Customer is seeing an issue with LoyEngineBatch component that remains in "Not Online " state.

The following sql-statenemt is seen in the LoyEngineBatch.log file when trying to start the component:

SELECT /*+ ALL_ROWS */
  T1.CONFLICT_ID,
  T1.LAST_UPD,
  T1.CREATED,
  T1.LAST_UPD_BY,
  T1.CREATED_BY,
  T1.MODIFICATION_NUM,
  T1.ROW_ID,
  T1.SYS_PREF_CD,
  T1.VAL
  FROM
  .S_SYS_PREF T1
  ORDER BY
  T1.SYS_PREF_CD

Note that the schema name is missing in front of
.S_SYS_PREF T1 and this seems to cause the issue that the component can not be started.
E.g. it should be for example SIEBEL.S_SYS_PREF T1

Changes

 New server datasource had been created

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms