Diagnosing ODI package errors for Oracle Knowledge Analytics
(Doc ID 1961796.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Knowledge - Version 126.96.36.199 and later
Information in this document applies to any platform.
ODI batch processing will sometimes fail. There are ways to check the ODI processes - packages to see how they are running. After a patch they could fail, there could be failures from testing data at startup, and something can happen to the resources needed by ODI that could cause the packages to fail.
If a patch was recently installed please verify that all the steps of the analytics patch were run correctly and successfully. Support will ask for documentation of the patch steps. Support does not debug missing patch steps. It is the customers responsibility to install the patch correctly.
The ODI component is a set of packages that run internally to ODI to move data from the staging table DW_STAGE.DW_STG_DATA table to the reporting tables. These tables can be in the same database or different databases.
The Analtyics Admin Guide is located here.
Make sure that error emails are set up to go out when there are completions errors successes as needed.
https://docs.oracle.com/cd/E38112_03/ok_8.6_analytics_admin_gd.pdf pg 24 Configuring Email Notification for Event Processing and Data Aggregation
Some important points to consider. A email notification process can be set up to monitor the ODI behavior. It is recommended that you verify that the email process from the ODI is running correctly. This will require access from the ODI server to your SMTP server. Settings are stored in the DW_WORK.ANALYTICS_PROPERTIES table. (If you have combined DW_WORK and DW_REPORTING, then it will be in the DW_REPORTING schema)
Trouble shooting Tips:
If you see that the JMS Queues are receiving messages, but no data is making it to DW_STAGE.DW_STG_DATA, then verify that your Deployments are in an active state. Queues can be found in the weblogic admin console at
Domain Structure -> Services -> Messaging -> JMS Servers -> <Choose a JMS Server from list> -> Monitoring Tab.
If the data is making it to the staging tables then it is time to look at the ODI processing.
If the ODI processing is going unusally slow it could be because there is old data in DW_STAGE.DW_STG_DATA or the resource allocation for ODI is too low.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|General steps for diagnosing package failures, clearing out old information and restarting packages.|
|Some conditions that may apply and notes that may help:|