Oracle 19c数据库备份与恢复权威指南

需积分: 9 41 浏览量更新于2024-07-15 收藏 4.58MB PDF 举报

Oracle Database Backup and Recovery Reference 19c 是一份详细的文档，它提供了Oracle数据库备份和恢复策略的专业指南。这份手册由Padmaja Potineni为主要作者，还有多位Oracle专家如K. Weill、L. Ashdown等人共同贡献，版权归属Oracle及其关联公司，日期为2019年1月。该文档涵盖了Oracle数据库19c版本，旨在帮助用户理解和执行高效、安全的数据备份与灾难恢复计划。本书包含了以下几个关键知识点： 1. **备份原理**：介绍了Oracle数据库备份的基础概念，包括全备（Full Backup）、增量备份（Incremental Backup）和差异备份（Differential Backup），以及冷备份（Cold Backup）和热备份（Hot Backup）的区别，以及它们各自的适用场景。 2. **备份策略**：探讨了如何制定适合组织需求的备份策略，包括备份频率、保留期限、备份集管理和备份窗口的选择。 3. **RMAN（Recovery Manager）**：作为Oracle数据库的主要备份工具，RMAN的使用方法、高级特性（如多段备份、并行备份等）和恢复流程被详细阐述，包括归档模式下的恢复策略。 4. **闪回技术**：包括闪回数据集、闪回事务、闪回查询等高级功能，这些在遇到问题时能快速恢复数据。 5. **备份优化**：提供了关于如何减少备份时间、存储空间占用以及提高备份性能的实用建议，例如利用备份压缩、自动备份管理等。 6. **恢复演练与验证**：指导用户如何进行定期的恢复演练，确保在实际故障时可以顺利恢复系统，并强调了验证恢复过程的重要性。 7. **灾备与高可用性**：讲解了如何设计灾难恢复计划（DRP），包括异地备份、远程复制（RMAN Channels）和实时应用重配置（Real Application Clusters，RAC）等方面的内容。 8. **法律法规和合规性**：提醒用户在备份和恢复过程中要遵守的数据保护法规，以及如何处理知识产权保护和许可协议的要求。 9. **错误处理与问题排查**：列举了常见备份恢复问题的解决方法，以及如何通过日志分析来定位和解决问题。 Oracle Database Backup and Recovery Reference 19c是任何Oracle数据库管理员或IT专业人士必备的参考资料，它深入浅出地解释了数据库备份和恢复的关键技术和实践，对于保障数据安全、提升业务连续性具有重要价值。

• SQL interface enhancements

You can now issue most SQL commands in RMAN without preceding the

command with the SQL keyword and enclosing the SQL command in quotes. This

greatly simplifies the syntax when the SQL command itself requires quotation

marks. For a few commands that exist in both RMAN and SQL, you can specify

the SQL keyword to eliminate ambiguity.

The SQL

ALTER

command replaces the RMAN command. The new RMAN

DESCRIBE

command provides the functionality of the SQL*Plus

DESCRIBE

command.

See:

– "DESCRIBE"

– "SQL"

• DUPLICATE enhancements

You can use the

NOOPEN

clause to specify that the duplicate database must not be

opened using

RESETLOGS

after it is created. You may prefer not to open the

duplicate database if you want to change the initialization parameters of the

duplicate database or if opening the duplicate database may start services in the

duplicate database that will conflict with the original database.

See "DUPLICATE".

Changes in This Release for Backup and Recovery Reference

xvi

In the syntax diagrams, keywords appear in rectangular boxes and an uppercase font,

like the word

CATALOG

in the example diagram. When used in text and code examples,

RMAN keywords appear in uppercase, monospace font, for example,

CATALOG

DATAFILECOPY

. You must use keywords in RMAN statements exactly as they appear in

the syntax diagram, except that they can be either uppercase or lowercase.

1.1.2 Placeholders in RMAN Syntax

Placeholders in syntax diagrams indicate non-keywords.

In the syntax diagrams, placeholders appear in ovals, as in the word integer in the

example diagram. When described in text, RMAN placeholders appear in lowercase

italic, for example,

'filename'

Placeholders are usually:

• Names of database objects (tablespace_name)

• Oracle data type names (date_string)

• Subclauses (datafileSpec)

When you see a placeholder in a syntax diagram, substitute an object or expression of

the appropriate type in the RMAN statement. For example, to write a

DUPLICATE

TARGET DATABASE TO

'database_name' command, use the name of the duplicate

database you want to create, such as

dupdb

, for the database_name placeholder in

the diagram.

The only system-independent, valid environment variables in RMAN quoted strings are

a question mark (

) for the Oracle home and an at-sign (

) for the SID. However, you

can use operating system-specific environment variables on the target system within

quoted strings. The environment variables are interpreted by the database server and

not the RMAN client.

The following table shows placeholders that appear in the syntax diagrams and

provides examples of the values you might substitute for them in your statements.

Placeholder Description Examples

Quoted strings such as

'filename'

'tablespace_name'

'channel_name'

'channel_parms'

A string of characters contained in

either single or double quotes. A quoted

string may contain white space,

punctuation, and RMAN and SQL

keywords.

"?/dbs/cf.f"

'dev1'

Nonquoted strings such

channel_id

tag_name

date_string

A sequence of characters containing no

white space and no punctuation

characters and starting with an

alphabetic character.

ch1

integer

Any sequence of only numeric

characters.

67843

1.1.3 Quotes in RMAN Syntax

RMAN syntax diagrams contain some placeholder values that are enclosed in required

or optional quotes.

Chapter 1

RMAN Syntax Diagrams

1-2

The syntax diagrams show single quotes, though in all cases double quotes are also

valid in RMAN syntax. For example, you may specify either

'filename'

"filename"

1.2 Format of RMAN Commands

The RMAN language is free-form. Keywords must be separated by at least one white

space character (such as a space, tab, or line break).

An RMAN command starts with a keyword corresponding to a command described in

RMAN Commands: @ (at sign) to QUIT, followed by arguments and ending with a

semicolon, as shown in the syntax diagrams.

The following example shows an RMAN backup command:

BACKUP DATABASE;

A command can span multiple lines. For example, you can rewrite each keyword in the

preceding command on a separate line as follows:

BACKUP

DATABASE

;

The maximum length for an RMAN command in a single line is 4000 characters. When

a command exceeds this length, you can either split the command into multiple

commands or use multiple lines for the command (use the Enter key to make the

command span multiple lines). For example, if a

BACKUP

command that backs up

multiple data files exceeds 4000 characters, then you can either split this command

into two separate

BACKUP

commands or make the single

BACKUP

command span

multiple lines.

You can insert a comment by using a pound (

) character at any point in a line. After

the

character, the remainder of the line is ignored. For example:

# run this command once each day

BACKUP INCREMENTAL LEVEL 1

FOR RECOVER OF COPY # using incrementally updated backups

WITH TAG "DAILY_BACKUP" # daily backup routine

DATABASE;

1.3 About RMAN Reserved Words

The RMAN language contains reserved words, which are or have been used in RMAN

commands. In general, avoid using reserved words in ways that conflict with their

primary meaning in the RMAN command language.

If you must use a reserved word as an argument to an RMAN command (for example,

as a file name, tablespace name, tag name, and so on), then surround it with single or

double quotes. Otherwise, RMAN cannot parse your command correctly and

generates an error. Example 1-1 shows correct and incorrect usage of RMAN

reserved words in RMAN commands.

Example 1-1 Using Reserved Words as Arguments to RMAN Commands

ALLOCATE CHANNEL backup DEVICE TYPE DISK; # incorrect

ALLOCATE CHANNEL "backup" DEVICE TYPE DISK; # correct

Chapter 1

Format of RMAN Commands

1-3

BACKUP DATABASE TAG full; # incorrect

BACKUP DATABASE TAG 'full'; # correct

See Also:

RMAN Reserved Words for a list of all the current reserved words

1.4 Summary of RMAN Commands

RMAN commands can be executed at the RMAN prompt, within a

RUN

command, or

both.

All commands from previous RMAN releases work with the current release, although

some commands and options are now deprecated (see Deprecated RMAN Syntax).

For command-line options for the RMAN client, refer to

RMAN

. Table 1-1 provides a

functional summary of the RMAN commands.

Table 1-1 Recovery Manager Commands

Command Purpose

@ (at sign)

Run a command file.

@@ (double at sign)

Run a command file in the same directory as another command file that is

currently running. The

command differs from the

command only when run

from within a command file.

ADVISE FAILURE

Display repair options.

ALLOCATE CHANNEL

Establish a channel, which is a connection between RMAN and a database

instance.

ALLOCATE CHANNEL FOR

MAINTENANCE

Allocate a channel in preparation for issuing maintenance commands such as

DELETE

BACKUP

Back up database files, copies of database files, archived logs, or backup sets.

CATALOG

Add information about file copies and user-managed backups to the repository.

CHANGE

Mark a backup piece, image copy, or archived redo log as having the status

UNAVAILABLE

AVAILABLE

; remove the repository record for a backup or

copy; override the retention policy for a backup or copy; update the recovery

catalog with the

DB_UNIQUE_NAME

for the target database.

CONFIGURE

Configure persistent RMAN settings. These settings apply to all RMAN sessions

until explicitly changed or disabled.

CONNECT

Establish a connection between RMAN and a target, auxiliary, or recovery

catalog database.

CONVERT

Convert data file formats for transporting tablespaces and databases across

platforms.

CREATE CATALOG

Create the schema for the recovery catalog.

CREATE SCRIPT

Create a stored script and store it in the recovery catalog.

CROSSCHECK

Determine whether files managed by RMAN, such as archived logs, data file

copies, and backup pieces, still exist on disk or tape.

Chapter 1

Summary of RMAN Commands

1-4

剩余535页未读，继续阅读

jesonqian

粉丝: 0
资源: 9

Oracle 19c数据库备份与恢复权威指南

MySQL表结构导出工具：database-export-3.2.0-SNAPSHOT.jar

Python库mongodb-backup工具发布0.1.1版本

Kenshin-backup: 构建可扩展时间序列数据库解决方案

Oracle Database Backup and Recovery Reference,11g Release 2(11.2).PDF

Oracle RMAN 11g Backup and Recovery

Oracle_DBA_Automation_Quick_Reference.rar

OracleDatabaseBackupAndRecoveryReference.pdf 英文原版

Oracle Certified Professional 063 - Multitenant .docx

Oracle官方文档阅读方法.pdf

Ubuntu The Complete Reference

最新资源