OnCommand Insight Data Warehouse 7.3.x (DWH) DWH ETL fails at extractor stage at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.16.0.j...OnCommand Insight Data Warehouse 7.3.x (DWH) DWH ETL fails at extractor stage at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.16.0.jar!/:2.16.0] Caused by: com.netapp.sanscreen.dwh.applications.inventory.InventoryException: Data validation failed with error: Internal volume with identifier "<bucket_name>" appears more than once with different ids. It can happen if two data sources are reporting on the same storage.
OnCommand Data Warehouse ETL fails and user is unable to access the ‘Connectors’ window due to DWH password encryption file mismatch. This issue is caused due to a conflict between the ‘Password encry...OnCommand Data Warehouse ETL fails and user is unable to access the ‘Connectors’ window due to DWH password encryption file mismatch. This issue is caused due to a conflict between the ‘Password encryption keys’ that are in the DWH server and what is currently being used by one or more of the OCI connectors.
OnCommand Insight DataWarehouse (DWH) 7.3.x OnCommand DataWarehouse connector Extract Transfer Load (ETL) process from the OnCommand Insight server does not complete. Caused by: org .m ariadb.jdbc.int...OnCommand Insight DataWarehouse (DWH) 7.3.x OnCommand DataWarehouse connector Extract Transfer Load (ETL) process from the OnCommand Insight server does not complete. Caused by: org .m ariadb.jdbc.internal.common.QueryException: Cannot add or update a child row: a foreign key constraint fails (`dwh_inventory_staging`.`storage_node_to_port`, CONSTRAINT `fk_storage_node_to_port_portId` FOREIGN KEY (`portId`) REFERENCES `dwh_inventory`.`storage_port` (`id`) ON DELETE CASCADE)
dwh.log (here truncated) shows the error as below for failed Datamarts Preparation step: Caused by: com.netapp.sanscreen.dwh.capacity.CapacityException: Failed to clean capacity staging area Caused by...dwh.log (here truncated) shows the error as below for failed Datamarts Preparation step: Caused by: com.netapp.sanscreen.dwh.capacity.CapacityException: Failed to clean capacity staging area Caused by: java.sql.SQLException: Schema 'dwh_cloud_cost_staging' does not exist, but schema directory '.\dwh_cloud_cost_staging\' was found. NOTE: Schema name can be other "xxx_staging" but the root cause/solution will be same if the log output is as above.
