Skip Navigation
Expand
Cached data used in reports
Answer ID 1917   |   Last Review Date 07/22/2019

Which database tables and standard reports are cached?

Environment:

Analytics, Automatic Caching
All versions

Resolution:

There are two different types of report caching. The first is automatic and has to do with the underlying data of which your database is constructed. This is the feature discussed in this answer.

The alternate option is caching you can schedule.  Refer to Answer 8997: Cache reports and dashboards at scheduled times for more information on that option.

When using the reports feature in your Oracle B2C Service application, you should understand caching and how it affects your report data. To have access to accurate report data quickly, the agedatabase utility should be scheduled to run every night. When agedatabase runs, it will cache much of the report data to prepare for the following day’s reporting needs. This enables reports to be generated more quickly -- especially those reports that display a large amount of data.

Many of the reports are generated solely on cached data. Some reports, however, produce real-time results when the report is generated. Cached data will remain constant throughout the day and will not be updated until the next day. For this reason, reports using cached data will not have data for the current date. Real-time data may change as incidents are added, updated, or deleted from your database. Understanding which reports use cached or real-time data is essential to accurately interpret your reports.

Some database tables that have cached data are:

  • inc_performance
  • session_summary
  • stats (some fields)
  • opp_performance
  • opp_snapshots
  • revenue_snapshots
  • pipeline_snapshots
  • rnl_staff_engaged
  • gap_info
  • dt_stats


Therefore, if you are using fields from these tables in a custom report, the data in your report is cached and the agedatabase utility must run in order for the data to be updated.


Purging report statistics: The default settings are configured so that reporting statistics are not purged from the database. In previous versions, the default was to purge report data older than 187 days. The PURGE_DELETE_STATS configuration setting specifies the number of days after which reporting statistics are removed from the database.


Reports using cached data: To determine which standard reports in your application used cached data, run the report and view the report definition by clicking the Report tab and selecting View Definition. Check the tables listed to determine if any are the cached tables listed above.


For more information regarding standard reports in your application, refer to the Report Management, or Agedatabase Caching for more information on cached data. To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.

Available Languages for this Answer:

Notify Me
The page will refresh upon submission. Any pending input will be lost.