RMAN warning?
Dear all,
Action Performed
On Apr-12-2009 Sunday (10:00 am) I have done full backup (level 0)
On Apr-12-2009 Sunday (23:00 pm) I have done daily backup ( incremental level 1 cumulative)
On AprMonday (18:00 pm) I have done daily backup again ( incremental level 1 cumulative )
I am not sure why RMAN delete 5 backup pieces after today's backup (Apr-13-2009) and those 5 backup pieces are backup on yesterday (Apr-12-2009). It seems relate to "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;"
I thought RMAN will delete the previous full backup + daily backup after perform next full backup. Here are the log file and backup scripts.
Log file
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 1 days
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 60 12-APR-09
Backup Piece 60 12-APR-09 /backup/db/backup/RMAN/c-1357907388-20090412-00.bck
Backup Set 61 12-APR-09
Backup Piece 61 12-APR-09 /backup/db/backup/RMAN/backup_PROD_683980327_63_1_1vkc9dh7_1_1.bck
Backup Set 84 12-APR-09
Backup Piece 84 12-APR-09 /backup/db/backup/RMAN/c-1357907388-20090412-01.bck
Backup Set 85 12-APR-09
Backup Piece 85 12-APR-09 /backup/db/backup/RMAN/backup_PROD_683982782_87_1_2nkc9ftu_1_1.bck
Backup Set 86 12-APR-09
Backup Piece 86 12-APR-09 /backup/db/backup/RMAN/backup_PROD_683982783_88_1_2okc9ftv_1_1.bck
Controlfile Copy 1692 12-APR-09 /home/oracle/rsbackup/PROD/backup_control.ctl
deleted backup piece
backup piece handle=/backup/db/backup/RMAN/c-1357907388-20090412-00.bck recid=60 stamp=683979545
deleted backup piece
backup piece handle=/backup/db/backup/RMAN/backup_PROD_683980327_63_1_1vkc9dh7_1_1.bck recid=61 stamp=683980328
deleted backup piece
backup piece handle=/backup/db/backup/RMAN/c-1357907388-20090412-01.bck recid=84 stamp=683982778
deleted backup piece
backup piece handle=/backup/db/backup/RMAN/backup_PROD_683982782_87_1_2nkc9ftu_1_1.bck recid=85 stamp=683982782
deleted backup piece
backup piece handle=/backup/db/backup/RMAN/backup_PROD_683982783_88_1_2okc9ftv_1_1.bck recid=86 stamp=683982784
Deleted 5 objects
Recovery Manager complete.
Daily Backup Daily completed successfully on date Mon Apr 13 18:43:07 HKT 2009
Backup Scripts
Run
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/db/backup/RMAN/%F.bck';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
allocate channel ch1 type disk format '/backup/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;
backup current controlfile;
backup spfile;
release channel ch1;
allocate channel for maintenance type disk;
delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;
Question 1:+
*=======*
I have 2 control files because I use controlfile autobackup on and explicit backup current control files, am I right?+
Yes two controlfile backup one is impilcit autobackup and one for explicit controlfile backup,moreover you should have two spilfe backup one is implicit and another one is explicit cause within yours script you are explicitly backing up the spfile also.
Question 2:+
*=======*
After finsihed level 1 backup on Apr-13-2009, I found that RMAN delete c-13592201-20090412-01.bck only. It remains c-13592201-20090412-02.bck in the backup directory. I assume 2 control files are the same and RMAN only delete the one "controlfile autobackup on". As a result, I still have one control file on level 0. Am I right?+
If yours script contains backup of explicit controlfile and spfile both for level 0 and level 1
backup current controlfile;
backup spfile;
then after successful compeltion of level 0 backup you would have one explicit spfile backup which will be obsolete after level 0 backup completion.
autobackup controlfile and spfile will be remain intact for that level 0 backup.
when you will go to take level 1 backup then now you would have
controlfile explicit backup (which you taken at the time of level 0) will be marked obsoleted now as well controlfile autobackup will also be marked obsoleted (which is taken by itself at the time of level 0),yours explicit spfile after completion of level 1 backup will also be obsoleted.
Now after taking level 1 backup you should have 4 obsoleted backup
-controlfile explicit backup after taking level 0 backup
-spfile explicit backup after taking level 1 backup
-controlfile autobackup after taking level 0 backup
-spfile explicit backup after taking level 1 backup
Question 3:+
*========*
I was using "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;", but I need to manual delete backup pieces due to sizing issue on disk. For my understanding:+
Sunday (Full - level 0)+
Mon (daily - level 1)+
Tue (daily - level 1)+
Wed (daily - level 1)+
Thur (daily - level 1)+
Fir (daily - level 1)+
Sat (daily - level 1)+
If I "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 Days", all the backup pieces will automatic delete by RAMN after a new backup level 0 is created.+
Retention policy will not affect incremental level 1 backups directly ,it will become obsoleted when its full backups obsoleted ,backup retention policy directly affect only full,level 0 and controlfile backups,archivlelog as well level 1 backup retention policy will affect indirectly.
If level 0 backup is obsoleted then its own alls subsequent level 1 backup is obsoleted it does not make sense to house keep those backup cause they always apply at full backup ,when full backup is no longer exist then there is no need to keep them.
For example if you have retention policy is 2 then
Days Level Status
Sat 0
Sun 1 No Report Obsoleted found
Mon 1 No Report Obsoleted found
Tues 1 No Report Obsoleted found
Wed 1 No Report Obsoleted found
Thurs 1 No Report Obsoleted found
Fri 1 No Report Obsoleted found
Sat 0 No Report Obsoleted found
Sun 1 No Report Obsoleted found
Mon 1 No Report Obsoleted found
Tues 1 No Report Obsoleted found
Wed 1 No Report Obsoleted found
Thurs 1 No Report Obsoleted found
Fri 1 No Report Obsoleted found
Sat 0 First week Sat level 0 backup will be obsoleted as well its own Level 1as you are going retention polciy with 7 days then you will have to accomodate
7* level 0 backup + 7*6 level 1 backup ,if you cannot accomodate then you have to reduce yours retention policy days to get more frequent obsolete backup piece and reclaim those space.Dont delete manually which may mess yours backup strategy which in turn create problem at the time of recovery.
Khurram
Similar Messages
-
Rman - "report unrecoverable" concept
Hi
I am readin g a book on rman (rman recipes 11g from APress).
I m not able to understand what is the purpose of "report unrecoverable" command. Book says:
>
Ref: Section 8.3 - page# 229:
You want to identify which datafiles have been affected by unrecoverable operations, since RMAN needs to back up those files as soon as possible after you perform an unrecoverable operation.
Use the report unrecoverable command to find out which datafiles in the database have been marked unrecoverable because they’re part of an unrecoverable operation. Here’s an example showing how to use the report unrecoverable command:
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
1 full /u01/app/oracle/data/prod1/example01.dbf
RMAN>Could someone please give example of unrecoverable operation(s)? And how could rman/oracle know before hand if such an unrecoverable operation is going to be performed on certain datafile(s)?
Thanksuser12033597 wrote:
Hi
I am readin g a book on rman (rman recipes 11g from APress).
I m not able to understand what is the purpose of "report unrecoverable" command. Book says:
Ref: Section 8.3 - page# 229:
You want to identify which datafiles have been affected by unrecoverable operations, since RMAN needs to back up those files as soon as possible after you perform an unrecoverable operation.
Use the report unrecoverable command to find out which datafiles in the database have been marked unrecoverable because they’re part of an unrecoverable operation. Here’s an example showing how to use the report unrecoverable command:
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
1 full /u01/app/oracle/data/prod1/example01.dbf
RMAN> Could someone please give example of unrecoverable operation(s)? And how could rman/oracle know before hand if such an unrecoverable operation is going to be performed on certain datafile(s)?
Thanks A datafile or tablespace are set to unrecoverable if any operation that had been performed (since the last backup taken on these datafiles) on datafile or tablespace that are unrecoverable.
A little explanation:
When ever a operation occurs on database i.e. any dml occurs on tables, these operation generates REDO information in redolog files. So when someone explicitly disable the logging information to redologfile(by hint no_logging), then datafile is marked as unrecoverable.
Oracle says it unrecoverable because oracle cannot perform recovery by reading from redologfile or archivefiles if datafile crashes and need a recovery. Thats why rman warns you about such operation which could have taken place and point you to datafile which had these operation performed. The operations which are unrecoverable are:
1) direct load/SQL load
2) direct-path inserts result from insert or merge statement
3) ALTER TABLE commands
4) CREATE and ALTER INDEX commands
5) INSERT /*+APPEND*/
6) partition manipulation
7) database object that has explicitly set with nologging option
8) Oracle eBusiness Suite concurrent job execution identified in Oracle metalink note: 216211.1
8) Oracle eBusiness Suite patches activities that involve database object manipulation
9) SQL*loader with nologging
So once you take the full backup of datafiles (which are affected by these operation) will clearout the Unrecoverable warning. Because now oracle has the backup of these files.
What preventions you can take for not making datafile to Unrecoverable?
Use force_logging
Also see
http://www.pythian.com/news/7401/oracle-what-is-an-unrecoverable-data-file/
Hope this help you in understanding -
RMAN-08591: WARNING: invalid archived log deletion policy
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
// log deletion policy was APPLIED but there was no mandatory
// archived log destinations.
// *Action: One of the following:
// 1) Change archived log deletion policy using CONFIGURE command
// 2) Make one or more of standby destination as MANDATORY. -
When I did archive log list on my primary, it gives me
archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u04/oradata/arch/PROD/
Oldest online log sequence 29627
Next log sequence to archive 29629
Current log sequence 29629
when I did archive log list on standby , it gives me
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u04/oradata/arch/STNBY/
Oldest online log sequence 29627
Next log sequence to archive 0
Current log sequence 29629
During the hot backup of primary, its showing up these errors.
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000029124.arc thread=1 sequence=29124
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000029125.arc thread=1 sequence=29125
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=/u04/oradata/arch/PROD/PROD_0001_749397572_0000029126.arc thread=1 sequence=29126
I am sure standby is not in sync with Primary.
Can someone explain me how to resolve this issue.
Thank youHere is how you can check whether or not your physical standby is in sync with the primary:
1. Check for GAP on standby
2. Check redo received on standby
3. Check redo applied on standby
Please refer to this url:
http://www.oraclemasters.in/?p=1255 -
RMAN-08120: WARNING: archived log not deleted, not yet applied by standby
i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
Check the below queries.
Primary:-
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
Standby:-
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
HTH. -
RMAN-08137: WARNING: archived log not deleted as it is still needed
I am trying to delete archive logs older than 7 days in streams environment.
1) we dont have a standby database
2) checkpoint_retention_time = 7
Please help me with this.
Regards,
MikeSQL> set serveroutput on
DECLARE
hScn number := 0;
lScn number := 0;
sScn number;
ascn number;
alog varchar2(1000);
begin
select min(start_scn), min(applied_scn) into sScn, ascn
from dba_capture;
DBMS_OUTPUT.ENABLE(2000);
for cr in (select distinct(a.ckpt_scn)
from system.logmnr_restart_ckpt$ a
where a.ckpt_scn <= ascn and a.valid = 1
and exists (select * from system.logmnr_log$ l
where a.ckpt_scn between l.first_change# and l.next_change#)
order by a.ckpt_scn desc)
loop
if (hScn = 0) then
hScn := cr.ckpt_scn;
else
lScn := cr.ckpt_scn;
exit;
end if;
end loop;
if lScn = 0 then
lScn := sScn;
end if;
dbms_output.put_line('Capture will restart from SCN ' || lScn ||' in the following file:');
for cr in (select name, first_time
from DBA_REGISTERED_ARCHIVED_LOG
where lScn between first_scn and next_scn order by thread#)
loop
dbms_output.put_line(cr.name||' ('||cr.first_time||')');
end loop;
end;
After i ran the above script from metalink i got the below output.
When I have run the above code that is given in metalink to check the minimum archive logs required to restart streams i got the below ouput.
Capture will restart from SCN 55313283790in the following file:
+FLASH/ORCL/archivelog/2011_02_22/thread_1_seq_842.346.443519740 (11-MAR-11)*
+FLASH/ORCL/archivelog/2011_02_22/thread_2_seq_832.189.440690538 (11-MAR-11)*
Does this mean that I will not be able to delete the archive logs from 11-mar-11 ?
Regards,
Mike -
RMAN-08138: WARNING: archived log not deleted - must create more backups
I ran:
1. CROSSCHECK ARCHIVELOG ALL
2. DELETE EXPIRED ARCHIVELOG ALL
I am getting this error. I am trying to free my arciver after an ORA-00257 error.
Can anyone help me out?Basically this error means you are trying to delete archivelogs still needed for recovery (according to your retention policy). Develop a strategy which backs up the archivelogs in regular intervals, after a successful backup delete the archivelogs from disk, for example:
backup archivelog all delete all input;
Werner -
RMAN duplicate target using set until telling me it can not find data files
I have RMAN scripts that I use freqently to clone a database from DB (production) to another (non-prod). These work just fine. I use the set until so that I can tell it at what point I want the new DB to be created from the backups of the source.
I had a request to go back a few weeks and the backup files (I do compressed backups to disk) were on tape. I had my backup person restore my backup directory for the source DB as it looked on a certain day (May 28). I have an 8 day retention policy and so the backup files that were restored showed files all the way back to 5/20 ( includes the point I want to use in my set until clause).
However, whenever I try to execute the rman clone, it tells me for each datafile:
RMAN-06023: no backup or copy of datafile 1 found to restore
Like I said, I am able to do this for a current backup that is on disk. I moved the backup files to the source db server and it works fine. However, from these files restored from tape it errors.
Here is the RMAN script:
spool log to c:\temp\clone_CSPROD_CSPRSUM1.log;
#connect to catalog <catalog info>
# target is the source and auxiliary is destination
#connect target <put in source info here>
#connect auxiliary /
run {
allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
##Archivelog number get from sql archive log list command
#set until sequence 831;
set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
duplicate target database to CSPRSUM1 nofilenamecheck
logfile
group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
Exit
Here is the output:
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog <redacted info>>
2> # target is the source and auxiliary is destination
3> #connect target <redacted info>
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> #set until sequence 831;
14> set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
starting full resync of recovery catalog
full resync complete
allocated channel: d1
channel d1: SID=534 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=532 device type=DISK
allocated channel: d4
channel d4: SID=531 device type=DISK
allocated channel: a1
channel a1: SID=530 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 15-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 260398799;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
"+data";
set newname for datafile 3 to
"+data";
set newname for datafile 4 to
"+data";
set newname for datafile 5 to
"+data";
set newname for datafile 6 to
"+data";
set newname for datafile 7 to
"+data";
set newname for datafile 8 to
"+data";
set newname for datafile 9 to
"+data";
set newname for datafile 10 to
"+data";
set newname for datafile 11 to
"+data";
set newname for datafile 12 to
"+data";
set newname for datafile 13 to
"+data";
set newname for datafile 14 to
"+data";
set newname for datafile 15 to
"+data";
set newname for datafile 16 to
"+data";
set newname for datafile 17 to
"+data";
set newname for datafile 18 to
"+data";
set newname for datafile 19 to
"+data";
set newname for datafile 20 to
"+data";
set newname for datafile 21 to
"+data";
set newname for datafile 22 to
"+data";
set newname for datafile 23 to
"+data";
set newname for datafile 24 to
"+data";
set newname for datafile 25 to
"+data";
set newname for datafile 26 to
"+data";
set newname for datafile 27 to
"+data";
set newname for datafile 28 to
"+data";
set newname for datafile 29 to
"+data";
set newname for datafile 30 to
"+data";
set newname for datafile 31 to
"+data";
set newname for datafile 32 to
"+data";
set newname for datafile 33 to
"+data";
set newname for datafile 34 to
"+data";
set newname for datafile 35 to
"+data";
set newname for datafile 36 to
"+data";
set newname for datafile 37 to
"+data";
set newname for datafile 38 to
"+data";
set newname for datafile 39 to
"+data";
set newname for datafile 40 to
"+data";
set newname for datafile 41 to
"+data";
set newname for datafile 42 to
"+data";
set newname for datafile 43 to
"+data";
set newname for datafile 44 to
"+data";
set newname for datafile 45 to
"+data";
set newname for datafile 46 to
"+data";
set newname for datafile 47 to
"+data";
set newname for datafile 48 to
"+data";
set newname for datafile 49 to
"+data";
set newname for datafile 50 to
"+data";
set newname for datafile 51 to
"+data";
set newname for datafile 52 to
"+data";
set newname for datafile 53 to
"+data";
set newname for datafile 54 to
"+data";
set newname for datafile 55 to
"+data";
set newname for datafile 56 to
"+data";
set newname for datafile 57 to
"+data";
set newname for datafile 58 to
"+data";
set newname for datafile 59 to
"+data";
set newname for datafile 60 to
"+data";
set newname for datafile 61 to
"+data";
set newname for datafile 62 to
"+data";
set newname for datafile 63 to
"+data";
set newname for datafile 64 to
"+data";
set newname for datafile 65 to
"+data";
set newname for datafile 66 to
"+data";
set newname for datafile 67 to
"+data";
set newname for datafile 68 to
"+data";
set newname for datafile 69 to
"+data";
set newname for datafile 70 to
"+data";
set newname for datafile 71 to
"+data";
set newname for datafile 72 to
"+data";
set newname for datafile 73 to
"+data";
set newname for datafile 74 to
"+data";
set newname for datafile 75 to
"+data";
set newname for datafile 76 to
"+data";
set newname for datafile 77 to
"+data";
set newname for datafile 78 to
"+data";
set newname for datafile 79 to
"+data";
set newname for datafile 80 to
"+data";
set newname for datafile 81 to
"+data";
set newname for datafile 82 to
"+data";
set newname for datafile 83 to
"+data";
set newname for datafile 84 to
"+data";
set newname for datafile 85 to
"+data";
set newname for datafile 86 to
"+data";
set newname for datafile 87 to
"+data";
set newname for datafile 88 to
"+data";
set newname for datafile 89 to
"+data";
set newname for datafile 90 to
"+data";
set newname for datafile 91 to
"+data";
set newname for datafile 92 to
"+data";
set newname for datafile 93 to
"+data";
set newname for datafile 94 to
"+data";
set newname for datafile 95 to
"+data";
set newname for datafile 96 to
"+data";
set newname for datafile 97 to
"+data";
set newname for datafile 98 to
"+data";
set newname for datafile 99 to
"+data";
set newname for datafile 100 to
"+data";
set newname for datafile 101 to
"+data";
set newname for datafile 102 to
"+data";
set newname for datafile 103 to
"+data";
set newname for datafile 104 to
"+data";
set newname for datafile 105 to
"+data";
set newname for datafile 106 to
"+data";
set newname for datafile 107 to
"+data";
set newname for datafile 108 to
"+data";
set newname for datafile 109 to
"+data";
set newname for datafile 110 to
"+data";
set newname for datafile 111 to
"+data";
set newname for datafile 112 to
"+data";
set newname for datafile 113 to
"+data";
set newname for datafile 114 to
"+data";
set newname for datafile 115 to
"+data";
set newname for datafile 116 to
"+data";
set newname for datafile 117 to
"+data";
set newname for datafile 118 to
"+data";
set newname for datafile 119 to
"+data";
set newname for datafile 120 to
"+data";
set newname for datafile 121 to
"+data";
set newname for datafile 122 to
"+data";
restore
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 15-JUN-11
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/15/2011 11:21:42
RMAN-01005: not all datafiles have backups that can be recovered to scn 260398799
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 122 found to restore
RMAN-06023: no backup or copy of datafile 121 found to restore
RMAN-06023: no backup or copy of datafile 120 found to restore
RMAN-06023: no backup or copy of datafile 119 found to restore
RMAN-06023: no backup or copy of datafile 118 found to restore
RMAN-06023: no backup or copy of datafile 117 found to restore
RMAN-06023: no backup or copy of datafile 116 found to restore
RMAN-06023: no backup or copy of datafile 115 found to restore
RMAN-06023: no backup or copy of datafile 114 found to restore
RMAN-06023: no backup or copy of datafile 113 found to restore
RMAN-06023: no backup or copy of datafile 112 found to restore
RMAN-06023: no backup or copy of datafile 111 found to restore
RMAN-06023: no backup or copy of datafile 110 found to restore
RMAN-06023: no backup or copy of datafile 109 found to restore
RMAN-06023: no backup or copy of datafile 108 found to restore
RMAN-06023: no backup or copy of datafile 107 found to restore
RMAN-06023: no backup or copy of datafile 106 found to restore
RMAN-06023: no backup or copy of datafile 105 found to restore
RMAN-06023: no backup or copy of datafile 104 found to restore
RMAN-06023: no backup or copy of datafile 103 found to restore
RMAN-06023: no backup or copy of datafile 102 found to restore
RMAN-06023: no backup or copy of datafile 101 found to restore
RMAN-06023: no backup or copy of datafile 100 found to restore
RMAN-06023: no backup or copy of datafile 99 found to restore
RMAN-06023: no backup or copy of datafile 98 found to restore
RMAN-06023: no backup or copy of datafile 97 found to restore
RMAN-06023: no backup or copy of datafile 96 found to restore
RMAN-06023: no backup or copy of datafile 95 found to restore
RMAN-06023: no backup or copy of datafile 94 found to restore
RMAN-06023: no backup or copy of datafile 93 found to restore
RMAN-06023: no backup or copy of datafile 92 found to restore
RMAN-06023: no backup or copy of datafile 91 found to restore
RMAN-06023: no backup or copy of datafile 90 found to restore
RMAN-06023: no backup or copy of datafile 89 found to restore
RMAN-06023: no backup or copy of datafile 88 found to restore
RMAN-06023: no backup or copy of datafile 87 found to restore
RMAN-06023: no backup or copy of datafile 86 found to restore
RMAN-06023: no backup or copy of datafile 85 found to restore
RMAN-06023: no backup or copy of datafile 84 found to restore
RMAN-06023: no backup or copy of datafile 83 found to restore
RMAN-06023: no backup or copy of datafile 82 found to restore
RMAN-06023: no backup or copy of datafile 81 found to restore
RMAN-06023: no backup or copy of datafile 80 found to restore
RMAN-06023: no backup or copy of datafile 79 found to restore
RMAN-06023: no backup or copy of datafile 78 found to restore
RMAN-06023: no backup or copy of datafile 77 found to restore
RMAN-06023: no backup or copy of datafile 76 found to restore
RMAN-06023: no backup or copy of datafile 75 found to restore
RMAN-06023: no backup or copy of datafile 74 found to restore
RMAN-06023: no backup or copy of datafile 73 found to restore
RMAN-06023: no backup or copy of datafile 72 found to restore
RMAN-06023: no backup or copy of datafile 71 found to restore
RMAN-06023: no backup or copy of datafile 70 found to restore
RMAN-06023: no backup or copy of datafile 69 found to restore
RMAN-06023: no backup or copy of datafile 68 found to restore
RMAN-06023: no backup or copy of datafile 67 found to restore
RMAN-06023: no backup or copy of datafile 66 found to restore
RMAN-06023: no backup or copy of datafile 65 found to restore
RMAN-06023: no backup or copy of datafile 64 found to restore
RMAN-06023: no backup or copy of datafile 63 found to restore
RMAN-06023: no backup or copy of datafile 62 found to restore
RMAN-06023: no backup or copy of datafile 61 found to restore
RMAN-06023: no backup or copy of datafile 60 found to restore
RMAN-06023: no backup or copy of datafile 59 found to restore
RMAN-06023: no backup or copy of datafile 58 found to restore
RMAN-06023: no backup or copy of datafile 57 found to restore
RMAN-06023: no backup or copy of datafile 56 found to restore
RMAN-06023: no backup or copy of datafile 55 found to restore
RMAN-06023: no backup or copy of datafile 54 found to restore
RMAN-06023: no backup or copy of datafile 53 found to restore
RMAN-06023: no backup or copy of datafile 52 found to restore
RMAN-06023: no backup or copy of datafile 51 found to restore
RMAN-06023: no backup or copy of datafile 50 found to restore
RMAN-06023: no backup or copy of datafile 49 found to restore
RMAN-06023: no backup or copy of datafile 48 found to restore
RMAN-06023: no backup or copy of datafile 47 found to restore
RMAN-06023: no backup or copy of datafile 46 found to restore
RMAN-06023: no backup or copy of datafile 45 found to restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 41 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN> Exit
Recovery Manager complete.
Edited by: kerrygm on Jun 15, 2011 11:36 AMMaybe making progress.
I got into RMAN and did a List backup command. In looking at the output, I see that it does have the 5/20 backup showing. Here is part of the output:
BS Key Type LV Size Device Type Elapsed Time Completion Time
965689 Full 19.86M DISK 00:00:01 16-JUN-11
BP Key: 967942 Status: AVAILABLE Compressed: NO Tag: TAG20110616T231223
Piece Name: F:\BACKUPS\CSPROD\C-368871413-20110616-01
SPFILE Included: Modification time: 16-JUN-11
SPFILE db_unique_name: CSPROD
Control File Included: Ckp SCN: 369596068 Ckp time: 16-JUN-11
BS Key Size Device Type Elapsed Time Completion Time
966218 403.84M DISK 00:00:00 20-MAY-11
BP Key: 967842 Status: AVAILABLE Compressed: YES Tag: TAG20110520T231012
Piece Name: F:\BACKUPS\CSPROD\A1\CSPROD_ARCH_5844
List of Archived Logs in backup set 966218
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2112 237027300 20-MAY-11 237046947 20-MAY-11
1 2113 *237046947* 20-MAY-11 237059284 20-MAY-11
1 2114 237059284 20-MAY-11 237216514 20-MAY-11
1 2115 237216514 20-MAY-11 237709545 20-MAY-11
1 2116 237709545 20-MAY-11 237722825 20-MAY-11
1 2117 237722825 20-MAY-11 237730431 20-MAY-11
1 2118 237730431 20-MAY-11 237860199 20-MAY-11
I then changed my rman script to use the *237046947* SCN number that says it is from 5/20. I them kicked off my rman script and got the following result.
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog 'rmancat/rmancat@rmancat';
2> # target is the source and auxiliary is destination
3> #connect target sys/<pwd>@csprod
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> set until sequence 237046947;
14> ##set until time "to_date('2011-05-20 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
allocated channel: d1
channel d1: SID=532 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=531 device type=DISK
allocated channel: d4
channel d4: SID=555 device type=DISK
allocated channel: a1
channel a1: SID=534 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 17-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 373021170;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
Starting restore at 17-JUN-11
channel d1: starting datafile backup set restore
channel d1: specifying datafile(s) to restore from backup set
channel d1: restoring datafile 00003 to +DATA
channel d2: restoring datafile 00122 to +DATA
channel d2: reading from backup piece F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149
channel d3: starting datafile backup set restore
channel d3: specifying datafile(s) to restore from backup set
channel d3: restoring datafile 00002 to +DATA
channel d3: restoring datafile 00020 to +DATA
channel d4: restoring datafile 00120 to +DATA
channel d4: reading from backup piece F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147
channel d1: piece handle=F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 tag=TAG20110616T230013
channel d1: restored backup piece 1
channel d1: restore complete, elapsed time: 00:01:15
channel d4: piece handle=F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147 tag=TAG20110616T230013
channel d4: restored backup piece 1
channel d4: restore complete, elapsed time: 00:03:15
channel d2: piece handle=F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149 tag=TAG20110616T230013
channel d2: restored backup piece 1
channel d2: restore complete, elapsed time: 00:03:35
channel d3: piece handle=F:\BACKUPS\CSPROD\D1\CSPROD_DATA_6146 tag=TAG20110616T230013
channel d3: restored backup piece 1
channel d3: restore complete, elapsed time: 00:04:55
Finished restore at 17-JUN-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CSPRSUM1" RESETLOGS ARCHIVELOG
MAXLOGFILES 23
MAXLOGMEMBERS 3
MAXDATAFILES 1021
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log' ) SIZE 50 M ,
GROUP 2 ( '+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log' ) SIZE 50 M ,
GROUP 3 ( '+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log' ) SIZE 50 M
DATAFILE
'+DATA/csprsum1/datafile/system.1535.754067379'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=754067676 file name=+DATA/csprsum1/datafile/sysaux.1536.754067379
datafile 121 switched to datafile copy
input datafile copy RECID=120 STAMP=754067677 file name=+DATA/csprsum1/datafile/waapp.1653.754067403
datafile 122 switched to datafile copy
input datafile copy RECID=121 STAMP=754067677 file name=+DATA/csprsum1/datafile/cu_custom.1549.754067381
contents of Memory Script:
set until scn 373021170;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 17-JUN-11
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/csprsum1/datafile/system.1535.754067379'
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/17/2011 15:14:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 3818 and starting SCN of 372868482 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3817 and starting SCN of 372685133 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3816 and starting SCN of 372593528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3815 and starting SCN of 372374385 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3814 and starting SCN of 372325053 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3813 and starting SCN of 372316138 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3812 and starting SCN of 372249619 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3811 and starting SCN of 371775981 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3810 and starting SCN of 371643855 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3809 and starting SCN of 371614442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3808 and starting SCN of 371432892 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3807 and starting SCN of 371121955 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3806 and starting SCN of 371047786 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3805 and starting SCN of 371029095 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3804 and starting SCN of 371018252 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3803 and starting SCN of 370947755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3802 and starting SCN of 370857440 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3801 and starting SCN of 370814417 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3800 and starting SCN of 370797061 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3799 and starting SCN of 370756569 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3798 and starting SCN of 370746833 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3797 and starting SCN of 370746693 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3796 and starting SCN of 370746568 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3795 and starting SCN of 370746068 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3794 and starting SCN of 370745451 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3793 and starting SCN of 370733767 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3792 and starting SCN of 370674629 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3791 and starting SCN of 370501026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3790 and starting SCN of 370498513 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3789 and starting SCN of 370497977 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3788 and starting SCN of 370497635 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3787 and starting SCN of 370497319 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3786 and starting SCN of 370496938 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3785 and starting SCN of 370495428 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3784 and starting SCN of 370491173 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3783 and starting SCN of 370390074 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3782 and starting SCN of 370385574 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3781 and starting SCN of 370385310 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3780 and starting SCN of 370385044 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3779 and starting SCN of 370368486 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3778 and starting SCN of 370333960 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3777 and starting SCN of 370330980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3776 and starting SCN of 370327876 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3775 and starting SCN of 370174433 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3774 and starting SCN of 370148373 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3773 and starting SCN of 370147821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3772 and starting SCN of 370147623 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3771 and starting SCN of 370141528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3770 and starting SCN of 369711271 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3769 and starting SCN of 369621694 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3768 and starting SCN of 369595614 found to restore
RMAN> Exit
Recovery Manager complete.
What I am not sure is if the SCN I used in my set until sequence command was from 5/20, when I look at the backup pieces that it is reading to restore from, they appear to be from backup files taken from June.
(e.g channel d1: reading from backup piece F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 -- this is a 6/16 backup file).
Also, as you can see it was not able to do a media recovery.
Thanks in advance for your help. -
Can you help me? I meet errors when I do incomplete recovery with RMAN
In recover step, There are following errors:
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
question:
1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
The following is the detail information:
The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
The following is the backup script:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
backup incremental level 0 filesperset 1
format 'ora8i_online<db01_%s:%t:%p>.dbf'
database
include current controlfile
archivelog all delete input;
I use it to do a full backup on July 16th,17th successfully.
And I use the following scripts to do incomplete recovery:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
sql "alter database mount";
set until time ='17.07.2004';
restore database;
recover database;
sql "alter database open resetlogs";
sql "alter database open";
There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter database mount
RMAN-03023: executing command: sql
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-03022: compiling command: recover
RMAN-03022: compiling command: recover(1)
RMAN-03022: compiling command: recover(2)
RMAN-03022: compiling command: recover(3)
RMAN-03023: executing command: recover(3)
RMAN-08054: starting media recovery
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
ORA-06512: at line 1
I repeat my questions:
1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
Can you help me ? Thank you.which o.s u are using i can't help you as i never worked on ver 8i,i can tell you incomplete recovery on oracle 9i on win 2000 server.
thanks : alok kumar -
Can you help me? I meet some errors when I do incomplete recovery with RMAN
In recover step, There are following errors:
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
question:
1. Should I restore archive log files generated on July 16th back to orignal archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
The following is the detail information:
The database is ok when I try to do incomplete recovery database that was fully backed up on July,16th,2004. The database is oracle 8.1.7 and is in the archive mode:
The following is the backup script:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db01,OB2BARLIST=ora8i_online)';
backup incremental level 0 filesperset 1
format 'ora8i_online<db01_%s:%t:%p>.dbf'
database
include current controlfile
archivelog all delete input;
I use it to do a full backup on July 16th,17th successfully.
And I use the following scripts to do incomplete recovery:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=ORACLE8,OB2APPNAME=db01)';
sql "alter database mount";
set until time ='17.07.2004';
restore database;
recover database;
sql "alter database open resetlogs";
sql "alter database open";
There script is successful in restore step. But there are some errors in recover step. The detail information is showing in following log:
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=13 devtype=SBT_TAPE
RMAN-08526: channel dev_0: HP OpenView OmniBack II A.04.10/176
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter database mount
RMAN-03023: executing command: sql
RMAN-03022: compiling command: set
RMAN-03022: compiling command: restore
RMAN-03022: compiling command: IRESTORE
RMAN-03023: executing command: IRESTORE
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2056 set_stamp=531622798 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08016: channel dev_0: starting datafile backupset restore
RMAN-08502: set_count=2180 set_stamp=531623409 creation_time=16.07.2004
RMAN-08089: channel dev_0: specifying datafile(s) to restore from backup set
RMAN-08523: restoring datafile 00001 to /d/db/oradata/db01/system01.dbf
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2180:531623409:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-08023: channel dev_0: restored backup piece 1
RMAN-08511: piece handle=netace_ora8i_online<db01_2212:531623994:1>.dbf tag=null params=NULL
RMAN-08024: channel dev_0: restore complete
RMAN-03022: compiling command: recover
RMAN-03022: compiling command: recover(1)
RMAN-03022: compiling command: recover(2)
RMAN-03022: compiling command: recover(3)
RMAN-03023: executing command: recover(3)
RMAN-08054: starting media recovery
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-11001: Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/d/db/oradata/db01/system01.dbf'
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06003: ORACLE error from target database: ORA-01220: file based sort illegal before database is open
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 7220
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 5053
ORA-06512: at line 1
I repeat my questions:
1. Should I restore archive log files generated on July 16th back to original archive directory in order to avoid to recover failure?
2. Or Should I add the command "sql 'alter system archive log current'" in the backup script in order to avoid to recover failure?
Can you help me ? Thank you.You are correct. In RMAN8i, you should add the "alter system archive log current; command before you backup the archive logs.
You are running into the case where Oracle needs additional redo to make the database consistent that was located in the current online log at the time of the backup.
If you set UNTIL TIME to an earlier time does the recover work?
In Oracle9i, if you issue the command, "backup database plus archive logs", RMAN will automatically archive the current online log before performing the archive log backups.
Thanks, Tammy -
Unable to recover database after rman recovery and database open resetlogs
I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
OPA-00600: ORA-00600: internal error code, arguments: ...
The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
I hope I have not dug myself into too deep of a hole here.
Here is the trace from my most recent attempt.
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> list incarnation of database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 08/02/2011 15:49:04
ORA-01507: database not mounted
RMAN> restore controlfile from autobackup;
Starting restore at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /opt/oracle/flash_recovery_area
database name (or database unique name) used for search: LCRSDEV
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 02-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
RMAN> restore database until scn 95676700;
Starting restore at 02-AUG-11
Starting implicit crosscheck backup at 02-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 6 objects
Finished implicit crosscheck backup at 02-AUG-11
Starting implicit crosscheck copy at 02-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 02-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/02/2011 15:52:04
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> restore database;
Starting restore at 02-AUG-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
Finished restore at 02-AUG-11
RMAN> recover database until scn 95676700;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:16:28
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN> recover database;
Starting recover at 02-AUG-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
unable to find archive log
archive log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/02/2011 16:25:04
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
*2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
*3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
*4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
*5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
*6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
*7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
*8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
*9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
However if I restore the controlfile to the earlier version I am getting the following output from the process:
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 3070230528 bytes
Fixed Size 2099424 bytes
Variable Size 301991712 bytes
Database Buffers 2751463424 bytes
Redo Buffers 14675968 bytes
RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
Starting restore at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
Finished restore at 03-AUG-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
RMAN> restore database until scn 92348137;
Starting restore at 03-AUG-11
Starting implicit crosscheck backup at 03-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 03-AUG-11
Starting implicit crosscheck copy at 03-AUG-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 03-AUG-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/03/2011 12:53:19
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
Edited by: K Doyle on Aug 3, 2011 10:22 AM -
Problem in recover physical standby database(Data Guard) by rman
Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS
would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PMhi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks -
RMAN 11gr2 ORA-00308 when dulplicate database from active
Hi,
I'm trying to clone a production database (Oracle 11.2.0.3) from HP-UX IA64 to Solaris 10 (Sparc 64) (source on Filesystem, target on ASM)
the previous steps was done (same oracle software installation, same patches, sqlnet comunication, etc.)
but the RMAN fails at end of the process:
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Aug 22 09:44:34 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SIN (DBID=634625013)
connected to recovery catalog database
connected to auxiliary database: SIN (not mounted)
RMAN> run
+2> {+
+3> allocate channel c1 type disk;+
+4> allocate channel c2 type disk;+
+5> allocate channel c3 type disk;+
+6> allocate channel c4 type disk;+
+7> allocate auxiliary channel a1 type disk;+
+8> allocate auxiliary channel a2 type disk;+
+9> set newname for datafile 1 to '+DG_DATA';+
+10> set newname for datafile 2 to '+DG_DATA';+
+11> set newname for datafile 3 to '+DG_DATA';+
+12> set newname for datafile 4 to '+DG_DATA';+
+13> set newname for datafile 5 to '+DG_DATA';+
+14> set newname for datafile 6 to '+DG_DATA';+
+15> set newname for datafile 7 to '+DG_DATA';+
+16> set newname for datafile 8 to '+DG_DATA';+
+17> set newname for datafile 9 to '+DG_DATA';+
+18> set newname for datafile 10 to '+DG_DATA';+
+... to...+
+398> set newname for datafile 390 to '+DG_DATA';+
+399> set newname for datafile 391 to '+DG_DATA';+
+400> duplicate target database to "sin" from active database nofilenamecheck+
+401> DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','+DG_DATA/',+
+402> '/u11/oradata/sin/','+DG_DATA/',+
+403> '/u07/oradata/sin/','+DG_DATA/',+
+404> '/u08/oradata/sin/','+DG_DATA/',+
+405> '/u09/oradata/sin/','+DG_DATA/');+
+406> }+
+407>+
starting full resync of recovery catalog
full resync complete
allocated channel: c1
channel c1: SID=1787 device type=DISK
allocated channel: c2
channel c2: SID=2406 device type=DISK
allocated channel: c3
channel c3: SID=850 device type=DISK
allocated channel: c4
channel c4: SID=1146 device type=DISK
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=1514 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
+...+
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 22-AUG-12
contents of Memory Script:
+{+
sql clone "create spfile from memory";
+}+
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
+{+
shutdown clone immediate;
startup clone nomount;
+}+
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 7317790720 bytes
Fixed Size 2173456 bytes
Variable Size 3808433648 bytes
Database Buffers 3489660928 bytes
Redo Buffers 17522688 bytes
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=758 device type=DISK
contents of Memory Script:
+{+
sql clone "alter system set control_files =
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
sql clone "alter system set db_name =
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+sql clone "alter system set db_unique_name =+
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+shutdown clone immediate;+
+startup clone force nomount+
+backup as copy current controlfile auxiliary format '+DG_DATA/sin/controlfile/current.512.791978153';+
+restore clone controlfile to '+DG_DATA/sin/controlfile/current.625.791978153' from+
+'+DG_DATA/sin/controlfile/current.512.791978153';+
+sql clone "alter system set control_files =+
+''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/current.625.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+shutdown clone immediate;+
+startup clone nomount;+
+alter clone database mount;+
+}+
+executing Memory Script+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.562.791978153'' comment= ''Set by RMAN'' scope=spfile+
+sql statement: alter system set db_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+sql statement: alter system set db_unique_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+Oracle instance shut down+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+Starting backup at 22-AUG-12+
+channel c1: starting datafile copy+
+copying current control file+
+output file name=/u06/tmpapp/rmanbkps/snapcf_sin.f tag=TAG20120822T094657 RECID=49 STAMP=791977621+
+channel c1: datafile copy complete, elapsed time: 00:00:01+
+Finished backup at 22-AUG-12+
+Starting restore at 22-AUG-12+
+channel a2: skipped, AUTOBACKUP already found+
+channel a1: copied control file copy+
+Finished restore at 22-AUG-12+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.625.791978153'' comment= ''Set by RMAN'' scope=spfile+
+Oracle instance shut down+
+connected to auxiliary database (not started)+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+database mounted+
+Using previous duplicated file +DG_DATA/sin/datafile/system.666.791914845 for datafile 1 with checkpoint SCN of 46164275052+
+Using previous duplicated file +DG_DATA/sin/datafile/undotbs1.678.791913821 for datafile 2 with checkpoint SCN of 46164227408+
+...+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.498.791939115 for datafile 389 with checkpoint SCN of 46165353395+
+Using previous duplicated file +DG_DATA/sin/datafile/mytablespace.674.791914359 for datafile 390 with checkpoint SCN of 46164253329+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.499.791939115 for datafile 391 with checkpoint SCN of 46165353396+
+contents of Memory Script:+
+{+
+sql 'alter system archive log current';+
+}+
+executing Memory Script+
+sql statement: alter system archive log current+
+contents of Memory Script:+
+{+
+backup as copy reuse+
+archivelog like "/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065832.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065833.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065834.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065835.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065836.ARC" auxiliary format+
+"+DG_DATA" ;+
+catalog clone start with "+DG_DATA";+
+catalog clone datafilecopy "+DG_DATA/sin/datafile/system.666.791914845",+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.679.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.689.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.690.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.677.791914357",+
+"+DG_DATA/sin/datafile/drsys.621.791939555",+
+"+DG_DATA/sin/datafile/high_idx.663.791914889",+
+"+DG_DATA/sin/datafile/tools.507.791939555",+
+...+
+"+DG_DATA/sin/datafile/bkptemp.497.791939113",+
+"+DG_DATA/sin/datafile/med_dat.498.791939115",+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359",+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+switch clone datafile 1 to datafilecopy+
+"+DG_DATA/sin/datafile/system.666.791914845";+
+switch clone datafile 2 to datafilecopy+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821";+
+switch clone datafile 3 to datafilecopy+
+...+
+"+DG_DATA/sin/datafile/med_dat.498.791939115";+
+switch clone datafile 390 to datafilecopy+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359";+
+switch clone datafile 391 to datafilecopy+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+}+
+executing Memory Script+
+Starting backup at 22-AUG-12+
+channel c1: starting archived log copy+
+input archived log thread=1 sequence=65832 RECID=48339 STAMP=791913640+
+channel c2: starting archived log copy+
+input archived log thread=1 sequence=65833 RECID=48340 STAMP=791933223+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65834 RECID=48341 STAMP=791939052+
+channel c4: starting archived log copy+
+input archived log thread=1 sequence=65835 RECID=48342 STAMP=791962351+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.791978259 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:00:35+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65836 RECID=48343 STAMP=791977692+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 RECID=0 STAMP=0+
+channel c1: archived log copy complete, elapsed time: 00:00:51+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.791978259 RECID=0 STAMP=0+
+channel c2: archived log copy complete, elapsed time: 00:01:41+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.791978295 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:01:06+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.791978259 RECID=0 STAMP=0+
+channel c4: archived log copy complete, elapsed time: 00:01:41+
+Finished backup at 22-AUG-12+
+searching for all files that match the pattern +DG_DATA+
+List of Files Unknown to the Database+
+=====================================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+cataloging files...+
+cataloging done+
+List of Cataloged Files+
+=======================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65835.516.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+List of Files Which Where Not Cataloged+
+=======================================+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+RMAN-07518: Reason: Foreign database file DBID: 0 Database Name:+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/system.666.791914845 RECID=442 STAMP=791978374+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.678.791913821 RECID=443 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.679.791913821 RECID=444 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.689.791913821 RECID=445 STAMP=791978375+
+cataloged datafile copy+
+...+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.498.791939115 RECID=830 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/mytablespace.674.791914359 RECID=831 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.499.791939115 RECID=832 STAMP=791978408+
+datafile 1 switched to datafile copy+
+input datafile copy RECID=442 STAMP=791978374 file name=+DG_DATA/sin/datafile/system.666.791914845+
+datafile 2 switched to datafile copy+
+input datafile copy RECID=443 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.678.791913821+
+datafile 3 switched to datafile copy+
+input datafile copy RECID=444 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.679.791913821+
+datafile 4 switched to datafile copy+
+input datafile copy RECID=445 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.689.791913821+
+...+
+datafile 389 switched to datafile copy+
+input datafile copy RECID=830 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.498.791939115+
+datafile 390 switched to datafile copy+
+input datafile copy RECID=831 STAMP=791978408 file name=+DG_DATA/sin/datafile/mytablespace.674.791914359+
+datafile 391 switched to datafile copy+
+input datafile copy RECID=832 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.499.791939115+
+contents of Memory Script:+
+{+
+set until scn 46167049411;+
+recover+
+clone database+
+delete archivelog+
+;+
+}+
+executing Memory Script+
+executing command: SET until clause+
+Starting recover at 22-AUG-12+
+starting media recovery+
+archived log for thread 1 with sequence 65832 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.7+
+91978259+
+archived log for thread 1 with sequence 65833 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.7+
+91978259+
+archived log for thread 1 with sequence 65834 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.7+
+91978259+
+archived log for thread 1 with sequence 65835 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.7+
+91978259+
+archived log for thread 1 with sequence 65836 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.7+
+91978295+
+archived log file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 thread=1 sequence=65832+
+released channel: c1+
+released channel: c2+
+released channel: c3+
+released channel: c4+
+Oracle Error:+
+ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below+
+ORA-01194: file 1 needs more recovery to be consistent+
+ORA-01110: data file 1: '+DG_DATA/sin/datafile/system.666.791914845'+
*+released channel: a1+*
*+released channel: a2+*
*+RMAN-00571: ===========================================================+*
*+RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============+*
*+RMAN-00571: ===========================================================+*
*+RMAN-03002: failure of Duplicate Db command at 08/22/2012 09:52:27+*
*+RMAN-05501: aborting duplication of target database+*
*+RMAN-03015: error occurred in stored script Memory Script+*
*+RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DG_DATA/sin/archivelog/2012_08_22/thre+*
*+ad_1_seq_65832.513.791978259'+*
*+ORA-00308: cannot open archived log '+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259'+*
+Recovery Manager complete.+
the error is always the same, a previous backup with RMAN was taken on tape on the source database (production).
Please help me to find what is wrong here!!Hi mseberg
that's exactly i'm doing:
1. Create an Oracle Password File for the Auxiliary Database
a. done, passwd file created*
2. Create the Directory Structure on the remote server
a. done, all the admin structure wa created.*
3. Oracle Net Setup ( you need an entry for the CLONE in your TNSNAMES.ORA on both servers ) ( I use SID_LIST_LISTENER entry for static )
a. done, i have the entries working on my tnsnames.ora (source and target with static listeners)*
4. Create an Initialization Parameter File for the Auxiliary Instance ( I use Parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change locations)
a. done, this is my initialization file:*
*.audit_file_dest='/u01/app/oracle/admin/sin/adump'*
*.audit_trail='db'*
*.compatible='11.2.0.0.0'*
*.db_block_size=8192*
*.db_create_file_dest='DG_DATA'+*
*.db_domain=''*
*.db_files=2048*
*.db_name='sin'*
*.db_recovery_file_dest='DG_DATA'+*
*.db_recovery_file_dest_size=20G*
*.diagnostic_dest='/u01/app/oracle'*
*.dispatchers='(PROTOCOL=TCP) (SERVICE=sinXDB)'*
*.log_archive_format='%t_%s_%r.dbf'*
*.memory_target=7340032000*
*.open_cursors=300*
*.processes=2000*
*.remote_login_passwordfile='EXCLUSIVE'*
*.sessions=2205*
*.undo_tablespace='UNDOTBS1'*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/')+
LOG_FILE_NAME_CONVERT=('/u04/oradata/sin/','DG_DATA/',+*
+'/u05/oradata/sin/','+DG_DATA/',+
+'/u03/oradata/sin/','+DG_DATA/',+
+'/u02/oradata/sin/','+DG_DATA/')+
and this is my command from RMAN:
run*
*+{+*
allocate channel c1 type disk;*
allocate channel c2 type disk;*
allocate channel c3 type disk;*
allocate channel c4 type disk;*
allocate auxiliary channel a1 type disk;*
allocate auxiliary channel a2 type disk;*
set newname for datafile 1 to 'DG_DATA';+*
set newname for datafile 2 to 'DG_DATA';+*
set newname for datafile 3 to 'DG_DATA';+*
set newname for datafile 4 to 'DG_DATA';+*
set newname for datafile 5 to 'DG_DATA';+*
set newname for datafile 6 to 'DG_DATA';+*
set newname for datafile 7 to 'DG_DATA';+*
set newname for datafile 8 to 'DG_DATA';+*
set newname for datafile 9 to 'DG_DATA';+*
set newname for datafile 10 to 'DG_DATA';+*
+...+
set newname for datafile 390 to 'DG_DATA';+*
set newname for datafile 391 to 'DG_DATA';+*
duplicate target database to "sin" from active database nofilenamecheck*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/');+
+}+
do you think the problem may be in the name of the database?, I am using the same name in the auxiliary
and when I get the error, I have the same dbid in both databases (source and destination)
Thanks
MM -
Gurus,
EBS : R12.1.2 (OS Linux)
Database: 11.2.0.3 (OS HP UX Itanium)
I am getting error in autoconfig with jtfictx.sh. I am cloning PROD to QA. Usually I use RMAN duplicate to clone the database and then Application file system are copied. I have performed this method for many times( say 25 times).
This iteration after the database recovery, I ran the RDBMS autoconfig which completed successfully. Then I ran the autoconfig on the concurrent manager server first and received the below error. There are no change of steps from my usual.
Executing script in InstantiateFile:
/ebs02/oracle/inst/apps/SID_servername/admin/install/jtfictx.sh
script returned:
jtfictx.sh started at Sun Sep 8 01:04:11 CDT 2013
SQL*Plus: Release 10.1.0.5.0 - Production on Sun Sep 8 01:04:11 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter value for 1: Enter value for 2: Enter value for 3: Connected.
DECLARE
ERROR at line 1:
ORA-29874: warning in the execution of ODCIINDEXALTER routine
ORA-29960: line 1,
DRG-10595: ALTER INDEX JTF_AMV_ITEMS_URL_CTX failed
DRG-11422: linguistic initialization failed
DRG-11446: supplied knowledge base file
/u01/oracle/orahome/11.2.0/ctx/data/enlx/droldUS.dat not installed
ORA-06512: at "SYS.DBMS_SQL", line 1199
ORA-06512: at line 96
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
jtfictx.sh exiting with status 1
ERRORCODE = 1 ERRORCODE_END
.end std out.
.end err out.
I usually backup the autoconfig/ context file before the refresh of EBS files from PROD. The previous refresh was performed 2 months ago and it was successful. There is no changes on database ORACLE_HOME as depicted in the error.
I see that someone have had asked similar error in forums and Hussein did recommend some Metalink Note. I did refer that but so far no success. Please do let me know if anyone faced similar issue and how did you solve it?
Notes Referred:
"Jtfictx.sh" Failed During Autoconfig On Application Tier, ORA-29874, DRG-10595 (Doc ID 1271186.1)
Autoconfig Failed On Apps Tier "jtfictx.sh INSTE8_PRF" . Running manually "jtfictx.sh " Failed on "DRG-10758: index owner does not have the privilege" (Doc ID 1357760.1)
Several Scripts Failing With A ORA-29855 Executing ODCIINDEXCREATE Routine During Upgrade To 12.1.1 (u6678700.drv) (Doc ID 1286033.1)
11i : Autoconfig Fails On The Application Tier in running jtfictx.sh (Doc ID 396174.1)
Thanks
Cherrish VaidiyanYes I did and below are the DB components from dba_registry:
Oracle Application Express APEX_030200 3.2.1.00.12 VALID
OLAP Catalog OLAPSYS 11.2.0.3.0 VALID
Oracle Data Mining DMSYS 11.2.0.3.0 VALID
Oracle XML Database XDB 11.2.0.3.0 VALID
Oracle Text CTXSYS 11.2.0.3.0 VALID
Spatial MDSYS 11.2.0.3.0 VALID
Oracle Multimedia ORDSYS 11.2.0.3.0 VALID
Oracle Database Catalog Views SYS 11.2.0.3.0 VALID
Oracle Database Packages and Types SYS 11.2.0.3.0 VALID
JServer JAVA Virtual Machine SYS 11.2.0.3.0 VALID
Oracle Database Java Packages SYS 11.2.0.3.0 VALID
Oracle XDK SYS 11.2.0.3.0 VALID
Oracle Real Application Clusters SYS 11.2.0.3.0 INVALID
OLAP Analytic Workspace SYS 11.2.0.3.0 VALID
Oracle OLAP API SYS 11.2.0.3.0 VALID
Only component invalid is RAC and I dont have RAC for this database.
Thanks
Cherrish Vaidiyan -
ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode
Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log
Maybe you are looking for
-
IPod mini windows - but own a mac
I got an iPod mini (1st generation) last year which is compatible with windows. But have just bought a new macbook. Will mini work on the macbook, and if not is there anything i can do to make it work with the macbook? Thanks go the socceroos!! MacBo
-
CVP 7.0(2) SIP RNA Timer with CUCM Hunt Group
I have a very simple ICM 7.5(9) script which simply assigns a call type then forwards to a label on CUCM 7.1(5), which is a hunt pilot containing a hunt list with 2 line groups...a circular LG with 10 members (RNA reversion timeout of 20 sec), follow
-
I added many songs to itunes that I didn't want on the ipod. I unchecked the boxes but when the ipod was connected it automatically updated the ipod and included all of the songs. Was there another step I was supposed to do? Thanks, JIm
-
How can we get help/advice amoungst each other? I have questions
How can we get help/advice amoungst each other? I have questions which might not be bug related and thought it would be nice if we could bounce questions off each other. Example: Why is my Reflow sample behaving like this? Should I have some kind of
-
Our ESS track has the following components checked in: SAP_ESS 603 sps2 EP_BUILDT nw7.0 sp16 SAP-JEE nw7.0 sp16 SAP_BUILDT nw7.0 sp16 SAP_JTECHS nw7.0 sp16 SAPPCUI_GP 600 sp13 In CBS we see our ESS/PER never builds successfully because of an error: d