GENERATING ARCHIVES

IN ORACLE 9I

Presented by :
NAVEEN SAINI
C.S.E 4th YEAR
Semester 7th
071058
ARCHITECTURE OF ORACLE
 PHYSICAL FILES OF A DATABASE
A) CONTROL FILE
 Every Oracle database has a control file. A control file is a small binary file that
records the physical structure of the database and includes:
 The database name
 Names and locations of associated datafiles and online redo log files
 The timestamp of the database creation
 The current log sequence number
 Checkpoint information

 The control file must be available for writing by the Oracle database server
whenever the database is open. Without the control file, the database cannot be
mounted and recovery is difficult.

 The control file of an Oracle database is created at the same time as the database.
By default, at least one copy of the control file is created during database creation
B) DATA FILE
Datafiles are physical files of the operating system that store the data of all
logical structures in the database. They must be explicitly created for each
tablespace. Oracle assigns each datafile two associated file numbers, an
absolute file number and a relative file number, that are used to uniquely
identify it.

Type of File Number

a) Absolute
Uniquely identifies a datafile in the database. In earlier releases of Oracle,
the absolute file number may have been referred to as simply, the "file
number."
b) Relative
Uniquely identifies a datafile within a tablespace. For small and medium size
databases, relative file numbers usually have the same value as the
absolute file number.
C) REDO LOG FILES
The most crucial structure for recovery operations is the online redo log, which consists of two or more preallocated
files that store all changes made to the database as they occur.

Every instance of an Oracle database has an associated online redo log to protect the database in case of an instance
failure i.e they are used to generate archive redo log files which are used in recovery of a database.

Archive redo log files

 Oracle enables you to save filled groups of online redo log files to one or more offline destinations, known collectively as
the archived redo log, or more simply archive log. The process of turning online redo log files into archived redo log files
is called archiving. This process is only possible if the database is running in ARCHIVELOG mode. You can choose
automatic or manual archiving.

 When running in ARCHIVELOG mode, the log writer process (LGWR) is not allowed to reuse and hence overwrite an
online redo log group until it has been archived. The background process ARCn automates archiving operations when
automatic archiving is enabled. Oracle starts multiple archiver processes as needed to ensure that the archiving of filled
online redo logs does not fall behind.
 
  
You can use archived redo logs to:
 Recover a database
 Update a standby database
 Gain information about the history of a database using the LogMiner utility
OBJECTIVES OF THIS PROJECT
• Describe the differences between ARCHIVELOG and
NOARCHIVELOG modes
• Configure a database for ARCHIVELOG mode
• Enable automatic archiving
• Perform manual archiving of logs
• Configure multiple archive processes
• Configure multiple destinations, including remote
destinations