Answer
Check the "idle time" setting across your Oracle profiles — setting it to UNLIMITED (rather than a finite idle-timeout value) has resolved this specific intermittent database-proxy-session-switch failure in a confirmed case; a finite idle-time setting closing out sessions unexpectedly in the background has been the underlying cause behind this particular error signature, even when the more commonly-suspected CONNECT-privilege angle checks out fine.