05-27-2015 12:50 AM
My customer recently updated his version 16.0.xxx of the Premium version to 16.2.xxx - latest in the ACT WEB install. This update database routine was also tested with the problem database using 16 SP3 of the non-web version.
ACT Schema failure:
*********** Schema Update failed **************
*********** Exception message follows *********
TBL_SYSTABLEKEY_SYNC_TRI: Processing error occurred in Sync Trigger
TBL_SYSTABLEKEY_SYNC_TRI, Table TBL_SYSTABLEKEY - No LUIDID value
The transaction ended in the trigger. The batch has been aborted.
Rebuild table keys for foreign keys2015-05-27 00:20:18.390
Schema Update failed.
I had already did the database intergrity check, actdiag, rebuilt indexes, databases, tested database etc etc and everything passed.
Any idea how i can correct the problem listed above? can i delete the table or something? After the failure, i can attempt to open the database, and it asks for the user name and password as per normal but says after the databased cannot be accessed etc.
Any help would be greatly appreciated.
05-27-2015 04:29 PM
This would need to go to database services, they have the schema script and should be able to update it for you.
I believe its free as well
05-27-2015 04:43 PM
05-27-2015 04:58 PM
What happens if you open the demp database, does it open up without a error?
05-27-2015 08:00 PM
i can open all databases and they convert to the update version 16.0.xxx --> 16.2 or 16.3 without any issue except for the one.
05-27-2015 09:36 PM
You will need to contact database services in the US, call the support number and tell them you need to contact database services.
They will be able to run SQL scripts to update the database, it used to be free, not sure if they have changed the policy or not.
05-27-2015 09:56 PM
Kurt is right on the money with this one. We have several internal tools for repairing databases in regards to a faulty upgrade, or schema update errors.
Here's is our Knowledgebase article for Database Services: http://kb.swiftpage.com/app/answers/detail/a_id/24758/kw/database%20services
At the bottom of that article is a PDF file that we need you to fill out and send to us. Simply check the 'Evaluation' option when you get to that point. Once we have looked at the database, and have understood the complexity of the issue, we will talk to you in regards to how much it will cost to fix, if any cost is associated. We usually only charge for hard or complex issues with a database.
In that PDF file is a series of instructions on how to get your database ready. If you cannot follow those steps, please contact us at support, or email the repair services email address listed in the PDF.
05-31-2015 11:45 PM
Dear Billy, Thank you for this link and information. The problem is relatively simple. There seems to be a foreign key (only 1) that the upgrade from version 16.0 to 16.2 or 16.3 sql schema doesn't like and fails. The data is clean working, rebuilt etc etc within 16.0 so the simple upgrade to 16.2, in theory, shouldn't have such a problem. I believe it was my customers custom fields ( maybe 20 or so) that he added to the standard database is where the problem started. The customer became frustrated and decided not to use that particular database anymore. I Actually would like to find out what went wrong with it. Thanks once again for your help. Grant Meyer