Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Archival Freeze - Painful lessons learned

Re: Archival Freeze - Painful lessons learned

From: <Brian_P_MacLean_at_eFunds.Com>
Date: Fri, 12 Apr 2002 14:38:28 -0800
Message-ID: <F001.00443C0C.20020412143828@fatcity.com>

After reading the other postings I better add this one too;^) (If ya didn't learn something new today, it's because ya didn't do anything today).

ORA-00257, "archiver error. Connect internal only, until freed."

Brian P. MacLean
Oracle DBA, OCP8i

                                                                                                                   
                    Brian P                                                                                        
                    MacLean              To:     ORACLE-L_at_fatcity.com                                              
                                         cc:     Rajesh.Rao_at_jpmchase.com                                           
                    04/12/02 02:19       Subject:     Re: Archival Freeze - Painful lessons learned(Document link: 
                    PM                   Brian P MacLean)                                                          
                                                                                                                   
                                                                                                                   



As Daffy Duck says -> http://www.dailywav.com/0700/dcorrect.wav

The archiver freaks first, and will keep trying to write/recover/looking for space. But the database will not hang until all the redo logs are full and none remain that have been archived (ie: all redo logs need archiving).

The error in the alert.log is some combination of:

ORA-00255, "error archiving log %s of thread %s, sequence # %s"
ORA-00270, "error creating archive log %s"
ORA-19504, "failed to create file \"%s\""
ORA-27040, "skgfrcre: create error, unable to create file"
ARCH: Archival stopped, error occurred. Will continue retrying SVR4 Error: 5: I/O error

Why do I have a list of the above errors you ask? Because I've been there
(painful lessons learned), and these are just some of the errors I look for
in my db status script.

Brian P. MacLean
Oracle DBA, OCP8i

                                                                                                                    
                    Rajesh.Rao_at_jpm                                                                                  
                    chase.com            To:     Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>        
                    Sent by:             cc:                                                                        
                    root_at_fatcity.c       Subject:     Archival Freeze                                               
                    om                                                                                              
                                                                                                                    
                                                                                                                    
                    04/12/02 02:13                                                                                  
                    PM                                                                                              
                    Please respond                                                                                  
                    to ORACLE-L                                                                                     
                                                                                                                    
                                                                                                                    





Hi Fellow DBAs,

I and a fellow DBA are currently debating about how insufficient space in the archive destination freezes up the DB. He claims that as soon as the ARCH process is unable to write to the disk, the db freezes. I am of the opinion that it does not. It will only report an error (Any idea, what the error code is?). It will only freeze when it cycles thru the rest of the redolog groups, and then when it tries to switch log to the one which has not been archived. That's why the error message is "cannot allocate new log".

Whats your say? He's also on this list.

Raj

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: Rajesh.Rao_at_jpmchase.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L

(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: Brian_P_MacLean_at_eFunds.Com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Fri Apr 12 2002 - 17:38:28 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US