Link to home
Start Free TrialLog in
Avatar of xoxomos
xoxomos

asked on

RMAN backup

Using RMAN in 10g, how would i backup just one schema?
ASKER CERTIFIED SOLUTION
Avatar of rbrooker
rbrooker
Flag of New Zealand image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of techji
techji

What is your requirement ?
Avatar of xoxomos

ASKER

Currently i do use export for backup, but the tablespace is sizable. (24GB)  There is not enough space left to make an rman backup of the entire database which would be about 60GB and there are 40+GB left free. There is a cold backup done by the systems people, but the user would like to have all tables for this particular schema backed up in a manner where it would not require intervention of the sys admin to restore.
how is the data organised in the database?  in a discrete number of tablespaces?  you can use transportable tablespaces to transfer the data from one database to another by tablespace, you can also use this to archive tablespaces for plugging back in at a later date.  will this work for you?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thanks techji :)
Avatar of xoxomos

ASKER

Yeah, that's sort of the impression i got.  Due to the size, export takes so long i was hoping there was something i wans't seeing.
Avatar of xoxomos

ASKER

".....archive tablespaces for plugging back in at a later date."  
Como?!  Not clear on what you mean here though.
Avatar of xoxomos

ASKER

Yes, this is essentially for archiving purposes.  A user is bringing an IBM mainframe system with big DB2 tables over and wants to be sure to have access after the mainframe system is shut down.
Hi,

a transportable tablespace is a tablespace that you export.

eg.
put tablespace in readonly mode
export tablespace ( creates dmp file )
copy tablespace ( and dmp file ) somewhere safe
mark tablespace read write.

this has now got you a copy of the tablespace outside of the database that you can import ( using the dmp file ) into another database

to import, put tablespace i correct place in relation to the target database
import the tablespace using the dmp file
voila, all the objects in the tablespace are now in the target database.

useful for refreshing dev instances etc..
:)