Skip to main content

Oracle PBS RMAN Stuck and Backup Fails Due to Extended Crosscheck Duration

Oracle PBS RMAN Stuck and Backup Fails Due to Extended Crosscheck Duration

Updated this week

Problem description

  • RMAN backup jobs were failing when executed with a script that included a crosscheck command spanning 14 days. The extended crosscheck duration caused the backup job to exceed the allocated window or system thresholds, resulting in failure.

  • This issue was observed in environments where a longer retention period for backup metadata caused performance degradation during crosscheck operations.

Cause

The crosscheck operation in RMAN was configured to run for the past 14 days. When the duration is too long, especially in environments with a high number of backup files or logs, it can significantly increase execution time, leading to timeout or resource exhaustion during RMAN job execution.

Traceback

rman_backup_windows.rman

crosscheck backup completed between 'sysdate-14' and 'sysdate';

Resolution

Reduce the number of days for which RMAN performs the crosscheck operation.

Steps to follow:

  1. Edit the RMAN backup script.

  2. Locate the crosscheck command, which may look like:
    ​crosscheck backup completed between 'sysdate-14' and 'sysdate';

  3. Modify it to reduce the duration. For example, to only crosscheck backups from the last 1 day:

    crosscheck backup completed between 'sysdate-1' and 'sysdate';

  4. Save the script and rerun the RMAN backup job.

  5. After making this change, the backup jobs should be successful

See also

Did this answer your question?