Novell ZENworks 11 Configuration Management Database
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3 Database
ZCC is unresponsive
Excessive network traffic
High utilization in zenserver process
zOSTarget table becomes very large
ERROR: com.novell.zenworks.webservice.lib.InternalAuthenticationException: java.lang.OutOfMemoryError: Java heap space
On ZCM 11, the zOSTarget table does not continue to grow, but a ZCM 10.3.x zone that had this issue and was then upgraded, may still have a large zOSTarget table
Workaround: if it is not possible to upgrade to 10.3.2 at this time, in the interim, Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=2Wgh0yxLITo~
as "ZCM 10.3.1 Combined patch for Zone performance degrades (see KB 7006967), Allow Windows 7 SP1 device to register (see KB 7007952), ZCC bundle status takes a long time to display (see KB 7006325)"
. This Patch should only be applied if the symptoms above are being experienced, and are causing problems.
This Patch has had limited testing, and should not be used in a production system without first being checked in a test environment. Some Patches have specific requirements for deployment, it is very important to follow any instructions in the readme at the download site. Please report any problems encountered when using this Patch, by using the feedback link on this TID.
For ZCM 11:
This is fixed in version 11.1 adding an auto-shrink of the database - see KB 7008746
"ZENworks Configuration Management 11.1 - update information and list of fixes" which can be found at https://www.novell.com/support
The fix in ZCM 11 prevents the zOSTarget table from continuing to grow large. However, manual steps to reset the table to its proper size may also be required if the ZCM 10.3.x patch had not already been applied before upgrading to ZCM 11 (not required on ZCM 11.1 or later, as this will automatically correct the table).
1. Clear the table using the appropriate database management tool
delete from zOSTarget;
2. Commit the change if using Sybase or MSSQL
3. Shrink the db if using MSSQL or Oracle
4. Restart the loader service on a primary server.