Page 1 sur 1

Migration from 1.12.1 to 1.20.1

Publié : ven. juil. 26, 2019 1:25 pm
par vince
Hello Guys,

I did manage to upgrade our squashtm base from 1.12.1 to 1.20.1.
I can log and have access to several data but accessing to testcases won't work :

Here is the error

Code : Tout sélectionner

SquashTM - 10123 ERROR [http-nio-8080-exec-2] [] --- org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/squash].[dispatcherServlet]: Servlet.service() for servlet [dispatcherServlet] in context with path [/squash] threw exception [Request processing failed; nested exception is org.springframework.dao.InvalidDataAccessResourceUsageException: could not extract ResultSet; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet] with root cause
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'testcase0_.UUID' in 'field list'
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_212] 
I
Can i track the DB resquest concerned ? Any help would be really appreciate.

Regards

Re: Migration from 1.12.1 to 1.20.1

Publié : ven. juil. 26, 2019 2:34 pm
par agoethals
Hello,

did you execute all upgrade scripts in the right order (1.13, 1.14, 1.15, 1.16, 1.17, 1.18, 1.19 and 1.20) ?

Re: Migration from 1.12.1 to 1.20.1

Publié : lun. juil. 29, 2019 8:42 am
par vince
Hello agoethals,

Of course I did. Here is the list :
  • mysql-upgrade-to-1.12.3.sql
    mysql-upgrade-to-1.13.0.sql
    mysql-upgrade-to-1.13.1.sql
    mysql-upgrade-to-1.13.3.sql
    mysql-upgrade-to-1.13.5.sql
    mysql-upgrade-to-1.14.0.sql
    mysql-upgrade-to-1.14.1.sql
    mysql-upgrade-to-1.15.0.sql
    mysql-upgrade-to-1.16.0.sql
    mysql-upgrade-to-1.17.0.sql
    mysql-upgrade-to-1.18.0.sql
    mysql-upgrade-to-1.19.0.sql
    mysql-upgrade-to-1.20.0.sql

Migration from 1 12 1 to 1 20 1

Publié : sam. déc. 14, 2019 2:24 am
par Kathrynvek
Hi All,

I need to migrate from WesSphere Application Server V6.1 to V7.0. ITIM is currently running on WAS. Can anyone pls guide me how to perform a smooth migration.

Thanks in Advance

Migration from 1 12 1 to 1 20 1

Publié : mar. janv. 28, 2020 12:24 pm
par KathrynGah
Hi Ed:
timestamp is a column on the table you intend to migrate. This field has to be a numeric value.
What is happening is the migration process check this value and if it is not numeric, the record is not migrated at all.
For the data you reported, something went wrong with the timestamp and it is not saved in a numeric format.

Could you tell us from what plugin are you trying to migrate from? Maybe that would give us a clue what's is going on.
Thank you

Re: Migration from 1.12.1 to 1.20.1

Publié : ven. nov. 27, 2020 5:17 pm
par Sana
Hello Vince,

Did you found the problem and how did you solve it?

Regards
vince a écrit : ven. juil. 26, 2019 1:25 pm Hello Guys,

I did manage to upgrade our squashtm base from 1.12.1 to 1.20.1.
I can log and have access to several data but accessing to testcases won't work :

Here is the error

Code : Tout sélectionner

SquashTM - 10123 ERROR [http-nio-8080-exec-2] [] --- org.apache.catalina.core.ContainerBase.[Tomcat].[localhost].[/squash].[dispatcherServlet]: Servlet.service() for servlet [dispatcherServlet] in context with path [/squash] threw exception [Request processing failed; nested exception is org.springframework.dao.InvalidDataAccessResourceUsageException: could not extract ResultSet; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet] with root cause
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'testcase0_.UUID' in 'field list'
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_212] 
I
Can i track the DB resquest concerned ? Any help would be really appreciate.

Regards