Micros. Wrong Version Info in micros res version information

[POSINSAM]

Hi guys. Hoping for your help on this one. This box is running Microsoft version 5.0. We are on able to rebuild the database, apparently because it somehow thinks the version is still 4.9. I ran the upgrade patch, I thought successfully, on a 4.9 box before importing the database into the 5.0 build. Now for some reason, the guest checks are not purging at night during auto sequence, and we cannot rebuild the database to try to fix. Would anybody possibly have any ideas? Attached is a .BMP of the version info from the 5.0 server:

 

[POSINSAM]

Here is the link

 

[POSINSAM]

Just to clarify. This server is running Micros 5.0 and we are unable to rebuild database.

 

[DJensen999]

Have you tried a forced upgrade with DM -u (path to database)?

 

[Moregelen]

Open command prompt and just type: DM -u

It will automatically attempt to reapply the upgrade scripts. Sometimes this happens. It restores fine, but doesn't upgrade. Some thing will work, some won't. Make sure to shut down ops and make sure the SQL server gets restarted before running, or locked tables can prevent the upgrade.

 

[POSINSAM]

I don't know why I never thought of that. I will do it as soon as I get back tonight. Thank you!

 

[POSINSAM]

Unfortunately, manually updating did not work. Here is the log:


1/13/2015 2:21:08 AM **Error Updating Database**, Database Update Failed!
1/13/2015 2:21:08 AM Check Micros dm.log for errors.
1/13/2015 2:22:22 AM DM Return Code = 1
1/13/2015 2:24:05 AM Starting database update.
1/13/2015 2:24:05 AM Updating Database
1/13/2015 2:24:27 AM Could not execute statement. Index 'XAK1rpt_template_def' for table 'rpt_template_def' would not be unique SQLCODE=-196, ODBC 3 State="23000" File: "Scripts.sql" on line 60134, column 1
1/13/2015 2:24:27 AM **Error Updating Database**, Database Update Failed!
Any Ideas would be greatly appreciated. I accidentally put this server into production, not knowing this was an issue.

 

[DJensen999]

Unfortunately, my 5.2 upgrade scripts are not lining up with your 5.0 upgrade script, so it's hard to tell the exact cause.

Two things to check from a quick review of the script: have you created any custom reports with an ID of less than 10,000? Also, the script seems to presume that the columns rpt_template_seq and obj_num are identical in the failing table rpt_template_def.

 

[Moregelen]

You may want to rebuild your database - even if you have to rebuild it from the RES 4 machine. You could also get into the rpt_template_def and blow it out temporarily, though that is a bit extreme. It honestly sounds like you've got a report template somewhere it shouldn't be. 1 - 1,000 is strictly reserved, obj_num and seq_num, for Micros reports.

 

[POSINSAM]

o you are saying to just go into DBISQL and remove the rpt_template_def table?

 

[POSINSAM]

I havnt made any custom reports under 10,000 Doesn't mean someone else didn't.... blowing out the rpt_template_def just errored on missing that table..... shoot..

 

[pmegan]

You can't just delete the table, that will cause a whole other mess.

It sounds like the upgrade is trying to insert a report with a number that already exists. Since this is a production server and you ran some modifications with the dba user it's going to get a little ugly. I'm surprised you were allowed to blow that table out, you should have received some referencing errors.

Did you delete that table or just clear it out?
Do you have a test server with the same version that you can restore the database to?

 

[pmegan]

Oh, and did you export the data from rpt_template_def before blowing it out?

 

[POSINSAM]

I tried removing it, had to end up going back to an image I took of that box before doing so. What actually ended up working was deleting the index file within that table and re-creating that index file with a with a false for it needing to be identical. I'm not sure what problems that will cause later, but, success!

 

[POSINSAM]

Thank you so much for your help guys! I could not have done it without you!