1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
According to the following Knowledge Center post, that error might happen because the access is granted just for the current objects present in a schema when the access was granted and a user tries to access newly created objects, since, by default, access isn’t automatically granted on future objects that are created under that schema.
Take a look at the attached link as it describes step by step the commands to execute to resolve the error.
I hope this helps you.
Relevant content
- asked a year ago
- asked 7 months ago
- asked 2 years ago
- asked a month ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
I have changed some permissions and now I am getting this error "Redshift endpoint doesn't exist in this region."