Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Dealing with the problem of Database error reporting when restoring Database by rman

2025-04-02 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

Error 1. Open block change tracking in the database, and open it after recovery because there is no error in the file.

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: changetracking 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' is not 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 can only be modified in open or mount status. When restoring, the block-change-track function should be turned off before opening the database after the restore.

$sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Tue Oct 25 15:15:43 2016

Copyright (c) 1982, 2013, Oracle. All rights reserved.

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 is executed, the statement to delete 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 are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS

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'% favored; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO'% favored; # 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'

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA/snapcf_zx.f'

RMAN > show default device type

RMAN configuration parameters for database with db_unique_name ZX are:

CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'

RMAN >

RMAN > configure channel device type 'SBT_TAPE' CLEAR

Old RMAN configuration parameters are successfully deleted

RMAN > show all

RMAN configuration parameters for database with db_unique_name ZX are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS

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'% favored; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO'% favored; # 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'

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA/snapcf_zx.f'

RMAN > CONFIGURE DEFAULT DEVICE TYPE TO 'disk'

Old RMAN configuration parameters:

CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'

New RMAN configuration parameters:

CONFIGURE DEFAULT DEVICE TYPE TO 'DISK'

New RMAN configuration parameters are successfully stored

RMAN > show all

RMAN configuration parameters for database with db_unique_name ZX are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO 'DISK'

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO'% favored; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK 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'

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA/snapcf_zx.f'

RMAN >

When finished, it is normal to log back in after exit.

Error 3: backup, encryption, restore, error

RMAN > restore controlfile from'/ dbbackup/CTL_ZX_8796_1_923736016.bak'

Starting restore at 2016-10-18 17:53:27

Using target database control file instead of recovery catalog

Allocated channel: ORA_DISK_1

Channel ORA_DISK_1: SID=1547 instance=jxkzx1 device type=DISK

Channel ORA_DISK_1: restoring control file

RMAN-00571: =

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-03002: failure of restore command at 10/18/2016 17:53:29

ORA-19870: error while restoring backup piece / dbbackup/CTL_ZX_8796_1_923736016.bak

ORA-19913: unable to decrypt backup

ORA-28365: wallet is not open

RMAN >

Fault handling:

RMAN > set dencryption on identified by '123456'

After setting the decryption password, start restoring the database.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report