[xwiki-users] Upgrade to 3.2 minor issues
Hello, Thanks a lot for 3.2 Release! From the good things I've noticed, the full text search indeed returns more relevant result - especially the look-up in search. However when doing an upgrade (from 3.1) I saw a weird exception 2011-10-12 07:57:54,556 [http://localhost/xwiki/bin/view/XWiki/WatchListRss?xpage=plain&outputSyntax=...] ERROR .x.x.s.XWikiHibernateBaseStore - Failed updating schema while executing query [alter table activitystream_events_param
s add index FKB94E2E7C763934E1 (eventId), add constraint FKB94E2E7C763934E1 foreign key (eventId) references activitystream_events (ase_eventid)] java.sql.SQLException: Can't create table './xwiki_utf8/#sql-dd6_11c9e.frm' (errno: 150)
I did not notice anything broken (well, except that work-spaces menu item did not show-up, but I guess some configuration must be done to enable it). Is it ok just to ignore this exception? Regards, Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p6883... Sent from the XWiki- Users mailing list archive at Nabble.com.
On 10/12/2011 04:01 AM, coldserenity wrote:
Hello,
Thanks a lot for 3.2 Release! From the good things I've noticed, the full text search indeed returns more relevant result - especially the look-up in search.
Please report anything you still don't like with the search results. Adjusting the scoring mechanism isn't something that can be precisely done without real word experiments, so real feedback is much appreciated (and needed).
However when doing an upgrade (from 3.1) I saw a weird exception
2011-10-12 07:57:54,556 [http://localhost/xwiki/bin/view/XWiki/WatchListRss?xpage=plain&outputSyntax=...] ERROR .x.x.s.XWikiHibernateBaseStore - Failed updating schema while executing query [alter table activitystream_events_param
s add index FKB94E2E7C763934E1 (eventId), add constraint FKB94E2E7C763934E1 foreign key (eventId) references activitystream_events (ase_eventid)] java.sql.SQLException: Can't create table './xwiki_utf8/#sql-dd6_11c9e.frm' (errno: 150)
I did not notice anything broken (well, except that work-spaces menu item did not show-up, but I guess some configuration must be done to enable it). Is it ok just to ignore this exception?
Weird, it doesn't look like code problem, but more like a database one. (Google pointed me to http://bugs.mysql.com/bug.php?id=25596). Can you provide the full stacktrace for this + mysql version? To answer your question, the activitystream_events_params table isn't important yet, it's not used by default, so yes, you can ignore the error for the moment, although we'd like to fix it.
Regards, Roman
-- Sergiu Dumitriu http://purl.org/net/sergiu/
Please report anything you still don't like with the search results. Adjusting the scoring mechanism isn't something that can be precisely done without real word experiments, so real feedback is much appreciated (and needed). I'll keep that in mind :)
Can you provide the full stack trace for this + mysql version? Stack trace: http://xwiki.475771.n2.nabble.com/file/n6884099/CannotCreateTableStackTrace.... CannotCreateTableStackTrace.txt MySQL version: 5.0.77
-- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p6884... Sent from the XWiki- Users mailing list archive at Nabble.com.
On 10/12/2011 04:53 AM, coldserenity wrote:
Please report anything you still don't like with the search results. Adjusting the scoring mechanism isn't something that can be precisely done without real word experiments, so real feedback is much appreciated (and needed). I'll keep that in mind :)
Can you provide the full stack trace for this + mysql version? Stack trace: http://xwiki.475771.n2.nabble.com/file/n6884099/CannotCreateTableStackTrace.... CannotCreateTableStackTrace.txt MySQL version: 5.0.77
Hm, it's really weird. Could you upgrade the version of MySQL used? Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? -- Sergiu Dumitriu http://purl.org/net/sergiu/
Could you upgrade the version of MySQL used? I can try to but that might take me couple of days since I'm not a MySQL guru
Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? I have attached the file http://xwiki.475771.n2.nabble.com/file/n6884313/XwikiDatabaseCollationsAndEn... XwikiDatabaseCollationsAndEngines.txt with engines/collations/encodings information. All of tables are on UTF8 but it turns out that all tables of my XWiki use 'MyISAM' engine except for 'activitystream_events_params' which uses 'InnoDB'. I have a strong feeling that's not how it should have been. Can this issue be also related to changing the hibernate dialect from 'org.hibernate.dialect.MySQLDialect' to 'org.hibernate.dialect.MySQL5InnoDBDialect'?
-- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p6884... Sent from the XWiki- Users mailing list archive at Nabble.com.
On 10/12/2011 06:02 AM, coldserenity wrote:
Could you upgrade the version of MySQL used? I can try to but that might take me couple of days since I'm not a MySQL guru
Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? I have attached the file http://xwiki.475771.n2.nabble.com/file/n6884313/XwikiDatabaseCollationsAndEn... XwikiDatabaseCollationsAndEngines.txt with engines/collations/encodings information. All of tables are on UTF8 but it turns out that all tables of my XWiki use 'MyISAM' engine except for 'activitystream_events_params' which uses 'InnoDB'. I have a strong feeling that's not how it should have been. Can this issue be also related to changing the hibernate dialect from 'org.hibernate.dialect.MySQLDialect' to 'org.hibernate.dialect.MySQL5InnoDBDialect'?
Yes, and my main suspect is the fact that MySQL doesn't support linking two types of tables with a foreign key. You can do two things: 1. Change the configuration back to MySQLDialect, drop the activitystream_events_params table, restart XWiki. 2. Change all the other tables to use the InnoDB engine, with a statement like this for each table: alter table xwikircs ENGINE=InnoDB; For the future, 2 is better. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Thanks Sergiu for your help. I'll go with the second approach. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Wednesday, October 12, 2011 21:44 PM To: XWiki Users Subject: Re: [xwiki-users] Upgrade to 3.2 minor issues On 10/12/2011 06:02 AM, coldserenity wrote:
Could you upgrade the version of MySQL used? I can try to but that might take me couple of days since I'm not a MySQL guru
Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? I have attached the file http://xwiki.475771.n2.nabble.com/file/n6884313/XwikiDatabaseCollation sAndEngines.txt XwikiDatabaseCollationsAndEngines.txt with engines/collations/encodings information. All of tables are on UTF8 but it turns out that all tables of my XWiki use 'MyISAM' engine except for 'activitystream_events_params' which uses 'InnoDB'. I have a strong feeling that's not how it should have been. Can this issue be also related to changing the hibernate dialect from 'org.hibernate.dialect.MySQLDialect' to 'org.hibernate.dialect.MySQL5InnoDBDialect'?
Yes, and my main suspect is the fact that MySQL doesn't support linking two types of tables with a foreign key. You can do two things: 1. Change the configuration back to MySQLDialect, drop the activitystream_events_params table, restart XWiki. 2. Change all the other tables to use the InnoDB engine, with a statement like this for each table: alter table xwikircs ENGINE=InnoDB; For the future, 2 is better. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
On 10/12/2011 04:50 PM, Roman Muntyanu wrote:
Thanks Sergiu for your help. I'll go with the second approach.
Please let me know if that solves the problem, so that I can put a warning in the release notes.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sergiu Dumitriu Sent: Wednesday, October 12, 2011 21:44 PM To: XWiki Users Subject: Re: [xwiki-users] Upgrade to 3.2 minor issues
On 10/12/2011 06:02 AM, coldserenity wrote:
Could you upgrade the version of MySQL used? I can try to but that might take me couple of days since I'm not a MySQL guru
Is the activitystream_events table correctly set up with utf8 encoding? Are the other tables using InnoDB or MyISAM? I have attached the file http://xwiki.475771.n2.nabble.com/file/n6884313/XwikiDatabaseCollation sAndEngines.txt XwikiDatabaseCollationsAndEngines.txt with engines/collations/encodings information. All of tables are on UTF8 but it turns out that all tables of my XWiki use 'MyISAM' engine except for 'activitystream_events_params' which uses 'InnoDB'. I have a strong feeling that's not how it should have been. Can this issue be also related to changing the hibernate dialect from 'org.hibernate.dialect.MySQLDialect' to 'org.hibernate.dialect.MySQL5InnoDBDialect'?
Yes, and my main suspect is the fact that MySQL doesn't support linking two types of tables with a foreign key.
You can do two things:
1. Change the configuration back to MySQLDialect, drop the activitystream_events_params table, restart XWiki.
2. Change all the other tables to use the InnoDB engine, with a statement like this for each table:
alter table xwikircs ENGINE=InnoDB;
For the future, 2 is better.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
I had the same issue, the workaround I used was solution 3 : move back table activitystream_events_params to use MyISAM ;) Switching to InnoDb is not without consequences : in my case I perform full online backups with mysqlhotcopy command, with InnoDb it won't be possible anymore. And to perform online backups I will have to switch to mysqldump's (what I was using to start with, and I stopped because I found it really not easy to restore backups, and really far longer than with hot copy of tables files - hours instead of minutes on slow FS). mysqlbackup is not part of the community edition of mysql ... :( -- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p6912... Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi Sergiu, I have updated my database engine to 'InnoDB'. I just took the query from previously attached file and by using Notepad++ and text replace created a set of alters to update engine. I ran those alters one-by-one. With a success :) ============================================== Some helpful queries and steps ============================================== 1. Backup current wiki mysqldump --user=xwiki --password=xwiki --default-character-set=utf8 xwiki_utf8 > dump.sql 2. Create new database CREATE DATABASE db_name xwiki_utf8_innodb CHARACTER SET=utf8 COLLATE=utf8_general_ci 3. Import data from backup into new database mysql --user=xwiki --password=xwiki --default-character-set=utf8 xwiki_utf8_innodb < dump.sql 4. Log-in to mysql mysql --user=xwiki --password=xwiki 5. Switch to newly created database use xwiki_utf8_innodb; 6. Get list of tables requiring update SELECT TABLE_SCHEMA, TABLE_NAME, ENGINE, COLLATION_NAME, CHARACTER_SET_NAME FROM information_schema.`TABLES` T, information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA WHERE CCSA.collation_name = T.table_collation AND T.table_schema = "xwiki_utf8_innodb"; 7. Capture the output from previous and replace '| xwiki_utf8_innodb |' -> 'ALTER TABLE' '| MyISAM | utf8_general_ci | utf8 |' -> 'ENGINE=InnoDB' 8. Run list of created alters from previous step one-by-one 9. Verify that all engines are updated. 10. Update your hibernate.cfg.xml to use new database 11. Restart Tomcat -- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p6964... Sent from the XWiki- Users mailing list archive at Nabble.com.
And yes, that solved original problem -- View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-to-3-2-minor-issues-tp6883965p6967... Sent from the XWiki- Users mailing list archive at Nabble.com.
participants (4)
-
coldserenity -
jerem -
Roman Muntyanu
-
Sergiu Dumitriu