Small bug in schema.Oracle upgrade

I found a small problem in the upgrade procedure for Oracle if you
upgrade from 3.2.x to 3.4.1. The upgrade schema file in directory 3.3.0
renames the table TicketCustomFieldValues to ObjectCustomFieldValues but
forget the Oracle sequence. Problem is you can’t rename a sequence so
you have to find out the current sequence value and recreate it starting
with that value. Thats beyond the possibilities of the upgrade script I
think so I did it by hand.

Hope someone benefits from this.


Joop van de Wege