BLOB/TEXT column 'oid' can't have a default value

Post support questions that relate to the Windows 2003/2000/XP operating systems.

Moderators: Developers, Moderators

Post Reply
RayFrangie
Posts: 3
Joined: Sun Nov 12, 2006 5:45 pm

BLOB/TEXT column 'oid' can't have a default value

Post by RayFrangie »

Hi There,

On performing the manual installation of Cacti, following BSOD's Windows Installation Guide (btw, well done on this document, very easy to follow), I'm getting the following error when attempting to import the Cacti.sql database:

Code: Select all

C:\Inetpub\wwwroot\SBNetwork>mysql -u sbnetworkuser -p sbnwmondb < cacti.sql
Enter password: ************
ERROR 1101 (42000) at line 1890: BLOB/TEXT column 'oid' can't have a default value
The following are the specifications of the install:

Operating System: Windows Server 2003 (Build 3790.srv03_sp1_rtm.050324-1447 : Service Pack 1)
Webserver: IIS v6.0
Cacti: 0.86i
Cactid: 0.86i
MySQL: 5.0.27-community-nt via TCP/IP
PHP: 5.20
RRDTool (CYGWIN version): 1.5.20
Net-SNMP: 5.3.1-1
Cygwin (cygwin1.dll version): 1.5.21

I've got another install on Windows Server 2003 for another one of my production servers running 0.86i, on MySQL 4.1.14-nt-max via TCP/IP and the installation works fine, and is running live now.

If anyone can provide some information on how to resolve the abovementioned error, it'll be greatly appreciated

Many Thanks in Advance

Kind Regards,

Ray Frangie
Systems & Network Engineer
anthony302
Posts: 4
Joined: Mon Nov 13, 2006 5:29 am

Post by anthony302 »

hi,

i have the same problem, and i had delete the ligne, and it worked
But now, i don't have any graph, so i don't know if it's a good issue.
(sorry for my english, i'm french)
anthony302
Posts: 4
Joined: Mon Nov 13, 2006 5:29 am

Post by anthony302 »

finally, i used the installer of cacti, and it runs nice, it's really easier too install, i just had the same problem as "rallen" here:
http://forums.cacti.net/about14946.html ... =installer

and i fixed it up as he said with the .dll
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Post by BSOD2600 »

What missing dll was that?
RayFrangie
Posts: 3
Joined: Sun Nov 12, 2006 5:45 pm

Post by RayFrangie »

Hi Anthony,

I can't use the installer as I'm installing it onto an existing system with PHP and MySQL as specified below running sites already.

I highly doubt a .DLL is at fault because using the same version of cacti on a server running MySQL 4.1.14-nt works perfectly fine when importing.

My guess is its something to do with MySQL 5.0 changes from 4.1.

If anyone can provide information on how to fix the issue at hand, running the below components, that'll be greatly appreciated

Thanks and Regards,

Ray Frangie.
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Post by BSOD2600 »

1) dump the cacti database and delete the stuff related to it in your \mysql\data\cacti\ folder.

2) Disable sql-strict mode in MySQL's my.ini file. Then re-attempt the mysql steps. That should hopefully fix your problem.
RayFrangie
Posts: 3
Joined: Sun Nov 12, 2006 5:45 pm

Post by RayFrangie »

Thanks for that BSOD.

That's worked perfectly.

I think its that Strict Mode that has something to do with it?

Many thanks for your help

Cheers,

Ray Frangie.
anthony302
Posts: 4
Joined: Mon Nov 13, 2006 5:29 am

Post by anthony302 »

BSOD2600 wrote:What missing dll was that?
this one : msvcr71.dll
I had the same problem as "rallen" here :
http://forums.cacti.net/about14946.html
and to solve it, i downloaded the dll and put it into c:\php.
Now, it works very well, your installer is really easier :)
thanks for all.
User avatar
lard
Cacti User
Posts: 165
Joined: Wed Jul 20, 2005 10:48 am
Location: UK - Cambridge

Post by lard »

Hi All,

Just to confirm that using mySQL 5.0.27 - editing out the strict use settings in my.ini solved this problem for me,

Many thanks,

Larry
---- lard007skype ----
SamuelHenderson
Posts: 8
Joined: Wed Jan 10, 2007 3:38 pm

Post by SamuelHenderson »

2) Disable sql-strict mode in MySQL's my.ini file. Then re-attempt the mysql steps. That should hopefully fix your problem

Uh oh. I already went and just removed "default ' ' " from line 1896 to fix it...
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests