Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1914002.1
Update Date:2016-09-06
Keywords:

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.  


Related Items
  • Oracle Communications Subscriber Data Management (SDM)
  •  
  • Oracle Communications Subscriber Data Management (SDM)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec SDM
  •  
  • Tools>Primary Use>Performance
  •  


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
Description
 Cause
 Changes
Occurrence
Symptoms
Workaround
Patches
History
References


Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.2 to SDM 9.3 [Release SDM 9.0]
Tekelec

Description

Subscriber 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.

Cause

With MEB the minimum size of the backup file is 20GB which has a intensive write operation on disk.

Changes

SDM (SPR) 9.3 uses MySQL Enterprise Backup for daily automatic backup feature.

Occurrence

  100% if the configuration does not use storage blade.

Symptoms

When 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.

Workaround

  Stop the backup.

Patches

 Patch 1 will be released to address this issue

 Following table summarizes where SDM 9.3 upgrade is recommended.

  Deployed SPR Systems  Is it OK to Upgrade to SPR 9.3               Comment
HP C-class with sidecar disk array                                  Yes      No additional configuration needed
HPG8 RMS with 8 disk array                                  Yes

Will work with high latency and high CPU usages by iowait (disk reads/writes).

Our recommendation to wait for SPR 9.3 Patch #1

All other 2 disk only setups                                   No Wait for SPR 9.3patch#1

 

 

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
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback