Fixing Maintenance Window Initialization Error in AIQUM

Cause

• The MaintenanceWindowScheduler.init() method in dfm-app.war accesses a Hibernate lazy proxy (MaintenanceWindow#1) outside of an active session.
• This was introduced by a code/mapping change in version 9.18P1.

Solution

• Database manipulation needed
• Please contact NetApp Technical Support or log into the NetApp Support Site to create a case. Reference this article for further assistance

Partner Notes

Additional Information

Internal Notes

• This is an L2 operation that requires direct database access on the AIQUM appliance.

Submitted CAIQUM-8929 for this issue.

• L2 procedure — database cleanup:

1. Connect to MySQL on the AIQUM appliance and select the Ocum database.
2. Select Ocum database
   USE OCUM;
3. Check the current maintenance window state:
   SELECT mw.id, FROM_UNIXTIME(mw.startTime/1000) AS start_time, FROM_UNIXTIME(mw.endTime/1000) AS end_time, m.resourceType, m.resourceId
FROM maintenance_window mw
LEFT JOIN maintenance_window_object_mapping m ON m.maintenanceWindowId = mw.id;
4. Delete all maintenance window records (ON DELETE CASCADE automatically cleans up maintenance_window_object_mapping):
   DELETE FROM maintenance_window;
5. Verify both tables are empty:
   SELECT COUNT(*) FROM maintenance_window;
SELECT COUNT(*) FROM maintenance_window_object_mapping;
6. Reboot the AIQUM server.