- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hi,
I would like to mention that the row format associated with the sys_config table should not effect the upgrade and should come as a warning. Also, as "sys" is a system managed database, the alter command is failing with the error of access denied to admin user as well.
when you start the upgrade please check "PrePatchCompatibility.log" I would like to mention that there are three types of issues you would notice in this log
- ERROR : Correct these issues before upgrading to avoid compatibility issues.
- WARNING : No fatal errors were found that would prevent an upgrade, but some potential issues were detected.
- NOTICE : No known compatibility errors or issues were found. But you can check the NOTICE Level error logs.
- You can check the row format of sys.sys_config table using below query:
select TABLE_SCHEMA,TABLE_NAME,ROW_FORMAT,CREATE_OPTIONS from information_schema.tables where table_schema = 'sys';
- Please be noted that the user will not have access to sys.sys_config system table. If you try to update you will receive the following error:
ALTER TABLE sys_config ROW_FORMAT=DYNAMIC; ERROR 1044 (42000): Access denied for user 'testuser'@'%' to database 'sys'
RDS being a managed service certain actions are restricted. Users will have only the following permissions: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.MasterAccounts.html
sys.config is system table and it is managed by AWS. And users will not have access to it.
- Also this message is warning and this shouldn’t block your upgrade.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren