ORA-01555
From: Mladen Gogala <no_at_email.here.invalid>
Date: Wed, 13 Oct 2010 21:14:20 +0000 (UTC)
Message-ID: <pan.2010.10.13.21.14.20_at_email.here.invalid>
I received ORA-01555. That in itself wouldn't be much to brag about, but the circumstances are curious. Being aware that this is a large table I imposed a shared lock on the table to prevent any concurrent updates. Despite the lock and despite manually executing a global checkpoint (yes, I need the keyword "global", there are 2 instances accessing the DB). The lock was granted, there were no commits in my transaction nor was the table updated. I checked the audit records, nothing there. How is it possible? Usually, I was receiving ORA-01555 when long running query was accessing table that has been concurrently modified. This time, there were no concurrent updates.
Date: Wed, 13 Oct 2010 21:14:20 +0000 (UTC)
Message-ID: <pan.2010.10.13.21.14.20_at_email.here.invalid>
I received ORA-01555. That in itself wouldn't be much to brag about, but the circumstances are curious. Being aware that this is a large table I imposed a shared lock on the table to prevent any concurrent updates. Despite the lock and despite manually executing a global checkpoint (yes, I need the keyword "global", there are 2 instances accessing the DB). The lock was granted, there were no commits in my transaction nor was the table updated. I checked the audit records, nothing there. How is it possible? Usually, I was receiving ORA-01555 when long running query was accessing table that has been concurrently modified. This time, there were no concurrent updates.
-- http://mgogala.byethost5.comReceived on Wed Oct 13 2010 - 16:14:20 CDT