 Posted 2/4/2009 10:36:37 AM
|
|
|
|
From a command prompt type in the following (depending on your OS/Shell):
set ORACLE_SID=your oracle SID
rman target /
my sid=orcl
You should see something similar to this:Recovery Manager: Release 11.1.0.6.0 - Production on Mon Feb 2 20:37:12 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1204953687)
RMAN> Next thing, is your database running in ARCHIVE LOG MODE?
You can check this by typing archive log list from the sql command prompt. sqlplus / as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Mon Feb 2 20:39:08 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 218
Current log sequence 220
SQL>
This will affect how you back up your database.
The above database is not running archive and I can only therefore carry out an OFFLINE backup. In rman you can issue this: RMAN> run {
shutdown immediate;
startup mount;
backup database;
alter database open;
} If your database is running in archive log mode you can issue this: run {
backup database include current controlfile;
backup (archivelog all delete input);
} The above command will backup the database and all existing archive log files and then it will delete those archive logs. Then type this command to list the backups: list backup; This is the basic rman backups.
|
|
|
Posted 2/4/2009 10:39:41 AM
|
|
|
|
| If you run the commands, and if you encounter the following message below, then you should check your connect string to make sure you issues something like: rman target sys/password
or
rman target /
RMAN> backup database include current controlfile;
Starting backup at 04-FEB-09
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 02/04/2009 12:23:17
RMAN-06171: not connected to target database
|
|
|
Posted 2/4/2009 10:41:43 AM
|
|
|
|
| This is true. Also, remember that there are many RMAN errors that you can encounter. If you have anything specific try posting it to our RMAN error codes forum. It'll be easier to find. http://www.franklinfaces.com/Forum59-1.aspx
|
|
|
|