1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Test in your development/staging environment running on MySQL major version 8 if you are able to create the procedure with same Create statement that is getting flagged by Precheck during upgrade.
If you are able to create the procedure during testing you could consider dropping the procedure before upgrade and recreating them post upgrade or consider reaching out to AWS Support via a support case.
Hope this helps!!
answered a year ago
Relevant content
- asked 2 months ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 months ago
That is of course a solution, but I see this as a last resort. We presently have 20+ stored procedures getting rejected for reasons we can't comprehend. So we would have to create scripts for dropping the procedures before the upgrade and re-reating after the upgrading. Not really a complication you want to add to an upgrade of a 265/24/7 system. As this wasn't a problem with previous versions of the upgrade pre-checks, I have a suspicion that at least some of the rejections simply aren't correct. So I guess we have to create a case with AWS. And at least understanding why the upgrade pre-check rejects such a simple stored procedure (with all reserved names quoted) would definitely be good.