ORA-00257:archiver error, connect internal only until freed

 

Issue:

Application log shows below error and users are unable to connect to the database.

0RA-00257:archiver error, connect internal only until freed

(OR)

0RA-00257:archiver error, connect internal only until freed
ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST


Fix:

1) Check if there are any errors for the archive destination(s). Make sure that the number of VALID archive destinations is greater than or equal to the value specified by LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter.

set pages 1000
col dest_name for a30
col destination for a60
SELECT dest_id, dest_name, binding, status, destination, error FROM v$archive_dest;

SHOW PARAMETER log_archive_min_succeed_dest

2) If space is full in one or more of the archive destinations (or if destination is not available), take any of the following steps:

2.a) Manually move the archives to another location and delete them from archive destination.
 

(OR)

2.b) Change the archive destination to an alternate archive destination which has space available.
             

SQL> alter system set log_archive_dest_1='LOCATION=<alternate location path>';

  
(OR)

2.c) If there are VALID archive destinations but are less than the value specified by LOG_ARCHIVE_MIN_SUCCEED_DEST, then set this parameter to a lower value:
            

 SQL> alter system set log_archive_min_succeed_dest=<>;

  
(OR)

2.d) Backup the archives and delete them using RMAN command - BACKUP ARCHIVELOG with DELETE INPUT; (Doc ID 388422.1)

3) In case, archiving does not resume even after freeing up space in archive destination, then probably archiver is stuck.In such case, issue the following command as per (Doc ID 121927.1), for each archive destination to resume automatic archiving:


alter system set LOG_ARCHIVE_DEST_.. = 'location=/<archive log path> reopen';

 

When Flash Recovery Area is in use ( Most of the cases we need to follow the below steps)

i) Check if flash_recovery_area is in use.

archive log list; 
Database log mode Archive Mode 
Automatic archival Enabled 
Archive Destination USE_DB_RECOVERY_FILE_DEST 
Oldest online log sequence 384 
Next log sequence to archive 386 
Current log sequence 386

ii) To immediately resolve this issue, allow more space in the DB_RECOVERY_FILE_DEST with the DB_RECOVERY_FILE_DEST_SIZE parameter :

SQL> alter system set db_recovery_file_dest_size=<>G scope=spfile;

OR

iii) To avoid the situation once DB_RECOVERY_FILE_DEST_SIZE is reached , specify and alternate location
(archiving is automatically performed to the alternate dest2) :

log_archive_dest_1='LOCATION=use_db_recovery_file_dest NOREOPEN ALTERNATE=LOG_ARCHIVE_DEST_2'
log_archive_dest_2='LOCATION=/other_dest_for_archiving'
log_archive_dest_state_1='enable'
log_archive_dest_state_2='alternate'
db_recovery_file_dest='/u01/app/oracle/product/10.1.0/db_1/flash_recovery_area'
db_recovery_file_dest_size=2G


iv)  To cleanup Flash recovery Area regularly in order to avoid hitting the space issue, refer to below document:


Space issue in Fast / Flash Recovery Area - FRA Full (Doc ID 829755.1)


Comments

Post a Comment

Popular posts from this blog

How to fix Oracle SQL Developer connection issue "Got minus one from a read call"

Image
 During connection from SQL Developer to EBS database got below error message: Status : Failure - Test failed: IO Error: Got minus one from a read call Following solution can be done : 1. Go to directory $ORACLE_HOME / network / admin 2. Modify sqlnet.ora file with following parameter : tcp.validnode_checking = no 3. If you don 't want to disable this, you can put the machine names as follows: tcp.invited_nodes=(machine1, machine2) 3. Bounce the listener. Due to security enhancements it is not good to put tcp.validnode_checking = no or comment out will through error when we start listener like below: Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=shsebs7idb1.appsolworld.com)(PORT=1522))) TNS-00584: Valid node checking configuration error TNS-12560: TNS:protocol adapter error Better plan is to add localhost or IP address of client (Local Computer) in the sqlnet.ora file That will solve the problem NAMES.DIRECTORY_PATH=(TNSNAMES, ONAMES, HOSTNAME) SQLNET.EXPI
Read more

Few Important steps of Oracle Database Clone

 Make Sure oraInst.loc location is correct and accessble. [demantra@dsiddem ~]$ cat /etc/oraInst.loc inventory_loc=/orastage/oraInventory inst_group=dba [demantra@dsiddem ~]$ cd /orastage/oraInventory [demantra@dsiddem oraInventory]$ ls -ltr total 16 drwxrwx---. 5 demantra dba 4096 Jul 22 19:37 backup drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 ContentsXML drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 locks drwxrwx---. 3 demantra dba 4096 Jul 23 10:08 logs Remove Oracle Home from Inventory [demantra@dsiddem oraInventory]$ cd $ORACLE_HOME/oui/bin [demantra@dsiddem bin]$ ./runInstaller -detachHome ORACLE_HOME=$ORACLE_HOME Starting Oracle Universal Installer... Checking swap space: must be greater than 500 MB.   Actual 3039 MB    Passed The inventory pointer is located at /etc/oraInst.loc Run Clone.pl [demantra@dsiddem bin]$ echo $ORACLE_HOME /dnbsid/demantra/oracle/19.0.0 [demantra@dsiddem bin]$ echo $ORACLE_BASE /dnbsid/demantra [demantra@dsiddem bin]$ E01=ORACLE_HOME=$ORACLE_HOME [dema
Read more

How to autopopulate user_guid in fnd_user table ( EBS Blank Page)

  Issue:  EBS Local Login url is working fine. When accessing sso url, users are getting error as below appended to the url. And login page will be blank. One of the reason could be : OAM Authentication is fine but during authorization process, OAM is unable to map guid from oid to user_guid in fnd_user. This can be due to user_guid being null in fnd_user table. As per the process, when user logins for the first time, user_guid need to be populated automatically (from oid) Query guid from oid and update fnd_user table with that. ldapsearch -h oidhost.appsolworld.com -p 3060 -D "cn=orcladmin" -w orcladmpwd -b "cn=Users,dc=dc,dc=online,dc=org" -s sub "(uid=$1)" orclsamaccountname krbprincipalname mail orcluserprincipalname orclguid Pass userid to this command which gives guid along with other details. Update fnd_user table with above guid : update fnd_user  set user_guid=' ' where user_name like ' '; Solution:  As per the process,  when user
Read more