Would you like to...

Print this page

Email this page

Post a comment

Subscribe me

del.icio.us

Digg it

Remove Highlighting

Edit this Article

Quick Edit

Export to PDF

User Opinions (1 vote)

100% 0%

---

How would you rate this answer?

Helpful

Not helpful Help us improve. Why was this unhelpful?

Thank you for rating this answer.

Last Updated: 12th May 2011 09:48:40 am

Due to a bug in License Statistics v3.8, it is possible that some features may be erroneously duplicated on more than one server. This bug has been fixed in License Statistics v3.9; however, any existing misplaced feature data must be moved manually from the incorrect server to the correct server.

To see a list of potentially duplicated features, go to the SQL Console tab on the Administration page, and execute the following query:

SELECT F.Name, GROUP_CONCAT(CONCAT(" ", LS.VendorName, " on ", LS.ServerName, " (id = ", LS.Id, ")")) AS LicenseServers
FROM FeatureVersionName F
    JOIN LicenseServerStrings LS ON F.LicenseServerId = LS.Id
GROUP BY F.Name
HAVING COUNT(*) > 1
ORDER BY F.Name;

This query will list all the feature names that are served by more than one license server. Example output from this query is as follows:

Name LicenseServers
BrokenFeature vendor1 on server1 (id = 20), vendor2 on server2 (id = 19)

In the above example, "BrokenFeature" is on two license servers (id = 19 and id = 20), but should only be on license server 19. To fix this, you must move the data back to the correct server using a stored procedure: MoveFeature (FeatureName, SourceLicenseServerId, DestinationLicenseServerIdParam). For the above example, you would execute the query:

CALL MoveFeature('BrokenFeature', 20, 19);

This will move the “BrokenFeature” data from license server 20 to license server 19.