RMAN-06172 Troubleshooting, rman-06172

RMAN-06172 Troubleshooting, rman-06172

 

The error "RMAN-06172: no autobackup found or specified handle is not a valid copy or piece" was encountered during the RMAN restoration test today, as shown below:

 

RMAN> restore spfile to pfile "/u01/app/oracle/product/10.2.0/db_1/dbs/initSCM2.ora"

From "/u04/backup/backupsets/ora_cfc-4095319980-20180327-00 ";

 

Starting restore at 28-MAR-18

Using channel ORA_DISK_1

 

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

RMAN-00569: ==================== error message stack follows ==========================

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

RMAN-03002: failure of restore command at 03/28/2018 14:20:12

RMAN-06172: no autobackup found or specified handle is not a valid copy or piece

 

Of course, here is the restoration parameter file. In fact, this error will occur when restoring the control file or other data files. The official explanation for this error is:

 

Versions 11.1, 11.2, 12.1

 

 

Error:RMAN-06172 no AUTOBACKUP found or specified handle is not a valid copy or piece

---------------------------------------------------------------------------

 

Cause:A restore cocould not proceed because no AUTOBACKUP was found or

 

Specified handle is not a valid copy or backup piece. In case

 

Restore from AUTOBACKUP, it may be the case that a backup exists,

 

It does not satisfy the criteria specified in the user's restore

 

Operands. In case of restore from handle, it may be the handle is not

 

Backup piece or control file copy. In may be that it does not exist.

 

 

Action:Modify AUTOBACKUP search criteria or verify the handle.

 

 

Versions 9.2, 10.1, 10.2

 

Error:RMAN-06172 no autobackup found or specified handle is not a valid copy or piece

---------------------------------------------------------------------------

 

 

Cause:A restore cocould not proceed because no autobackup was found or

 

Specified handle is not a valid copy or backup piece. In case

 

Restore from autobackup, it may be the case that a backup exists,

 

It does not satisfy the criteria specified in the user's restore

 

Operands. In case of restore from handle, it may be the handle is not

 

Backup piece or controflile copy. In may be that it does not exist.

 

 

Action:Modify autobackup search criteria or verify the handle.

 

 

The cause of the RMAN-06172 error is as above, but the cause of this error is very many, I summarized it, probably from the following aspects to identify, analysis:

 

 

 

1: The backup set expires or the backup file does not exist.

 

 

RMAN> list backup of controlfile;

 

RMAN> list backup of spfile;

 

If the backup set file does not exist, this error is certainly returned. In addition, if backuppiece expires, the above command will display spfile or controlfile expiration (expired). In this case, you need to run a command similar to the following to solve the problem.

 

RMAN> crosscheck backup of controlfile;

 

The backup set has two states: A (Available, which RMAN considers to exist on the backup media); X (Expired, where the Backup exists in the control file or recovery directory, but it does not physically exist on the backup media)

The purpose of the crosscheck backup command is to check the RMAN directory and physical files. If the physical file does not exist on the media, it is marked as Expired. If a physical file exists, it will maintain Available.

If the original backup set marked as Expired exists on the backup media again (for example, after the damaged disk drive is restored), crosscheck backup marks the status again from Expired back to Available.

 

There is also a case where a RMAN-06172 error occurs when restoring from an automatic backup. This is because the backup set does not exist. You can also check and confirm through list backup of xxx.

 

RMAN> restore spfile from autobackup;

 

 

2: The rman channel is incorrectly configured.

 

See official documentation: Restore of controlfile autobackup using LiteSpeed (tape) fails with RMAN-06172 (Document ID 2021758.1)

 

Cause analysis:

 

LiteSpeed requires a tape channel to be allocated. A disk channel will not work even though when using LiteSpeed you can see the controlfile backup on disk. if a 'list backup of controlfile "shows the backup as on tape, a tape channel must be allocated.

LiteSpeed

 

A tape channel needs to be allocated. Even if LiteSpeed is used, the disk channel does not work. You can view the backup of the control file on the disk. If "list backup of Control Files" displays the backup as a tape, you must allocate a tape channel.

 

Solution:

 

Use a run block with a tape channel allocation:

Run {

Allocate channel dev device type 'sbt _ tape ';

Restore controlfile from '<full path/file name to controlfile backup> ';

Release channel dev;

}

 

 

3: Media Manager installation error

 

Refer to the official document Cannot restore controlfile from RMAN backup (Document ID 1054412.1)

 

Solution:

 

After reinstalling the Lite Speed Media Manager the controlfile was able to restore successfully.

Support for third party Media Management software that interacts with RMAN is provided by the 3rd party software vendo

 

 

4: File Permission issues

 

In this case, I used SFTP to copy the backup file under the root account. The owner of the file is the root user, and the RMAN command is run under the oracle user. Therefore, during restoration, due to permission issues, RMAN considers the file does not exist and reports a RMAN-06172 error.

 

The steps for determining and verifying this situation are as follows:

 

1: Find the corresponding backup file

 

List backup of xxx

 

2: Use ls-lrt to check File Permission attributes.

 

3: Modify the owner of the backup file

 

Chown oracle: oinstall *