Skip to main content
NetApp Knowledge Base

Removing ONTAP Cluster from AIQUM servers using ".sql" script

  1. Last updated
  2. Save as PDF
Views:
2,930
Visibility:
Public
Votes:
1
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

ActiveIQ Unified Manager

Issue

  • Removing the cluster from AIQUM UI > General > Storage Management > Cluster Setup > UI Shows
    • Operation == Deletion
    • Operation State == Failed 
    • Operation State == In Progress
    • Operation State == Completed
  • AIQUM logs are not very helpful when we try to remove the ONTAP cluster from AIQUM UI
    • ocumserver.log
    • DEBUG [oncommand] [inventory-change-notify-342] [clustername(incremental@08:22:26.709)|notify|system_health_alert|delete] [o.s.t.jta.JtaTransactionManager] Participating in existing transaction
    • DEBUG [oncommand] [inventory-change-notify-342] [clustername(incremental@08:22:26.709)|notify|system_health_alert|delete] [o.s.t.jta.JtaTransactionManager] Participating in existing transaction
    • DEBUG [oncommand] [inventory-change-notify-342] [clustername(incremental@08:22:26.709)|notify|system_health_alert|delete] [com.zaxxer.hikari.pool.HikariPool] um-default-data-source - Add connection elided, waiting 6, queue 7
    • ERROR [common-pool-2331] c.o.s.a.f.d.BaseDataSource (DataSourceErrorException.java:246) - clustername [Error retrieving data] - Timed out waiting for cluster, recommend increasing timeout value ([Device name General Device]: Timed out waiting for cluster, recommend increasing timeout value)
  • Failed to add cluster in AIQUM. The AIQUM GUI returned the error “cluster already exists”, which was caused by a duplicate entry in the MySQL database.
  • If the Cluster is already decommissioned or changed, you might see another error because it does not even start acquisition.
    • Server_mega.log
      • 2019-06-25 07:23:28,595 ERROR [ServerService Thread Pool -- 390] c.n.o.n.e.EmsZapiManager (EmsZapiManager.java:740) - Failed to call system-get-version -- : java.io.IOException: The host [cluster name] not be resolved
    • ocum-error.log
      • 2026-03-31 01:03:46,015 ERROR [oncommand] [reconciliation-0] [c.n.d.c.ClusterStatusListener] Socket connection error for cluster: Cluster-mgmt java.net.ConnectException: Connection timed out: connect
        2026-03-31 01:03:46,015 ERROR [oncommand] [reconciliation-0] [c.n.d.c.ClusterStatusListener] Cluster : Cluster-mgmt is not reachable. Generating cluster not reachable event.

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.