Q1. Describe three ways to backup an Oracle database

Respond to the following in 100 words or less. Be sure to cite your content. (Id: 1957781) Oct 4, 2015 6:44 PM
Within Oracle you can use the following for backup and recovery (Oracle, 2015):

1. Incremental backups – this method will store only blocks that have changed since the previous backup. This will allow backups to be more compact and will provide faster recovery.

2. Binary compression – this method is integrated with Oracle Database and will reduce the size of the backups

3. Automated database duplication – creates a copy of your database with various storage configurations, specifically direct duplication between ADM databases

Oracle (2015). Introduction to backup and recovery. Oracle Database Online Documentation 11g Release 2 (11.2). Retrieved from http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmintro.htm

Q2. Describe the advantages/disadvantages and what is happening between archivelog mode and no archivelog mode. How does it affect backup and recovery?

Q3. Describe the jobs mechanism in Oracle. How are they scheduled?

Q4. We’ve been using pluggable databases all course long….describe the benefits of using pluggable databases. Why would you not use a pluggable database?

Q5. Describe the jobs mechanism in Oracle. How are they scheduled?

Respond to the following in 100 words or less. Please cite your work.
2731638) Oct 4, 2015 2:00 PM
The choice of using ARCHIVELOG mode or not depends on system requirements. ARCHIVELOG mode allows for full backups and should be enabled for mission-critical data. If a database is in NOARCHIVELOG mode, then a backup can only be recovered to the point of the last full backup. Any additional changes made after this point are not logged, so they cannot be recovered. Also, in this mode, tablespace backups cannot be performed while the database is online. They must be performed while the database is closed (Choosing Between NOARCHIVELOG and ARCHIVELOG Mode, n.d.).

ARCHIVELOG mode essentially enables the use of redo logs to archive transactions. It offers three advantages:

A full database recovery can be performed with a combination of the last full database backup and the online redo log files.
You can use a backup taken while the database is open and in normal use.
You can keep a redundant, standby database current with its original counterpart by continuously applying the redo log produced by the original database to the standby.
The one major disadvantage of ARCHIVELOG mode is that it requires additional space in order to store the log information.

NOARCHIVE mode does have its advantages. Because there is no writing of transactions to a redo log, performance is increased.

To perform a “cold” backup in NOARCHIVELOG mode, the following steps are required:

Shut down the database
Create backup copies of all the data files, control files, and temporary database files
Restart the database
To perform a “hot” back with ARCHIVELOG mode, the following steps are required:

Alter the database/tablespace into backup mode
Copy the data files with an OS utility
Alter the database/tablespace out of backup mode
Archive the current online redo log
Backup the control file
Backup any archive redo log files generated during the backup
References

Choosing Between NOARCHIVELOG and ARCHIVELOG Mode. (n.d.). Retrieved from https://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo002.htm

Kuhn, D. (2013). Pro Oracle Database 12c Administration. Apress

Respond to the following in 100 words or less. Please cite your work. 2731638 Oct 5, 2015 6:00 AM
When it comes to automating jobs in Oracle, there are two general approaches: 1) scheduling jobs inside of Oracle using the Oracle Scheduler and 2) scheduling them at the OS level via crons. While many DBA prefer to use crons because they are easy to setup, the Oracle Scheduler provides quite a bit of additional flexibility including the ability to make jobs depend on the status of other jobs, creating jobs based on events, and running status reports using the data dictionary.
The following procedure demonstrates how to schedule a job using the Oracle Scheduler (Kuhn, 2013):

BEGIN

DBMS_SCHEDULER.CREATE_JOB(

job_name => ‘RMAN_BACKUP’,

job_type => ‘EXECUTABLE’,

job_action => ‘/orahome/oracle/bin/rmanback.bsh’,

repeat_interval => ‘FREQ=DAILY;BYHOUR=9;BYMINUTE=35′,

start_date => to_date(’17-01-2013′,’dd-mm-yyyy’),

job_class => ‘”DEFAULT_JOB_CLASS”‘,

auto_drop => FALSE,

comments => ‘RMAN backup job’,

enabled => TRUE);

END;

This procedure is called CREATE_JOB and its purpose is to schedule regular backups using the RMAN utility. The job_action parameter points the schedule to the script that needs to be run and the repeat_interval specifies the frequency to run the script. In this case, the script is ran daily at 9:35am and starts on January 17th, 2013. The syntax for the job is rather easy to understand upon observation.

A couple of other parameters that are less obvious to their meanings are job_class and auto_drop. The job_class allows you to assign multiple jobs to a single class that have aspects in common. All of the jobs in a job class might have the same logging requirements, for instance. The auto_drop parameter instructs Oracle to either drop the job after it’s done running (TRUE) or keep it (FALSE).

References

Kuhn, D. (2013). Pro Oracle Database 12c Administration. Apress