The Oracle implements the backup of the database through transferring the RMAN, it plans to make a full backup of the data files and archive logs of the oracle database. Before starting the operation, the user has deleted the archive logs which have not the backup manually. Hence, we can’t make the backup successfully.
1. Connect to the RMAN.
Execute the command “rman target / nocatag”.
2. Synchronize the archive logs information recorded in the management file with the one in the hard disk. Tag the archive logs which have been deleted by the user manually as invalid, so that it will not be replicated.
Execute the command “RAMN>crosscheck archivelog all”.
3. Implement the backup again, the process has finished successfully. It just replicates the archive logs which haven’t the backup in the hard disk.
In the management file of the Oracle, it has recorded the archive logs which have produced and recorded whether the archive log has a backup. While the backup process is beginning, firstly, it will query which archive logs need to make backup in the oracle’s management file, then keeps on the backup process according to the feedback of the management file. However, while the process is implementing to the archive log which is deleted by the user, it can’t find the archive log in the hard disk, so it will consider this log has been damaged illegally. Then the backup process will be terminated, and produce the error prompt.
1. While writing the oracle backup script or configuring the oracle backup policy, make the function about deleting the archive log after it has finished making a backup.
2. Don’t delete the archive logs manually via the operating system command. If you want to delete the archive logs, you can use the RMAN command.