Skip to main content
NetApp Knowledge Base site will be down for 3 hours between Oct 26, 23:59 PST and Oct 27, 02:59 PST, for system maintenance and infrastructure update.
NetApp Stage KB

Active IQ Unified Manager virtual appliance upgrade fails with error: "Failed to Upgrade platform_base"

Views:
1
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
OM
Last Updated:

 

Applies to

  • Active IQ Unified Manager (AIQUM)  9.6P1
  • VMware OVA

Issue

  • Active IQ Unified Manager upgrade fails with Failed to Upgrade platform_base

errors.png

  • In the upgrade.log:
Jun 10 19:10:33 ocum systemd[1]: [0;1;39mmysql.service: Unit entered failed state.[0m
Jun 10 19:10:33 ocum systemd[1]: [0;1;39mmysql.service: Failed with result 'signal'.[0m
dpkg: error processing package mysql-community-server (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-community-server (= 8.0.21-1debian10); however:
  Package mysql-community-server is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
 mysql-community-server
 mysql-server
W: --force-yes is deprecated, use one of the options starting with --allow instead.
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: Sub-process /usr/bin/dpkg returned an error code (1)
Jun 10 19:10:33:  Failed to upgrade platform_base
Jun 10 19:10:33:  Upgrade of Active IQ Unified Manager failed.
Jun 10 19:10:33:  Contact technical support with appropriate AutoSupport information.
Jun 10 19:10:33:  For more information about AutoSupport,
Jun 10 19:10:33:  refer to the product documentation in the Support Site.
  • In MySQL error.log:
2021-06-03T00:27:30.133311Z 29 [ERROR] InnoDB: Failed to find tablespace for table `ocum`.`annotationofcluster` in the 
cache. 
Attempting to load the tablespace with space id 68583
2021-06-03T00:27:30.133483Z 29 [ERROR] InnoDB: In file './ocum/annotationofcluster.ibd', tablespace id and flags are 
68618 and 0, but in the InnoDB data dictionary they are 68583 and 0. Have you moved InnoDB .ibd files around without 
using the commands DISCARD TABLESPACE and IMPORT TABLESPACE? 
Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-06-03T00:27:30.133497Z 29 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2021-06-03T00:27:30.133505Z 29 [ERROR] InnoDB: The error means the system cannot find the path specified.
2021-06-03T00:27:30.133514Z 29 [ERROR] InnoDB: Could not find a valid tablespace file for `ocum/annotationofcluster`. 
Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2021-06-03T00:27:30.133562Z 29 [Warning] InnoDB: Cannot calculate statistics for table `ocum`.`annotationofcluster` 
because the .ibd file is missing. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for 
how to resolve the issue.
  • Select * from ocum.annotationofcluster fails with: 
    Tablespace is missing error for table ocum.annotationofcluster

 

 

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.