KB Article #176542
How to fix when Sentinel startup errors with non-unicode mode with a unicode database
Problem
Sentinel not able to start after applying SP3.It throws the following error:
"[TemplateServer ] FATAL L512 TemplateServer.doExecuteStartCommand - Unable to start Sentinel server: either the server is in non-unicode mode with a unicode database or the server is in unicode mode but the database is not unicode."
Resolution
This kind of error occurs if the Sentinel Database is not updated properly while applying the service pack.
In order to resolve this, please follow the steps below.
- Stop Sentinel.
- Use any SQL tool to open the Sentinel database and then open the 'RuleVariable table'.
- Confirm the data type of 'varValue' column is 'varchar (512 bytes)'.
- Now, browse to the XDBM directory found in the Sentinel installation directory. ( For example, /opt/Axway/tools/XDBM/).
- Please find xdbmcmd_Sentinel_4.0_1.bat (Windows)/ xdbmcmd_Sentinel_4.0_1.sh (Unix) script and run it. This script checks the DB and makes any changes that were leftover and corrects the DB.
- Now, go back to the Database view and confirm if the 'varValue' data type is now 'varchar(1024 bytes)'.
- Finally, start up Sentinel again and verify that it starts up successfully.