Thanks in advance for your input -
I have oracle rman clients performing backups and cleanup scripts.
Several times after changes on the oracle side the rman cleanup scripts are not working, but dbas are unaware of this.
It's bad berries for me because I run out of tapes and tape slots while trying to identify the problem.
All of my oracle rman client nodenames start with "ORACLE_" prefix. rman cleanup scripts delete anything older than 2 weeks. I think it would be safe to identify oracle rman client data older than 30 days.
I need a script to identify any oracle rman data older than 30 days.
the following is a rough guess at the select statement, but I want only the date not date/time and only data older than 30 days.
select NODE_NAME,FILESPACE_NAME,HL_NAME,LL_NAME,BACKUP_DA TE,DEACTIVATE_DATE from backups where node_name like 'ORACLE%%' and backup_date<(current_timestamp-30 days) order by node_name,filespace_name.backup_date
I have oracle rman clients performing backups and cleanup scripts.
Several times after changes on the oracle side the rman cleanup scripts are not working, but dbas are unaware of this.
It's bad berries for me because I run out of tapes and tape slots while trying to identify the problem.
All of my oracle rman client nodenames start with "ORACLE_" prefix. rman cleanup scripts delete anything older than 2 weeks. I think it would be safe to identify oracle rman client data older than 30 days.
I need a script to identify any oracle rman data older than 30 days.
the following is a rough guess at the select statement, but I want only the date not date/time and only data older than 30 days.
select NODE_NAME,FILESPACE_NAME,HL_NAME,LL_NAME,BACKUP_DA TE,DEACTIVATE_DATE from backups where node_name like 'ORACLE%%' and backup_date<(current_timestamp-30 days) order by node_name,filespace_name.backup_date