Oracle Error Log: ORA-00257, oracleora-00257

Oracle Error Log: ORA-00257, oracleora-00257

The following error is reported when the program is started this afternoon:

Caused by: java. SQL. SQLException: ORA-00257: archive program error. Only internal connections are allowed before release.

It is found that the oracle database logs are full and marked below!

Ora-00257: Archive errors, limited to internal links before release how to solve?

I. Brief Introduction
First, there are two types of database log files:

Online log files and archive log files will overwrite the previous ones and will not be backed up.

Archive log files are backed up, resulting in the full storage of archived logs. solution:

If the archive log space is full, export the old archive log to another disk to free up disk space. You can also add a new archive target disk.

Solution 1:
Manually delete the logs in D: \ oracle \ product \ 10.2.0 \ flash_recovery_area, and then use rman to delete the archived logs.
1) # rman target/
2) rman> crosscheck archivelog all;
3) rman> delete expired archivelog all;
4) rman> exit

Solution 2: changed the FLASH_RECOVERY_AREA size.
SQL> alter system set db_recovery_file_dest_size = 8G scope = both;
SQL> show parameter db_recovery_file_dest_size

Ii. Detailed process Introduction
1. Connection
$ Sqlplus/as sysdba

SQL * Plus: Release10.2.0.1.0-Production on Mon Jan 17 10:00:24 2011

Copyright (c) 1982,200 5, Oracle. All rights reserved.
Connected:
Oracle Database10gRelease10.2.0.1.0-64bit Production
2. view the archiving status
SQL> select * from v $ log;

If the ARC status is NO, the system cannot perform automatic archiving.

3. view the location of the archived log
SQL> show parameter recover;

SQL> exit
$ Exit
4. Enter the log storage directory
# Cd
# Ls
. TTauthority cdrom proc
. Xauthority configassist. log sbin
. Dt dev smit. log
. Dtprofile etc smit. script
. Java home smit. transaction
. Mh_profile lib sqlnet. log
. Sh_history lost + found tftpboot
. Vi_history lpp tmp
. Wmrc mnt u
Mail nmo42_aix5L_64.tar.gz unix
TT_DB nsr usr
Audit opt... the remaining full text>

Oracle 10g Report ORA-00257

10 Gb is not much. It will soon be used up. We suggest setting more.
In addition, check your backup and archiving logs. useless information can be deleted to avoid occupying so much space.
In RMAN, you can run the following command to check for redundant backups:
Report obsolete
Then delete it:
Delete obsolete