Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

   
Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





   

 

 

 

Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation

 

 


 

 

 

      
 
     Donald K. Burleson

Installing the RMAN Catalog

The catalog should be owned by a user with the resource role grant. I suggest a user in a small database dedicated to system administration functions such as the RMAN catalog and Enterprise Manager catalog. Create a tablespace for use by the RMAN user and assign that as the user’s default tablespace with unlimited quota. For example, if we wanted our user to be named rman_Remote DBA, the steps would be as follows:

The steps mentioned are available in Mike Ault’s Oracle Remote DBA Made Simple by Rampant TechPress.

Once the catalog is built, the recovery manager can be utilized. The command is either rman, rman80, or RMAN80 depending on your operating system. There are literally dozens of commands for use with the RMAN facility. I suggest reviewing the Oracle8i Server Backup and Recovery Guide, Release 8.1.5 (or most current release) (Oracle Corporation, 1999) before using RMAN.

The following are some example scenarios showing how the commands can be made into scripts.

Connection to rman in UNIX on early versions can be tricky. On some UNICES the double quote (“) character has to be escaped, and you need to use the double quotes to log into rman (at least on early versions). Assuming the database to be backed up is ORTEST1 with a TNS alias of ORTEST1, the user is as specified earlier, and the catalog database is ORRMAN, the connection to RMAN for the user SYSTEM password MANAGER would look like this:

 $ rman ORTEST1\ system/manager@ORTEST1 rcvcat "rman_dbo/rman_dbo@ORRMAN\"

 Intuitive, isn’t it? A sample session from Recovery Manager (RMAN) is shown next.

The target database service name in the “tnsnames.ora” file is “ORTEST1.” The recovery catalog database service name in the “tnsnames.ora” file is “ORRMAN.”

The steps mentioned are available in Mike Ault’s Oracle Remote DBA Made Simple by Rampant TechPress.

 

The above text is an excerpt from Mike Ault’s Oracle Remote DBA Made Simple by Rampant TechPress.

  

OCP Instructors Guide for Oracle Remote DBA Certification

 

If you need expert advice on teaching Oracle OCP exam certification concepts or if you just want an easy to understand guide to Oracle database administration, the OCP Instructors Guide for Oracle Remote DBA Certification is for you.

 

Get your copy of today and receive immediate access to the Online Code Depot and OCP study summary! It’s only $19.95 (I don’t think it is right to charge a fortune for books!) and you can buy it right now and get immediate access to the online code depot:

 

 

http://www.rampant-books.com/book_2003_2_OCP_print.htm

 

 

 

     

     

Remote DBA Service
 

Oracle Tuning Book

 

Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software

 

 

 

 

 

 

 

 

 

BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.