- Newest
- Most votes
- Most comments
There is an internal issue going on in the backend which is giving rise to the error for many of the users. Confirmed this with the internal team as well. They are actively working towards it's resolution. Currently, as a immediate workaround please try setting the UseResultsetStreaming=0 as suggested by @sstens. Any inconvenience caused due to this is deeply regretted.
The internal issue has been resolved October 4 6:18 PM PDT
@Fabrizio@aws which solution that solve the issue and not create slows the query speed dow. could you explain please?
Exact same issue as you, please post if you find a solution. As a temp fix, you can add UseResultsetStreaming=0 to the connection string (or configure it in Advanced Settings in the DSN). However, this slows the query speed down a lot so a permanent solution needs to be found. Something definitely changed in the last 24 hours as I had never seen this error before yesterday.
Thanks sstens! Setting UseResultsetStreaming=0 is working as a workaround for now, but it is indeed slower.
Same error here, searching for an answer everywhere, but clueless about solution. ResultsetStreaming=0 worked for me, but waiting to understand what happened. It started since Oct3rd, so I think it can be general.
If you find any solution, please post here!
Relevant content
- asked 3 months ago
- asked 3 years ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated 5 months ago
in every forum that i looking for this issue the solution is the same. Like SSTENS However, this slows the query speed down a lot so a permanent solution needs to be found. Something definitely changed in the last 24 hours as I had never seen this error before yesterday. Like Alejandro_aviles muy issue started since Oct3rd. Any solution that solve this issue without lost query speed??