Bug ID 627360: Upgrade fails with "DBD::mysql::db do failed: Too many partitions (including subpartitions) were defined" errors in ASM log

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, Install/Upgrade(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2

Fixed In:
13.0.0, 12.1.2 HF1

Opened: Nov 08, 2016
Severity: 3-Major

Symptoms

These errors come up in asm log, upon first start after upgrade: ------------------------- 2016-11-02T08:33:09-06:00 localhost notice boot_marker : ---===[ HD1.2 - BIG-IP 12.1.1 Build 0.0.184 <HD1.2> ]===--- Nov 2 08:35:34 c5af5ltm1b info set_ibdata1_size.pl[18523]: Setting ibdata1 size finished successfully, a new size is: 8466M Nov 2 08:36:03 c5af5ltm1b info tsconfig.pl[21351]: ASM initial configration script launched Nov 2 08:36:17 c5af5ltm1b info tsconfig.pl[21351]: ASM initial configration script finished Nov 2 08:36:23 c5af5ltm1b info asm_start[19802]: ASM config loaded Nov 2 08:37:40 c5af5ltm1b crit perl[19802]: 01310027:2: ASM subsystem error (asm_start,F5::DbUpgrade::__ANON__): DBD::mysql::db do failed: Too many partitions (including subpartitions) were defined Nov 2 08:38:28 c5af5ltm1b crit perl[19802]: 01310027:2: ASM subsystem error (asm_start,F5::DbUpgrade::__ANON__): DBD::mysql::db do failed: Cannot remove all partitions, use DROP TABLE instead Nov 2 08:38:28 c5af5ltm1b crit perl[19802]: 01310027:2: ASM subsystem error (asm_start,F5::ConfigSync::load_traffic_data): Could not import table data PRX.REQUEST_LOG - ASM configuration save aborted Nov 2 08:38:33 c5af5ltm1b info perl[21860]: 01310053:6: ASM starting -------------------------

Impact

Upgrade fails

Conditions

ASM provisioned Local request logging enabled Upgrade of a maintenance release, HF or EHF

Workaround

Upgrade by the means of saving a UCS, performing a clean install and then loading the UCS. In the manual save/load UCS process, the upgrade of the Request Log can be disabled, which will workaround the error and the UCS will load fine. There are two options to disable the upgrade of the Request Log, when upgrading by the means of a UCS: ------------------- 1) do not load a Request Log, when loading a UCS: # tmsh modify sys db ucs.asm.traffic_data.load value never 2) do not save a Request Log, when saving a UCS: # tmsh modify sys db ucs.asm.traffic_data.save value disable -------------------

Fix Information

None

Behavior Change