It Takes Long Time To Display The Activity Hierarchy Zone In The Activity Portal
(Doc ID 2686517.1)
Last updated on SEPTEMBER 26, 2022
Applies to:
Oracle Utilities Meter Data Management - Version 2.2.0.3.0 to 2.3.0.2.0 [Release 2.2 to 2.3] Information in this document applies to any platform.
Symptoms
On : 2.2.0.3.0 version, Database
ACTUAL BEHAVIOR --------------- It takes long time to display the activity hierarchy zone in the activity portal
- After Customer upgrades the MDM from version 2.1 to 2.2 during last weekend, the user reported a performance issue on Activity Page. o When user navigates to Activity portal page, the Activity Hierarchy zone takes long time to display. Before the Activity Hierarchy tree is displayed, user cannot navigate to any other page. That results a serious impact to user operation since Activity portal page is one of the most used page in their business. o Following are the time taken to display the Activity Hierarchy for 3 different execution. 8.3 sec, 9.5 sec, 8.1 sec o When D1-IMD is running, the time even much worse. 33.5 sec, 53.1 sec, 38.5 sec o According to business user, this page was originally taken 1 to 2 sec in previous version (v2.1) before upgrade. - During our initial investigation, we identified the Activity Hierarchy zone uses service script which will execute a SQL from the zone D1-ACTHIERQ. If we run the SQL in SQL developer, it also takes around 8 sec to return result. We found that same SQL is used in 2.1 and 2.2 version. Therefore, we suspect the performance is due to difference behavior of this SQL in version 2.1 and 2.2. - We attached several SQL Plan and result in this SR for your reference. They are done on different Database. Followings are the explanation of the difference o S2 is the current Production database which is running MDM v2.2 using Oracle DataBase version [12.2.0.1]. It contains about 7 million meters. o H2 is Testing environment of MDM v2.1 using Oracle Database version [11.2.0.4] It contains only 0.8 million meters o T2 is Testing environment of MDM v2.2 using same version of DataBase as S2. As it is upgraded from H2, it contains same number of meters as H2. - Customer is expecting the same response time as before. Please provide solution.
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!