| Archieve log problem helpme! [message #52392] |
Thu, 18 July 2002 14:33  |
emme
Messages: 13
Registered: July 2002
|
Junior Member |
|
|
Os info: NT SP4
Oracle info: Oracle 8.0.4
when i try to connect to sql*plus,
I am getting the following error
ERROR:
ORA-00257:archiver error.connect internal only,until freed.
Then the server,
SVRMGR>ALter System archive log all;
ORA-00255:Error archiving log of 2 of thread 1,sequence #5648
ORA-00312:Online log 2 thread 1:'c:oracle_homedatabaselog2.0ra'
ORA-00334:archived log:'c:oracle_homedatabasearchivearc0000005648.0001' blockno 1 (blacksize=512)
ORA-27072:SFGFDISP:I/O error
OSD-04008:Writefile() failure,unable to write to file
O/S-Error:(OS 112)There is not enogh space on the disk
ORA-00272:error writing archive log 'c:oracle_homedatabasearchivearc0000005648.0001'
ORA-19502:Write error on file 'c:oracle_homedatabasearchivearc0000005648.0001'
blockno 1 (blacksize=512)
ORA-27072:SFGFDISP:I/O error
OSD-04008:Writefile() failure,unable to write to file
O/S-Error:(OS 112)There is not enogh space on the disk
|
|
|
|
| Re: Archieve log problem helpme! [message #52393 is a reply to message #52392] |
Thu, 18 July 2002 15:13  |
Radek
Messages: 33
Registered: April 2002
|
Member |
|
|
Hi,
DO NOT PANIC !!! =:>)
Your hard drive is just full and there is no free space. Remove some unused files and you'll be back in the game again. I would suggest to take a look in in c:oracle_homedatabasearchive and delete some old archived redo logs.
Radek
|
|
|
|
|
|
|
|
| Re: Archieve log problem helpme! [message #55503 is a reply to message #55500] |
Tue, 28 January 2003 01:52 |
psmyth
Messages: 81
Registered: October 2002
|
Member |
|
|
The error message for ORA-00257 is as follows:
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.
Follow the guidelines in the 'Action' section of the description - check the archiver trace files for more information as to why you are getting the error, and check that ARCHIVE_LOG_DEST is set correctly.
The most frequent cause of this error is that the filesystem where the archive logs are written to (ARCHIVE_LOG_DEST) has no more freespace. If that is the case, move or delete the older archive logs (make sure you have backups or copies), and compress the rest of them to make some space. The archiver will normally continue to function properly.
If you have run out of space in ARCHIVE_LOG_DEST, never ever do a shutdown abort. You are almost certain to lose information and may require recovery.
You can read up in metalink all about that ;-)
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
