Processing of error problem of Rman restoring database Database

Last Update:2016-10-31 Source: Internet

Author: User

Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

Error 1, the database to open block change tracking, after the completion of the restoration of the file does not exist error.

rman> ALTER DATABASE open resetlogs;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE, STACK follows ===============

RMAN-00571: ===========================================================

Rman-03002:failure of Alter DB command at 10/25/2016 15:02:16

Ora-19751:could not create the change tracking file

Ora-19750:change tracking file: ' +data/cx/changetracking/ctf.348.875544631 '

Ora-17502:ksfdcre:4 Failed to create file +data/cx/changetracking/ctf.348.875544631

Ora-15046:asm file name ' +data/cx/changetracking/ctf.348.875544631 ' isn't in single-file creation form

Ora-17503:ksfdopn:2 Failed to open file +data/cx/changetracking/ctf.348.875544631

Ora-15012:asm file ' +data/cx/changetracking/ctf.348.875544631 ' does not exist

Rman>

Fault handling:

Turn off the Block-change-track function and only modify it in the open or Mount state. You should turn off the Block-change-track feature before you open the database at the end of the restore.

$ sqlplus/as SYSDBA

Sql*plus:release 11.2.0.4.0 Production on Tue Oct 25 15:15:43 2016

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0-64bit Production

With the partitioning, Real application Clusters, Automatic Storage Management, OLAP,

Data Mining and Real application testing options

Sql> select Status,filename from v$block_change_tracking;

Select Status,filename from V$block_change_tracking

ERROR at line 1:

Ora-19755:could not open change tracking file

Ora-19750:change Tracking File:

' +data/cx/changetracking/ctf.348.875544631 '

Ora-17503:ksfdopn:2 Failed to open file

+data/cx/changetracking/ctf.348.875544631

Ora-15012:asm file ' +data/cx/changetracking/ctf.348.875544631 ' does not

Exist

Sql> ALTER DATABASE disable block change tracking;

Database altered.

After the command executes, the statement that deletes the +data/cx/changetracking/ctf.348.875544631 file can be found in the warning log.

sql> ALTER DATABASE open;

Database altered.

Sql>

Error 2

rman> Restore Database;

Starting restore at 2016-10-19 10:23:51

Allocated Channel:ora_disk_1

Channel ora_disk_1:sid=1933 instance=zx1 Device Type=disk

Allocated Channel:ora_disk_2

Channel ora_disk_2:sid=2319 instance=zx1 Device Type=disk

Allocated Channel:ora_disk_3

Channel ora_disk_3:sid=2705 instance=zx1 Device Type=disk

Allocated Channel:ora_disk_4

Channel ora_disk_4:sid=3091 instance=zx1 Device Type=disk

Released Channel:ora_disk_1

Released Channel:ora_disk_2

Released Channel:ora_disk_3

Released Channel:ora_disk_4

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE, STACK follows ===============

RMAN-00571: ===========================================================

Rman-03002:failure of Restore command at 10/19/2016 10:23:52

Ora-19554:error allocating device, device Type:sbt_tape, device name:

ora-27211:failed to load Media Management Library

Additional Information:2

Rman>

Fault handling:

Rman> Show All;

RMAN configuration parameters for database with Db_unique_name ZX is:

CONFIGURE RETENTION POLICY to RECOVERY WINDOW of;

CONFIGURE BACKUP optimization OFF; # Default

CONFIGURE DEFAULT DEVICE TYPE to ' sbt_tape ';

CONFIGURE controlfile autobackup OFF; # Default

CONFIGURE controlfile autobackup FORMAT for DEVICE TYPE DISK to '%F '; # Default

CONFIGURE controlfile autobackup FORMAT for DEVICE TYPE sbt_tape to '%F '; # Default

CONFIGURE DEVICE type DISK PARALLELISM 4 BACKUP type to BACKUPSET;

CONFIGURE DEVICE type Sbt_tape PARALLELISM 1 BACKUP type to BACKUPSET; # Default

CONFIGURE datafile BACKUP COPIES for DEVICE TYPE DISK to 1; # Default

CONFIGURE datafile BACKUP COPIES for DEVICE TYPE sbt_tape to 1; # Default

CONFIGURE ARCHIVELOG BACKUP COPIES for DEVICE TYPE DISK to 1; # Default

CONFIGURE ARCHIVELOG BACKUP COPIES for DEVICE TYPE sbt_tape to 1; # Default

CONFIGURE maxsetsize to UNLIMITED; # Default

CONFIGURE encryption for DATABASE OFF; # Default

CONFIGURE encryption algorithm ' AES128 '; # Default

CONFIGURE COMPRESSION algorithm ' BASIC ' as of RELEASE ' DEFAULT ' OPTIMIZE for LOAD TRUE; # Default

CONFIGURE ARCHIVELOG deletion POLICY to NONE; # Default

CONFIGURE SNAPSHOT controlfile NAME to ' +data/snapcf_zx.f ';

Rman> show default device type;

RMAN configuration parameters for database with Db_unique_name ZX is:

CONFIGURE DEFAULT DEVICE TYPE to ' sbt_tape ';

Rman>

Rman> Configure channel device type ' Sbt_tape ' CLEAR;

Old RMAN configuration parameters is successfully deleted