Upgrade of Cloverleaf from 5.7 to 6.1.2 – ODBC issues??

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Upgrade of Cloverleaf from 5.7 to 6.1.2 – ODBC issues??

  • Creator
    Topic
  • #55372
    Rick Haddorff
    Participant

      We upgraded our Cloverleaf from 5.7 to 6.1.2.

      We began seeing an issue where files of messages were being co-mingled between state department of healths for reportable disease results.

      We have a tcl script that loads the files into the PHINMS database through ODBC commands.  We suspect that is where the problem is occurring.

      Has anyone experienced a issue in differences of ODBC between versions of Cloverleaf?

      Any thoughts or suggestions welcomed!!

      Thanks

    Viewing 5 reply threads
    • Author
      Replies
      • #85101
        Peter Heggie
        Participant

          We use a lot of ODBC but we started with 5.8.4, so I’m not sure we ever had a migration issue.

          Maybe you can provide more technical detail on the process used. You are going from a file to a database? And you are calling the ODBC from a TCL script – is this script run inside a thread or from a command line?

          And you have multiple tables in the database, or one table with a column that identifies the different DOHs?

          Peter Heggie
          PeterHeggie@crouse.org

        • #85102
          Rick Haddorff
          Participant

            A thought from one of our developers:

            I see that SQLFreeHandle is being called but does the ODBC connection need to be closed?

            maybe.  that’s what I need guidance on

            it may be behaving differently now

          • #85103
            Rick Haddorff
            Participant

              I am waiting on our developers to get more info – but this is wha I know so far – to answer your questions:

              Maybe you can provide more technical detail on the process used. You are going from a file to a database? Yes

              And you are calling the ODBC from a TCL script – is this script run inside a thread or from a command line? Thread

              And you have multiple tables in the database, or one table with a column that identifies the different DOHs?  (Waiting to hear on this one – I think it is one database table)

            • #85104
              Aaron Markley
              Participant

                I’m on Rick’s team and assisting.  

                We’re calling odbctcl inside of a TCL script which is inside a thread as a UPOC.  We are using this script to insert multiple fields into a single MSSQL table.  This script runs once per file, with one state’s messages per file.  Once the ODBC insert happens, the application which uses the database encrypts the payload and sends it via HTTPS to external receivers.

                As of the date of our upgrade, it appears that one of the database fields (which contains the main message payload) sometimes contains messages from multiple state files.  A database record could be sent to Washington (for example), but in the payload field, our receiving contact reported seeing messages for Washington and Illinois.  We have verified that in SMAT, the messages look correct and are not mixed by the time they hit the ODBC script.

              • #85105
                Charlie Bursell
                Participant

                  Are you using the ODBC API supplied with Cloverleaf or another?  The term ODBCTcl concerns me.

                  What OS?  The ODBC API, as far as I know, has not changed and should work in one place as well as another.

                  I don’t think I have ever had to use the SQLFreeHandle  command.  But if used certain prereqs are required.

                  Perhaps a call to Support or supply the code you are using.

                • #85106
                  Todd Horst
                  Participant

                    Maybe using globals and your data is getting overwritten by different threads

                Viewing 5 reply threads
                • The forum ‘Cloverleaf’ is closed to new topics and replies.