Rman backup appears ORA-19625

Rman backup appears ORA-19625:

The reason is that the archive log is deleted in the operating system and has not been backed up yet. When rman backs up the log, the archive fails to be found. You can solve this problem by using the following methods:

RMAN> change archivelog all crosscheck;
----------------------------------
After you manually delete the archive file of the database, you need to use this command for synchronization.

(Archive logs are deleted physically, but the control file is not known. Therefore, cross-check is required to synchronize information)

Crosscheck archivelog all;

When you manually delete the backup level of RMAN, you need to use the following command:
Crosscheck backup;

The difference between them is that the synchronization content is different. One is to synchronize the status of the archive file, and the other is to synchronize the RMAN backup information.

-------------------------------------------
Repost another article as follows:

Crosscheck archivelog all

During RMAN backup (archiving log backup fails due to exceptions in archiving logs by backup software such as Veritas), the solution is also very unordered, it is to execute two RMAN commands:
1. Enter rman
2. connect target/
3. crosscheck archivelog all;
4. delete expired archivelog all;
======================================
What are the principles of these two commands. It is described below:
Each archivelog information is recorded in the controlfile. When we delete these physical files or perform abnormal changes under the OS, the archivelog information is still recorded in the controlfile, after we manually clear the files under the archive directory, these records are not cleared from the controlfile, that is, Oracle does not know that these files do not exist! In this case, we need to manually clear it.
Crosscheck archivelog all; checks the differences between the control file and the actual physical file.
Delete expired archivelog all; synchronize the information of the control file and the actual physical file.
If crosscheck is executed separately but delete is not executed, the backup still fails because the information of the control files is different from the actual information.
Crosscheck backupset

Crosscheck backupset is used to check the backup set and actual files.
1 backup set has two statuses: A (Available, which RMAN considers to exist on the backup media) X (Expired, which is stored in the control file or recovery directory,
Yes, it does not physically exist on the backup media)
2 crosscheck is used to check the RMAN directory and physical file. If the physical file does not exist on the media, it is marked as Expired. If the physical file
Yes, it will maintain Available. If the backup set marked as Expired is stored on the backup media again (for example, after the damaged disk drive is restored ),
Crosscheck marks the status again from Expired back to Available.
3 The crosscheck output is divided into two parts. The first part lists all backup set slices that are determined to exist on the backup media, and the second part lists the copies that do not exist on the backup media.
The backup set and mark it as Expired. After a backup storage policy is set, a backup expires, and the backup status marked as discarded after crosscheck is still
Availabel: delete the discarded backup delete obsolete