DMON problem - SUMMARY

Morning all,

thanks to all who replied both privately and on-list. This is a summary of what happened :

... orakill took out the offending DMON process which ALTER SYSTEM KILL
SESSION couldn't do as it was not a user process.

... DMON restarted itself quite happily.

... The stuck and unarchived log (in group 14) 44419 happily archived
itself and was quickly fetched and applied by the standby.

... The standby rapidly applied all other pending logs and is now up to
date.

... The primary did not need to be closed and the users are happy.
Performance is back to normal.

I'm just about to dive into the trace file (over 1 GB in size !) by sending it over to a Unix server for ease of viewing. That assumes that it is actually readable of course.

Thanks again.

Cheers,
Norman.

Norman Dunbar.
Contract Oracle DBA.
Rivers House, Leeds.

Internal : 7 28 2051
External : 0113 231 2051

Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.

We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.

If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk

--
http://www.freelists.org/webpage/oracle-l