1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello,
In this context, to check whether the error is indeed due to MV being refreshed at the time of the query, you can co-relate the timings that you are facing this error with the information from the system table SVL_MV_REFRESH_STATUS. The SVL_MV_REFRESH_STATUS view contains a row for the refresh activity of materialized views.
[+] https://docs.aws.amazon.com/redshift/latest/dg/r_SVL_MV_REFRESH_STATUS.html
Sample query to view the refresh status of materialized views -
select * from svl_mv_refresh_status;
You can compare the starttime, endtime columns with the time of the occurrence of the error.
That being said, if you would like resource based troubleshooting, please raise a support case with AWS for further information. If a support case has already been created please be assured that we will get back to you and assist you in the best way possible.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata un anno fa