Hello,
We have Mirth 1.2.0 running on Redhat Enterprise Linux 3. We had a channel setup to receive ADT from an EMR system. We had not been actively monitoring it since setting it up though it has remained up and active. Initially, we also were not purging records older than 30 days, so, what has happened is that the table(s) in the mirth database grew and hit the 2 gig file size limit on the older linux (RHEL3 still being the 2.4 kernel). now we get a flood of exception about table being too big. we tried disabling it, but, it seems to not be responding to anything. we can, of course, just kill mirth.
what we would like to do is purge the internal mirth tables and reset everything. we aren't exactly sure how to do this. if we could get it function enough as it is we could export the channel(s) and then just reset, but we can't even get that to work. so, from an "outside" approach, what can we do to truncate the tables while not losing our channel stuff????
thanks!
Mark
We have Mirth 1.2.0 running on Redhat Enterprise Linux 3. We had a channel setup to receive ADT from an EMR system. We had not been actively monitoring it since setting it up though it has remained up and active. Initially, we also were not purging records older than 30 days, so, what has happened is that the table(s) in the mirth database grew and hit the 2 gig file size limit on the older linux (RHEL3 still being the 2.4 kernel). now we get a flood of exception about table being too big. we tried disabling it, but, it seems to not be responding to anything. we can, of course, just kill mirth.
what we would like to do is purge the internal mirth tables and reset everything. we aren't exactly sure how to do this. if we could get it function enough as it is we could export the channel(s) and then just reset, but we can't even get that to work. so, from an "outside" approach, what can we do to truncate the tables while not losing our channel stuff????
thanks!
Mark
Comment