Qwerty

________________

Appendix A Practices
________________

Practice 2: Configuring Recovery Manager Background: You need to configure backup and recovery settings. Some of this you do with RMAN, and some with Enterprise Manager. These settings will, unless overridden later, provide the configuration for the backup and recovery activity you do later. These configurations include definingretention policy, control-file autobackup, and excluded tablespaces. Important Note: As preparation for the workshop at the end of this course, before doing anything else, run the following script in an XTerm command shell to prepare a copy of your database files:
$ $HOME/labs/lab_02_copy.sh

1. Set the NLS_LANG environment variable to "yyyy-mm-dd hh24:mi:ss" in your XTerm window, and then connectto your database as the target database in the default NOCATALOG mode as the SYS user. 2. Use the RMAN SHOW ALL command to generate a listing of the RMAN configuration settings. 3. Configure RMAN to automatically back up the control file and SPFILE whenever a backup of the database or data files is taken. Leave the RMAN session connected. You will need it again. 4. Use the Enterprise Manager (EM)Database Control Console to set the backup retention policy to a recovery window of 2 days. Log in to the Database Control Console as the SYS user (with password oracle, connect as SYSDBA). If this is the first time you are logging in to EM as the SYS user, you will need to click “I agree” on the License Agreement screen. The URL is of this format: http://.us.oracle.com:1158/em Your machine nameappears in the upper-left corner of the Xterm window you started. You can also look in the $ORACLE_HOME/install/readme.txt file and find the URL under the “Enterprise Manager 10g Database Control URL” heading. 5. Verify the backup retention policy setting using the RMAN utility and the SHOW command. 6. Application development tells you that there will be a daily loading of data from an externalsource, and there needs to be a staging area set up for that data. Run the lab_02_06.sql script to create the STAGING tablespace, to hold this data. Then configure RMAN to exclude this tablespace from backup tasks. You can do this because, if you ever lose this data, you do not need to recover it; you can simply reload the data from the external source. Then verify that the tablespace is excluded. 7.Exit RMAN.

Oracle Database 10g: Administration Workshop II

A-2

Practice 3: Using Recovery Manager Background: In this exercise, you become familiar with using RMAN to perform and manage backups. You need to put your database into ARCHIVELOG mode, and take a full backup of your database. 1. Using SQL*Plus or the EM Database Control Console, verify that the database is in ARCHIVELOG mode.If not, alter the database to enable archiving of the online redo logs. Note that the database must be in the MOUNT state in order to change the archive log mode. Ensure that the database is open after this step. Note: If you see the following error, click OK, and continue to click Refresh. This error will go away eventually.

2. Connect to your database using RMAN in the NOCATALOG mode. Youcannot use an existing RMAN session because the database has been restarted. First, ensure that your XTerm shell has the NLS_LANG environment variable set as indicated in Practice 2. 3. Use the RMAN REPORT command to generate a listing of your database structure. 4. Obtain a listing of all database backup sets that currently exist. There should be none. 5. Use RMAN to back up the data files belongingto the EXAMPLE and USERS tablespaces. Verify that: • • • The current control file and the server parameter file are backed up with this backup Your backups are placed in the flash recovery area The format of the backup is a backup set

Oracle Database 10g: Administration Workshop II

A-3

Practice 3: Using Recovery Manager (continued) 6. Create an image copy of two data files. Use the...