OCP-1Z0-053-200题-22题-603

最新推荐文章于 2019-08-30 09:06:46 发布

原创最新推荐文章于 2019-08-30 09:06:46 发布 · 3.8k 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

OCP-1Z0-053 专栏收录该内容

796 篇文章

订阅专栏

本文介绍了一种使用Oracle Data Pump工具（expdp和impdp）来迁移恢复目录的方法。通过导出和导入操作，可以在不同数据库间移动恢复目录，并保持目标数据库元数据的一致性。

QUESTION 22

While performing a regular check on your recovery catalog you realized that the catalog database is running

out of space and you do not have options to increase the space.

However, you have another database where more spaceis available and you want to move your existing

recovery catalog to this database.

The options that can be considered while moving the recovery catalog are as follows:

1. Using one of the Oracle expdp utilities to export the catalog data

2. Creating a recovery catalog user and granting the necessary privileges in the other database

3. Creating the recovery catalog using the CREATE CATALOG command

4. Using the corresponding impdp utility to import the catalog data into the other database

5. Registering the target database in the new catalog database using the REGISTER DATABASE command

Identify the option with the correct sequence for moving the recovery catalog.

A. 2, 3, 5

B. 1, 2, 4

C. 1, 2, 4, 5

D. 1, 2, 3, 4, 5

Answer: B

同603题：http://blog.csdn.net/rlhua/article/details/13260893

Explanation/Reference:

Section: Backup, Recovery & Recovery Manager (RMAN)

As you can with any database, you can use the OracleData Pump export and import utilities expdp and impdp

to create logical backups of the recovery catalog. You can use this logical backup to move the recovery

catalog to another database. Follow these general steps to move a recovery catalog to another database:

1. Use an export utility to copy the recovery catalog schema to an export dump file.

2. Create the recovery catalog owner on thetarget catalog database with the appropriate permissions; see reate the Recovery Catalog Owner?earlier in this chapter.

3. Use the corresponding import utility to copy the recovery catalog schema to the target catalog database.

The next time you launch RMAN, you connect to the same target database but a different recovery catalog database. However, even though the recovery catalogdatabase name is different, the target database's metadata is identical to the metadata in the previous recovery catalog.

You can also use transportable tablespaces to move arecovery catalog schema from one database to another.

You do not need to run an RMAN CREATE CATALOG command in this scenario; the tables, columns, and views are already in place from the source database.