APAR status
Closed as duplicate of another APAR.
Error description
Schema verification step (for one participant) when defining a master replicate on a single table (cdr define replicate ... -M, the default since v12.10) would take longer the more tables there are in that participant's database, yet this would still remain within few seconds with some thousand tables, if those tables aren't fragmented. With fragmented tables, though, the effect becomes increasingly (exponentially) worse the more fragmented tables there are, regardless of the actual number of fragments per table. For instance: duration with so many fragmented tables 4 secs 1000 14 secs 2000 27 secs 3000 ... many minutes with multiple 10.000 tables The same obviously will be true for realizing a template, yet only the first verification for a given realization server would take this long, so the net effect would be alleviated by the template comprising multiple tables.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
This APAR is a duplicate of IT27586
APAR Information
APAR number
IT21954
Reported component name
INFORMIX SERVER
Reported component ID
5725A3900
Reported release
B70
Status
CLOSED DUA
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-08-09
Closed date
2019-09-25
Last modified date
2019-10-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 October 2019