Are you using EXECUTE or doing a straight CREATE TEMP TABLE ...?
Maybe a sample with sensitive info changed?
The insert you mention happens in the same procedure or is there a nested
procedure?
It is a straight CREATE TEMP TABLE. It does not happen on the same procedure every time. It happens on different
proceduressometimes they are nested. These store procedures have been working for many years the same way. Only
recentlyhas this error been intermittently occurring on temp tables. Sometimes it occurs on the create, sometimes it
occurson an insert, update or delete on a temp table
Is there a database pooler in the mix?
Are there any other errors in the logs at the same time that might pertain?
There is no database pooler and there are never any other errors in the log at the time of this error.
