Re: [otrs] DBUpdate-to-3.2 errors during upgrade from 3.1.12 -> 3.2.2

2013-03-18 Thread Ralf Hildebrandt
* Michiel Beijen :

> the ticket_answered column does exist in OTRS 3.1 databases (otherwise the
> ticket API would not work); so if it's not there when you run the DBUpdate
> SQL this is probably because this is the second time you ran it? 

Only ran it once, BTW. I cut&pasted from the screen output.

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
http://www.charite.de  Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
-
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

Re: [otrs] DBUpdate-to-3.2 errors during upgrade from 3.1.12 -> 3.2.2

2013-03-18 Thread Ralf Hildebrandt
* Michiel Beijen :

> > otrs:/opt/otrs# cat scripts/DBUpdate-to-3.2.mysql.sql | mysql -p -f -u root 
> > otrs
> > Enter password:
> > ERROR 1091 (42000) at line 20: Can't DROP 'ticket_answered'; check that 
> > column/key exists
> >
> 
> the ticket_answered column does exist in OTRS 3.1 databases (otherwise the
> ticket API would not work); 

So why would the 3.1 -> 3.2 migration script want to drop that?
I mean if it's not there to being with in 3.1, why drop it?

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
http://www.charite.de  Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
-
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

Re: [otrs] DBUpdate-to-3.2 errors during upgrade from 3.1.12 -> 3.2.2

2013-03-18 Thread Michiel Beijen
Hi Ralf,


On Mon, Mar 18, 2013 at 2:25 PM, Ralf Hildebrandt <
ralf.hildebra...@charite.de> wrote:

> otrs:/opt/otrs# cat scripts/DBUpdate-to-3.2.mysql.sql | mysql -p -f -u
> root otrs
> Enter password:
> ERROR 1091 (42000) at line 20: Can't DROP 'ticket_answered'; check that
> column/key exists
>

the ticket_answered column does exist in OTRS 3.1 databases (otherwise the
ticket API would not work); so if it's not there when you run the DBUpdate
SQL this is probably because this is the second time you ran it? Also re.
your remark of the Full Text Index.


> Also, the TABLE group_users had two full text indices which I had to
> remove due to the chamge from myisam -> innodb.
>

Full text indexes, really?? We never added those in OTRS code, many
customers run on InnoDB and can't have those - or actually could not have
those until  MySQL 5.6. I think they might be added by your DBA... but
they'll not be of much use unless you also implement the WHERE MATCH
(fields) AGAINST (string) query somewhere in the OTRS code.

--
Mike
-
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

[otrs] DBUpdate-to-3.2 errors during upgrade from 3.1.12 -> 3.2.2

2013-03-18 Thread Ralf Hildebrandt
otrs:/opt/otrs# bin/otrs.CheckDB.pl
Trying to connect to database
DSN: DBI:mysql:database=otrs;host=localhost;
DatabaseUser: otrs

Connected.

otrs:/opt/otrs# cat scripts/DBUpdate-to-3.2.mysql.sql | mysql -p -f -u
root otrs
Enter password: 
ERROR 1091 (42000) at line 20: Can't DROP 'ticket_answered'; check that 
column/key exists
INFO: Foreign key constraint FK_article_flag_article_id_id does not exist, 
skipping.
INFO: Foreign key constraint FK_article_flag_article_id_id does not exist, 
skipping.
INFO: Foreign key constraint FK_article_flag_create_by_id does not exist, 
skipping.
INFO: Foreign key constraint FK_article_flag_create_by_id does not exist, 
skipping.
ERROR 1091 (42000) at line 37: Can't DROP 'article_flag_create_by'; check that 
column/key exists
ERROR 1091 (42000) at line 41: Can't DROP 'ticket_queue_view'; check that 
column/key exists

Should I worry? So far everything seems to be in perfect working order!

Also, the TABLE group_users had two full text indices which I had to
remove due to the chamge from myisam -> innodb.

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de

-
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