After you install the Oracle Database, the backup module installer file oci_installer.zip is available in the Oracle home directory (see Table 31-2).

$ java -jar oci_install.jar

The mandatory parameters include the host name for the Oracle Cloud Infrastructure account and the private key used to sign Oracle Cloud Infrastructure API requests. For example:

java -jar oci_install.jar
-host https://objectstorage.us-phoenix-1.oraclecloud.com
-pvtKeyFile oci_private_key -pubFingerPrint oci_public_fingerprint 
-uOCID user_ocid -tOCID tenancy_ocid
-walletDir /wallet_directory

After you install the Oracle Database, the Oracle Database Cloud Backup Module for OCI Classic zip file opc_installer.zip is available in the Oracle home directory.

$ java -jar opc_install.jar

For information about encryption methodologies and choosing an encryption algorithm, see Configuring Backup Encryption.

If a backup is not encrypted, the RMAN reports this error message when you try to back up to OCI.

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

Recovery Manager (RMAN) encrypted backups are securely created, transmitted, and stored in the cloud. Use one of the following RMAN encryption modes to encrypt backups:

• Password encryption

• Transparent Data Encryption (TDE)

• Dual-mode encryption (combination of password and TDE)

You can either create a new bucket or use an existing bucket to store backups that must be automatically moved to Archive Storage.

To archive backups, you must store them in a standard container that is associated with a Lifecycle Tiering Policy (LTP). The LTP is a container policy that defines the type of tiering that is associated with the standard container. After the number of days specified by the LTP elapses, the backups stored in the standard container are automatically archived. You can explicitly exclude specific objects from being archived automatically.

To configure automatic archive of backups to Oracle Cloud Infrastructure Object Storage Service with Swift APIs:

1. Use one of the following techniques, when installing the Oracle Database Cloud Backup Module for OCI Classic, to specify the container to which backups must be archived:

   • Create a standard container that is associated with an LTP

     Specify the name that must be used for the new standard container by using the -container parameter. Set the -containerClass parameter to Tiering. To specify a user-defined LTP, use the -containerLTP parameter. If you omit this parameter, the default LTP is associated with the new container.

     See Run the Backup Module for OCI Classic Installer

     For example:

     -container PAYROLL_ARC
     -containerClass Tiering

     The standard container with the specified name is created and a default LTP is assigned to it. All backups, except XML objects, are archived when the number of days specified by the LTP elapses. This automatically adds the OPC_CONTAINER and OPC_CONTAINER_CLASS parameters to the opcSID.ora file so that these settings are used for backups.

   • Specify only the container class

     Set -containerClass to Tiering.

     The OPC_CONTAINER_CLASS parameter is set to Tiering in the opcSID.ora configuration file. The Oracle Database Cloud Backup Module for OCI Classic installer attempts to find an existing standard container that is associated with an LTP. If no such container is found, a new standard container with the default LTP is created. The naming convention used for the new container is oracle-data-account_name-index.

   • Use an existing standard container that is associated with an LTP

     Include the -container parameter with the name of an existing standard container that is associated with an LTP.

     For example:

     -container PAYROLL_ARC

     This automatically adds the OPC_CONTAINER parameter to the opcSID.ora configuration file so that the specified container is used to store backups.

2. Configure an RMAN channel that corresponds to the Oracle Database Cloud Backup Module for OCI Classic. See Configuring SBT Channel for Oracle Cloud (OCI).

In Oracle Cloud Infrastructure (OCI) Object Storage, an immutable bucket is a storage location governed by time-bound retention rules that protect data from modification or deletion for a specified duration. Use immutable buckets to implement a flexible backup retention strategy for each target database, and to prevent any modification to backups.

The Oracle Database Cloud Backup Module supports storing backups in immutable buckets that you have created in OCI.

To store backups in immutable buckets, you must first create these buckets in OCI Object storage:

• Regulatory Compliance Bucket configured with retention rules and rule lock (if necessary)

  You can also reuse an existing bucket associated with retention rules.

• Temporary Metadata Bucket with no retention rules or retention settings

  During backup operations, the temporary bucket is used to store backup metadata and files temporarily.

For more information about creating buckets and retention rules, see OCI Object Storage documentation.

To Store Immutable Backups with Oracle Database Cloud Backup Module for OCI

With the Oracle Database Cloud Backup Module for OCI, a default bucket is created. With the Oracle Database Cloud Backup Module for OCI Classic, a default storage container is created.

Custom containers and custom buckets can be created using REST calls or third-party tools such as CloudBerry Explorer.

To create containers using the REST API, see the tutorial Oracle Cloud Infrastructure Object Storage Classic: Creating Containers Using the REST API. For related Oracle Cloud Infrastructure Object Storage Classic Service documentation, see Creating a Container.

To create buckets using the REST API or the OCI Console, see Managing Buckets.

Prerequisites

• Install the backup module that corresponds to the destination in which backups must be stored.

  • To create backups to Oracle Cloud Infrastructure, install the Oracle Database Cloud Backup Module for OCI. Backups created using this module are stored in Oracle Cloud Infrastructure Object Storage. See Installing the Oracle Database Cloud Backup Module for OCI.

  • To create backups to Oracle Cloud Infrastructure Classic, install the Oracle Database Cloud Backup Module for OCI Classic. Backups created using this module are stored in Oracle Cloud Infrastructure Object Storage Classic. See Installing the Oracle Database Cloud Backup Module for OCI Classic.

• Configure an RMAN channel that will be used to create the required backups.

  To configure channels, see Configuring SBT Channel for Oracle Cloud (OCI). To configure other backup settings, see Additional Options for Using Oracle Database Backup Cloud Service.

  To automatically move infrequently-used backups to archive storage, see Configuring Automatic Archival to Oracle Cloud Infrastructure Object Storage Service with Swift API.

Prerequisites

See Prerequisites for Backups and Restores with Oracle Database Backup Cloud Service for prerequisites.

Procedure

1. Specify the password that must be used to encrypt backups. Use the SET ENCRYPTION command.
2. Back up the database using the BACKUP DATABASE command. Include archived redo log files, if required.

Prerequisites

See Prerequisites for Backups and Restores with Oracle Database Backup Cloud Service for prerequisites.

Procedure

1. Enable encryption using the SET ENCRYPTION command.

   If TDE is configured for the Oracle Database you're backing up, omit the ONLY keyword with the SET ENCRYPTION command to indicate the backup is protected with both a password and the configured transparent encryption.

2. Back up the database using the BACKUP DATABASE command. Include archived redo log files, if required.

For information about restoring and recovering backups, see Restoring Backups from Oracle Database Backup Cloud Service.

Prerequisites

To back up using TDE you need to have a TDE wallet (TDE keystore), which is different from the OPC wallet that stores Oracle Database Backup Cloud Service credentials.

See Prerequisites for Backups and Restores with Oracle Database Backup Cloud Service for prerequisites.

Procedure

To create a TDE wallet if you don’t already have one:

1. Add the following line to the sqlnet.ora file:

   ENCRYPTION_WALLET_LOCATION=
     (SOURCE=(METHOD=FILE)(METHOD_DATA=
       (DIRECTORY=path_to_TDE_wallet)))
   

   where path_to_TDE_wallet is the location where the TDE wallet is to be created; this must be different from the OPC wallet location.

2. Start SQL*Plus as sys:

   sqlplus / as sysdba

3. Create the TDE wallet in the location specified in sqlnet.ora:

   SQLPLUS> alter system set encryption key identified by "TDE-password";

   where TDE-password is the password that must be used to open the TDE wallet.

4. Whenever the database is restarted, open the TDE wallet with the following command:

   SQLPLUS> alter system set encryption wallet open identified by "TDE-password";

For complete information about TDE, see Using Transparent Data Encryption in Oracle Database Advanced Security Guide.

To back up an Oracle Database that uses TDE:

1. Connect Recovery Manager (RMAN) to the target database to be backed up and configure encryption for the database:

   RMAN> SET ENCRYPTION ON;

2. Back up the database:

   RMAN> BACKUP DATABASE;

For information about restoring and recovering backups, see Restoring Backups from Oracle Database Backup Cloud Service.

Prerequisites

See Prerequisites for Backups and Restores with Oracle Database Backup Cloud Service for prerequisites.

Procedure

To back up image copies from FRA to Oracle Database Backup Cloud Service, use these commands:

RMAN> BACKUP RECOVERY AREA;
RMAN> BACKUP DEVICE TYPE sbt COPY OF DATABASE;
RMAN> BACKUP RECOVERY FILES;
RMAN> BACKUP RECOVERY FILE DESTINATION;

To back up backup sets from FRA to Oracle Database Backup Cloud Service, use this command:

RMAN> BACKUP DEVICE TYPE sbt BACKUPSET ALL;

For information about restoring and recovering backups, see Restoring Backups from Oracle Database Backup Cloud Service.

You can quickly increase the limit by purchasing more capacity on demand. Once you buy more capacity, you can continue doing backups. You can also free up space by using RMAN to delete obsolete backups.

You can monitor how much storage capacity you've used by viewing detailed metrics about your usage. If your backups are stored in Object Storage Classic, use the Infrastructure Classic Console. If your backups are stored in Object Storage, use the Cost Analysis tools. See Monitor Your billing Data in Oracle Cloud Managing and Monitoring Oracle Cloud or Checking Your Balance and Usage in the Oracle Cloud Infrastructure documentation or .

You can also check the capacity used by your account or under a container by using cURL.

Example commands for Oracle Cloud Infrastructure Classic:

# curl -v -s -X GET
       -H "X-Storage-User: service-identitydomain:userid"
       -H "X-Storage-Pass: password"
       https://identitydomain.storage.oraclecloud.com/auth/v1.0

Use the Auth—Token entry to get the header information:

# curl -v -X HEAD
       -H "X-Auth-Token: auth-token"
       https://identitydomain.storage.oraclecloud.com/v1/service-identitydomain

Example output (pertinent details in bold):

< HTTP/1.1 204 No Content
< X-Account-Container-Count: 2
< X-Account-Object-Count: 567
* Server Oracle-Storage-Cloud-Service is not blacklisted
< Server: Oracle-Storage-Cloud-Service
< X-Account-Meta-Policy-Georeplication: us2
< X-Account-Meta-Policy-Archive: arch-us2
< X-Timestamp: 1446492266.33718
< X-Account-Bytes-Used: 7884540569
< X-Account-Meta-Quota-Bytes: 536870912000
< Accept-Ranges: bytes
< X-Trans-Id: txeb611621958647a681cd6-0056a4404bga
< Date: Sun, 24 Jan 2016 03:08:59 GMT
< Connection: keep-alive
< X-Storage-Class: Standard
< X-Container-Meta-Policy-Georeplication: us2
< X-Last-Modified-Timestamp: 1446492266.33718
< Content-Type: text/plain;charset=UTF-8

Example output for a tiering container (pertinent details in bold):

< HTTP/1.1 204 No Content
< X-Container-Object-Count: 0
< X-Container-Write: myIdentity4.Storage.Storage_ReadWriteGroup
< Accept-Ranges: bytes
< X-Timestamp: 1531949125.70314
< X-Container-Read: myIdentity4.Storage.Storage_ReadOnlyGroup,myIdentity3.Storage.Storage_ReadWriteGroup
< X-Container-Bytes-Used: 0
< X-Trans-Id: tx0d71e235b8814b94b197b-005b4fb04ega
< Date: Wed, 18 Jul 2018 21:25:34 GMT
< Connection: keep-alive
< X-Storage-Class: Standard
< Container-Meta-Policy-Georeplication: uscom-central-1
< Container-Policies-Enabled: tiering
< Last-Modified-Timestamp: 1531949125.70314
< Content-Type: text/plain;charset=utf-8
< Server: Oracle-Storage-Cloud-Service

If your database backups are stored in OCI Object Storage, then you can use the odbsrmt.py tool to manually extract the backup metadata into an XML file.

The odbsrmt.py file and the associated readme are both located in the Oracle home directory (ORACLE_HOME/rdbms/admin) of the target database.

Before you restore backups, configure an RMAN channel that corresponds to the location where the backup that must be restored is stored. The backups can be stored in Oracle Cloud Infrastructure Object Storage or Oracle Cloud Infrastructure Object Storage Classic. For information about configuring channels, see Configuring SBT Channel for Oracle Cloud (OCI).

For example, if password encryption was used to encrypt the backup, commands for a typical restore for the entire database would look as follows, specifying the password that was used to encrypt the backup:

RMAN> SET DECRYPTION IDENTIFIED BY 'my_pswd';
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;

If Transparent Data Encryption (TDE) was used to encrypt the backup, use this command to perform restore and recovery:

RMAN> SET ENCRYPTION ON;
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;

Backups can be stored in Oracle Cloud Infrastructure Archive Storage or archive storage in Oracle Cloud Infrastructure Classic. Backups stored in archive storage need to be recalled first before they can be restored. You must plan in advance for restore and recover operations using backups stored in archive storage. Use RESTORE DATABASE PREVIEW … RECALL to initiate a recall operation for the required backups. After you begin the restore operation, if the backups are still not available to read from the archive storage, then the restore operation waits until the required backups are available. This may slow down the restore operation.

To perform the steps in this example, the new host must have the following:

• Internet connectivity to connect to Oracle Database Backup Cloud Service

• A compatible operating system with the same endian format as the source host

• The same version of Oracle Database software as the source host

  If the new host has a higher version of Oracle software, ensure that there is a supported upgrade path between the Oracle Database version on the source host and the destination host. Then, perform the steps required to upgrade the destination database after the RMAN restore.

You must also know the following:

• DBID of the source database

• Password used to encrypt the backup if password-based encryption was used

• TDE encryption wallet from the source database if TDE encryption was used

To restore from a cloud backup stored using Oracle Cloud Infrastructure or Oracle Cloud Infrastructure Classic to a new host:

1. Install the Oracle Database Cloud Backup Module for OCI or Oracle Database Cloud Backup Module for OCI Classic on the new host using the same subscription credentials and custom container (if any) used for the backup. For information about installing the module, see Run the Backup Module for OCI Installer or Run the Backup Module for OCI Classic Installer.

   For example, with Oracle Cloud Infrastructure Classic, the service name (-serviceName), identity domain (-identityDomain), user name (-opcId), password (-opcPass), and container name (-container), if you used a custom container, must be the same. With Oracle Cloud Infrastructure, the tenancy OCID (-tOCID), user OCID (-uOCID), and bucket (-bucket), if you used a custom bucket, must be the same.

2. On the new host, connect to Recovery Manager (RMAN), set the decryption password, set the DBID, and restore the SPFILE.

   For example:

   rman target /
   RMAN> STARTUP NOMOUNT;
   RMAN> SET DECRYPTION IDENTIFIED BY 'my_bkup_pwd';
   RMAN> SET DBID=3389098001;
   RMAN> RUN {
   ALLOCATE CHANNEL t1 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_PFILE=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcDUP.ora)';
   RESTORE SPFILE TO PFILE '/u01/app/oracle/product/12.1.0/dbhome_1/dbs/initDUP.ora' FROM AUTOBACKUP;
   }

   The same password used to encrypt the backup must be used for restore and recovery operations.

   If the TDE wallet was used to encrypt the backup, the wallet must be copied to the new host and the wallet location must be set in the sqlnet.ora file before restoration is started. Also, use SET ENCRYPTION ON; instead of SET DECRYPTION IDENTIFIED BY 'my_bkup_pwd'; as shown in the example above.

   See My Oracle Support Note 1560327.1.

3. Edit the PFILE to reflect the new host, changing control file locations, create and recovery file destinations, and audit file destinations. For example, change the *_dest parameters so all destinations are correct, change the control_files parameter, and so on. If necessary, create the relevant directories on the new host.

4. Shut down the target database instance on the new host, restart the instance to the NOMOUNT state, restore the control file, and mount the database.

   For example:

   RMAN> SHUTDOWN IMMEDIATE;
   RMAN> STARTUP NOMOUNT;
   RMAN> RUN {
   ALLOCATE CHANNEL t1 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_PFILE=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcDUP.ora)';
   RESTORE CONTROLFILE FROM AUTOBACKUP;
   }
   RMAN> ALTER DATABASE MOUNT; 

5. If necessary, use the SET NEWNAMES command to define a new location for the restored data file (Oracle Database 10g and later) or database (Oracle Database 11g and later), and then start the restoration and recovery.

   For example:

   RMAN> RUN {
   SET NEWNAME FOR DATABASE TO '/u02/app/oracle/oradata/DUP/%U';
   ALLOCATE CHANNEL t1 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_PFILE=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcDUP.ora)';
   ALLOCATE CHANNEL t2 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_PFILE=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcDUP.ora)';
   ALLOCATE CHANNEL t3 DEVICE TYPE sbt PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_PFILE=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcDUP.ora)';
   RESTORE DATABASE;
   SWITCH DATAFILE ALL;
   SQL "ALTER DATABASE RENAME FILE ''+DATA/ASMDEMO1/ONLINELOG/group_3.263.873380343'' TO ''/u04/app/oracle/redo/redo03.log''";
   SQL "ALTER DATABASE RENAME FILE ''+FRA/ASMDEMO1/ONLINELOG/group_3.260.873380343'' TO ''/u04/app/oracle/redo/redo01.log''";
   SQL "ALTER DATABASE RENAME FILE ''+DATA/ASMDEMO1/ONLINELOG/group_2.262.873380341'' TO ''/u04/app/oracle/redo/redo02.log''";
   SQL "ALTER DATABASE RENAME FILE ''+FRA/ASMDEMO1/ONLINELOG/group_2.259.873380341'' TO ''/u04/app/oracle/redo/redo04.log''";
   SQL "ALTER DATABASE RENAME FILE ''+DATA/ASMDEMO1/ONLINELOG/group_1.261.873380341'' TO ''/u04/app/oracle/redo/redo05.log''";
   SQL "ALTER DATABASE RENAME FILE ''+FRA/ASMDEMO1/ONLINELOG/group_1.258.873380341'' TO ''/u04/app/oracle/redo/redo06.log''";
   }

6. Find the system change number (SCN) to make the database consistent:

   RMAN> RESTORE DATABASE PREVIEW DEVICE TYPE SBT;

   The output includes the name and location of backup pieces that will be used when restoring the database.

7. Recall any required backup pieces that were archived.

   If the RESTORE...PREVIEW command output contains a section named List of remote backup files, it means that some required backup pieces were archived. Recall these backup pieces using the following command:

   RMAN> RESTORE DATABASE PREVIEW RECALL DEVICE TYPE SBT;

8. Restore the database using the following command:

   RESTORE DATABASE DEVICE TYPE SBT;

9. Recover the database to that point:

   RMAN> RECOVER DATABASE DEVICE TYPE SBT UNTIL SCN scn;

   where scn is the SCN identified in the previous step.

   For Oracle Database 12c Release 2 (12.2) and higher, you can use the RECOVER DATABASE UNTIL AVAILABLE REDO command.

10. Open the database with the RESETLOGS option after restore and recovery is complete:

    RMAN> ALTER DATABASE OPEN RESETLOGS;

One way to create a standby database is to restore the backup performed from the on-premises production database.

I get a Request to set the lifecycle policy failed error

Specific error:

Exception in thread "main" java.lang.RuntimeException: 
SetBucketLCP: 400 Bad Request. at oracle.backup.opc.install.BmcConfig.SetBucketLCP(BmcConfig.java:851) 
  at oracle.backup.opc.install.BmcConfig.setBucket(BmcConfig.java:620) 
  at oracle.backup.opc.install.BmcConfig.doBmcConfig(BmcConfig.java:236) 
  at oracle.backup.opc.install.BmcConfig.main(BmcConfig.java:219)
Failed: 1 ()

SetbucketLCP is setting the lifecycle policy on the bucket, which means enableArchive was set to True. But the Object Storage service in the region was not granted the permission to manage objects, and hence the request to set the lifecycle policy failed.

Authorize the Object Storage service to move backups to Archive Storage. See Service Permissions in the Required IAM Policies section of the Oracle Cloud Infrastructure documentation.

I get an HTTP response code error when I run the installer for Oracle Cloud Infrastructure Classic

Specific error:

Server returned HTTP response code: 504 for URL:
https://identityDomain.storage.oraclecloud.com/v1/storage-identityDomain/?format=xml

Use the -host parameter when you run the installer, instead of the -serviceName and -identityDomain parameters. For example:

https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/hr-abc

Exclude /?format=xml at the end of the URL. For information about these parameters, see Parameters to Run the Oracle Database Cloud Backup Module for OCI Classic Installer.

I get a ConfigFile was not specified error when I run the installer

Specific error:

ConfigFile was not specified, and a default location could not be
determined because ORACLE_HOME and ORACLE_SID are not both set.

Set ORACLE_HOME and ORACLE_SID and rerun the installer.

I get a Specified directory does not exist error when I run the installer

Specific error:

Specified directory /home/oracle/OPC/lib does not exist.

The directory specified for the -libDir parameter does not exist. Create the directory and rerun the installer.

I get a java.io.IOException or java.io.FileNotFound error when I run the installer

For example:

java.io.IOException: Server returned HTTP response code: 401 for
the URL URL-name

The installer can't connect to Oracle Cloud with the information you provided. Try the following:

• Make sure the user name, password, service name, and identity domain used to run the installer are correct. With Oracle Cloud Infrastructure, make sure that the user OCID, tenancy OCID, fingerprint, and keys are correct.

  Enclose the user name and password in single quotes, for example 'myAccount@myCompany.com' and 'opc_pswd'. On Windows systems, use double quotes if the user name or password contains special characters.

  Fix any errors and rerun the installer. If the information you provided is correct, contact Oracle Support to verify your account information.

  Note:

  If you have a pre-paid metered subscription for Oracle Cloud Infrastructure Classic, the default service name is Storage (case sensitive). This is the name you'll use for the -serviceName parameter when you install the backup module.

• Check connectivity and see if you can reach the cloud storage endpoint URL from your database server. For example:

  $ ping storage.us2.oraclecloud.com
  PING storage.us2.oraclecloud.com (160.34.0.51): 56 data bytes
  64 bytes from 160.34.0.51: icmp_seq=0 ttl=239 time=63.738 ms
  64 bytes from 160.34.0.51: icmp_seq=1 ttl=239 time=67.288 ms

I get a Could not authenticate or 403 Forbidden error when I run the installer for Oracle Cloud Infrastructure Classic

This could be because you need to select a data center. See Request Trial or Paid Subscription to Oracle Database Backup Cloud Service.

The replication policy must be set before you run the backup module installer. Otherwise you'll get errors such as Could not authenticate to Oracle Database Cloud Backup Module or 403 Forbidden. Set the replication policy and wait at least 10 minutes for synchronization to complete before you retry the installation.

I get a Failed to load Media Management Library error

If you’re on a Windows system and keep getting System or Media Management Loading errors, 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.

If the problem persists, run the following operating system command (all platforms):

sbttest -f foo.txt -libname full-path-to-libopc|oraopc-library

The output shows why the module is not being loaded.

I’m using a Solaris 64-bit operating system and keep getting ORA-27211 - Failed to load Media Management Library

Installation is most likely failing because the libc.so.1 file does not exist in your environment. Confirm this by running the following operating system command:

sbttool -f foo.txt -libname full-path-to-libopc.so

To resolve the issue, set the operating system variable LD_LIBRARY_PATH_64 to the 64-bit library path that has the libc.so.1 file. If that doesn't resolve the issue and you're using an Oracle Solaris release earlier than Solaris 10 Update 10 (s10u10), upgrade your system to at least s10u10.

I get an Exception in thread error when I run the installer

Specific error:

Exception in thread "main" java.io.FileNotFoundException:
orclhome/dbs/opcdb1210.ora (No such file or directory)

The installer can't create the configuration file under the ORACLE_HOME/dbs directory. Make sure the directory is accessible. Also make sure the path for ORACLE_HOME is set correctly.

I get a PKIX path building failed: unable to find valid certification path to requested target error when I run the installer

Your database server's Java keystore does not have the SSL certificate of Oracle Cloud. You can work around this problem by using the -no-check-certificate option from the command line.

The wallet directory can't be created by the installer

I have a pre-paid metered subscription and don’t know what service name to use to install the Oracle Database Cloud Backup Module for OCI Classic

If you have a pre-paid metered subscription, the service name is Storage (case sensitive). This is the name you'll use for the -serviceName parameter when you install the backup module.

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. See Run the Backup Module for OCI Classic Installer.

If you are 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 did not include 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 forgot the password — how do I restore the backup?

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

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 Autobackups. Also check for proper syntax.

I get connectivity errors from my database server

This could be caused by any number of things, including network bandwidth issues and incorrect proxy settings. Test to see if you can reach general URLs from your system.