System Update fails when using external database

  • 7011743
  • 01-Feb-2013
  • 01-Feb-2013

Environment

Novell ZENworks Asset Management 11.2
Novell ZENworks Configuration Management 11.2 System Update
Novell ZENworks Endpoint Security Management 11.2
Novell ZENworks Patch Management 11.2

Situation

Upgrading ZCM from 11.2 to 11.2.x
Zone uses external database (Sybase, MSSQL or Oracle)
Upgrade fails: system-update log contains
ERROR;ERROR_STARTING_PROCESS;C:\Program Files (x86)\Novell\ZENworks\bin\novell-zenworks-configure.bat,The exit code of the process did not match with success codes.;
DEBUG;;;An error occured during command execution...details should have already been logged


novell-zenworks-configure.log contains
[2013.01.29-18:03:22] SEVERE:
com.novell.zenworks.datamodel.exceptions.InternalDataModelException:
org.hibernate.exception.ConstraintViolationException: could not insert:
[com.novell.zenworks.datamodel.objects.locations.ZENLocation]
com.novell.zenworks.datamodel.exceptions.InternalDataModelException:
com.novell.zenworks.datamodel.exceptions.InternalDataModelException:
org.hibernate.exception.ConstraintViolationException: could not insert:
[com.novell.zenworks.datamodel.objects.locations.ZENLocation]
    at
com.novell.zenworks.datamodel.services.locations.LocationAdminImpl.createUnknownLocation(LocationAdminImpl.java:1807)
    at
com.novell.zenworks.configure.actions.UnknownLocationConfigureAction.configure(UnknownLocationConfigureAction.java:41)
    at
com.novell.zenworks.configure.ZENworksConfigure.execConfigAction(ZENworksConfigure.java:1671)

..................................

Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Index
'uniq_zZENObject_Path' for table 'zZENObject' would not be unique
    at sybase.jdbc4.sqlanywhere.IIPreparedStatement.executeUpdate(Native
Method)
    at
sybase.jdbc4.sqlanywhere.IPreparedStatement.executeUpdate(IPreparedStatement.java:303)

Resolution

Establish time sync between the Primary server and the Database server, then retry the upgrade

Cause

Time on the Database server was ahead of the time on the Primary server: timesync should always be checked before starting upgrade operations