Backing Up Oracle - Computing at Cornell

Chapter 11. Day-to-day monitoring on Windows 2000
Once the TDP for Oracle implementation and environment has been set up,
as described in the preceding chapters, it is recommended that the regular
day-to-day tasks be monitored and automated for more efficient execution.
This chapter details some of the processes and tasks which can be used.
11.1 Automating database tasks
There are some Oracle database tasks which can be automated as detailed
below. These are best determined by the Oracle DBA.
11.1.1 Starting SQL*Net and RDBMS services at system reboot
During the Oracle installation process, the Oracle services are set to start
automatically. If they are not starting automatically, check the services to see
what the startup mode is and modify it appropriately.
11.2 Automating RMAN backups
In order to automate Oracle RMAN backups, you use the RMAN cmdfile
option. When you specify cmdfile when invoking RMAN, then RMAN
executes the file specified line by line. The file should be plain text. In
Section 10.3.1, “Consistent whole database backup” on page 163 we
discussed the creation of the scripts directory to hold our RMAN scripts. Also
in that section, we showed how to run the script backup_offline_beach using
the cmdfile option.
Instead of typing in the SET ORACLE_SID and RMAN commands each time,
we created a simple command file called AUTORMAN.CMD, that uses simple
variable substitution to call the RMAN script and create the log file. This file is
based on a database SID of BEACH, where the internal password of the
BEACH database is manager, and the user/password and database of the
recovery catalog is rman/rman@rio, a directory c:\oracle\admin\scripts that
contains the RMAN scripts. You will need to modify all of these values to
correspond with your environment.
set ORACLE_SID=BEACH
rman target internal/manager@beach rcvcat rman/rman@rio
cmdfile=c:\oracle\admin\scripts\%1 log=c:\oracle\admin\scripts\%1.log
© Copyright IBM Corp. 2001 171