Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - DanG

#106
General Support / Re: 1.1.4 database upgrade error
September 12, 2011, 04:08:31 PM
I used fully qualified name, but that didn't work. Loging under the NetXMS user did it.

Upgrading the database then gave following error:
Upgrading database...
Upgrading from version 236 to 237
SQL query failed ([Microsoft][SQL Server Native Client 10.0][SQL Server]The obje
ct 'DF__business___statu__4C0144E4' is dependent on column 'status'.):
ALTER TABLE business_services DROP COLUMN status
Rolling back last stage due to upgrade errors...

Which i removed with :
ALTER TABLE business_services DROP CONSTRAINT DF__business___statu__4C0144E4;


After that database upgrade when on to success:

Upgrading database...
Upgrading from version 236 to 237
Upgrading from version 237 to 238
Upgrading from version 238 to 239
Upgrading from version 239 to 240
Database upgrade succeeded

I can now start the core service.

Thanks Victor.

I guess this sould be corrected in the install  procedure?

Dan
#107
General Support / Re: 1.1.4 database upgrade error
September 12, 2011, 03:57:08 PM
running the alter tabel returns the following error:
Msg 4902, Level 16, State 1, Line 2
Cannot find the object "business_services" because it does not exist or you do not have permissions.

It souldn't be premission as I'm logged in as sa.

Tried deleting using the SQL Server Management Studio, however I get the same:
The Defualt "DF_business..." does not exist.

Any Idea?

Dan
#108
General Support / 1.1.4 database upgrade error
September 12, 2011, 03:13:56 PM
Hello,

When trying to upgrade using MS SQL Express 2008 R2 I receive an error with the native SQL driver being newer than the to be installed.
Since I'm using ODBC (as the native driver did not work inn 1.1.3)  this error is strange.
I then uninstalled NetXMS 1.1.3. Installed a clean 1.1.4 and followed the wizard to reconfigure all settings. I selected the same ODBC config.
Installation wend without any error.
Since the core service was not started I continued with the database upgrade, however I get receive the following error:


C:\Program Files\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 1.1.4

Upgrading database...
Upgrading from version 236 to 237
SQL query failed ([Microsoft][SQL Server Native Client 10.0][SQL Server]The obje
ct 'DF__business___paren__4B0D20AB' is dependent on column 'parent_id'.):
ALTER TABLE business_services DROP COLUMN parent_id
Rolling back last stage due to upgrade errors...
Database upgrade failed

I guess there's a foreigner key problem.

What should I do?

Thanks,

Dan
#109
Victor,

This is great news! I Look forward to using the next release.

Dan
#110
I'm glad to hear you agree with me  ;D

The points you mentioned about maintaining compatibility are without any doubt very important.

If I may propose a solution, you may want to introduce named parameters instead op %digit notation.
This will solve all the problems as current parameters will remain unchanged and new parameters will have another form. I believe using named parameters present other advantages:
-   Easier to read.
-   Easier for you to extend over time, no ordering issues and no issue when the number of parameters becomes large.
-   Can be made easier to type with a auto-complete (this is I guess me just getting too excited) ;-)
There is some performance penalty when replacing named parameters with there values, but I don't think  this should be significant.

Dan
#111
Feature Requests / parameters SYS_THRESHOLD_REARMED
July 29, 2011, 11:57:11 AM
Documentation states that the SYS_THRESHOLD_REARMED event has 4 parameters which is less than those available for a triggering event.
It would be better if all parameters would be available for the SYS_THRESHOLD_REARMED event as well as these give valuable information.
As an example when monitoring free disk space, when the capacity goes above the threshold it's nice to know what the threshold was and was is the current value. Unless of course this can be achieved in some other way?