Re: OMS Down, the reason?
- From: Martijn Bos <maboc@xxxxxxxx>
- To: mek s <sidi.bouzid.meknessy@xxxxxxxxx>
- Date: Thu, 12 Jan 2012 13:59:19 +0100
Can it be that your archiving destination is full on the database end of the
OMS when it happens.
It can be the cause of what Stephane Faroult is telling.
Oracle tells me:
01:48 PM oracle@xxxxxxxxx:~/scripts/oracle(tijnprim) $ oerr ora 257
00257, 00000, "archiver error. Connect internal only, until freed."
// *Cause: The archiver process received an error while trying to archive
// a redo log. If the problem is not resolved soon, the database
// will stop executing transactions. The most likely cause of this
// message is the destination device is out of space to store the
// redo log file.
// *Action: Check archiver trace file for a detailed description
// of the problem. Also verify that the
// device specified in the initialization parameter
// ARCHIVE_LOG_DEST is set up properly for archiving.
Best Regards,
Martijn
--
//www.freelists.org/webpage/oracle-l
Other related posts:
