ZAM 7.5 can't move filestore in the manager when using Oracle database

  • Document ID:3049667
  • Creation Date:01-Apr-2008
  • Modified Date:27-Apr-2012
    • Micro Focus Products:
      ZENworks Asset Management

Environment

Novell ZENworks Asset Management 7.5 Interim Release 10
Microsoft Windows Server 2003 Service Pack 2

Situation

Moving the filestore in the manager will not work because of a case-sensitivity/multiple entries problem in the Oracle database.
If you try to move the filestore from the manager, and there are multiple entries in the Oracle database for something like spacew32.exe in the nc_filestorecatalog (differing only by case), the move fails. The manager does pop up an error in that case, which will be seen.

Resolution

Fixed in ZENworks Asset Management 7.5 Interim Release 12 or newer

Interim Releases can be scheduled to run automatically or can be downloaded manually at Novell Downloads.  The Interim releases can be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section details of how to set up automatic downloads if desired.

Each interim release is cumulative. If Interim Release 10 is not available due to a newer interim release being placed on the website, be assured that the code needed is in the later release.

Additional Information

The case sensitivity issue prevents the manager-based move from working, because when you try to change the location of the filestore from the manager, it immediately checks that everything in nc_filestorecatalog is actually on the disk. It gets to one of the "extra" instances of spacew32.exe (or some other file) listed in the DB, and sees that is not in the filestore".

If you edit the nc_filestore record in the DB manually, that check is not done. So everything is fine in that case.

When you change File Store location from the manager, the manager does two things:

1. Checks the location you entered to make sure it contains all the stuff listed in nc_filestorecatalog

2. Updates nc_filestore with the new location

It doesn't do step 2 if step 1 fails.

Cleaning up the multiple entries in nc_filestorecatalog should resolve the problem