OFSAA 8.0.7 Application Hangs With Blank Screen After EFPA Consumes All Memory Through Increasing "ADPAFNRE" Cube's Metadata
(Doc ID 2654238.1)
Last updated on MARCH 02, 2023
Applies to:
Oracle Financial Services Enterprise Financial Performance Analytics - Version 8.0.7 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Business Intelligence Enterprise Edition (OBIEE)
Oracle Financial Services Enterprise Financial Performance Analytics (EFPA/PFTBI) previously known as Oracle Financial Services Profitability Analytics
Reporting
Oracle Financial Services Enterprise Performance Management (EPM)
Symptoms
On OFSAA 8.0.7 with EFPA, web app server hangs with blank screen.
After restarting OFSAA services, the apps work fine for an hour. After that (without any activity or process execution), OFSAA suddenly starts to increase memory use and finally the web app stops responding.
In SMSService.log, it has been noticed that there is a process doing the same query every time:
[27-02-20 17:00:18,328 GMT PM] [DEBUG] [APP] [SMS] [NA] [DACDATABASEGATEWAY] [BIND VARIABLES DDL Query for debug] : [SELECT CUBE_VARIATION.* FROM VIEW_CUBE_MEASURE_VARIATION CUBE_VARIATION WHERE DSN_ID = '<INFODOM>' AND METADATA_CODE = 'ADPAFNRE' AND METADATA_VERSION = '0' ORDER BY MEASURE_NAME, ELEMENT_ORDER ]
The issue is always with METADATA_CODE = 'ADPAFNRE'. Following query towards VIEW_CUBE_MEASURE_VARIATION returns approximately 37 million records:
Above query solved the issue, ensuring no memory issues for the moment, however below questions were raised:
Question 1. What was the source of the problem? After installation of PFT BI Modules, metadata for BI Apps was not changed. On metadata_master, the modified_dt is few years back, so it has not been modified after more recent installation.
Question 2. What is the correct configuration on view_cube_measure / metadata_element_master for this CUBE? The metadata_element_master has millions of duplicate records for ADPAFNRE. Each v_element_code dimensions has 524k records for each V_ELEMENT_VALUE (only has different n_elemnt_order).
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |