RDS RMAN backup fails as rdsadmin_rman_util_backup_database command abruptly ends after transferring few RMAN backup pieces to RDS local storage

Description: RDS RMAN backup fails as rdsadmin_rman_util_backup_database command abruptly ends after transferring few RMAN backup pieces to RDS local storage

Symptoms

RDS RMAN backup fails abruptly after transferring some data with below errors:

• ORA-06512: at "SYS.RDS_SYS_RMAN_UTIL", line 870
• ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted
• ORA-06512: at "SYS.DBMS_ISCHED", line 242
• ORA-06512: at "SYS.DBMS_SCHEDULER", line 566
• ORA-06512: at "SYS.RDS_SYS_RMAN_UTIL", line 379
• ORA-06512: at "SYS.RDS_SYS_RMAN_UTIL", line 855
• ORA-06512: at "SYS.RDS_SYS_RMAN_UTIL", line 1205
• ORA-06512: at "SYS.RDS_SYS_RMAN_UTIL", line 1265
• ORA-06512: at "RDSADMIN.RDSADMIN_RMAN_UTIL", line 181
• ORA-06512: at line 2

Causes

Either the local RDS storage space is not sufficient, or the backup commands are not run manually.

Resolution

1. Verify that you have sufficient space on Amazon RDS to backup RMAN dumps. For full backup of the RMAN, you must have:

   • Same amount of space which is of RDS database size (1x) on the local Amazon RDS storage
   • Space to accommodate the archive logs

2. If storage is not an issue, manually run rdsadmin_rman_util_backup_database.

3. Verify backup commands manually using Oracle XE edition or SQL developer.

4. You can try running the backup script manually using a SQLPLUS command line logged into RDS as the same RDS user. An appropriate Oracle directory must be created in RDS instance up front to hold the backup files.