Hi crythias,
Thank you for all the help and suggestions. I appreciate your time and effort.
Thank You
SK
Search found 4 matches
- 12 Jan 2014, 21:20
- Forum: Help
- Topic: Upgrading From 3.2.13 to 3.3.0
- Replies: 8
- Views: 7733
- 12 Jan 2014, 20:11
- Forum: Help
- Topic: Upgrading From 3.2.13 to 3.3.0
- Replies: 8
- Views: 7733
Re: Upgrading From 3.2.13 to 3.3.0
Hi crythias;
I think the most simple way to do this will be to execute "SHOW TABLE STATUS" after selecting the database. All my tables are InnoDB and the default engine is set to InnoDB in /etc/my.cnf. If I remember correctly, OTRS required InnoDB before 3.2.10.
Thank You
SK
I think the most simple way to do this will be to execute "SHOW TABLE STATUS" after selecting the database. All my tables are InnoDB and the default engine is set to InnoDB in /etc/my.cnf. If I remember correctly, OTRS required InnoDB before 3.2.10.
Thank You
SK
- 12 Jan 2014, 14:05
- Forum: Help
- Topic: Upgrading From 3.2.13 to 3.3.0
- Replies: 8
- Views: 7733
Re: Upgrading From 3.2.13 to 3.3.0
Hi Crythias, Thank you for the prompt response. I will reply the points suggested and then explain what has been done since. 1. Indexes I don't know how to do this. 2. queue_standard_template doesn't exist on 3.2.13. This only gets created when migrating to 3.3.0. The current 3.2.13 is still operati...
- 27 Dec 2013, 13:01
- Forum: Help
- Topic: Upgrading From 3.2.13 to 3.3.0
- Replies: 8
- Views: 7733
Upgrading From 3.2.13 to 3.3.0
Hi, We are using OTRS 3.2.13 we have been trying to upgrade directly to 3.3.3 and indirectly 3.3.0.beta-3.3.0.beta2.....3.3.3. Unfortunately both of these attempts have failed. 1. DBUpdate-to-3.3.mysql.sql indicates an error at the following statement. ALTER TABLE standard_response DROP INDEX standa...