SQL errors in 1.2.2 ?

[macro]

Guys... Just a reminder or in case you are not aware. Please do not use SQLite for production. SQLite is not designed to handle big data volumes or a high DB load. Don't get me wrong, SQLite is still a great DB engine and does very well what its designed for. But it's just not up to the task for an average NetXMS production environment. Use NetXMS with SQLite for trying out, testing new features or if you monitor home network with 3 nodes But stay away from it in the production!!! You will be really better off with MySQL, Postgres or Oracle.

As for the topic. There is a fix for this specific problem committed yesterday. Well, actually this is a work around some obscure SQLite behaviour (see warning above!). It will go into 1.2.3. If you need it faster feel free to get it off the svn and test

[dhewison]

Hi,

 Is there an easy way to migrate existing configuration and history to a better dB product ?

Regards,
David

[victor]

Hi!

There are export/import option in nxdbmgr. What it basically does is exporting data from your existing database into SQLite database file, and the importing into another database. As you have SQLite already, you can try to just create empty database on another engine, create correct netxmsd.conf, and the use your existing database file as input for nxdbmgr import command.

Best regards,
Victor

[dhewison]

Hi,

 I have now installed MySQL Community Server 5.5.27 (x64), re-installed NetXMS to include MySQL client support. I setup MySQL database thus:

 mysql> CREATE DATABASE netxms;
 mysql> GRANT ALL ON netxms.* TO netxms@localhost IDENTIFIED BY 'password'

 netxmsd.conf:
---------------------------------------------------------------------------------
#
# NetXMS Server configuration file
# Created by NetXMS Server configuration wizard at Wed May 09 15:31:46 2012
#

LogFile = {syslog}
DBDriver = C:\NetXMS\bin\mysql.ddr
DBServer = localhost
DBName = netxms
DBLogin = netxms
DBPassword = password
LogFailedSQLQueries = yes
---------------------------------------------------------------------------------

I initialised the database using:

 nxdbmgr.exe init C:\NetXMS\lib\sql\dbinit_mysql.sql

then I tried importing the existing configuration and history using:

 mxdbmgr.exe import C:\NetXMS\database\bn-netxms

 this results in the following output:

-------------------------------------------------------------------------
NetXMS Database Manager Version 1.2.2

WARNING!!!
This operation will clear all configuration and collected data from database.
Are you sure? (Y/N) Y
Database successfully cleared
Importing table config
Importing table config_clob
Importing table users
-------------------------------------------------------------------------

 The import generates an exception, logged as follows:

-------------------------------------------------------------------------
Faulting application name: nxdbmgr.exe, version: 0.0.0.0, time stamp: 0x500d3368
Faulting module name: libnetxmsw.dll, version: 0.0.0.0, time stamp: 0x500d32f4
Exception code: 0xc0000005
Fault offset: 0x000000000001c5ab
Faulting process id: 0x11b8
Faulting application start time: 0x01cd8c3483769b7d
Faulting application path: C:\NetXMS\bin\nxdbmgr.exe
Faulting module path: C:\NetXMS\bin\libnetxmsw.dll
Report Id: c265019d-f827-11e1-ad02-00155d002212
-------------------------------------------------------------------------

Regards,
David

[dhewison]

Hi,

 I forgot to mention, I had to upgrade the database with nxdbmgr.exe upgrade after the init.

Regards,
David

[victor]

Hi!

Just try to reproduce the error on my system, but without success. Is it possible to send me your SQLite database because I suspect that some combination of data causes this crash. If it violates your security policy, we will find other ways to debug it.

Best regards,
Victor

[dhewison]

Hi Victor,

 Is it possible to send it to you directly rather than making it publicly available here ?

Regards,
David

[victor]

Sure. Send it to [email protected].

Best regards,
Victor

[dhewison]

Hi Victor,

 It is too big to email and I don't want to put it on the forum so have you any suggestions on how I can debug the problem ?

Regards,
David

[dhewison]

Many thanks Victor, 1.2.3 has sorted the dB import error.

Best regards,
David