The operation cannot be completed until the DML operation is in progress. When you exit SQLPLUS, there is no response-you cannot exit normally if you are stuck. Log on to the host where the database is located and use SQLPLUS to log on to D.
The operation cannot be completed until the DML operation is in progress. When you exit SQLPLUS, there is no response-you cannot exit normally if you are stuck. Log on to the host where the database is located and use SQLPLUS to log on to D.
Symptom:
The operation cannot be completed until the DML operation is in progress. When you exit SQLPLUS, there is no response-you cannot exit normally if you are stuck.
When you log on to the host where the database is located and use SQLPLUS to log on to the DBA, an error occurred while archiving.
[Oracle @ oel-01 ~] $ Sqlplus bys/bys
SQL * Plus: Release 11.2.0.1.0 Production on Sun Jul 21 17:55:09 2013
Copyright (c) 1982,200 9, Oracle. All rights reserved.
ERROR:
ORA-00257: archiver error. Connect internal only, until freed.
1. Check the log and prompt that a REDO log cannot be archived.
[Oracle @ oel-01 ~] $ Tail alert_bys001.log
ORA-19502: write error on file "", block number (block size =)
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/bys001/redo03.log'
Sun Jul 21 18:01:18 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance bys001-Archival Error
ORA-16014: log 3 sequence #219 not archived, no available destinations
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/bys001/redo03.log'
Errors in file/u01/app/oracle/diag/rdbms/bys001/bys001/trace/bys001_arc1_6050.trc:
ORA-16014: log 3 sequence #219 not archived, no available destinations
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/bys001/redo03.log'
2. Check the hard disk usage and find that ORACLE_HOME is already used in the directory where the archive file is located.
[Oracle @ oel-01 ~] $ Df-h
Filesystem Size Used Avail Use % Mounted on
/Dev/sda2 19 GB 18G 3.8 M 100%/
/Dev/sda1 99 M 21 M 74 M 22%/boot
Tmpfs 3.0G 529 M 2.5G 18%/dev/shm
/Dev/sda5 4.6G 2.6G 1.9G 58%/backup
Iii. Here I use RMAN to delete archived logs
[Oracle @ oel-01 ~] $ Rman target/
RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;
Delete archived logs before today
RMAN> delete archivelog until time 'sysdate-1 ';
You can also use
RMAN> delete archivelog all; delete all archives
4. Check the disk space. A part of the disk space has been released.
[Oracle @ oel-01 ~] $ Df-h
Filesystem Size Used Avail Use % Mounted on
/Dev/sda2 19 GB 18G 588 M 97%/
/Dev/sda1 99 M 21 M 74 M 22%/boot
Tmpfs 3.0G 529 M 2.5G 18%/dev/shm
/Dev/sda5 4.6G 1.8G 2.6G 42%/backu
For more details, please continue to read the highlights on the next page:
Related reading:
SPFILE error causing database startup failure (ORA-01565)
ORA-01172, ORA-01151 error handling
ORA-00600 [2662] troubleshooting
Troubleshooting for ORA-01078 and LRM-00109
Notes on ORA-00471 Processing Methods
ORA-00314, redolog corruption, or missing Handling Methods
Solution to ORA-00257 archive logs being too large to store