Skip to main content
Solved

How to Keep Oracle Archive Logs for 24 Hours Without “delete input” in RMAN Script?

  • December 15, 2025
  • 4 replies
  • 73 views

Forum|alt.badge.img+1

I have an Oracle 12.1 environment and need to keep the archive logs for 24 hours. I tried multiple configurations:

  • Subclients (Default and ArchiveLog): Tested with “Archive Delete” enabled and disabled.
  • Schedule: Tried “Delete Archive Log” with:
    • Older than 1 day and Backed up 2 times.
    • Also tested with these options disabled.

Results: The only change occurred when using Older than 1 day and Backed up 2 times, which added the following line:

delete noprompt archivelog until time = 'sysdate-1' backed up 2 times to sbt;

However, the line:

(archivelog all delete input);

remains in the script, and I don’t know how to remove it.

I will try a custom script, but I prefer a Commvault solution. During my research, I found a possible approach using three subclients:

  • Default: Full backup + archive logs without deleting.
  • Archivelogs: Hourly backups of archive logs without deleting.
  • DeleteArchive: Daily deletion of archive logs.

For now, this option is not possible because even with every delete flag disabled, the delete input line remains in the script.

Best answer by J Victor

So my problem was solved.

 

I want to add that the archivelog schedule did not have the “Custom RMAN Script” tab, only the full database schedule had this tab. And when we ran manually was good.

 

As workaround we made a custom rman script on server and schedule on crontab, then deleted the archivelog schedule on Commvault.

 

During support assistance we did create another schedule and IT WORKED! Even the “Custom RMAN Script” showed up.

 

SOLUTION: Delete and create a new schedule.

The first schedule was created with command center, the second schedule was created with comcell console.

4 replies

CV_GK
Vaulter
Forum|alt.badge.img+7
  • Vaulter
  • December 16, 2025

Hi ​@J Victor 

What is the CV version on CS and Client?


Forum|alt.badge.img+1
  • Author
  • Novice
  • December 16, 2025

Hi ​@CV_GK,thank you for the response.

The version on CS and Client is 11.40.22.

CS - Windows Server 2025

Client - Oracle Linux 7.9 with Oracle 12.1


Forum|alt.badge.img+1
  • Author
  • Novice
  • Answer
  • December 18, 2025

So my problem was solved.

 

I want to add that the archivelog schedule did not have the “Custom RMAN Script” tab, only the full database schedule had this tab. And when we ran manually was good.

 

As workaround we made a custom rman script on server and schedule on crontab, then deleted the archivelog schedule on Commvault.

 

During support assistance we did create another schedule and IT WORKED! Even the “Custom RMAN Script” showed up.

 

SOLUTION: Delete and create a new schedule.

The first schedule was created with command center, the second schedule was created with comcell console.


dude
Community All Star
Forum|alt.badge.img+18
  • Community All Star
  • December 19, 2025

@J Victor would you mind sharing the reason or the "thing” that only made this new schedule to work in the JAVA GUI and not in the Command Center?