No question at this time
DBA Top 10
1 B. Vroman 15100
2 M. Cadot 14200
3 A. Kavsek 9300
4 J. Schnackenberg 6100
5 T. Boles 5500
6 M. Hidayathullah ... 5400
7 P. Wisse 2500
8 T. P 900
9 R. Wauben 500
9 H. Steijntjes 500
About
DBA-Village
Download PLATO
The free tool for auditing and tuning your database
Version 55 now available
Sep 02, 2016
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48178
Total active users1670
Act. users last 24h2
Act. users last hour0
Registered user hits last week257
Registered user hits last month1287
Go up

RMAN and expired backup sets
Next thread: Columns Getting Deleted from a table "XXQF_OBJECTIVE_HISTORY"
Prev thread: SPM 12c

Message Score Author Date
I'm moving an 8tb database and 3 other smaller dat...... Kirt Thomas Apr 05, 2018, 15:27
Put all your backup files in a directory. Execu...... Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts Michel Cadot Apr 05, 2018, 19:34
I don't think I can put all the backup files on di...... Kirt Thomas Apr 05, 2018, 20:14
You can recatalog all backup files using "catalo...... Michel Cadot Apr 05, 2018, 20:21
Ok, so from my 'list backup summary' - this snippe...... Kirt Thomas Apr 05, 2018, 20:25
Do not connect to the catalog, just to the auxil...... Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts Michel Cadot Apr 05, 2018, 20:30
I still get this... RMAN-00571: ===============...... Kirt Thomas Apr 05, 2018, 21:29
You didn't do what I said. ... Michel Cadot Apr 05, 2018, 21:32
I connect to the target and aux; then ran the scri...... Kirt Thomas Apr 05, 2018, 21:33
Show the COMPLETE session. ... Michel Cadot Apr 05, 2018, 21:34
Good Morning. First of all: You are talking abo...... Score: 600 PtsScore: 600 PtsScore: 600 PtsScore: 600 PtsScore: 600 Pts Jan Schnackenberg Apr 06, 2018, 09:17
Jan that is it exactly. It makes perfect sense. ...... Kirt Thomas Apr 06, 2018, 17:20
There was no crosscheck done, but I assume a 'list...... Kirt Thomas Apr 06, 2018, 20:43
Sure thing... /u01/app/oracle/admin/tlog_ip (tl...... Kirt Thomas Apr 06, 2018, 20:49
Total System Global Area 3223535616 bytes Fi...... Kirt Thomas Apr 06, 2018, 20:49
So do you backup your controlfile as part of the p...... Tim Boles Apr 09, 2018, 16:17
Yes, Tim, the control files are backuped up. I ...... Kirt Thomas Apr 09, 2018, 16:25
This is an interesting problem. Personally I w...... Tim Boles Apr 09, 2018, 17:12
If I don't use a reco catatalog, then I need a con...... Kirt Thomas Apr 09, 2018, 17:19
On our EBS systems after the RMAN backup we backup...... Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts Tim Boles Apr 09, 2018, 17:42
Sorry...I forgot from your original posting you ca...... Tim Boles Apr 09, 2018, 17:55
Jan, I have an idea of what's going on and would a...... Kirt Thomas Apr 09, 2018, 18:00
Hi Kirt, sorry for the delay. I see you did qui...... Score: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 Pts Jan Schnackenberg Apr 10, 2018, 09:22
Jan, thanks - it's always nice when someone smarte...... Kirt Thomas Apr 10, 2018, 15:55

Follow up by mail Click here


Subject: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 05, 2018, 15:27, 13 days ago
Os info: AIX 6
Oracle info: 11.2.0.3
Message: I'm moving an 8tb database and 3 other smaller databases (<1tb) to another location about 1500 miles away (keeping the original). For reasons, I'm not able to do a simple restore, or standby. What I am planning on doing (and testing) is using rman's duplicate db. I use this locally a lot to create tst and dev instances.

The way this is working, I take a cold backup of the RMAN database, and do an offsite DR style backup of the others and then ship the tapes. At the other location I bring up the the 'backup' RMAN db and use that as my recovery catalog.

I have a retention policy recovery window of 7 days. The first test I did was within that window on a smaller db, and went fine. However it was about 3 weeks before I could try another database, and it failed with

"RMAN-06024: no backup or copy of the control file found to restore"

Which I narrowed down to having expired backupsets. It seems like RMAN reads the target databases control files and expires backups that don't fit that retention policy (along with updating the catalog with any recent backups). I figured I could solve this easy enough by:

change backupset 18612567 available;

That returns an error:

RMAN-06481: WARNING: backup piece 'c-3792119878-20180220-00' cannot be found on the storage medium changed backup piece expired

I restored the 'backup' RMAN catalog database, and didn't let it resync, and the same backupset that the RMAN-06481 refers to was able to be restored. But as soon as I ran a "List backup summary" resync occurred and all the older backups were marked expired.

Does anyone know how I can 'unexpire' the older sets, or prevent RMAN from resyncing its information with the control files on the target db? Or have other interesting solutions.

*My new 'plan' is to set retention to 30 days, and make and send new tapes, and complete within the 30 day window - however my concern over this is 1) It will take a week to get everything made and shipped and receieved and the tapes put back in the TSM library and 2) what will this do to the size of my control files, and how will that affect performance.

Thanks :)
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Michel Cadot, France
Date: Apr 05, 2018, 19:34, 13 days ago
Score:   Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts
Message:
Put all your backup files in a directory.
Execute the following in RMAN:
connect target /

connect auxiliary sys/<psw>@<sourcedb>
startup nomount pfile='${ORACLE_HOME}/dbs/init<targetinst>.ora'
configure default device type to disk;
configure device type disk parallelism <X>;
catalog start with <directory of the backup files>;
catalog backup piece <last control file autobackup>;
duplicate target database to '<targetdb>'
db_file_name_convert (<name conversion rules>)
nofilenamecheck
until time "to_date('<time>','yyyymmddhh24miss')"
pfile='${ORACLE_HOME}/dbs/init<targetinst>.ora'
logfile
group 97 ('<log file>') size 50m,
group 98 ('<log file>') size 50m,
group 99 ('<log file>') size 50m
;
}


After that create new redo log groups with appropriate size and destroy the above ones.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 05, 2018, 20:14, 13 days ago
Message: I don't think I can put all the backup files on disk, they are all on tape in TSM, as parts of the hot backup. Not to mention coming up with enough spare space.

Is this essentially creating a new catalog? Right now I start with a connection on the auxilliary db server to rman..

rman target sys/<syspass>@<targetsid> catalog reco/<reco>@<catalog db> auxilliary sys/<syspwd>

Then run my recovery script:

sql "alter session set optimizer_mode=RULE";
allocate auxiliary channel aux1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux3 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux4 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux5 type disk;
allocate auxiliary channel aux6 type disk;
duplicate target database to aytst1
until time "to_date('2018-02-21:23:00:00', 'yyyy-mm-dd:hh24:mi:ss')";

This works, except for on expired backupsets.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Michel Cadot, France
Date: Apr 05, 2018, 20:21, 13 days ago
Message:
You can recatalog all backup files using "catalog backuppiece".

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 05, 2018, 20:25, 13 days ago
Message: Ok, so from my 'list backup summary' - this snippet;

18619584 B A A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619585 B A A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619600 B 0 A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619601 B 0 A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619602 B 0 A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619603 B 0 A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619604 B 0 A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619605 B 0 A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619702 B A A SBT_TAPE 22-FEB-18 1 1 NO LEVEL0_AYPRD1
18619727 B F X SBT_TAPE 22-FEB-18 1 1 NO TAG20180222T025722

I can do a:

recatalog backuppiece on each member of the set? Allowing me to then make them available? Will this also update the control files on the target db, or only effect the catalog? Thanks.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Michel Cadot, France
Date: Apr 05, 2018, 20:30, 13 days ago
Score:   Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts
Message:
Do not connect to the catalog, just to the auxiliary and the target.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 05, 2018, 21:29, 13 days ago
Message: I still get this...

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/05/2018 14:04:14
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore

With the recovery window set to 7 days, on reflection, the control file doesn't even know. The catalog knows, and Tivoli knows, but is choking on the expired backup set. If I could prevent the automatic resync with the control files then the backup set isn't expired. I tested this by restoring the rman db, then running a 'list backup summary', but immediately hitting control-c, I got a message saying resync was interrupted. Then I ran the duplicate db script, and it restored the db. So it seems to all come down to the expiration of the backupset.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Michel Cadot, France
Date: Apr 05, 2018, 21:32, 13 days ago
Message:
You didn't do what I said.

Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 05, 2018, 21:33, 13 days ago
Message: I connect to the target and aux; then ran the script. What did I miss?
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Michel Cadot, France
Date: Apr 05, 2018, 21:34, 13 days ago
Message:
Show the COMPLETE session.

Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Jan Schnackenberg, Germany
Date: Apr 06, 2018, 09:17, 13 days ago
Score:   Score: 600 PtsScore: 600 PtsScore: 600 PtsScore: 600 PtsScore: 600 Pts
Message: Good Morning.

First of all: You are talking about EXPIRED backups.

RMAN marks a backuppiece as EXPIRED because it cannot find (or access) the file.

As far as I understand your setup, you took the original of the tapes from your source datacenter to the destination and loaded them into the TSM instance there. I guess you also had TSM scan and inventorize the tapes.

Also you made a backup of your RMAN catalog database and restored it in the destination datacenter. Also my guess is, that you did this BEFORE telling the source database that the backup tapes are not accessible any more.

Backups on tape are a little special
1. There is no "documented" way to catalog backup pieces on tape (it's possible and works, but it's slow)
2. TSM does not really know anything about the contents of the tapes, except for the "filenames".

If the backuppieces are listed as EXPIRED, someone did a crosscheck with an active TSM channel but without the needed tapes in place. Or, if the tapes were in place, TSM didn't have the inventory of all the tapes present.

To see which "filenames" TSM knows that are unknown to RMAN use tdposync. Use it to connect to your RMAN catalog database (the one in the destination datacenter) and give the OPT-file used for RMAN to access TSM as parameter. It will list all files known to TSM but unknown to RMAN.

To remove the EXPIRED mark from those backupsets that are actually still present you can do another CROSSCHECK while having an active channel to TSM. This will once again check the availability of all backup pieces.

Now, if RMAN tells you RMAN-06481, then the backuppiece is not available. It's as easy as that. You need to figure out if this is a backuppiece that [b]should[/b] be on the tapes and if so why it isn't visible to RMAN.


Regarding your new plan: Backuppieces not needed to fulfill the RETENTION perion are OBSOLETE not EXPIRED. This is something completely different. And even if a backuppiece is OBSOLETE, it will only be deleted if you execute DELETE OBSOLETE. While still present it can be used for restores without any problems.

Regards,
Jan
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 06, 2018, 17:20, 12 days ago
Message: Jan that is it exactly. It makes perfect sense. I'm stuck in a production issue right now, but talking with the AIX admin we both feel like you hit the nail on the head. Thanks.

On a side note; if I did change the window, that would increase the control file size; does that have anything but a negligible effect on performance?
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 06, 2018, 20:43, 12 days ago
Message: There was no crosscheck done, but I assume a 'list backup summary' can effect things the same way?

I was able to restore one of the databases (that I had not so far connected to as a target) by immediately running the duplicate db script. I blew that db away and tried again and it failed on the control file error. Running a crosscheck has marked all the older backupsets expired.

Restoring the catatlog, and immediately running the duplicate again lets me restore the db, so I know the files are on tape in TSM.

Is this because, in the 'home' location, backups continue to run and once the catalog is synced, file locations on the tape are changed? Which can be fixed with tdposync?

I need to figure out what is making the files on tape (that I know are present) invisible to RMAN.

Also - regarding crosscheck an syncing. I show backups in the remote catalog that are occurring locally - my assumption was the sync was reading the target control files and updating the catalog.

There is no network path that would allow the two environments to see either catalogs, tsm, or tape libraries - connection to the target only works by using the ip address in tnsnames.

When I ran a crosscheck backup on the remote catalog, it shows me this...

RMAN> crosscheck backup;
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=7 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 7.1.3.0
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: SID=201 device type=SBT_TAPE
channel ORA_SBT_TAPE_2: Data Protection for Oracle: version 7.1.3.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=404 device type=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=PLOGIP_v9suugk4_1.level0.28Mar2018 RECID=19415 STAMP=971981444
crosschecked backup piece: found to be 'AVAILABLE'

Marking backup pieces 'available' even though those files are not in the remote's TSM library? Shouldn't they not be found and marked expired? Or am I confused (likely). Thanks.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 06, 2018, 20:49, 12 days ago
Message: Sure thing...

/u01/app/oracle/admin/tlog_ip (tlog_ip) >rman target sys/<pass>@plogip auxiliary sys/<pass>
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Apr 6 13:46:29 2018
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PLOGIP (DBID=3259399862)
connected to auxiliary database: TLOG_IP (not mounted)
RMAN> run {sql "alter session set optimizer_mode=RULE";
2> allocate auxiliary channel aux1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
3> allocate auxiliary channel aux2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
4> allocate auxiliary channel aux3 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
5> allocate auxiliary channel aux4 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
6> allocate auxiliary channel aux5 type disk;
7> allocate auxiliary channel aux6 type disk;
8> duplicate target database to tlog_ip
9> until time "to_date('2018-02-20:23:00:00', 'yyyy-mm-dd:hh24:mi:ss')";}

using target database control file instead of recovery catalog
sql statement: alter session set optimizer_mode=RULE
allocated channel: aux1
channel aux1: SID=488 device type=SBT_TAPE
channel aux1: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux2
channel aux2: SID=585 device type=SBT_TAPE
channel aux2: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux3
channel aux3: SID=683 device type=SBT_TAPE
channel aux3: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux4
channel aux4: SID=3 device type=SBT_TAPE
channel aux4: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux5
channel aux5: SID=99 device type=DISK
allocated channel: aux6
channel aux6: SID=197 device type=DISK

Starting Duplicate Db at 06-APR-18
contents of Memory Script:
{
set until scn 7444748129350;
sql clone "alter system set db_name =
''PLOGIP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
sql clone "alter system set db_unique_name =
''TLOG_IP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile;
alter clone database mount;
}
executing Memory Script
executing command: SET until clause
sql statement: alter system set db_name = ''PLOGIP'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''TLOG_IP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 06, 2018, 20:49, 12 days ago
Message:
Total System Global Area 3223535616 bytes
Fixed Size 2223944 bytes
Variable Size 1560281272 bytes
Database Buffers 1644167168 bytes
Redo Buffers 16863232 bytes
allocated channel: aux1
channel aux1: SID=488 device type=SBT_TAPE
channel aux1: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux2
channel aux2: SID=585 device type=SBT_TAPE
channel aux2: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux3
channel aux3: SID=682 device type=SBT_TAPE
channel aux3: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux4
channel aux4: SID=3 device type=SBT_TAPE
channel aux4: Data Protection for Oracle: version 7.1.3.0
allocated channel: aux5
channel aux5: SID=99 device type=DISK
allocated channel: aux6
channel aux6: SID=197 device type=DISK
Starting restore at 06-APR-18
Oracle instance started
Total System Global Area 3223535616 bytes
Fixed Size 2223944 bytes
Variable Size 1560281272 bytes
Database Buffers 1644167168 bytes
Redo Buffers 16863232 bytes
contents of Memory Script:
{
sql clone "alter system set db_name =
''TLOG_IP'' comment=
''Reset to original value by RMAN'' scope=spfile";
sql clone "alter system reset db_unique_name scope=spfile";
shutdown clone immediate;
}
executing Memory Script
sql statement: alter system set db_name = ''TLOG_IP'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/06/2018 13:47:30
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN>
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Tim Boles, United States
Date: Apr 09, 2018, 16:17, 9 days ago
Message: So do you backup your controlfile as part of the process? It seems that it can not find a copy of it.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 09, 2018, 16:25, 9 days ago
Message: Yes, Tim, the control files are backuped up.

I have 4 databases on the tapes, I successfully did a point in time on one, via catatalog by only connecting (rman target sys/sys@target catalog reco/pass@rman auxiliary sys/syspass@aux) Then immediately running the duplicate script:

sql "alter session set optimizer_mode=RULE";
allocate auxiliary channel aux1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux3 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux4 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate auxiliary channel aux5 type disk;
allocate auxiliary channel aux6 type disk;
duplicate target database to tlog_ip
until time "to_date('2018-02-21:23:00:00', 'yyyy-mm-dd:hh24:mi:ss')";

This was successful. If I issue any command (ie list backup summary) - it updates the 'new' rman database, and the saem restore fails on the finding the control file.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Tim Boles, United States
Date: Apr 09, 2018, 17:12, 9 days ago
Message: This is an interesting problem.

Personally I would attempt the following:

1) Do not use a recovery catalog. I have always found problems when trying to use a recovery catalog when I am attempting to do multiple restores/duplicates of the same database.

2) Do not connect to the TARGET database if possible.

I would attempt my restores using the processes described on My Oracle Support for difference scenarios that make sense in my case. Not using the catalog or TARGET should help in avoiding issues with backup pieces being maked as unavailable.

Perform Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups (Doc ID 1375864.1)

RMAN 11GR2 : DUPLICATE Without Target And Recovery Catalog Connection (Doc ID 874352.1)

As long as you tell it where your backups are then it should have no problem in duplicating your database without connecting to the TARGET or CATALOG. I have done this often with Disk backups but never with Tape backups.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 09, 2018, 17:19, 9 days ago
Message: If I don't use a reco catatalog, then I need a control file a that also knows where the backup pieces are. I can do a restore, that's not a problem, I want to do a duplicate because with EBS that will be easier in the long run.

I read the note on duping without a target, and I don't think I can do that, one of the databases is 8tb, and I'm not sure how I'd pull only what's needed off tape since it's cryptically keyed.

I think Jan has the right idea, and pointing out that 'expired' means rman can't see them. Now since I know the backup pieces are on tape, I need to figure out why rman can't see them (after the forced sync) and if it is the sync, how to stop that from happening.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Tim Boles, United States
Date: Apr 09, 2018, 17:42, 9 days ago
Score:   Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts
Message: On our EBS systems after the RMAN backup we backup the control file as part of the OS backup of the ORACLE_HOME.

In this manner we can restore the ORACLE_HOME and then restore the database (not duplicate just restore) to another system. We do this all the time. No problem.

And it actually kind of is a "tape" backup because we use Data Domain and DDBoost for the process.

In your case I would backup the control file separately and then just transfer it to the other server outside the tape backup. The controlfile will know all the information it needs to restore the system, and just don't bother with the duplication.

Regards
Tim

Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Tim Boles, United States
Date: Apr 09, 2018, 17:55, 9 days ago
Message: Sorry...I forgot from your original posting you can not do a simple restore. But even with a duplication the principle should hold true....I an not sure why you can do a duplication and not a restore. Can you give me some insight into that aspect. I am curious.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 09, 2018, 18:00, 9 days ago
Message: Jan, I have an idea of what's going on and would appreciate your input.

In each local daily backup script I do this:
report obsolete;
delete noprompt obsolete;

Does this update TSM letting it know to delete the backup pieces/sets from the library? I don't know if that matters, but it will update the control file telling it that they are gone (confirming by listing backup summary on the 'real' catalog which shows none of the older backups).

Then as soon as I connect to the target, it syncs, and tells my 'remote' rman that the files have been deleted. So now it will never be able to find them.

If I either change my retention window to allow me to get all the restores done before they are deleted, OR, stop deleting obsolete until I've done the restores things should work?

I know this is a little scattered, but does it smell right? Thanks
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Jan Schnackenberg, Germany
Date: Apr 10, 2018, 09:22, 9 days ago
Score:   Score: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 Pts
Message: Hi Kirt,

sorry for the delay. I see you did quite a lot of "remote debugging" with Tim. I'm really confused why a simple restore is impossible but a duplicate is not. But anyhow.

A "DELETE NOPROMPT OBSOLETE" will delete all backuppieces that are not needed to fulfill the retention period. They will not only be deleted from the catalog (in the controlfile as well as in the catalog database) but also from the tape library. So yes, they will be gone.

I think you hit the nail on the head with your guess. Yes, the "target" database of the duplicate has the information about these backups in it's local (controlfile) catalog and will sync this information to your remote RMAN catalog database. The backups will now be invisible (they should still be on tape and will remain there forever, unless you clear the complede node/pool in TSM or use TDPOSYNC to list the files and subsequently recatalog them.

So, yes, I guess this would work. Depending on the work it will take you to re-ship a new set of tapes, you might want to try recataloging the backuppieces on the tapes in your remote datacenter.

Regards,
Jan
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: RMAN and expired backup sets
Author: Kirt Thomas, United States
Date: Apr 10, 2018, 15:55, 8 days ago
Message: Jan, thanks - it's always nice when someone smarter than I am confirms my ideas :)

I'm going to stop deleting obsolete until I've duplicated all the databases remotely. I'm making a new tape set starting today, so next week I'll start fresh on everything.

A simple restore is indeed possible, and is what I will do if all else fails. I do a complete DR on all of these DB's and systems every 6 months at a Sunguard facility, so I have all the parts in place for that. I'm going the duplicate db route because I don't want to hassle with all the renaming, I'm using Oracle's EBS 11 and can eventually script a more hands off duplication of 'it'. This looks like it could become regular (every 6 weeks or so) process, and the least amount of work for me is to duplicate the db. And I wanted to figure this out. LOL it's no extra work for me, I just ask my AIX admin to make a new offsite tape set :)

Also, thanks everyone that responded, you all make this community special.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here