Chart Console fails to save changes each time you restart the console (NETIQKB72035)

Chart Console fails to save changes each time you restart the console.

To resolve this issue you should perform the following operations:

WARNING:  The following instructions include steps which require making manual changes to your repository database.  Please be sure to make a backup of your repository database before making any manual changes.

1. Verify the permissions on the blob table
   1. Open SQL Management Studio and connect to the SQL server containing the AppManager Repository database
   2. Expand Databases then expand your Repository database.  (Note:  Default name is QDB)
   3. Expand Tables then look for the dbo.blob table.
   4. Right click on the dbo.blob table and choose Properties
   5. In the Table Properties - blob window, click on Permissions
   6. Under Users or Roles, look for the Public role and select it.
   7. If the Public role is missing, continue with step 2 below
   8. If the Public role is not missing, select it
   9. Under Explicit Permissions for public look at the Select permission and confirm that there is a check in the box under the Grant column.  If there is no check continue to step 2 below.  If there is a check in the box under the Grant column then you may have another issue not addressed by this article.  Please contact NetIQ Technical Support for assistance and reference this Knowledge Base article.
2. Correcting the permissions problem
   1. If the Public role was missing from the Users or Roles section of the Table Properties - blob window perform the following:
      1. Click the Add button
      2. Type public in the Enter the object names to select box and click the Check Names button
      3. public should change to [public]
      4. Click Ok
      5. Select the Public role in the Users or Roles section
      6. Under Explicit permissions for public find the row with permission Select and check the box in the Grant column
      7. Click OK to save changes
   2. If the Public role was not missing from the Users or Roles section of the Table Properties - blob window but the Grant option for Select was not selected perform the following:
      1. Under Explicit permissions for public find the row with permission Select and check the box in the Grant column
      2. Click OK to save changes

Once you have made these changes the permission problem will be resolved.  Some manual clean up still needs to happen to the blob table to ensure everything is working properly.  The following query will remove all duplicates from the table leaving on the most recent entry for each user.

Note:  You may want to run the BackupBlob procedure to make a new backup of the table prior to running the query below.  Please note that if you do it will overwrite your previous backup.

WARNING:  The following instructions include steps which require making manual changes to your repository database.  Please be sure to make a backup of your repository database before making any manual changes.

DECLARE @tempcomment varchar(255)
DECLARE @tempblobid int

CREATE TABLE #t
  (
    comment varchar(255)
  )

INSERT #t (comment) SELECT DISTINCT comment FROM blob WHERE comment is not NULL

DECLARE tempblob_cursor CURSOR FOR
  SELECT comment FROM #t
OPEN tempblob_cursor

FETCH NEXT FROM tempblob_cursor INTO @tempcomment
WHILE (@@FETCH_STATUS = 0)
BEGIN
  SELECT @tempblobid = MAX(blobid) FROM blob WHERE comment = @tempcomment
  DELETE FROM blob WHERE comment = @tempcomment AND blobid <> @tempblobid
  FETCH NEXT FROM tempblob_cursor INTO @tempcomment
END
DEALLOCATE tempblob_cursor
DROP TABLE #t

If you continue to have issues after performing the steps above, please contact NetIQ Technical Support for more assistance and reference this Knowledge Base article.

This is caused by a problem in the database.  Chart information is stored in the blob table.  If the configuration of the blob table gets altered for any reason this can lead to a situation where you wind up with new duplicate entries in the blob table each time you open and close the application.  This is caused by improper permissions on the blob table.

Formerly known as NETIQKB72035