Lab 2.2: Putting the Database

in ARCHIVELOG Mode

In this exercise, you will configure the database for ARCHIVELOG mode. You will then actually put the database in ARCHIVELOG mode.

1.Create a directory called c:\oracle\arch\arch.

C:\>mkdir oracle C:\>cd oracle C:\oracle>mkdir arch C:\oracle>cd arch

C:\oracle\arch>mkdir orcl C:\oracle\arch>cd orcl C:\oracle\arch\orcl>

2.Log into your database using SQL*Plus. Check the log mode the database is in by querying the LOG_MODE column in V$DATABASE.

C:\oracle\orabackup\orcl>sqlplus sys as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Aug 14 19:37:19 2008 Copyright (c) 1982, 2007, Oracle. All rights reserved.

Enter password: Connected to:

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production With the Partitioning, OLAP, Data Mining

and Real Application Testing options SQL> select log_mode from v$database; LOG_MODE

------------

NOARCHIVELOG

3.Using the alter system command, set the LOG_ARCHIVE_DEST_1 parameter to point to the new directory you created in step 1.

SQL> Alter system set log_archive_dest_1=’location=c:\oracle\arch\orcl’; System altered.

4.Shut down the database using the shutdown immediate command.

SQL> shutdown immediate Database closed.

692  Appendix A  n  Lab Exercises

Database dismounted.

ORACLE instance shut down.

5.Put the database in MOUNT mode with the startup mount command. Confirm that the database is in MOUNT mode by querying the OPEN_MODE column in V$DATABASE.

SQL> startup mount

SQL> select open_mode from v$database; OPEN_MODE

----------

MOUNTED

6.Now put the database in ARCHIVELOG mode using the alter database archivelog command.

SQL> alter database archivelog; Database altered.

7.Open the database with the alter database open command. Check the LOG_MODE parameter of the V$DATABASE view to ensure that the database is in ARCHIVELOG mode.

SQL> alter database open; Database altered.

SQL> select log_mode from v$database; LOG_MODE

------------

ARCHIVELOG

8.To ensure that the database is configured correctly, force a log switch.

SQL> Alter system switch logfile; System altered.

9.Now check the directory c:\oracle\arch\orcl to ensure that the archived redo logs are being created correctly.

SQL> Host dir c:\oracle\arch\orcl Volume in drive C has no label.

Lab 2.3: Executing a Manual

Online (Hot) Backup

In this lab, you will perform an online/hot backup of your database, with the database still running.

1.Create a directory for the backups. In this lab, we use c:\oracle\orabackup\orcl\hot. We assume that the directory structure c:\oracle\orabackup\orcl is already created from the work you did in Lab 2.1.

C:\>cd oracle\orabackup\orcl C:\oracle\orabackup\orcl> mkdir hot

2.Log into your database using SQL*Plus. Check the log mode the database is in by querying the LOG_MODE column in V$DATABASE. It should be in ARCHIVELOG mode.

C:\oracle\orabackup\orcl>sqlplus sys as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Aug 14 19:37:19 2008 Copyright (c) 1982, 2007, Oracle. All rights reserved.

Enter password: Connected to:

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production With the Partitioning, OLAP, Data Mining

and Real Application Testing options SQL> select log_mode from v$database; LOG_MODE

------------

ARCHIVELOG

3.Using the DBA_DATA_FILES view, determine the datafiles that you will need to back up.

SQL> select tablespace_name, file_name from dba_data_files;

---------- ---------- ----------------

17 CURRENT

25 INACTIVE

36 INACTIVE

8.Take the database out of hot backup mode with the alter database end backup command.

SQL> alter database end backup; Database altered.

9.Use the alter system switch logfile command to force a switch from log sequence 7.

SQL> alter system switch logfile;

There may be times when you will need to use the alter system archive log all; command to get the latest archived redo-log files archived in a timely manner.

10.Check the archive-log directory to make sure log-file sequences 4 through 7 have been created. Note that we also checked the LOG_ARCHIVE_FORMAT parameter value. This is so we can know in the filename of the archived redo logs where the sequence number is.

696  Appendix A  n  Lab Exercises

Note in this output that the filename convention has the sequence number of the archived redo log right after the ARC value. Thus we have ARC00003 for log sequence 3, ARC00004 for log sequence 4, and so on. In the preceding output, we appear to have all log sequences that are required to recover this backup.

11.Copy the archived redo logs to the backup location.

SQL> Host copy c:\oracle\arch\orcl\arc*.* c:\oracle\orabackup\orcl\hot\*.* c:\oracle\arch\orcl\ARC00003_0662757171.001 c:\oracle\arch\orcl\ARC00004_0662757171.001 c:\oracle\arch\orcl\ARC00005_0662757171.001 c:\oracle\arch\orcl\ARC00006_0662757171.001 c:\oracle\arch\orcl\ARC00007_0662757171.001

5 file(s) copied.

12.Check the backup directory to ensure that all the files needed are in place.

SQL> Host dir c:\oracle\orabackup\orcl\hot\*.*

Volume in drive C has no label.

Volume Serial Number is 08DE-E1AB

Directory of c:\oracle\orabackup\orcl\hot

Here is a checklist: