CSDBB - Oracle Database Backup Cloud Service
CSDBB - Oracle Database Backup Cloud Service
CSDBB - Oracle Database Backup Cloud Service
February 2016
Documentation that describes how to use Oracle Database
Backup Cloud Service to back up Oracle databases to Oracle
Cloud.
Oracle Cloud Using Oracle Database Backup Cloud Service, Release 15.4
E54730-07
Copyright © 2014, 2016, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface ................................................................................................................................................................. v
Audience ........................................................................................................................................................ v
Related Resources ......................................................................................................................................... v
Conventions................................................................................................................................................... v
iii
Backing Up from the Fast Recovery Area (FRA) to Oracle Database Backup Cloud Service ....... 3-3
iv
Preface
This document describes how to use Oracle Database Backup Cloud Service to back
up Oracle databases to Oracle Cloud.
Topics:
• Audience
• Related Resources
• Conventions
Audience
This document is intended for administrators who want to use Oracle Database
Backup Cloud Service to back up Oracle databases to Oracle Cloud.
It is assumed you know the following:
• The operating system environment under which you run Oracle Database
Related Resources
For more information, see these Oracle resources:
• Oracle Database Backup Cloud Service FAQ (My Oracle Support Doc ID 1640149.1)
http://support.oracle.com
Conventions
The following text conventions are used in this document:
v
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
vi
1
Getting Started with Oracle Database
Backup Cloud Service
Oracle Database Backup Cloud Service is a cloud storage solution for storing Oracle
Database backups. Here's what you need to know to get started.
Topics
Using RMAN backup compression, you can conserve bandwidth and improve
performance by reducing the size of backups before they’re sent to the cloud for
storage.
For licensing information about these optimizations, see Oracle Database Backup
Cloud Service in Oracle Database Licensing Information.
Oracle Database Backup Cloud Service is used to store Oracle Database backups only.
To store other types of data, use Oracle Storage Cloud Service. For more information,
see Using Oracle Storage Cloud Service.
Oracle Database Backup Cloud Service can also be used to back up and restore Oracle
Database Cloud - Database as a Service instances and Oracle Database Exadata Cloud
Service instances.
For instances created using the Oracle Database Cloud Service - Virtual Image service
level, download the Oracle Database Cloud Backup Module and perform tasks as
described in this document.
For Database as a Service (non-Virtual Image) and Exadata Cloud Service instances,
instance images come with the backup module already installed, so you don't need to
install the module, configure RMAN, and so on. For information about backup and
recovery in this case, see Backing Up and Restoring a Database as a Service Instance in
Using Oracle Database Cloud - Database as a Service. For information about billing, see
relevant details in How to Begin with Database as a Service Subscriptions in Using
Oracle Database Cloud - Database as a Service. For information about backup and
recovery in Exadata Cloud Service, see the corresponding topics in Using Oracle
Database Exadata Cloud Service.
Oracle Database Backup Cloud Service trials and paid subscriptions appear as
Oracle Storage Cloud Service subscriptions. See Important Information About
Oracle Database Backup Cloud Service Subscriptions.
2. Activate and verify the service. See Activating Your Trial Subscription or
Activating Your Order in Getting Started with Oracle Cloud.
4. Important Step: Select a data center for your service (you'll see Replication Policy
Not Set for Oracle Storage Cloud Service when you sign in to the My Services
application). See Selecting a Replication Policy for Oracle Storage Cloud Service in
Using Oracle Storage Cloud Service.
5. Create accounts for your users and assign them appropriate privileges and roles.
See Managing User Accounts and Managing User Roles in Managing and Monitoring
Oracle Cloud.
Note:
For Oracle Database Public Cloud Services subscriptions, users must have
either the Storage Administrator or Database Backup Administrator role to
back up to the cloud.
To administer Oracle Database Backup Cloud Service, you'll install the module needed
for cloud backups, configure Recovery Manager (RMAN) settings, and perform other
tasks.
Topics
Download the Oracle Download the Oracle Database Downloading and Installing the Backup
Database Cloud Backup Cloud Backup Module installer Module
Module from Oracle Technology Network
(OTN).
Install the Oracle Run the Oracle Database Cloud Downloading and Installing the Backup
Database Cloud Backup Backup Module installer. Module
Module
Perform backup and Connect to the target database and Backing Up to Oracle Database Backup Cloud
recovery configure an RMAN channel, then Service
issue standard RMAN backup, Restoring Backups from Oracle Database
restore, and recovery commands. Backup Cloud Service
Monitor the service Check on the day-to-day operation Managing and Monitoring Oracle Cloud
of your service, monitor Services in Managing and Monitoring Oracle
performance, and review Cloud
important notifications. Also see Monitoring Your Storage Capacity
Topics
• The required patch if you’re using the Standard Edition of Oracle Database
See My Oracle Support Doc ID 1640149.1 at http://support.oracle.com.
• Values for the parameters required to run the Oracle Database Cloud Backup
Module installer
It’s best to compile this information before you run the installer. See Parameters
Used to Run the Backup Module Installer.
Note:
If your database server has multiple Oracle homes, the backup module must
be installed into each ORACLE_HOME. Alternatively, you can copy the library
file (libopc.so or oraopc.dll, depending on your operating system) to
other Oracle home library locations, along with the opcSID.ora
configuration file (assuming you're using the same cloud credentials for
backing up all databases in the database server).
Copy and rename the opcSID.ora file for each database instance you are
backing up to the cloud, where SID matches the SID for the database instance.
Operating system (64 bits) Linux, Solaris x86-64, SPARC, Windows, AIX,
HP-UX, zLinux
The following table lists required parameters. Optional parameters are also listed.
Parameters can also be displayed by running the following command from the
directory that contains the opc_install.jar installer file:
java -jar opc_install.jar
—libPlatform Operating system for the SBT library used for Optional
backups and restores.
In most cases, you don’t need to specify this
parameter because the installer automatically
determines the correct operating system.
Exceptions might be if you see error messages
indicating your operating system can’t be
identified or if you need to download the library
for use on a different system.
Supported values for this parameter:
• linux64
• windows64
• solaris_sparc64
• solaris_x64
• zlinux64
• hpux_ia64
• aix_ppc64
For information about supported operating
systems, see Supported Databases and Operating
Systems.
-opcID 'myAccount@myCompany.com'
-opcPass 'abc123$'
-serviceName myService
-identityDomain myDomain
-libDir /home/oracle/OPC/lib
-walletDir /home/oracle/OPC/wallet
1. Download the Oracle Database Cloud Backup Module from Oracle Technology
Network (OTN):
http://www.oracle.com/technetwork/database/availability/
oracle-cloud-backup-2162729.html
Accept the license agreement, click All Supported Platforms, and provide your
OTN user name and password when prompted. Then download the ZIP file that
contains the installer (opc_installer.zip) to your system.
The file contains the installer file, opc_install.jar, and a README file.
3. Run the installer from the directory that contains opc_install.jar, providing
the required parameters in one line, with each parameter preceded by a hyphen
and followed by its value. For information about required parameters, see
Parameters Used to Run the Backup Module Installer.
The following is an example run of the installer. This example shows how the installer
automatically downloads the Oracle Database Cloud Backup Module for your
operating system, creates a wallet that contains Oracle Database Backup Cloud Service
identifiers and credentials, creates the Oracle Database Cloud Backup Module
configuration file, and downloads the library necessary for cloud backups and
restores.
java -jar opc_install.jar -serviceName myService
-identityDomain myDomain -opcId 'myAccount@myCompany.com'
Note:
You can run the installer and install the backup module as many times as you
like. Periodically perform the installation procedure to get the latest RMAN
SBT library module, and also to update the password after you change it in
Oracle Cloud.
For example:
RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt
PARMS='SBT_LIBRARY=/orclhome/lib/libopc.so,
SBT_PARMS=(OPC_PFILE=/orclhome/dbs/opct1.ora)';
Note:
For Oracle Database 10g Release 2 (10.2), specify the ENV parameter instead of
the SBT_PARMS parameter shown in the previous example. For example:
RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt
PARMS='SBT_LIBRARY=/orclhome/lib/libopc.so,
ENV=(OPC_PFILE=/orclhome/dbs/opct1.ora)';
On Windows systems, you’ll need to specify the ENV parameter. For example:
RMAN> CONFIGURE CHANNEL DEVICE TYPE sbt
PARMS='SBT_LIBRARY=C:\tmp\oraopc.dll,
ENV=(OPC_PFILE=C:\tmp\opct1.ora)';
Note:
Use the SHOW ALL command to confirm you’ve configured RMAN to use Oracle
Database Backup Cloud Service as the backup destination:
RMAN> SHOW ALL;
Configuring Autobackup
As a best practice, you should also configure RMAN to automatically back up the
database control file and server parameter file. With a control file autobackup, RMAN
can recover the database even if the current control file, recovery catalog, and server
parameter file are inaccessible.
The autobackup feature is disabled by default. To enable autobackup, use the
following command:
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
For information about autobackups, see Oracle Database Backup and Recovery User's
Guide.
For a complete list of RMAN commands, see Oracle Database Backup and Recovery
Reference.
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
Backups must be in the form of backup sets, not image copies. For information about
configuring compression for backups, see Configuring Compression Options in Oracle
Database Backup and Recovery User's Guide.
• RMAN interface
Use the RMAN command-line interface to execute familiar commands and perform
backups on demand. You can also create automated backup jobs using the cron
utility.
• Third-party tools
Use third-party tools such as CloudBerry Lab's cloud backup solution. See
http://www.cloudberrylab.com/oracle-db-backup-software.aspx.
Note:
To store backups in a custom container, include the —container parameter and the
custom container name when you run the Oracle Database Cloud Backup Module
installer.
For example:
-container PAYROLL_DB
This automatically adds the OPC_CONTAINER parameter to the opcSID.ora
configuration file so the custom container is used for backups, where SID is the
system identifier of the Oracle database being backed up to Oracle Database Backup
Cloud Service.
To specify a custom container after you’ve installed the Oracle Database Cloud
Backup Module, add the OPC_CONTAINER parameter and the container name to
opcSID.ora.
For example:
OPC_CONTAINER=PAYROLL_DB
For information about parameters used by the installer, see Parameters Used to Run
the Backup Module Installer.
For information about the opcSID.ora configuration file, see Files Created When the
Backup Module is Installed.
After you install the Oracle Database Cloud Backup Module and configure Recovery
Manager (RMAN) settings, you can perform backup and restore operations using
familiar RMAN commands. You’ll also use RMAN to specify retention policies,
perform crosschecks, and delete backups.
Information about your cloud backups is maintained in the database control file, and
in the recovery catalog if you use one.
Encryption is required to back up to Oracle Database Backup Cloud Service. You can
use password encryption, Transparent Data Encryption (TDE), or dual-mode
encryption, which is a combination of password and TDE.
Note:
For information about performing various types of backup and restore operations, see
Oracle Database Backup and Recovery User's Guide.
For a complete list of RMAN commands, see Oracle Database Backup and Recovery
Reference.
Topics
• Backing Up from the Fast Recovery Area (FRA) to Oracle Database Backup Cloud
Service
Note:
If you forget or lose the password, you won’t be able to restore the backup.
For information about restoring and recovering backups, see Restoring Backups from
Oracle Database Backup Cloud Service.
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 Oracle Database Advanced Security Guide.
To back up an Oracle database that uses TDE:
For information about restoring and recovering backups, see Restoring Backups from
Oracle Database Backup Cloud Service.
Note:
If you forget or lose the password, you won’t be able to restore the backup.
For information about restoring and recovering backups, see Restoring Backups from
Oracle Database Backup Cloud Service.
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 use standard Recovery Manager (RMAN) commands to perform restore and
recovery operations from Oracle Database Backup Cloud Service.
A few possible scenarios are addressed here. For complete information about using
RMAN to perform various types of restore and recovery operations, see Oracle
Database Backup and Recovery User's Guide. For a complete list of RMAN commands,
see Oracle Database Backup and Recovery Reference. The concepts and commands in these
RMAN guides are applicable to the database backed up to Oracle Database Backup
Cloud Service.
Topics
If Transparent Data Encryption (TDE) was used to encrypt the backup, you'd specify
something like this:
RMAN> SET ENCRYPTION ON;
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;
• A compatible operating system with the same endian format as the source host
1. Install the Oracle Database Cloud Backup Module 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 Downloading and Installing the
Backup Module.
For example, the following must be the same:
• Password (-opcPass)
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_FILE=//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. For details, see relevant information in My Oracle Support
Doc ID 1560327.1 at http://support.oracle.com. Also, use SET
ENCRYPTION ON; instead of SET DECRYPTION IDENTIFIED BY
'my_bkup_pwd'; as shown in the example above.
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_FILE=//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 datafile (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_FILE=/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_FILE=/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_FILE=/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:
RESTORE DATABASE PREVIEW DEVICE TYPE SBT;
8. Open the database with the RESETLOGS option after restore and recovery is
complete:
RMAN> ALTER DATABASE OPEN RESETLOGS;
Service, you need to create a standby database in the cloud to be used with Oracle
Data Guard or Oracle Active Data Guard.
One way to create a standby database is to restore the backup performed from the on-
premises production database. For detailed information, see Appendix I in the
Disaster Recovery to the Oracle Public Cloud white paper. The appendix describes
how to create a database from Oracle Database Backup Cloud Service.
You might encounter some problems when you use Oracle Database Backup Cloud
Service.
This section lists common problems and their possible solutions.
Also see the Oracle Database Backup Cloud Service FAQ (My Oracle Support Doc ID
1640149.1) and Cloud Backup Performance Analysis (My Oracle Support Doc ID
2078576.1) at http://support.oracle.com.
Topics
• Use multiple RMAN channels for higher parallelism, which results in full
utilization of the network. You can configure as many RMAN channels as you
want. For example, the following configuration uses eight channels in parallel to
back up to the cloud:
RMAN> CONFIGURE DEVICE TYPE sbt PARALLELISM 8;
Try increasing the parallelism until you find the optimal transfer rate.
• Use multisection backups. With these, multiple RMAN channels are used in
parallel to back up large data files in separate sections.
You create multisection backups by specifying the SECTION SIZE parameter with
the BACKUP command. For example, the following command specifies a backup
section size of 1 GB:
RMAN> BACKUP DEVICE TYPE sbt DATABASE SECTION SIZE 1g;
• Use a backup strategy of weekly full and daily incremental backups. This results in
faster backups and could save a significant amount of network bandwidth. Use the
RMAN fast incremental backup feature (based on block change tracking) to
optimize the performance of your daily incremental backups.
• Use a recovery catalog to store long-term backups. For information about recovery
catalogs, see Managing a Recovery Catalog in Oracle Database Backup and Recovery
User’s Guide.
Note:
You can test network throughput by using the throughput measurement tool.
See Testing Network Throughput in Managing and Monitoring Oracle Cloud.
Note:
• Backup module: Make sure you’ve downloaded the latest backup module
from Oracle Technology Network (OTN)
• Proxy or firewall issues: Make sure your proxy is set up correctly, and you
can reach general URLs from your system
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.
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.
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.
Enclose the user name and password in single quotes, for example
'myAccount@myCompany.com' and 'myPassword'. 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, 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
This could be because you need to select a data center. See How to Begin with Oracle
Database Backup Cloud Service Subscriptions.
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’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.
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 have a pre-paid metered subscription and don’t know what service name to use
to install the backup module
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.
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 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 Database Backup Cloud Service.
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 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 Backup Module.
If you're using Oracle Database Cloud - Database as a Service or Oracle Database
Exadata Cloud Service and use object storage for backups, after you change your
password for Oracle Cloud, follow the steps for updating the password for backing up
to the storage cloud as described in Using Oracle Database Cloud - Database as a Service
or Using Oracle Database Exadata Cloud Service.
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
from the My Services dashboard. Click the service name to display the details page for
the service, and then click the Metrics tile to see usage data. You can also check the
capacity used by your account or under a container by using cURL. See Monitoring
Your Storage Capacity.
https://www.microsoft.com/en-us/download/details.aspx?id=40784.
Choose the 64-bit version and execute the downloaded EXE file. This should resolve
the problem.
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;