Weird RMAN catalog issue

Question

I am on 10.2.0.4, RMAN + RMAN catalog + Data Gurad and I am desporate :)
My db crashed with the following:
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 49: Disc quota exceeded
A look in the FRA showed that it was 100% full. Archived logs take all of the space. I delete archived logs via OS method and then do delete expired archvied log all. If I am connected to recovery catalog while doing this, Oracle DOES NOT delete archieved logs from FRA (I don't see them on diks, but FRA stays full). If I connect to target only and do not connect to the catalog and do the same thing, FRA gets emptied out. WHY???? Thank you for any input!!!
p.s. Here is my delete archvied log script:
#!/bin/ksh -x
# Script to delete archive logs older then 4 days
find /data/archive/PROD/archivelog -mtime +4 -exec rm -r {} \;
. /data/app/oracle/.profile
export ORACLE_SID=PROD
export DATESTAMP="`date +"%y:%m:%d"`"
rman <<EOF
SPOOL MSGLOG TO '/data/app/home/dba/backup_files/archive_logs/PROD_clear_a
rch${DATESTAMP}.log'
@/data/app/home/dba/scripts/connect_nocat.rman
run {
allocate channel d1 device type disk;
crosscheck archivelog all;
delete noprompt expired archivelog all;
release channel d1;
EXIT;
EOF

Answer 1

hi,
you wrote: +"...Oracle DOES NOT delete archieved logs from FRA..."+
If you try to delete needed files (depends on your retention policy:
show RETENTION POLICY;
report need backup;
restore archivelog all preview summary;
) you may have to use "force" option in the statement. Even if they don't exist on disk, RMAN will throw errors.
What is the output of:
crosscheck archivelog all;
delete noprompt expired archivelog all;
P.S. it's better not to delete oracle files in OS if RMAN handles B&R policy ;-)