Error After Upgrade to 3.3.7 [SOLVED]

Moderator: crythias

Locked
davidbann
Znuny newbie
Posts: 92
Joined: 21 Jun 2010, 22:51
Znuny Version: 6.5.2
Real Name: David Bann
Location: South Africa

Error After Upgrade to 3.3.7 [SOLVED]

Post by davidbann »

Hi,

I am running OTRS on windows...

I just upgraded from 3.2.8 to 3.3.7. While doing the upgrade I got an error when running the MYSQL upgrade script (scripts/DBUpdate-to-3.3.mysql.sql).

The error I received was:

Code: Select all

ERROR 1072 (42000): Key column 'a_message_id_md5' doesn't exist in table.
I then ran scripts/DBUpdate-to-3.3.pl which and gave a smiliar error:

Code: Select all

Message: Unknown column 'a_message_id_md5' in 'field list', SQL: '
               UPDATE article
               SET a_message_id_md5 = MD5(a_message_id)
               WHERE a_message_id IS NOT NULL
               '

Traceback (37356):
  Module: main::_GenerateMessageIDMD5 (unknown version) Line: 582
  Module: DBUpdate-to-3.3.pl (unknown version) Line: 99
What do I need to do to get this working correctly again?

Any help will be very much appreciated!

Regards,
David
Last edited by davidbann on 19 May 2014, 21:22, edited 1 time in total.
davidbann
Znuny newbie
Posts: 92
Joined: 21 Jun 2010, 22:51
Znuny Version: 6.5.2
Real Name: David Bann
Location: South Africa

Re: Error After Upgrade to 3.3.7

Post by davidbann »

Ok some more useful information - when the MySql script tries to add the new column to the articles table it also shows an error "table is full". I am using InnoDB, and searches indicate that the problem is either that my partition has run out of space, or I need to make sure that I have set innodb_data_file_path=ibdata1:10M:autoextend which I have done. Even with the new setting and after making sure that the partition is nowhere near full, I still get this error...

My /mysql/data/ibdata1 file is currently 1.1Gb - I am running Win 2003 64 bit on NTFS, so I dont think the file size should be an issue. Here are my InnoDB settings for MySql:

Code: Select all

mysql> show variables LIKE 'innodb%';
+-----------------------------------------+------------------------+
| Variable_name                           | Value                  |
+-----------------------------------------+------------------------+
| innodb_adaptive_hash_index              | ON                     |
| innodb_additional_mem_pool_size         | 2097152                |
| innodb_autoextend_increment             | 8                      |
| innodb_autoinc_lock_mode                | 1                      |
| innodb_buffer_pool_size                 | 52428800               |
| innodb_checksums                        | ON                     |
| innodb_commit_concurrency               | 0                      |
| innodb_concurrency_tickets              | 500                    |
| innodb_data_file_path                   | ibdata1:10M:autoextend |
| innodb_data_home_dir                    | C:\otrs\mysql\data\    |
| innodb_doublewrite                      | ON                     |
| innodb_fast_shutdown                    | 1                      |
| innodb_file_io_threads                  | 4                      |
| innodb_file_per_table                   | OFF                    |
| innodb_flush_log_at_trx_commit          | 1                      |
| innodb_flush_method                     |                        |
| innodb_force_recovery                   | 0                      |
| innodb_lock_wait_timeout                | 50                     |
| innodb_locks_unsafe_for_binlog          | OFF                    |
| innodb_log_buffer_size                  | 8388608                |
| innodb_log_file_size                    | 12582912               |
| innodb_log_files_in_group               | 2                      |
| innodb_log_group_home_dir               | C:\otrs\mysql\data\    |
| innodb_max_dirty_pages_pct              | 90                     |
| innodb_max_purge_lag                    | 0                      |
| innodb_mirrored_log_groups              | 1                      |
| innodb_open_files                       | 300                    |
| innodb_rollback_on_timeout              | OFF                    |
| innodb_stats_on_metadata                | ON                     |
| innodb_support_xa                       | ON                     |
| innodb_sync_spin_loops                  | 20                     |
| innodb_table_locks                      | ON                     |
| innodb_thread_concurrency               | 8                      |
| innodb_thread_sleep_delay               | 10000                  |
| innodb_use_legacy_cardinality_algorithm | ON                     |
+-----------------------------------------+------------------------+
35 rows in set (0.00 sec)
Any ideas?
davidbann
Znuny newbie
Posts: 92
Joined: 21 Jun 2010, 22:51
Znuny Version: 6.5.2
Real Name: David Bann
Location: South Africa

Re: Error After Upgrade to 3.3.7

Post by davidbann »

Ok I finally figured this one out. I added innodb_file_per_table to my.ini, restarted, ran the sql script again and it worked. I then ran the perl database file again and that worked too - all sorted now :)
Locked