Mysql table and column errors during upgrade

[tparson]

Fedora Core 5
PHP 4.4.6
MySql 4.1.1

Sugar Version where problem lies 4.51 OS

MySql buffs, sharpen your pencils. I have just pulled a customers OS from 3.0.1 up to 4.5.1 with much pain, but sucessfully. Data seems to be solid. So now I'm trying to move them to Pro. Using patch SugarOS-to-SugarPro-Upgrade-4.5.1b

I upload the file after getting the all clear on precheck and then the following errors are shown:



table exists::CREATE TABLE `session_active` ( `id` char(36) NOT NULL default '', `session_id` varchar(100) default NULL, `last_request_time` datetime default NULL, `session_type` varchar(100) default NULL, `is_violation` tinyint(1) default '0', `num_active_sessions` int(11) default '0', `date_entered` datetime default NULL, `date_modified` datetime default NULL, `deleted` tinyint(1) NOT NULL default '0', PRIMARY KEY (`id`), UNIQUE KEY `idx_session_id` (`session_id`) )

table exists::CREATE TABLE `session_history` ( `id` char(36) NOT NULL default '', `session_id` varchar(100) default NULL, `date_entered` datetime default NULL, `date_modified` datetime default NULL, `last_request_time` datetime default NULL, `session_type` varchar(100) default NULL, `is_violation` tinyint(1) default '0', `num_active_sessions` int(11) default '0', `deleted` tinyint(1) NOT NULL default '0', PRIMARY KEY (`id`) )

Duplicate column name 'portal_password'::ALTER TABLE `contacts` ADD COLUMN `portal_password` varchar(32) NULL AFTER `portal_active`


Any ideas? I've gone through the database, and yes they do already exist. Should they not? If not, how on earth did they get there and how do I make them go away safely?

Thanks!

Tracy

[ruchida]

Hi
I think these tables should not be there. I don't see these ones in Sugar Open Source 4.5.1.

Regarding the duplicate column error, have you installed any custom module? If yes, it might have added the same column.

[tparson]

Thank you for your reply.

I was also wondering if there is a module added that might cause this. I guess I'll back up, remove the column/tables and see what happens.

Thank you.

Tracy

[tparson]

A final note on this subject: Removing the tables and extra column worked perfectly, no harm done. Upgrade went smoothly.

Thank you for your ideas.

Tracy