Share
ReportS0334.05.jpg"font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;">
We then restart utilities with the intention of continuing with remaining DBs while we research the above error to find a resolution.
However, after restarting we notice that the above referenced company does not have the customary 'X' indicating that the DB failed to upgrade and we are able to select it again.
We opt to include this DB in our next run of the upgrade and receive the following errors:
We have to click about 20-30 times on the above error until we are presented with the below error:
We click OK on the above and the upgrade proceeds and finally completes the DB upgrade 'sucesfully' and proceeds to the next DB.
The next DB continues without error and we are currently monitoring the next DB (which is so far proceeding without issue).
I queried the AAG20001 table on their former production environment for the DB that produced the error and there is no data in the table (nor does their appear to be any data in any AAG setup tables). Client has AA but doesn't appear to be utilizing it in this particular DB.
My question is, should we be concerned with the initial error(s) that were encountered? It's strange that we were able to proceed past by simply restarting utilities and clicking past the subsequent errors. We have about 3 and a half days to go for the full set of DBs to complete and are concerned that this apparently minor/irrelevent error could in-fact be an issue.
Please let me know your thoughts and/or if you would like additional information.
Thanks!
Tom
*This post is locked for comments
All responses (
Answers (
291,269
