Re: ORA-01555
Date: Wed, 13 Oct 2010 21:18:37 +0000 (UTC)
Message-ID: <pan.2010.10.13.21.18.37_at_email.here.invalid>
On Wed, 13 Oct 2010 21:14:20 +0000, Mladen Gogala wrote:
> 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.
BTW, I am re-running now with the entire tablespace being turned to read only. If I get ORA-01555, I will start drinking.
-- http://mgogala.byethost5.comReceived on Wed Oct 13 2010 - 16:18:37 CDT