Active IQ Unified Manager Discussions

OCUM 7.2 Upgrade - Performance Data Migration failed - SQLException !

sanadmin_stadtdo
10,280 Views

Hello,

we have updated our OCUM (vmware appliance) from 7.1 to 7.2. The performance data must be migrated for 4 clusters with a total of 10 nodes.
While this has worked smoothly with 3 clusters, a cluster with 4 nodes breaks again and again with 'Failed':

 

Wed Aug 23 08:12:50 CEST 2017 - Data migration completed for Optional[summary_wafl]
Wed Aug 23 08:12:50 CEST 2017 - Data migration completed for Optional[summary_networklifVserver]
Wed Aug 23 08:12:50 CEST 2017 - Data migration completed for Optional[summary_nfsv3]
Wed Aug 23 08:12:50 CEST 2017 - Data migration completed for Optional[summary_aggregate_1]
Wed Aug 23 08:12:50 CEST 2017 - Data migration completed for Optional[summary_cifsvserver]
Wed Aug 23 08:12:51 CEST 2017 - Data migration completed for Optional[summary_quos_workload_queue_dblade_1]
Wed Aug 23 08:12:51 CEST 2017 - Data migration completed for Optional[summary_quos_workload_queue_nblade_1]
Wed Aug 23 08:12:51 CEST 2017 - Data migration completed for Optional[summary_disk_1]
Wed Aug 23 08:12:52 CEST 2017 - Data migration completed for Optional[summary_quos_workload_detail_1]
Wed Aug 23 08:12:52 CEST 2017 - Data migration completed for netapp_performance database
Wed Aug 23 08:19:26 CEST 2017 - Error Message: PreparedStatementCallback: uncategorized SQLException for SQL [SELECT Cause : java.io.EOFException: unexpected end of stream, read 31 bytes from 80

Do you want to retry the data mirgation from cluster FAS80402 (failed) Y/N ?

 

 

It is always the SQLException above.

Once at "read 31 bytes from 80", then "read 57 bytes from 76" or even "read 61 bytes from 77"

 

 

Any idea?

Many Thanks

Michael

1 ACCEPTED SOLUTION

niels
10,060 Views

Hi Michael,

 

this looks familiar and unfortunately you are not alone. This could be a known problem which is logged under BURT 1102280.

Please open a case and refer to that BURT. Support should be able to provide you parameters to tweak some MySQL settings.

Basically the migration wizard runs into a timeout because of a large number of objects that need to be retrieved from old OPM DB.

 

regards, Niels

 

----

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both.

View solution in original post

15 REPLIES 15
Public