Cause: ORA-00257 error (lack of space error), by looking for information, the vast majority of this is due to the archive log too much, occupy all the hard disk space caused by the simple deletion of the log or increase storage space can be resolved.
Solution:
1, login server, user Oracle, connect Oracle
[root@userbeta~]# su-oracle
[Oracle@userbeta~]$ Sqlplus/nolog
Sql> Connect/as SYSDBA
2, check the use of Flash recovery area, you can see the archivelog has been very large, reached 99.94
Sql> select * from V$flash_recovery_area_usage;
3, now to clean up the Archivelog archive log, production environment recommended backup
Query Log directory Location
Show parameter recover;
4, Exit Sqlplus, log in with root user, and delete archived log after backup
Enter a target address first; Create a new Oracle archive log backup directory
mkdir Oracle Archived Log Backups
Enter archive log source file directory (ORCL is the database instance name):
cd/u01/app/oracle/flash_recovery_area/orcl/archivelog/
First enter the Archivelog directory outside:
Cd..
Backup Archivelog the archive log below to the newly created Oracle archive log backup directory:
CP-RF archivelog/mnt/oracle Archive Log backup/
Delete archived logs that have been backed up after waiting for backup to complete
5, after the archive log is deleted, the control file must be maintained with Rman, otherwise the space display is still not released
Use the Oracle User Login server to enter Rman maintenance:
Rman Target Sys/pass
Check out some useless archivelog.
Rman> crosscheck Archivelog All;
Delete all Archivelog up to the previous three days
rman> Delete archivelog until time ' sysdate-3 ';
6, again query the use of Flash recovery area:
Follow step 1 to enter the Sqlplus environment, and then use the following command to query for discovery, using only 0.54%, which indicates that the archive log was cleared successfully.
Sql> select * from V$flash_recovery_area_usage;