Bikle.com

Ajax Demo:

Plain HTML
(no Ajax here):

of URLs:

rmandoc.html 12-09-2001 Bikle ----------------- A Simple Demonstration of RMAN Setup This page is contains a demonstration of setting up RMAN. Once the setup is complete, we show how to use RMAN to backup the tools tablespace to disk. At that point the reader would be well set to take advantage of books and other resources which discuss the guts of RMAN. We started our efforts by creating an RCAT database to hold an RMAN object called the "catalog". We started the build of the RCAT database by creating a softlink on a host which already contained a running Oracle database. cd /oracle/app/oracle/product/ ln -s 816 RCAT Then, we edited some files which are displayed below: /var/opt/oracle/oratab /export/home/oracle/.RCAT /export/home/oracle/RCAT.csh /oracle/app/oracle/product/RCAT/dbs/initRCAT.ora /oracle/app/oracle/product/RCAT/network/admin/listener.ora /oracle/app/oracle/product/RCAT/network/admin/tnsnames.ora Next, we created all directories listed in the file initRCAT.ora. Next, we crafted a set of scripts to create the RCAT database: /oracle/app/oracle/admin/RCAT/create/crdbRCAT.sql /export/home/oracle/admin/RCAT/create/crGeneric.sql /export/home/oracle/admin/RCAT/create/runCatScripts.sql Next, we created all directories listed in the above files. Then, we ran the above scripts. Results of above scripts are in the directory: /export/home/oracle/admin/RCAT/create/ At this point we had a generic empty database. Next, we bounced the listener and verified that we could establish a Net8 connection to each database using the connect descriptions in the file below: /oracle/app/oracle/product/RCAT/network/admin/tnsnames.ora Next, we turned to the Oracle document listed below (Chap 3): Oracle8i Recovery Manager User's Guide and Reference Part Number A76990-01 A url: http://gwynne.cs.ualberta.ca/~oracle/817doc/server.817/a76990/recocat.htm#435634 We crafted a script: /oracle/app/oracle/admin/RCAT/create/crRMAN.sql Output: /oracle/app/oracle/admin/RCAT/create/crRMAN.lst We crafted another script: /oracle/app/oracle/admin/RCAT/create/rman1.sh Output: /oracle/app/oracle/admin/RCAT/create/rman1.sh.out Next, we turned our attention away from the RCAT database and towards the BIKLE55 database which is the one we wanted to backup using RMAN. First, we created an ops$oracle account inside of the BIKLE55 database (often referred to as the "target" database in the RMAN documentation). The syntax was simple: GRANT DBA TO ops$oracle IDENTIFIED BY oxacle; ALTER USER ops$oracle DEFAULT TABLESPACE GENDATA TEMPORARY TABLESPACE TEMP; The above account allows most Oracle tools to connect and authenticate to the database by passing a "/" on the command line. The database will allow the tool to connect if it is being run from the UNIX oracle account. Next, we crafted a simple script designed solely to get us into the RMAN command line interface: RMANprompt.sh A demo is linked below: RMANprompt-demo.txt We used the above script to "register" the target database: "register" screen dump Next, we wrote a script to do a full backup of the tools tablespace: rmanFull-tools.sh We ran the above script and captured a screen dump: rmanFull-tools-sh-sd.txt Next, we wrote and ran a script to look inside the RMAN catalog: RMANlist.sh A screen dump from us running the script is displayed below: RMANlist-sh-sd.txt When we inspect the above screen dump, we see that the backup of the tools tablespace has indeed been cataloged. We expected this. We did not expect to see a large amount of information from other backups. A little bit of detective work revealed that the target database had been backed up by RMAN back in October. Those backups had been cataloged in the target database's control files. Then, in December, we came along and built this demonstration. When we built the catalog database in December, a mechanism inside the RMAN utility detected the catalog inside the target database's control files. Then, it copied this information into that catalog database. Next, we demonstrate how to 'restore' a datafile from the backup we just took. First, we wrote a script: RMANrestore.sh Next, we ran the above script and captured a screen dump: RMANrestore-sh-sd.txt When we inspect the above screen dump, we see that the RMAN restore script only restored the data file to disk. Since the restored data file does not appear in the dba_data_files view, we can see the RMAN restore script did not affect the target database in any way. RMAN does give the DBA the ability to 'recover' a data file after it has been restored. Essentially this means attaching the restored data file to the database and synchronizing the data inside the data file with data inside the rest of the database. I prefer to do recovery operations from sqlplus rather than from within RMAN. Since this page is concerned more with setting up RMAN rather than using it, we leave the reader at this point. We may come back to this page at a later time after we take some time to document how to get RMAN talking directly to tape.