Account/InsCheck/Deposit Problem

[drtech]

I am running 7.0.7.

We just found on one particular pt, a bunch of supplimental ins payments on a pt have dissapeared. They no longer show as on the check if I search the system for a person on ins check (user query) and the deposit sum is now wrong. The accounting module has the right amt that we actually deposited at the bank (verfied with the bank), but the deposit total is now off by the missing portion of a check. This is for multiple occations. I ran database maint and I got a report for deposit sums recalculated on dates that match the missing checks and they amt changed matches the missing amt. Any I idea what is wrong here? The pt's balance is off by quite a bit as there are five $125 payments missing dating back to fall of last year.

HELP!

[jordansparks]

Yes, I'm afraid I do know what's going on. I'll get back to you shortly.

[jordansparks]

http://www.opendental.com/manual/bugcp.html

I'm still finishing that page, but there's enough there for you to start to read.

[jclaydds]

Just getting a little nervous. I did some updates last week. I can' t remember the versions but somewhere in the vicinity of 7.0.4 or 7.0.5. I received an email from Open Dental Support telling me about the bug and the need to update again. I ran the update and ran database maintenance. I did not see any signicant issues when running database maintenance.

Based on the comments in the forum today, I have now updated to 7.0.9 and ran database maintenance again. Still no errors showing in the log. I also went to the page you referenced in the previous post that discusses the bug and ran the 2 querys to look for duplicates. No results from either query. i checked the repairlog.txt file and no issues that I can see. Should I be looking elsewhere to try to determine if I have problems with my data? We haven't noticed any problems with data today but not sure we would have caught it given the thousands of accounts that we have in our database. The reason that I am a little nervous is my backups get overwritten after a few days and I am trying to figure out if i need to try to preserve one in the event I find a problem down the road.

[drtech]

keep a monthly backup forever in case you do need to reference something....it isn't really that big and will preserve all data just in case...

This is good for legal reasons too...just in case...

[jordansparks]

Keep in mind that it is a very specific and limited sort of issue. We will be quickly developing a tool to pin down this bug. The tool will make use of a backup and will do a database comparison. Very close to 100% of our customers will have a database backup already sitting in their mysql folder. So as long as you have a backup from before 3/17, I really wouldn't worry about it. You will be able to rest easy soon.

Naturally, it's all we are working on now.

[DavidWolf]

I assume this only affects offices who have updated to version 7.x.x.x
I am still running 6.9.19.0 any issues with going to 6.9.27???

THANKS.

[jordansparks]

It does affect 6.9, but if you jump from 6.9.19 to 6.9.27, you will be jumping right over the problem and it will not affect you at all.

[drtech]

when I try to run the "temp db integrity check" tool I get an unhanded exception v7.0.11

SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-datacheck.claimproc WHERE DateEntry > '2010-03-16" at line 1

************** Exception Text **************
MySql.Data.MySqlClient.MySqlException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-datacheck.claimproc WHERE DateEntry > '2010-03-16'' at line 1

[wjstarck]

David-

What do you have set as the default location your backups are going to in Manage > Backup?

[drtech]

i don't ever use that...I have mysql dumps automatically on my linux server every hour...and I just restored a backup from 3-16-10 using SQLyog....

I checked the paths there and they are to inaccurate paths from when I first started using OD on a windows mysql server. Does this have to be set to run the check?

[wjstarck]

I think so...

[jclaydds]

I have ran the Temporary Database Integrity Check based on a backup prior to 3-17-10. It found 15 Missing Claim Payments. I printed the results, ran the required backup and then ran the fix. I printed those results as well. I then ran Database Maintenance after the fix and I am pretty sure the Database Maintenance Tool reversed the fixes. Could this be possible?

[jordansparks]

when I try to run the "temp db integrity check" tool I get an unhanded exception v7.0.11

David, I think you have a dash in your database name. That's not allowed.

[jordansparks]

I have ran the Temporary Database Integrity Check based on a backup prior to 3-17-10. It found 15 Missing Claim Payments. I printed the results, ran the required backup and then ran the fix. I printed those results as well. I then ran Database Maintenance after the fix and I am pretty sure the Database Maintenance Tool reversed the fixes. Could this be possible?

I am doubtful, but after last week, I have a very hard time being dogmatic about it. What version are you using? If anyone is at all unsure about the results, simply give us a copy of both databases and we will quality check them on our end.

[drtech]

yes, the dash in the database was the problem...

Here are my results
**************************************
Duplicate claim payments: None found. Database OK.

Duplicate supplemental payments: None found. Database OK.

Missing claim payments found: 21
Missing claim checks found: 6

[jordansparks]

OK, perform the fix.

[drtech]

looks like it worked fine, except when I checked one of the deposits that was off...it was still off. (it was from 3-16-2010...so not sure if it wasn't on the database I restored from (3-16-2010)...but I thought it was from the night of 3-16-2010...

should I run my backup of 3-17-2010 and see if it includes the missing check?? I think that was after I ran the update, but not 100% sure when I updated...

[jordansparks]

It would be easier to fix the one check manually.

[jordansparks]

jclaydds wrote:
I have ran the Temporary Database Integrity Check based on a backup prior to 3-17-10. It found 15 Missing Claim Payments. I printed the results, ran the required backup and then ran the fix. I printed those results as well. I then ran Database Maintenance after the fix and I am pretty sure the Database Maintenance Tool reversed the fixes. Could this be possible?

Your database is fine. The 15 "missing" entries were not missing at all. They were false positives. Your staff had intentionally deleted a few claims for one reason or another, and those were the claimprocs attached to those claims. So after running the db maint tool, which correctly redeleted them, you are good to go.

This is an example of why we/I should be the only one using the fix features of this tool. It's just too complicated to try to explain to people what a false positive is, when to correct it, when not to correct it, what kind of research to do before pressing the fix buttons, etc. Let us do it please.

[jclaydds]

Jordan,

Thanks for checking out the issue and the I appreciate the peace of mind knowing that the database is fine.

Jeff