![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||
Solution Type Sun Alert Sure Solution 1914002.1 : Tekelec Service Bulletin - Performance to the System Will Be Affected - Daily Backup Will Affect the Traffic Due to the Intensive Write Operation on the Disk.
SPR 9.3 creates large backup files and increase the write operation on disk which will impact traffic if there is no storage blade is used in the system configuration. In this Document
Applies to:Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.2 to SDM 9.3 [Release SDM 9.0]Tekelec DescriptionSubscriber Data Management (SDM) release 9.3 and SDM (Home Location Register - HLR) 9.2.6 uses MySQL Enterprise Backup (MEB) v3.10.1 for the daily automatic backup. With this MEB the minimum size for a backup file is 20G. The customer which has storage blade system can use MEB without any issue. However, in a system without storage blade, the intensive write (of at least 20G of a backup) would cause latency on traffic due to disk write contention. CauseWith MEB the minimum size of the backup file is 20GB which has a intensive write operation on disk. ChangesSDM (SPR) 9.3 uses MySQL Enterprise Backup for daily automatic backup feature. Occurrence100% if the configuration does not use storage blade. SymptomsWhen daily backup is running system cannot process the rated capacity traffic successfully. Sh traffic experiences longer latency, which in turn shows up as failures at PCRF, which is sending Sh traffic. Intensive write operation of the backup will slow the system dramatically. WorkaroundStop the backup. PatchesPatch 1 will be released to address this issue Following table summarizes where SDM 9.3 upgrade is recommended.
History
04-08-2014 - Doc Created 06-08-2014 - Doc has been modified from Alert to Bulletin. 07-08-2014 - Corrected some info based on PV testing and inserted the table. 3--20-2015 - changed document back to an Alert - TSBs = KM Alerts References<BUG:19297683> - MYSQL BACKUP SHOULD BE REMOVED TO PREVENT MANY PROBLEMS.<BUG:19117090> - [239392]NEW MYSQL BACKUP VERSION CAUSES MANY PROBLEMS, WHEN DATABASE B <BUG:19324532> - EXCESSIVE SH TRAFFIC LATENCY AND FAILURE OBSERVED WHILE DAILY BACKUP MEB RUNS Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||
|