Databases Reference
In-Depth Information
How It Works
Most RMAN tasks require that you connect to the target database with a user who has the
sysdba
database privilege.
You can connect to your target database with
sysdba
privileges in one of two ways:
•
Use an OS-authenticated account.
•
Use a password file that contains the username and password information of schemas granted
the
sysdba
privilege.
■
a new sys level privilege is available in oracle Database 12c named
sysbackup
. You can grant this privilege to
database users to allow them to specifically perform rMan backup and recovery tasks. This allows you to grant a user
the privileges required to back up, restore, and recover the database without having to grant them all of the privileges
associated with
sysdba
.
Tip
A useful way to troubleshoot the root cause of an
ORA-01031
error is to attempt to log in to SQL*Plus with the
same authentication information as when trying to connect through RMAN. This will help verify either that you are
using an OS-authenticated account or that the username and password are correct.
If OS authentication is working, then you should be able to log in to SQL*Plus as follows:
$ sqlplus / as sysdba
If you're using a password file, you can verify that the username and password are correct (and that the user has
sysdba
privileges) by logging in as shown here:
$ sqlplus <username>/<password> as sysdba
If you receive an
ORA-01031
error from attempting to log in to SQL*Plus, then either you aren't using an
OS-authenticated account or your username and password combination does not match what is stored in the
password file (for users attempting to connect as sysdba).
If you are using an OS-authenticated account, it doesn't matter what you specify for the username and password.
You can specify any text strings for the username and password, and Oracle will allow you to connect. This is because
Oracle performs OS authentication first. If that OS authentication succeeds, the username and password combination
is not validated.
Another issue that you might encounter when first connecting to and using RMAN is this:
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-06553: PLS-213: package STANDARD not accessible
RMAN-04015: error setting target database character set to US7ASCII
If you receive the prior messages, ensure your data dictionary has been properly created (via catalog.sql and
catproc.sql).
Another error commonly encountered when first accessing RMAN is as follows:
$ rman target /
rman: can't open target
