RE: Session migrated to another instance
Date: Thu, 20 Jun 2013 17:13:32 +0000
Message-ID: <CE70217733273F49A8A162EE074F64D90D88FC_at_exmbx06.thus.corp>
In this example you end up on the same instance - and the original SID with the ORIGINAL SERIAL# is still alive. What was the status of the old session ? ACTIVE, SNIPED, KILLED etc. ? And what was the state and event ?
This looks a little unexpected - buggy even - but are you using any new(-ish) features that might be related; the first one that springs to mind is database resident connection pooling.
Regards
Jonathan Lewis
From: oracle-l-bounce_at_freelists.org [oracle-l-bounce_at_freelists.org] on behalf of Hemant K Chitale [hemantkchitale_at_gmail.com] Sent: 19 June 2013 15:46
To: ORACLE-L
Subject: Fwd: Session migrated to another instance
Testing today
Curious. My SID has changed from 1234 to 6789 sometime between 09:56
and 11:28. I've verified that no instance in the cluster has been
restarted. I had issued NO commands from this SQLPlus session.
The TNS connect-string I use is a simple connect string specifying the SCAN
address.
So, my session has been migrated maybe from instance 1 to instance 2 or 3 and then back to instance 1 in that 1.5 hours (while it was idle) ? Was it migrated because the service was migrated ? I think I can discount server-side TAF because no instance was restarted.-- http://www.freelists.org/webpage/oracle-l Received on Thu Jun 20 2013 - 19:13:32 CEST