Recently, an OCPM (OnCommand performance manager) managed NetApp Cluster data was migrated to OCUM (OnCommand Unified Manager) v7.2P1.
The steps to migrate the cluster data was straight forward and the steps are mentioned here.
The trouble was that after the migration was initiated the job remained IN-PROGRESS for almost 2 weeks and there was no way to ascertain if the job was in progress.
A support case was raised with NetApp and a support bundle was generated. Upon analysis it was found that there was an events table that was too large. Here is a snippet from the logs:
If you are running into a similar issue then it is best to raise a support case and share a support bundle with them .
If you are experiencing something similar then feel free to leave a message/note.
The steps to migrate the cluster data was straight forward and the steps are mentioned here.
The trouble was that after the migration was initiated the job remained IN-PROGRESS for almost 2 weeks and there was no way to ascertain if the job was in progress.
A support case was raised with NetApp and a support bundle was generated. Upon analysis it was found that there was an events table that was too large. Here is a snippet from the logs:
c.n.d.u.m.i.m.o.OpmBaseMigrator
(http://OpmBaseMigrator.java:76)
- Migrating data from table - continuous_event_participant succeeded in 20,066
sec
2018-11-06
04:59:29,890 INFO [main] c.n.d.u.m.i.m.o.OpmBaseMigrator (http://OpmBaseMigrator.java:68)
- Migrating data from table - continuous_event_participant_stats
2018-11-06
11:47:12,191 INFO [main] c.n.d.u.m.u.MigrationUtil (http://MigrationUtil.java:96)
- Looking for process id - 8,149. Process list command output - Optional[[ 8149
java]]
2018-11-06
11:47:12,265 INFO [main] c.n.d.u.m.i.MigrationStatusService (http://MigrationStatusService.java:310)
- Validate Active Migrations - Found a datasource with id 2 and its java
process id 8,149
2018-11-06
11:47:12,269 INFO [main] c.n.d.u.m.i.MigrationStatusService (http://MigrationStatusService.java:253)
- Unable to find data source to migrate or there is no datasource in scheduled
status.
If you are running into a similar issue then it is best to raise a support case and share a support bundle with them .
If you are experiencing something similar then feel free to leave a message/note.
No comments:
Post a Comment