NextGen (Mirth) Connect 3.11.0 Released!

NextGen (Mirth) Connect 3.11.0 is now available as an appliance update and on our GitHub page. This release contains improvements to licensing and the NCPDP data type. It also includes various security fixes, general bug fixes, and improvements to commercial extensions. See the release notes for the complete list of fixes and improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

upgrading from M1.5 to M1.6

  • 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 to add 3 columns.

    Am I wrong?

    Now seems to be ok.
    ... checking further ...
    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


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

      Hi chrisl,

      On winXPpro
      I've stopped Mirth service
      and launched mirth-
      it worked successfully but table 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(
      com.webreach.mirth.client.ui.Frame.retrieveChannel s(
      com.webreach.mirth.client.ui.Frame$12.doInBackgrou nd(
      com.webreach.mirth.client.ui.Frame$12.doInBackgrou nd(
      org.jdesktop.swingworker.SwingWorker$ n Source)
      java.util.concurrent.FutureTask$Sync.innerRun(Unkn own Source) Source) Source)
      java.util.concurrent.ThreadPoolExecutor$ Task(Unknown Source)
      java.util.concurrent.ThreadPoolExecutor$ (Unknown Source) 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 Mastrogiacomo


      • #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