Magento

From 1.1.8
upgrade using Mage_All_Latest tag with the cache disable
settings are set to Stable
I have Improved_Search module installed as well as languages module installed

I tested with removing Improved_Search before upgrading, but I have the same exception. ( full PDO exception attached )

Error in file: “/var/www/test/app/code/core/Mage/CatalogSearch/sql/catalogsearch_setup/mysql4-upgrade-0.7.5-0.7.6.php” - SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘catalogsearch_result’ already exists
Trace:
#0 /var/www/test/app/code/core/Mage/Core/Model/Resource/Setup.php(287): Mage::exception(’Mage_Core’, ‘Error in file: ...’)
#1 /var/www/test/app/code/core/Mage/Core/Model/Resource/Setup.php(179): Mage_Core_Model_Resource_Setup->_modifyResourceDb(’upgrade’, ‘0.7.4’, ‘0.7.6’)
#2 /var/www/test/app/code/core/Mage/Core/Model/Resource/Setup.php(146): Mage_Core_Model_Resource_Setup->_upgradeResourceDb(’0.7.4’, ‘0.7.6’)
#3 /var/www/test/app/code/core/Mage/Core/Model/Resource/Setup.php(121): Mage_Core_Model_Resource_Setup->applyUpdates()
#4 /var/www/test/app/code/core/Mage/Core/Model/Config.php(215): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5 /var/www/test/app/code/core/Mage/Core/Model/App.php(241): Mage_Core_Model_Config->init(Array)
#6 /var/www/test/app/Mage.php(427): Mage_Core_Model_App->init(’’, ‘store’, Array)
#7 /var/www/test/app/Mage.php(446): Mage::app(’’, ‘store’, Array)
#8 /var/www/test/index.php(52): Mage::run()

PDOException.txt  (File Size: 12KB - Downloads: 395)

Same error here.

Same error here

Bump. Any ideas anyone?

ok it seems that somehow the script try to run twice, just found that on an earlier backup that I dont have catalogsearch_result into it.

for those who have this issue either

- You wait for magento to resolv this
- You just create a NEW table and import a backup that has been made before the 1.2.0 first try upgrade and try again with all cache disable.

good luck

Please specify the value of the table core_resource with code catalogindex_setup

If the version 0.7.9
run

In this case, the problem aside extension that create magento module (catalogsearch) table, which should not create
These extension, must be create tables with the extension name prefix.

Has anyone been able to get around this one? I posted the problem in a different thread before I discovered this one. Seems quite a number of people are reporting similar issues.

Just open up that file in your editor and then comment out the php code that tries to create the table.
This type of error happens when the upgrade script already ran once and it tries to run again so commenting them out is totally fine.

You will probably run into couple more of these, repeat the steps for the other files it complains about as well.

As far as I know, there is extension of finding which does not include the core, and that create a table catalogsearch_result
Therefore, before commenting creating tables - sure to create an identical table as the upgrade

If a table set up another module: is recommended to remove or rename the table and start the process of upgrade

Guys I’m getting the same f********g error..

What is causing the errors and what is the simplest way to troubleshoot these and/or fix them???

Fortunately I had a full bkup for the App directory so have simply untarred that again..

This really stinks..  Why is it so difficult to simply upgrade the store????

Life is going from bad to worse..

I have tried to revert to my backup files and now I am getting even more errors???

Can anyone help please?  The url is http://capitalhairandbeautyspain.com/store/

Hi Mike,

What did you do to get your site back up?

I solved this by changing the data in the database.
Table core_resource holds current versions of all modules. It seems that it wasn’t updated during the update process.
I had to make three changes:

First I changed catalogsearch_setup from version 0.7.5 to 0.7.6 and reloaded my homepage.
Next error was about cataloginventory_setup, so I changed it from 0.7.4 to 0.7.5 and reloaded homepage
Finally, I changed cataloginventory_setup to 0.7.9. After that all was fine.

Maybe it is possible to change cataloginventory_setup to 0.7.9 right away, but don’t take my word for it.

Hope this helps someone.

Sincerely,

Bojan Hrnkas

Commenting out the part where the table is created, helped. Thanks Simple Helix

This is what I commented out:

CREATE TABLE `{$installer->getTable(’catalogsearch_result’)}` (
`query_id` int(10) unsigned NOT NULL,
`product_id` int(10) unsigned NOT NULL,
`relevance` decimal(6,4) NOT NULL default ‘0.0000’,
PRIMARY KEY (`query_id`,`product_id`),
KEY `IDX_QUERY` (`query_id`),
KEY `IDX_PRODUCT` (`product_id`),
KEY `IDX_RELEVANCE` (`query_id`, `relevance`),
CONSTRAINT `FK_CATALOGSEARCH_RESULT_QUERY` FOREIGN KEY (`query_id`) REFERENCES `{$installer->getTable(’catalogsearch_query’)}` (`query_id`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `FK_CATALOGSEARCH_RESULT_CATALOG_PRODUCT` FOREIGN KEY (`product_id`) REFERENCES `{$installer->getTable(’catalog_product_entity’)}` (`entity_id`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Not sure if this causes trouble with future updates but I’ll stay away from that for a while