I get an RMAN encryption error when I try to back up

Specific error:

RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 08/15/2014 14:00:43
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
   KBHS-01602: backup piece 14p0jso8_1_1 is not encrypted

Backups must be encrypted before they can be sent to the cloud. Specify encryption and try backing up again.

I changed my password for Oracle Cloud and now my backups to Oracle Cloud Infrastructure Classic are failing

When you change your password for Oracle Cloud, you also need to update your password in the wallet used for backing up to Oracle Cloud Infrastructure Classic. Credentials in the wallet are used to authenticate to the cloud before backup data is sent. If the password isn't updated in the wallet, the backup fails because of the incorrect password.

To update the password in the wallet, rerun the Oracle Database Cloud Backup Module for OCI Classic installer with the new credentials. You can omit the -libdir parameter if you don't want to download the library. For more information about running the installer, see Downloading and Installing the Oracle Database Cloud Backup Module for OCI Classic.

If you're using Oracle Database Cloud Service or Oracle Database Exadata Cloud Service and use object storage for backups, you need to update the password used for backing up after you change your password for Oracle Cloud. For Database Cloud Service, see Updating the Password for Backing Up to the Storage Cloud in Using Oracle Database Cloud Service. For Exadata Cloud Service, see Updating the Password for Backing Up to the Storage Cloud in Using Oracle Database Exadata Cloud Service.

I get a Request Entity Too Large error when I try to back up

When you subscribe to Oracle Database Backup Cloud Service, you purchase the amount of storage capacity you want. If you reach your storage capacity limit and try to back up your database, your backup will fail. An error related to this might look as follows:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 12/02/2014 16:35:58
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
KBHS-01404: See trace file /u01/app/oracle/admin/proddb/diag/rdbms/proddb/trace/
sbtio_5884_123456.log for details
KBHS-00700: HTTP response error 'Request Entity Too Large'

You can quickly increase the limit by purchasing more storage capacity on demand. Once you buy more capacity, you can continue doing backups. You can also use the RMAN DELETE operation to free up space. As a best practice you should set up a proper retention period and periodically run RMAN backup management operations such as CROSSCHECK, OBSOLETE, and DELETE.

You can monitor how much storage capacity you've used by viewing detailed metrics. You can also check the capacity used by your account or under a container by using cURL. See Monitoring Your Storage Capacity.

I'm on a Windows system and keep getting System or Media Management Loading errors when I try to back up. How do I resolve this?

Your Windows environment could be missing C libraries needed by the RMAN backup module. Download the Redistributable Package for Visual Studio 2013 from https://www.microsoft.com/en-us/download/details.aspx?id=40784. Choose the 64-bit version and run the downloaded EXE file. This should resolve the problem.

How do I get more information when a backup fails?

Add the following parameter to the opcSID.ora configuration file to enable tracing, and then rerun the RMAN command:

_OPC_TRACE_LEVEL=100

This adds trace data to the sbtio.log file. To disable tracing, remove the _OPC_TRACE_LEVEL parameter or set the value to 0.

For information about the opcSID.ora configuration file, see Files Created When the Oracle Database Cloud Backup Module for OCI Classic is Installed.

I get an error when I use password-based encryption for my backup

Specific error:

RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 08/15/2014 11:10:57
ORA-19914: unable to encrypt backup
ORA-28361: master key not yet set

You probably didn’t add the ONLY parameter when you specified password encryption. It should be something like this:

RMAN> SET ENCRYPTION ON IDENTIFIED BY 'my_pswd' ONLY;

I used password-based encryption for my backup and don’t remember the password — how do I restore the backup?

Unfortunately, you can’t. The password used to encrypt a backup must also be used to decrypt it for restore and recovery operations. If you forget or lose the password, you cannot restore the backup.

RMAN restores from another location, not the cloud

Use SHOW ALL to confirm that RMAN is configured to use Oracle Database Backup Cloud Service as the backup destination. See Configuring Recovery Manager (RMAN) Settings. Also check for proper syntax.