Welcome Guest ( Log In | Register )


 
 
 
 
 
 

 
 
Oracle 

Performance Tuning Reference poster
 
Oracle training in Linux 

commands
 
Oracle training Weblogic Book
 
Easy Oracle Jumpstart
 
Oracle training & performance tuning books
 
Burleson Consulting Remote DB Administration
 
 
 
Reply to this topicStart new topic
> ora-00257-00000-archiver-error-connect-internal-only-until-freed
Joe Valiyaveetti...
post May 18 2017, 01:24 AM
Post #1


Newbie
*

Group: Members
Posts: 7
Joined: 25-April 17
Member No.: 51,933



When I was connecting to my database through SQL Developer tool I was getting error message as below:

ORA-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.


So I archive the log files by,

alter system archive log all;

Still the same issue was there. So I checked the space using below commands:

SQL> select name, round(space_limit/1048576),round(space_used/1048576), round(( round(space_used/1048576)*100)/(round(space_limit/1048576))) pct_used 2 from v$RECOVERY_FILE_DEST;

NAME
---------------------------------------------------------------------------

ROUND(SPACE_LIMIT/1048576) ROUND(SPACE_USED/1048576) PCT_USED
-------------------------- ------------------------- ----------
C:\app\oracle\fast_recovery_area
104448 63931 61



Lots of space are still available and I checked the below command also.....

SQL> show parameter log_archive;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_config string DG_CONFIG=(jordan_local,india_
local)
log_archive_dest string
log_archive_dest_1 string location=c:\app\oracle\f
ast_recovery_area\local\ARCHIV
ELOG\ valid_for=(all_logfiles,
all_roles) db_unique_name=loca
l
log_archive_dest_10 string
log_archive_dest_11 string
log_archive_dest_12 string

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_13 string
log_archive_dest_14 string
log_archive_dest_15 string
log_archive_dest_16 string
log_archive_dest_17 string
log_archive_dest_18 string
log_archive_dest_19 string
log_archive_dest_2 string SERVICE=local LGWR SYNC db_uni
que_name=india_local
log_archive_dest_20 string
log_archive_dest_21 string


I checked archive log list too....

SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination %ORACLE_HOME%\RDBMS
Oldest online log sequence 10655
Next log sequence to archive 10655
Current log sequence 10657


What could be the reason..... Please help me to sort it out........

Thanks in advance....
Go to the top of the page
 
+Quote Post
burleson
post May 22 2017, 10:05 AM
Post #2


Advanced Member
***

Group: Members
Posts: 13,577
Joined: 26-January 04
Member No.: 13



Hi Joe,

Sorry about the delay in responding!

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

This may help:

http://www.dba-oracle.com/sf_ora_00257_arc...until_freed.htm

ORA-00257 is a common error in Oracle. You will usually see ORA-00257 upon connecting to the database because you have encountered a maximum in the flash recovery area (FRA), or db_recovery_file_dest_size .

First, make sure your automatic archiving is enabled. To check the archive lo made, try:

SQL> archive log list;

Now, note thatyou can find archive destinations if you are using a destination of USE_DB_RECOVERY_FILE_DEST by:

SQL> show parameter db_recovery_file_dest;

The next step in resolving ORA-00257 is to find out what value is being used for db_recovery_file_dest_size, use:

SQL> SELECT * FROM V$RECOVERY_FILE_DEST;

You may find that the SPACE_USED is the same as SPACE_LIMIT, if this is the case, to resolve ORA-00257 should be remedied by moving the archive logs to some other destination.

You next need to archive the log files by,

SQL> alter system archive log all;

It is important to note that within step five of the ORA-00257 resolution, you may also encounter ORA-16020 in the LOG_ARCHIVE_MIN_SUCCEED_DEST, and you should use the proper archivelog path and use (keeping in mind that you may need to take extra measures if you are using Flash Recovery Area as you will receive more errors if you attempt to use LOG_ARCHIVE_DEST):

SQL>alter system set LOG_ARCHIVE_DEST_.. = 'location=/archivelogpath reopen';

The last step in resolving ORA-00257 is to change the logs for verification using:

SQL> alter system switch logfile;




--------------------
Hope this helps . . .

Donald K. Burleson
Oracle Press author
Author of Oracle Tuning: The Definitive Reference
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Lo-Fi Version Time is now: 22nd October 2017 - 09:41 PM