Brandon, http://pastebin.ca/710464 is the ASH info from the last hang. The time frame is 15:00-15:59, the first shared row latches appear at 15:27 and the database was noticably hung shortly afterward for about 5 minutes. This time coincides with a bulk load (insert append via external tables), as all hanging did while the archive log dest disk was in the "paused" relayout state. I see a "Log archive I/O" at 15:22, but those occur throughout the day as well. I don't see the event that you specify at all. It looks like the problem is indeed behind us, but I definitely want to pin down precisely why the database behaved as it did, if anyone has any thoughts. Don. On 9/21/07, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote: > If the database was hanging on archived logs, wouldn't you have seen a > lot of 'log file switch (archiving needed)' wait events? I haven't > looked back through the whole thread, but I don't remember any mention > of log file wait events - only change block tracking wait events. Is > your change block tracking file also on disk that was being reconfigured > and paused? > > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Don Seiler > > > We *think* we have found the issue, and it isn't quite Oracle-related > (of course). > > The SA had been doing a Veritas online relayout on the disk partition > that is our archivelog destination. > > Privileged/Confidential Information may be contained in this message or > attachments hereto. Please advise immediately if you or your employer do not > consent to Internet email for messages of this kind. Opinions, conclusions > and other information in this message that do not relate to the official > business of this company shall be understood as neither given nor endorsed by > it. > > -- Don Seiler oracle: http://ora.seiler.us ultimate: http://www.mufc.us -- //www.freelists.org/webpage/oracle-l