Help upgrade 2.0 to 2.2.6 errors
Went through upgrade as per notes (I think) all went ok it seemed until I tried logging into OTRS again. Can login, but will not show tickets. have I missed something? I have run the extra database ALTER TABLE ticket ADD escalation_response_time INTEGER; ALTER TABLE ticket ADD escalation_solution_time INTEGER; as per some notes I picked up from users. Any help appreciated to get my OTRS back up and running. Software error: Can't use an undefined value as a HASH reference at ../..//Kernel/System/Ticket/Article.pm line 1409. For help, please send mail to the webmaster (root@localhost mailto:root@localhost), giving this error message and the time and date of the error. -- Gary Smith -
Gary Smith wrote:
Went through upgrade as per notes (I think) all went ok it seemed until I tried logging into OTRS again. Can login, but will not show tickets.
have I missed something?
I have run the extra database
ALTER TABLE ticket ADD escalation_response_time INTEGER; ALTER TABLE ticket ADD escalation_solution_time INTEGER;
as per some notes I picked up from users.
Any help appreciated to get my OTRS back up and running.
Have you also run the other database upgrade scripts? Nils Breunese.
Thanks Nils, #cat $OTRS_HOME/scripts/DBUpdate-to-2.2.mysql.sql | mysql -p -f -u otrs otrs #cat $OTRS_HOME/scripts/DBUpdate-to-2.1.mysql.sql | mysql -p -f -u root otrs #cat $OTRS_HOME/scripts/DBUpdate-to-2.0.mysql.sql | mysql -p -f -u root otrs I did them all as I picked up in he notes. Running it again produces the following errors. Are these normal for a Upgrade script to be ran more than once? It looks like it to me. Can anyone tell me what the error signifies? Is it a premissions related error, or database? Thanks Gary bash-3.00$ cat /opt/otrs/scripts/DBUpdate-to-2.2.mysql.sql | mysql -p -f -u otrs otrs Enter password: ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists ERROR 1054 (42S22) at line 36: Unknown column 'escalation_time' in 'queue' ERROR 1060 (42S21) at line 37: Duplicate column name 'first_response_time' ERROR 1060 (42S21) at line 38: Duplicate column name 'solution_time' ERROR 1060 (42S21) at line 43: Duplicate column name 'valid_id' ERROR 1050 (42S01) at line 49: Table 'ticket_type' already exists ERROR 1062 (23000) at line 60: Duplicate entry 'default' for key 2 ERROR 1060 (42S21) at line 68: Duplicate column name 'freetime3' ERROR 1060 (42S21) at line 69: Duplicate column name 'freetime4' ERROR 1060 (42S21) at line 70: Duplicate column name 'freetime5' ERROR 1060 (42S21) at line 71: Duplicate column name 'freetime6' ERROR 1060 (42S21) at line 72: Duplicate column name 'type_id' ERROR 1060 (42S21) at line 73: Duplicate column name 'service_id' ERROR 1060 (42S21) at line 74: Duplicate column name 'sla_id' ERROR 1060 (42S21) at line 75: Duplicate column name 'escalation_response_time' ERROR 1060 (42S21) at line 76: Duplicate column name 'escalation_solution_time' ERROR 1060 (42S21) at line 82: Duplicate column name 'type_id' ERROR 1062 (23000) at line 87: Duplicate entry 'TypeUpdate' for key 2 ERROR 1062 (23000) at line 91: Duplicate entry 'ServiceUpdate' for key 2 ERROR 1062 (23000) at line 95: Duplicate entry 'SLAUpdate' for key 2 ERROR 1146 (42S02) at line 103: Table 'otrs.ticket_watcher' doesn't exist ERROR 1146 (42S02) at line 104: Table 'otrs.ticket_watcher' doesn't exist ERROR 1050 (42S01) at line 109: Table 'service' already exists ERROR 1050 (42S01) at line 127: Table 'service_customer_user' already exists ERROR 1050 (42S01) at line 140: Table 'sla' already exists ERROR 1091 (42000) at line 164: Can't DROP 'xml_content_key'; check that column/key exists ERROR 1091 (42000) at line 165: Can't DROP 'xml_type'; check that column/key exists ERROR 1091 (42000) at line 166: Can't DROP 'xml_key'; check that column/key exists ERROR 1061 (42000) at line 167: Duplicate key name 'xml_storage_xml_content_key' ERROR 1061 (42000) at line 168: Duplicate key name 'xml_storage_key_type' bash-3.00$ Gary Smith - Director Phoenix Broadband Ltd 116 Henderson Street, Bridge of Allan, STIRLING, FK9 4HF, UK. Tel : 0870 055 3152 Fax : 0870 0553154 Mob: +44 (0) 7971 504798 Sales / Accounts Tel 0870 220 0573. www.medusabusiness.com *** BCA "Trade Supplier of the Year 2006" *** Phoenix Broadband Ltd Registered Number SC 240139 (Scotland) Phoenix Broadband Ltd VAT Registation Number GB 806 1548 41 Phoenix Broadband Ltd Registered Office 116 Henderson Street Bridge of Allan Stirling FK9 4HF -- This e-mail transmission is intended exclusively for the individual(s) to whom it is addressed and may contain information that is privileged, or confidential. If you receive this e-mail in error, please advise the sender immediately and then delete the e-mail. Nils Breunese (Lemonbit) wrote:
Gary Smith wrote:
Went through upgrade as per notes (I think) all went ok it seemed until I tried logging into OTRS again. Can login, but will not show tickets.
have I missed something?
I have run the extra database
ALTER TABLE ticket ADD escalation_response_time INTEGER; ALTER TABLE ticket ADD escalation_solution_time INTEGER;
as per some notes I picked up from users.
Any help appreciated to get my OTRS back up and running.
Have you also run the other database upgrade scripts?
Nils Breunese. _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
Gary Smith wrote:
#cat $OTRS_HOME/scripts/DBUpdate-to-2.2.mysql.sql | mysql -p -f -u otrs otrs #cat $OTRS_HOME/scripts/DBUpdate-to-2.1.mysql.sql | mysql -p -f -u root otrs #cat $OTRS_HOME/scripts/DBUpdate-to-2.0.mysql.sql | mysql -p -f -u root otrs
This seems like the wrong order to run these scripts in. You said you were running 2.0, so you I'd first run the update to 2.1 and then the update to 2.2 script.
I did them all as I picked up in he notes. Running it again produces the following errors. Are these normal for a Upgrade script to be ran more than once? It looks like it to me.
You will get those 'already exists' errors when running the scripts again. There is no real harm in that I believe. There are other errors there though. I'd start over with a backup of your 2.0 database and then apply the update to 2.1 and then to 2.2. Nils Breunese.
Hi Nils, I did execute in the correct order, just listed them incorrectly below. I dropped database, restored from backup and re applied the 2.1 and 2.2 Sql files below. Now am getting different errors. Got no Ticket Object! at ../..//Kernel/Output/HTML/NavBarModuleAdmin.pm The database seems ok and updates to database went in without faults. Any thoughts on what these might be? Thanks Again Gary Nils Breunese (Lemonbit) wrote:
Gary Smith wrote:
#cat $OTRS_HOME/scripts/DBUpdate-to-2.2.mysql.sql | mysql -p -f -u otrs otrs #cat $OTRS_HOME/scripts/DBUpdate-to-2.1.mysql.sql | mysql -p -f -u root otrs #cat $OTRS_HOME/scripts/DBUpdate-to-2.0.mysql.sql | mysql -p -f -u root otrs
This seems like the wrong order to run these scripts in. You said you were running 2.0, so you I'd first run the update to 2.1 and then the update to 2.2 script.
I did them all as I picked up in he notes. Running it again produces the following errors. Are these normal for a Upgrade script to be ran more than once? It looks like it to me.
You will get those 'already exists' errors when running the scripts again. There is no real harm in that I believe. There are other errors there though. I'd start over with a backup of your 2.0 database and then apply the update to 2.1 and then to 2.2.
Nils Breunese. _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
Gary Smith wrote:
I did execute in the correct order, just listed them incorrectly below.
I dropped database, restored from backup and re applied the 2.1 and 2.2 Sql files below.
Now am getting different errors.
Got no Ticket Object! at ../..//Kernel/Output/HTML/ NavBarModuleAdmin.pm
The database seems ok and updates to database went in without faults.
Any thoughts on what these might be?
I guess you also upgraded the OTRS files to 2.2? If you're running OTRS under mod_perl you need to restart apache. Other than that I have no ideas at this time. Nils Breunese.
participants (2)
-
Gary Smith -
Nils Breunese (Lemonbit)