CCB Running Slow Using The Demo Install after upgrade to 126.96.36.199.0
(Doc ID 2163523.1)
Last updated on SEPTEMBER 16, 2022
Applies to:Oracle Utilities Customer Care and Billing - Version 188.8.131.52.0 and later
Oracle Utilities Framework - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 4.2 to 4.3]
Information in this document applies to any platform.
After importing the demo dmp file from the Customer Care and Billing (CCB) oracle database archive from oracle software delivery cloud (V78183-01 - exp_demo.dmp.gz), starting CCB and any navigation in the application has become significantly slower. For example, going to Control Central > Account Information and Control Central > Customer Information takes about 35 secs to load the page. It also takes 20-25 minutes for the application to start when the issue occurs (when using hibernate.properties). It only takes about 3 minutes for application to start when using weblogic.
As a workaround, switching from hibernate.properties to weblogic by logging into weblogic console, services > data sources > new jdbc data source and modifying hibernate.properties and the installation to use weblogic instead of hibernate.properties seems to resolve the issue.
This issue did not occur in CCB 2.3.1, where a different issue where sessions were not closing can occur. However, no performance issues were noticed on this version.
If you are using sql developer, you may notice that sessions stay in the database after a user logs out in previous versions of CCB (2.3.1), but this is not the case for CCB 18.104.22.168.0, where the session is disconnected after 1-2 minutes.
STEPS TO REPRODUCE
The issue can be reproduced at will with the following steps on ccb 22.214.171.124.0 :
1. download the CC&B oracle database archive from oracle software delivery cloud (V78183-01 - exp_demo.dmp.gz) and import data into database of CCB 126.96.36.199.0 instance
2. After issue occurs, log into weblogic console, go to services > data sources > new jdbc data source. modify hibernate.properties, run initial setup, and restart the application. The issue should no longer occur
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