Unable to perform 5.4 SP1 update due to failed database schema checks
Hello,
I'm trying to perform the 5.4 SP1 update. When I run it I get this:
first db: one
second db: two
There are no differences detected.
[Fri Mar 22 17:48:41 EDT 2013] [notice] Verifying that ORG1 Database matches expected schema...
[Fri Mar 22 17:48:49 EDT 2013] [notice] one is ORG1, two is /kbox/bin/kbserver/templates/factory_org.sql
first db: one
second db: two
HD_ARCHIVE_TICKET.CUSTOM_FIELD_VALUE15 column is only in first db
HD_ARCHIVE_TICKET.CUSTOM_FIELD_VALUE16 column is only in first db
HD_ARCHIVE_TICKET.CUSTOM_FIELD_VALUE17 column is only in first db
HD_ARCHIVE_TICKET.CUSTOM_FIELD_VALUE18 column is only in first db
HD_ARCHIVE_TICKET.CUSTOM_FIELD_VALUE19 column is only in first db
[Fri Mar 22 17:48:49 EDT 2013] [notice] K1000 Server Update 5.4.76847 Canceled, failed database schema checks, see previous lines for specific errors, contact support@kace.com to upgrade properly.About K1000 | © 2012 Dell Inc. Session Timeout:11:57:28 - 03/22/2013 18:09:28 Submit Support Ticket
I have a ticket open with support but as usual they have changed the status to "Engineering Consult" where it will sit for months while someone calls once a week asking if they can close the ticket...
Anyone seen this? I may try a "Reboot with Extended DB Check" tonight. My provisioning and Dell updates are also broken. I'm hoping this SP will fix it, as Dell has had tickets open for both of those for months with no solution.
Answers (3)
The patch did the trick. It was called "kbox_patch_5_4_70402_DBcompare_20130228.kbin"
Have you tried calling support directly asking about the status? Ask for an escalation of the ticket. You may also want to get your sales person involved so they can escalate the ticket as well.
Comments:
-
Yes I have. I've asked to have all of my tickets "escalated". They still sit in "Engineering Consult" and the support reps keep telling me they are busy and it takes forever to get them to respond.
I've yet to have Dell support fix a single issue for me. I usually find it myself from a forum post. - edwimb 11 years ago
I had the same issue but unfortunately I have to wait to for support to resolve it. There wasn't anything I could do on my end to get this fixed. They had to SSH in and resolve the issue.
