Ok I had the same EXACT problem once before...This is my solution. Taken from another post on the same subject I posted over at mbdc.net
It was my nuke_banners table.
I looked at the .sql file that came with Nuke 6.0 and I was comparing it to my SQL tables that I have in MySQL database.
Anyway to make a long story short. My nuke_banners table only had like 9 rows when it should have been 12 or so. I dropped my nuke_banners table and then cut the nuke_banners information from the nuke.sql file and pasted it in notepad. saved it as banners.sql and uploaded it to MySQL with phpadmin.
VIOLA. I have NO MORE SQL ERRORS!!!
WOO-HOO.
If anyone needs to repeat this process and can't figure it out, lemme know. Your error or errors may not be associated to the same table mine was. Check through your MySQL tables and compare them one at a time to another 6.0 site with 2.0.6 port SQL Database, or to the nuke.sql file.
Here's what you need to make a new nuke_banners table. Just copy and paste this in notepad and save as banners.sql. You can then upload it through phpmyadmin after you Drop your exisiting nuke_banners table. This will erase all your banner data if you use banners. But worth getting rid of the SQL errors in my opinion.
Code:
#
# Table structure for table `nuke_banner`
#
CREATE TABLE nuke_banner (
bid int(11) NOT NULL auto_increment,
cid int(11) NOT NULL default '0',
imptotal int(11) NOT NULL default '0',
impmade int(11) NOT NULL default '0',
clicks int(11) NOT NULL default '0',
imageurl varchar(100) NOT NULL default '',
clickurl varchar(200) NOT NULL default '',
alttext varchar(255) NOT NULL default '',
date datetime default NULL,
dateend datetime default NULL,
type tinyint(1) NOT NULL default '0',
active tinyint(1) NOT NULL default '1',
PRIMARY KEY (bid),
KEY bid (bid),
KEY cid (cid)
) TYPE=MyISAM;
#
# Dumping data for table `nuke_banner`
#
mikem