Page: https://docs.netwrix.com/docs/dataclassification/5_7/kb/migration-and-maintenance/how-to-migrate-netwrix-data-classification-to-another-server
Issue or question:
If you are migrating with 5.7.10.1 onwards, you could run into this error.
The only current way to fix this is by changing the value of the primary Collector, Indexer and Classifier server in the NDC DB.
PLEASE CONSULT WITH YOUR SENIOR TSE BEFORE TOUCHING THE NDC DB. Only applies for Non-DQS instances.
The query should be as follows
Update DBStats
SET
Collector1 = 'NewServerName',
Indexer1 = 'NewServerName',
Classifier1 = 'NewServerName'
Per Dev's team - That isn't a bug, that is expected behaviour. If you want to migrate an NDC instance with the current version, you'll need to run that SQL query.
Page: https://docs.netwrix.com/docs/dataclassification/5_7/kb/migration-and-maintenance/how-to-migrate-netwrix-data-classification-to-another-server
Issue or question:
If you are migrating with 5.7.10.1 onwards, you could run into this error.
The only current way to fix this is by changing the value of the primary Collector, Indexer and Classifier server in the NDC DB.
PLEASE CONSULT WITH YOUR SENIOR TSE BEFORE TOUCHING THE NDC DB. Only applies for Non-DQS instances.
The query should be as follows
Update DBStats
SET
Collector1 = 'NewServerName',
Indexer1 = 'NewServerName',
Classifier1 = 'NewServerName'
Per Dev's team - That isn't a bug, that is expected behaviour. If you want to migrate an NDC instance with the current version, you'll need to run that SQL query.