Errors RMAN-03009 ORA-19809 ORA-19804 When doing a backup

If you are trying to do a backup of your database and are receiving these errors below:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/11/2010 11:27:28
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 5218762752 limit

Check if you are using the db_recovery_dest as the backup destination and if yes, increase the value of db_recovery_file_dest_size initialization parameter to a value that could behave your database size.

Example:
alter system set db_recovery_file_dest_size=15G scope=both;


Best Regards,
Paulo Portugal

How to solve "Concurrent Request error Ora-20100 FND_FILE failed to create .tmp file"

If you are experiencing Ora-20100 when running a concurrent on your Oracle E-Business Suite environment, soexecute these steps below to solve this problem:

1-First, check if the .tmp file exists in the temp directory defined by $APPLPTMP variable. Example:

$echo $APPLPTMP
/usr/tmp

If is there any file with the same name but with a different owner, (this could happens if ou have a lot of EBS envronments at the same server what is not a good idead), remove this temp file and try running the concurrent again.

2- Otherwise, login through a sqlplus session using the apps user and execute command below to test generation of a temp file;
SQL> exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'TEST FND_FILE Utility');

If this command shows errors like ORA-20100 and ORA-0652, then, you need to stop the concurrent manager using adcmctl script, kill all FNDLIB that are still runing and start the concurrent manager agai. Steps below:

--Login as apps application owner under OS
cd $INST_TOP (for R12)
cd admin/scripts
adcmctl stop apps/passwod

--Kill FNDLIB
ps -ef | grep FNDLIB

--Login as apps user on database and run the cmclean.sl script
SQL>show user
USER is "apps"
SQL>@cmclean.sql
SQL>commit;

--Start Concurrent manager again
adcmctl start apps/pssword

--Run the concurrent and see if the problem was solved



Best Regards,
Paulo Portugal