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

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 3,790

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.
Cloud Agent is enabled and REST collection is configured, however AIQUM continues to perform ZAPI-based collection for the affected cluster.
- Ocumserver.log
2026-04-28 14:41:55,065 INFO [oncommand] [org.springframework.jms.listener.DefaultMessageListenerContainer#1-1] [com.netapp.ipc.jms.OCIE_Events] OCIE JMS notification message received: {WarningCount=0, DatasourceName=clustername, DatasourceID=60, Error0_ClusterManagementIP=clustername, PackageName=netappfoundation, TotalReportTime=-1, PollStartTime=1777380083790, ErrorCount=1, Success=false, DurationTime=31263, Error0_Message=Internal Error, TotalZAPITime=-1, NotificationType=PACKAGE_COMPLETED, Error0_Type=INTERNAL_ERROR, UpdateTime=1777380115065, Error0_Port=443, MessageType=PACKAGE_NOTIFICATION, Error0_Zapi=null}
- AU.log
2026-04-28 14:56:55,023 ERROR [common-pool-156] c.o.s.a.d.n.b.z.c.n.ClusterBuilder (ClusterBuilder.java:286) - [netappfoundation] clustername - ExecutionException encountered on Builder java.util.concurrent.ExecutionException: java.lang.NullPointerException: storage_shelf key field 'uuid' may not be null.
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.