Backing up remote databases with RMAN?

Hi there
Implementing RMAN (10g) for the first time, and have a few general questions.
We want to use RMAN to backup a number of remote instances.
1. What would be the architecture for this? Would i have a single, central RMAN instance ie a blank database with only a rec cat installed, and from there have all the target databases connecting in?
2. How would these remote target dbs communicate with the RMAN instance? TNS? dblinks?
I know they have to be registered with the RMAN instance, but how would they be recognised to begin with?
3. If i'm backing up to storage, does the storage need to be connected to the RMAN server, or the target database server?
I know these are probably really basic, but i've read through the manuals and these questions aren't adequately answered.
Thanks in advance to all who answer!
Rup

1. Its always a good idea to have seperate recovery catalog database, in case of a database loss, you have your backup information on other database.
2. you can connect rman to target database as
connect target /
or
connect target user/pass@mylink
connect catalog catuser/catuser@catdblink
when connecting for backup, you have to connect to target (which you want to backup) and then to catalog database , so RMAN knows which is to backed up and where to catalog
3. in all cases, rman will generate backup sets on target database server, you will have to nfs mount your storage to that server, if using tape library, then configure media manager for that target
null

Similar Messages

Trying to restore a database with RMAN in new server

Hello,
Database: Oracle 10gR2
O/S: Windows Server 2003
My RMAN backuppieces are stored in a network drive:
\\old_location\FULL
and
\\old_location\INC
I'm trying to restore a whole database with RMAN in another server from my FULL backup.
For that, I copy all backuppieces files
from: \\old_location\FULL
to new server: D:\new_location\
Also I created the relevant folder hierarchy under <ORACLE_BASE> directory, as follows:
a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>\admin' directory
b. Create <DATABASE_NAME> directory under '<ORACLE_BASE>\oradata' directory
c. pfile.ora and controlfile (CTL_MTDPROD_2308_20120401_1.CTL) are backup from original database and they are in D:\new_location\
d. I copied pfile.ora and controlfile to folder: C:\oracle\product\10.2.0\db_1\database\
I started creating an instance in new server from scratch:
C:\>oradim -new -sid MTDPROD -intpwd mtdprod
C:\> SET ORACLE_SID=MTDPROD
C:\> rman
RMAN> connect target sys
RMAN> SET DBID=21692876873
RMAN> STARTUP force nomount PFILE=C:\oracle\product\10.2.0\db_1\database\init_mtdprod.ora
RMAN> restore controlfile from 'C:\oracle\product\10.2.0\db_1\database\CTL_MTDPROD_2308_20120401_1.CTL';
RMAN> alter database mount;
#Since I want to read my backuppieces from D:\new_location and not from \\old_location\FULL then I catalog and restore like:
RMAN> catalog start with 'D:\new_location\';
RMAN> restore database;
Starting recover at 25/04/12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=541 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile copies to recover
recovering datafile copy fno=00003 name=D:\BD_MTDPROD\CONTROLFILES\SYSAUX01.DBF
recovering datafile copy fno=00004 name=D:\BD_MTDPROD\CONTROLFILES\USERS01.DBF
recovering datafile copy fno=00007 name=D:\BD_MTDPROD\DATAFILES_DATA\MSE.ORA
recovering datafile copy fno=00010 name=D:\BD_MTDPROD\DATAFILES_DATA\EXPEDIENTES2.ORA
channel ORA_DISK_1: reading from backup piece \\old_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: failover to piece handle=D:\new_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK tag=TAG20120401T190004
.....(continues)
Questions:
1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\
Please, advice.

user521219 wrote:
Questions:
1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\Is this a cold backup? Did you change the location of control file in your PFILE or is it still pointing to old location?
You may want to check the output of RESTORE DATABASE PREVIEW command, which will just report which backup files it uses without actually restoring thhe DB.

Creating a Data Guard Database with RMAN in 10&11g

I found this notes for 9i, looking for same for 10g & 11g
183570.1 Creating a Data Guard Database with RMAN (Recovery Manager) using Duplicate Command

These notes just show duplicating dbs without datagurd, i am looking for Creating a Data Guard DB with RMAN in 10 &11g.

Inserting data in remote database with remote procedure

Hi,
I have a problem concerning inserting data in a remote database (10g) by using a remote procedure.
I call the procedure from a 11g database just by doing:
begin
getlocalfilecontent@remoteserv(param)
commit;
end;
And it wouldn't insert the data into the remote table.
While when I execute the same procedure locally on that remote database (10g)
It does insert the data I want.
What could be causing the problem here, am I overseeing something?
Edited by: user7634309 on 14-Aug-2009 02:14

Already thanks for the fast replies
The dblink works perfectly. I can select data etc with this dblink.
The procedure on the remote database is the same.
One other thing, when I execute the remote procedure on local database 2nd time I get the
ORA-ERR: ORA-02041: client database did not begin a transaction.
This could be fixed by doing a commit or rollback but still no inserting in remote table.
So to sum it up:
What doesn't work:(no inserting)
On 11g server that calls remotely the procedure
begin
getlocalfilecontent@remoteserv(parameter);
commit;
end;
What works(does insert)
On 10g server calling the procedure locally
begin
getlocalfilecontent(param);
commit;
end;
So everything is the same except on the 11g server I add the dblink spec behiind the procedurecall

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

How to create new database with rman backup

hi,
i took a rman backup with nocatelog. can i make a new database with that rman backup.
if yes then how ? i m using oracle 9i.
thxs

'NEW' doesn't seem to be the right word here, but you can DUPLICATE (clone) an existing database or restore it to a new host:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/toc.htm
Werner

Backing up DPM2012R2 Database with a different DPM Server

Hi,
is it still a recommended way to backup up a DPM 2012R2 database (-> pure SQL on the same Server) with another DPM2012R2 Server?
So just attach it and back it up (like in DPM2010)?
Or shall one always use dpmbackup.exe?
If supported / recommended is it possible to backup a DPM 2012SP1 database with a DPM 2012R2 Server?
Thanks in advance
/bkpfast
My postings are provided "AS IS" with no warranties and confer no rights

Hi,
Using native DPM backup using D2D is fine for non disaster recovery scenario, otherwise D2T or D2D2T or using secondary protection is best. DPMBACKUP is non automated, so that is good for ad-hoc backups before major updates.
Scheduling native SQL backups is also viable solution.
If using Secondary DPM Server, both primary and secondary must be the same DPM versions including updates.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

Standby Database with RMAN on ASM

Hi,
I am using redhat Linux AS 4 and my database is 10.2.0.1. This database used ASM for storage of data files, control files, online redo logs. Flash recovery area is also configured in the ASM.
I want to create a physical standby database on a different machine by using RMAN. Can someone kindly point me to some easy to follow document? I have scoured the oracle docs, but am more confused than ever.
regards

Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
Note: the examples in this document use regular filesystems but the process is the same regardless, ie, in db_file_name_convert use your diskgroup rather than a filesystem (db_file_name_convert=+DG_SOURCE,+DG_TARGET)
another note to complement the first one:
Step By Step Guide On Creating Physical Standby Using RMAN Duplicate In ASM Filesystem For ASM Primary [ID 837102.1]
Edited by: rui_catcuddler on Sep 2, 2010 6:51 AM

Duplicating a Database with RMAN

Hi,
When Duplicating the database using RMAN,
does it build the auxilary database from the existing rman backups of the target database
or
will it build direcly from the open / mount stage of the target dabase (where there is no concept of rman backups)
Please advice.
Thanks
Naveen.

>
When Duplicating the database using RMAN,
does it build the auxilary database from the existing rman backups of the target database
or
will it build direcly from the open / mount stage of the target dabase (where there is no concept of rman backups)
>
That depends on the version- Before 11g, RMAN took a previous created backup to duplicate. In 11g, we introduced the new command
RMAN> duplicate target database *from active database* ;that does it "on the fly" without backup needed.
Kind regards
Uwe
http://uhesse.wordpress.com

Backing several databases with rman does require one catalog/

Thanks in advance. I've never liked RMAN, but now I need to get smart on how to best use it.
Please advise on the following:
1. I have several databases that need to be backed up using rman
2. I've create a new database that will be used to backup all of the databases
3. Will I need to create one catalog for all of the databases that will be backed up or do I create one catalog for each database that will need to be backed up? Thanks for any other advise
Additionally I'll be backing up two RAC databases.

attitude? ethics? they wont do.
Posters, please mind these common-sense rules when participating here:
- When asking a question, provide all the details that someone would need to answer it. Consulting documentation first is highly recommended.
- When answering a question, please be courteous and respectful; there are different levels of experience represented here. A poorly worded question is better ignored than flamed - or better yet, help the poster ask a better question.
- It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
- See more tips in the FAQ
Thanks for doing your part to make this community as valuable as possible for everyone!
- OTN

ORA-19602 during backup of a RAC database with RMAN

Dear All,
We have an Oracle 10g database on a 2 nodes. This database is running in noarchivelog mode. While doing an offline backup of this database, we encountered ora-19602 errors. See below:
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:55
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/30/2009 09:56:10
ORA-19602: cannot backup or copy active file in NOARCHIVELOG modeBelow were the steps that we followed:
1. We stopped both instances using "srvctl stop instance -d test -i test1,test2"
2. We then "rman target /"
3. In RMAN, we "startup mount"
4. In RMAN, we "backup database;"
5. RMAN failed with the above errors
Can someone advice what went wrong? Thanks!

Hi..
1. We stopped both instances using "srvctl stop instance -d test -i test1,test2"
2. export oracle_sid=sid
3. We then "rman target /"
4. In RMAN, we "startup mount"
5. In RMAN, we "backup database;"
Changed step 2.
Also, from sqlplus can you check the
select name,open_mode from v$database;
select STATUS from v$instance;
Anand

Backing up database with read-only tablespaces

I am trying to develop a script that will dynamically build RMAN scripts for backing up
a database with read-only tablespaces. The application running on this database creates
new tablespaces in read-write mode on weekly basis, populates them, and then puts them in read-only mode. So I need to backup all read-write tablespaces plus take backup of all read-only tablespaces once. The problem is that the application also includes a process that puts a tablespace back into read-write mode, updates it, and puts it back into read-write mode. So I need to be able to access "a history" of the tablespace - when was it put into read-only mode - to compare it with a history of backups. While history of backups is available in RMAN views, I couldn't find any way to extract tablspaces
history.
There should be RMAN command to the effect
"backup all read-write tablespaces and read-only tablespaces if they have not been backed up at least once since becoming read-only".
Regards,
Sev
null

just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off.

Duplicating DB with RMAN,DB mode:NOARCHIVE LOG?

Hello,
I want to get a duplicate database on a remote server machine with same file structure by using internet of VPN(virtual private network). My question is ...
can we duplicate the database to remote server if the Database is in NOARCHIVELOG MODE ??
I have surffed on net for the same i got the method to duplicated the database but not sure weather i can do that in noarchivelog mode !
Regarding the steps if anyone has some better ideas to perform duplication of Database with RMAN or any other tool let me know or any more optimized steps ....will be appreciated. But please keep this point that the database is in norachivelog mode.
ORACLE 10g R2
Windows server 2003 32bit
Thanks in advance....
Regards,
DBA4

If the database is in noarchivelog mode, then you can only take offline backup of database through RMAN in the mount state. Previously database shouldn't be shutdown
abnormally.
SQL> select LOG_MODE from v$database;
LOG_MODE
NOARCHIVELOG
1 row selected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 209715200 bytes
Fixed Size                  1289748 bytes
Variable Size             138412524 bytes
Database Buffers           67108864 bytes
Redo Buffers                2904064 bytes
Database mounted.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining options
D:\Test>rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Mer. Mai 30 19:46:13 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: MIKA (DBID=1492747861, not open)
RMAN> backup database;Now move that backup to another machine, and restore this backup.
On the target machine, do the following steps:
D:\Test>rman target /
rman>RUN
STARTUP NOMOUNT FORCE;
allocate channel d1 type disk;
RESTORE SPFILE;
SHUTDOWN IMMEDIATE;
STARTUP NOMOUNT;
RESTORE CONTROLFILE;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
ALTER DATABASE OPEN RESETLOGS;
regardsregards

Starting up a database in RMAN

I am running Oracle 8i (8.1.6) under Alpha OpenVMS 7.2. For some reason, I cannot start up a database in RMAN. I get the following error. Help from anyone will be greatly appreciated. Thanks.
$rman target / nocatalog
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: OEDSDB (DBID=3483140195)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN> shutdown immediate;
RMAN-06405: database closed
RMAN-06404: database dismounted
RMAN-06402: Oracle instance shut down
RMAN> startup pfile='ora_db:init.ora';
RMAN-06193: connected to target database (not started)
RMAN-06196: Oracle instance started
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06403: could not obtain a fully authorized session
RMAN-04005: error from target database: ORA-03113: end-of-file on communication
channel
RMAN-04015: error setting target database character set to US7ASCII
RMAN>

I'm using RMAN 8.1.6.0 since last June 2000
and it works very good. (Solaris 2.6)
Regarding your issue, first of all, you
have to connect to your target db with
a SYSDBA user. That means that the user you
are trying to connect to, must have been granted the SYSDBA privilege.
Sencondly, the init.ora file must reside in the same server where you are running RMAN from.
We have 25 servers running solaris 2.6 and rdbms 8.1.6.0. And i have created a RMAN catalog on my local server. I have all the init.ora files on my server in order to startup remote db with RMAN.
Best luck
null

ORA-28150 when accessing data from a remote database

Portal Version: Portal 3.0.9.8.0
RDBMS Version: 8.1.6.3.0
OS/Vers. Where Portal is Installed:: Solaris 2.6
Error Number(s):: ORA-28150
I have a problem with using a database link to access a table in
a remote database. So long as the dblink uses explicit logins
then everything works correctly. When the dblink does not have a
username then I get the ORA-28150 message. The database link is
always public. A synonym is created locally that points to a
synonym in the remote database. I am using the same Oracle user
in both databases. The Oracle portal lightweight user has this
same Oracle user as its default schema. The contents of the
remote table are always visible to sqlplus, both when the link
has a username and when it doesn't have a username.
All the databases involved are on the same version of Oracle.
I'm not sure which Oracle login is being used to access the
remote database, if my lightweight user has a database schema
of 'xyz' then does portal use 'xyz' to access the remote
database? I would be very grateful for any help or pointers that
might help to solve this problem.
James
To further clarify this, both my local and remote databases
schemas are owned by the same login.
The remote table has a public synonym.
The link is public but uses default rather than explicit logins.
The local table has a public synonym that points to the remote
synonym via the database link.
If I change the link to have an explicit login then everything
works correctly.
I can view the data in the remote database with TOAD and with
sqlplus even when the database link has default login rather
than explicit login.
This seems to point to Portal as being the culprit. Can anyone
tell me whether default logins can be used across database links
with portal?
TIA
James

832019 wrote:
One way to do this is by creating a database link and joining the two tables directly. But this option is ruled out. So please suggest me some way of doing this.Thus you MUST use two connection strings.
Thus you are going to be either constructing some intricate SQL dynamically or you are going to be dragging a lot of data over the wire and doing an in memory search.
Although realistically that is what the database link table would have done as well.
Might be better to look at moving the table data from one database to the other. Depends on size of course.

Backing up remote databases with RMAN?

Similar Messages

Maybe you are looking for