Hello Tim,

I found "using target database control file instead of recovery catalog" and I 
do not know about RMAN behavior in this case. I am using Recovery Catalog 
Database instead of control file:



Recovery Manager: Release 10.2.0.4.0 - Production on Tue Feb 9 08:31:58 2010



Copyright (c) 1982, 2007, Oracle.  All rights reserved.



connected to target database: IFNSDB (DBID=1091737065)

connected to recovery catalog database



RMAN> show all;



RMAN configuration parameters are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 31 DAYS;

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO 
'/home/oracle/product/10g/dbs/snapcf_ifns.f'; # default



This is my script to cross check backups ($RC_USER, $RC_PASSWORD and 
$RC_SERVICE for Recovery Catalog Database, $1 is database SID):



rman <<EOF

#

# Connect to Recovery Catalog database

connect catalog $RC_USER/$RC_PASSWORD@$RC_SERVICE;

#

# Connect to target database

connect target;

#

# Allocate channel for maintenance

allocate channel for maintenance type 'sbt_tape' parms

        'ENV=(TDPO_OPTFILE=/home/oracle/admin/tdpo/$1.opt)';

#

# Set date and time format

sql 'alter session set NLS_DATE_FORMAT = "YYYY-MM-DD:HH24:MI:SS"';

#

# Resynchronize catalog

resync catalog;

#

# List database incarnations

list incarnation;

#

# List backups

list backup summary;

#

# Crosscheck backups

crosscheck backup;

#

# List expired backups

list expired backup summary;

#

# Delete expired backups

delete noprompt expired backup;

#

# Delete obsolete backups

delete noprompt obsolete;

#

# Release channel

release channel;

#

# Allocate channel for maintenance

allocate channel for maintenance type disk;

#

# Check archived logs on disk

crosscheck archivelog all;

#

# Remove obsolete archived redo logs

delete noprompt expired archivelog all;

#

# Release channel

release channel;

#

exit

EOF





Grigori G. Solonovitch



Senior Technical Architect



Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com



Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com



Please consider the environment before printing this Email





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tim Brown
Sent: Monday, February 08, 2010 10:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] tsm and rman



Results of rman show all;



RMAN> show all;



RMAN configuration parameters are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO 
C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFCHPROD1.ORA'; # default

RMAN>





Results of list backup device type 'SBT_TAPE';  NO FILES PRIOR TO 23-JAN-2010



Recovery Manager: Release 10.2.0.4.0 - Production on Sat Feb 6 06:48:11 2010



Copyright (c) 1982, 2007, Oracle.  All rights reserved.



connected to target database: CHPROD (DBID=275426368)



RMAN> list backup device type 'SBT_TAPE';

2>

using target database control file instead of recovery catalog



List of Backup Sets

===================



BS Key  Size       Device Type Elapsed Time Completion Time

------- ---------- ----------- ------------ ---------------

34568   219.00M    SBT_TAPE    00:02:10     26-JAN-10

        BP Key: 34568   Status: AVAILABLE  Compressed: NO  Tag: 
TAG20100125T211212

        Handle: df_709257735_34717_1   Media:



  List of Archived Logs in backup set 34568

  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time

  ---- ------- ---------- --------- ---------- ---------

  1    71905   12860770047 24-JAN-10 12860773882 24-JAN-10

  1    71906   12860773882 24-JAN-10 12860778290 24-JAN-10

  1    71907   12860778290 24-JAN-10 12860781963 24-JAN-10

  1    71908   12860781963 24-JAN-10 12860787188 24-JAN-10

  1    71909   12860787188 24-JAN-10 12860789947 24-JAN-10



BS Key  Size       Device Type Elapsed Time Completion Time

------- ---------- ----------- ------------ ---------------

34569   218.75M    SBT_TAPE    00:02:10     26-JAN-10

        BP Key: 34569   Status: AVAILABLE  Compressed: NO  Tag: 
TAG20100125T211212

        Handle: df_709257872_34718_1   Media:



  List of Archived Logs in backup set 34569

  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time

  ---- ------- ---------- --------- ---------- ---------

  1    71770   12858008336 23-JAN-10 12858011683 23-JAN-10





Tim



-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of

Grigori Solonovitch

Sent: Monday, February 08, 2010 2:27 PM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: Re: tsm and rman





We have recovery window 31 days. We are running full backups for databases 
every 2 weeks and incremental backus all other days.

In this case RMAN command

list backup summary;

shows backups for last 31 - 45 days. Number of days depends on current date and 
weekly backup schedule.

So you definately have problem.

Are you sure recovery window is set for your database? Each database has to be 
configured separately, because recovery window is not a global parameter.





________________________________________

From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Tim 
Brown [tbrown AT CENHUD DOT COM]

Sent: Monday, February 08, 2010 7:09 PM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: [ADSM-L] tsm and rman



We have our RMAN policy set to:



CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;



After each daily backup the RMAN list backup only

shows backups for the past 15 days.



Shouldnt it show last 28 days ?



Tim Brown

Systems Specialist - Project Leader

Central Hudson Gas & Electric

284 South Ave

Poughkeepsie, NY 12601

Email: tbrown AT cenhud DOT com <mailto:tbrown AT cenhud DOT com>

Phone: 845-486-5643

Fax: 845-486-5921

Cell: 845-235-4255





This message contains confidential information and is only for the intended 
recipient.  If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.  Thank you.



Please consider the environment before printing this Email.



"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."