Using Relocator to correct Collation differences


Webtrends On Premises 9.x


During migration from OP to OD, you are required to bring the client’s data, configs and databases in house to test and prepare an OnDemand migration. There are also situations where you may be simply move the system over laterally to a new server.

As you integrate the database into your own system, you find that the Webtrends UI and Tomcat services will not stay started.


Check the properties of the database. If the collation is not SQL_Latin1_General_CP1_CI_AS, then the collation needs to be replaced.


Run Relocator on the databases that have the bad collation, then restore the clean databases you created when you first installed Webtrends on the server run Relocator again to import the database data.

Relocator only copies the data, not the properties of an imported database. Therefore it won’t carry the collation forward into the destination database.