Announcement

Collapse
No announcement yet.

upgrading from M1.5 to M1.6

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • upgrading from M1.5 to M1.6

    Hi ,

    I've installed Mirth 1.6 over an existing Mirth 1.5
    I was using an Oracle Db.

    Installation was ok but the oracle db needs an alter table on mirth.channel to add 3 columns.

    Am I wrong?

    Now seems to be ok.
    ... checking further ...
    Bye.
    Stefano Mastrogiacomo

  • #2
    Re:upgrading from M1.5 to M1.6

    Did you run the installer? Mirth 1.6 will automatically migrate 1.5 tables (and supports migration for future versions automatically - even without running the installer).
    Chris Lang

    Comment


    • #3
      Re:upgrading from M1.5 to M1.6

      Hi chrisl,

      On winXPpro
      I've stopped Mirth service
      and launched mirth-1.6.0.2714-setup.exe
      it worked successfully but table mirth.channel was untouched.

      The db is on the same machine and it is referred as localhost in the MirthServerManager

      Then Administration started ok but channel panel referred an error.

      com.webreach.mirth.client.core.ClientException: method failed: HTTP/1.1 500 com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
      --- The error occurred in oracle/oracle-channel.xml.
      --- The error occurred while applying a result map.
      --- Check the Channel.get-channel-result.
      --- Check the result mapping for the 'postprocessingScript' property.
      --- Cause: java.sql.SQLException: Nome colonna non valido
      Caused by: java.sql.SQLException: Nome colonna non valido
      com.webreach.mirth.client.core.ServerConnection.ex ecutePostMethod(ServerConnection.java:99)
      com.webreach.mirth.client.core.Client.getChannel(C lient.java:164)
      com.webreach.mirth.client.ui.Frame.retrieveChannel s(Frame.java:1705)
      com.webreach.mirth.client.ui.Frame$12.doInBackgrou nd(Frame.java:1657)
      com.webreach.mirth.client.ui.Frame$12.doInBackgrou nd(Frame.java:1661)
      org.jdesktop.swingworker.SwingWorker$1.call(Unknow n Source)
      java.util.concurrent.FutureTask$Sync.innerRun(Unkn own Source)
      java.util.concurrent.FutureTask.run(Unknown Source)
      org.jdesktop.swingworker.SwingWorker.run(Unknown Source)
      java.util.concurrent.ThreadPoolExecutor$Worker.run Task(Unknown Source)
      java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
      java.lang.Thread.run(Unknown Source)

      So I checked for an update script for the db and I found some difference in the create db script.

      I've used three alter table as referred in #3480 .

      Thanks again
      Stefano
      Stefano Mastrogiacomo

      Comment


      • #4
        Re:upgrading from M1.5 to M1.6

        Interesting - can you report this as a bug? The DB should have migrated automatically when first started.
        Chris Lang

        Comment

        Working...
        X