Changes In OSB Report Logging Between 11g And 12c
(Doc ID 2940372.1)
Last updated on MAY 14, 2024
Applies to:
Oracle Service Bus - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Goal
We are in the closing stage of an Oracle SOA Suite 11g to 12c upgrade, and we are facing a major problem regarding the report functionality with OSB 12c.
Our understanding, is that WLI_QS_REPORT_ATTRIBUTE and WLI_QS_REPORT_DATA are the tables on the SOA_INFRA schema where the report information are saved. However, the behaviour betwen our 11g environment and 12c environment is much different.
We never had problems with 11g. But, with 12c, and with the exact same developments (exported from 11g OSB and imported on 12c OSB), the table WLI_QS_REPORT_DATA is consuming much more space. Right now, we are consuming 10+gb of data per day on 12c, when with about 14gb we can have the information from the last 60 days in 11g.
1. What are the reason for this change of behavior?
2. What are the real differences between 11g and 12c report logging?
3. What are the recommendations for dealing and controlling the amount of information generated and to safely purge the tables?
4. What are the settings available to change the behavior of 12c?
Solution
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
Goal |
Solution |
References |