Performance Issue With REPORT_LOG Table - embedded BI Publisher
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.7 and later
Information in this document applies to any platform.
Performance issues are experienced with the REPORT_LOG table if numerous records build up over time.
If there is no separate Reports server, the purgeRepLog.sh script to purge the table can't be used.
This raises the following questions:
1. How to purge historical data without using purgeRepLog.sh?
2. Is there any impact when creating an index on the job_number column?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms