K1000 upgrade to v5.4 failing on ibdata1 is too large error
We have been stuck trying to upgrade our K1000 appliance to v5.4. The install fails during a pre-installation check of the system. It says the ibdata1 is too large. I've attempted to contact support but they have not found a resolution yet. I figured I woul ask the masses to see if they know what it is.
[notice] A condition was detected that is not optimal for an upgrade.
[notice] The upgrade was stopped. Please contact technical support
[notice] - ibdata1 is too large (20940062720)
Answers (4)
You cannot do anything without support, our server tech had same problem and he had to work thru tech support. They ended up giving us a file that bypassed the pre checks the only side effect we had after was half of our smart labels vanished.
Comments:
-
I would export and save your info on another box so if something gets dropped you can reimport it. - SMal.tmcc 11 years ago
-
Looks like I need to push support to provide me those files. Thanks for the heads up on the smart labels. - Tomsquatch 11 years ago
-
I would push to get elevated - SMal.tmcc 11 years ago
ibdata1 is a db storage file for mysql , it cannot be modified. (even if you had command line access to the appliance). there are options as far as dumping the data using SQL however that would have to be done by support.
I would suggest while you are waiting for support , back up your appliance. Then run "reboot with extended DB check" under System Maintenance. That may decrease the size of ibdata1
Other than that , I would wait for support.
Comments:
-
Great suggestion! Support tried the run a back and try again approach but never had me to the reboot with extended DB check. - Tomsquatch 11 years ago
-
Hi Scott, I just attempted the steps and still no go. Thanks for the help anyways! - Tomsquatch 11 years ago
I had the same problem, but KACE support was able to walk me through it. They provided links for a couple of downloads.
kbox_patch_sizereport.kbin and kbox_patch_rebuildBloatedTables.kbin
We ran sizereport, this confirmed several tables were too large.
We ran rebuildBloatedTables, this reduces the dbase from 160MB to 40MB.
Ran sizereport again to confirm the tables were small enough.
We disabled Agent log retention.
We backed up the K1000.
The update ran after that, without any other problems.
The tech on the phone did say there is a way to disregard the warning and continue, but the problem would need to be elevated to the next level of support for that to happen.
Comments:
-
We went thru same thing, and ended up getting elevated. - SMal.tmcc 11 years ago
-
Thanks for the help Dubnium. Those were the first steps support took me through and unfortunately didnt fix the issue. I should have put that in my original post. Sorry! Thank again for the help! - Tomsquatch 11 years ago
Support should either bypass or fix the table after checking for several factors.
The rebuild bloated tables patch should not be run except by support request. The file size patch checks for a condition and if it exists then the rebuild patch is used. Otherwise it's useless and can cause further issues.
If you have followed the upgrade steps and they had you run the above patches then the next step would be to have an engineer to tether into your machine. Do an off the box backup and if they aren't in the process already let support know you wish this to happen or the bypass patch.
Comments:
-
Yup! I would not recommend the by-pass patch as you cannot be certain that the issue you already having is not ported over to your new 5.4 box. Tether is the best approach and the DB can be fixed as you say.. - RaSko 11 years ago
-
Never run the bypass patch on your own. A lot of times after the engineer has worked on the db he will have you run the patch anyways to get it to upgrade. If your db is big it's big. That isn't necessarily a bad thing in and of itself, but let an engineer decide. - jdornan 11 years ago
