Environment
Novell Data Synchronizer Mobility Pack 1.2.5.299
Novell Data Synchronizer Mobility Pack 1.2.4
Situation
Upgrading from Mobility Pack 1.2.4. to Mobility Pack 1.2.5 takes a long time
/opt/novell/datasync/update.sh stuck
Resolution
Updating from Mobility Pack 1.2.4 to Mobility Pack 1.2.5 modifies a lot of entries in the database and may take some time. If the Nightly Maintenance has never run, it will take longer. Please check if Nightly Maintenance is enabled
-
Edit /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/mobility/connector.xml
-
Check for the following lines and make sure that no xml tags are set to NONE
<databaseMaintenanceStartHour>0</databaseMaintenanceStartHour>
<databaseMaintenance>1</databaseMaintenance>
<databaseMaintenanceStopHour>6</databaseMaintenanceStopHour>
If any of the above is not set properly, its possible that Maintenance has never been run and it will take a long time to complete the maintenance
Also, please look at the following TID to make sure it has been completing successfully