Time for incomplete recovery.

Hello everybody! )
i have a backup of Oracle 10gR2 database using rman script:
run{
backup database;
backup archivelog all;
backup current control file;
i need restore this database on other server over 2 months
How can i find the time for incomplete database recovery.
Thanks.

Hello.
I have full backup of database plus archivelogs;
RMAN> list backupset summary;
Key-TY-LV-S-Device-Type-Completion_Time--------Pieces-Copies---Compressed Tag
1412---B--F--A DISK------26-11-2010 20:45:18 1-----1-----NO------TAG20101126T195011
1413---B--F--A DISK------26-11-2010 20:46:45 1-----1-----NO------TAG20101126T195011
1414---B--F--A DISK------26-11-2010 21:01:43 1-----1-----NO------TAG20101126T195011
1415---B--F--A DISK------26-11-2010 22:01:14 1-----1-----NO------TAG20101126T195011
1416---B--F--A DISK------27-11-2010 01:17:52 1-----1-----NO------TAG20101126T195011
1417---B--A--A DISK----- *27-11-2010 01:20:48* 1-----1-----NO------TAG20101127T011822
1418---B--A--A DISK------27-11-2010 01:20:49 1-----1-----NO------TAG20101127T011822
1419---B--A--A DISK------27-11-2010 01:20:51 1-----1-----NO------TAG20101127T011822
1420---B--A--A DISK------27-11-2010 01:20:59 1-----1-----NO------TAG20101127T011822
1421---B--A--A DISK------27-11-2010 01:21:08 1-----1-----NO------TAG20101127T011822
1422---B--A--A DISK------27-11-2010 01:21:42 1-----1-----NO------TAG20101127T011822
and i set until time to
set until time '27-11-2010 01:18:00';
restore database;
recover database;
but rman show error:
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
Edited by: OraUser on Nov 29, 2010 6:33 AM

Similar Messages

Is this cause for incomplete recovery?

Hi.
I read here http://download.oracle.com/docs/cd/B10501_01/server.920/a96519/recov.htm#1004797 and other places, the reasons for incomplete recovery. I see that "if a user drops a table.." we would consider incomplete recovery. That "data loss" means we need to recover ...
Yet what if the user simply deletes some rows from a table? If the user does not commit, do we still need to do incomplete recovery? Similarly, if the user does not commit, is that a reason for not using incomplete recovery?
Sorry for splitting hairs - but its important!
Thanks,
DA

Hi,
>>t if those few rows are gone forever (a committed delete), we would have to at least consider incomplete recovery??
The same thing ...
It is 12:00 AM and the EMP table was deleted or updated by mistake at 11:45 AM
Then you can:
1) shutdown the database and make a backup
2) restore all datafiles from most recent backup
3) mount the database
4) recover the database like below:
SQL> recover database until time '2008-03-30:11:44:00'
5) synchronize the datafile with control files and redo log files like below:
SQL> alter database open resetlogs
6) Make a backup of your databaseIn this case, time-based recovery, also called point-in-time recovery (PITR), recovers the data up to a specified point in time.
Ps: Disadvantage of using this method: Any data entered after the recovery time (11:44 AM) will need to be reentered ...
Cheers
Legatti

Link for Incomplete recovery.

Hi please post a link on "Incomplete Recovery" in oracle 9i.

http://download.oracle.com/docs/cd/B10501_01/server.920/a96572/ostspitr.htm#BRUMG007
http://download.oracle.com/docs/cd/B10501_01/server.920/a96519/recov.htm#1004797
-Anantha

Reasonable time for instance recovery in RAC

Hi,
We're running with Oracle RAC configuration. The configuration is 2 instances one active one passive and we simulate failure of the active instance under load of ~1500 transactions per second.
In our tests we're seeing that between failure time until 2nd passive instance is taking responsibility it might take more than 1 or 2 minutes.
The question is: Is this behavior is reasonable? Fine - what SLA we can expect in those scenarios? other scenarios?
Where can we read about this in details.
Thank you,
Moshe

user12187426 wrote:
Harish Kumar Kalra wrote:
SLA depends on your business requirement but wrt to recovery of the second instance, this looks reasonable based on 1500 active transactions and induced failure on first instance. Look at FAST_START_MTTR_TARGET parameter to tune this further.
Ta
I am not agree with this, 1500 transaction per second if you lost it in 2 mins that means 180000 transaction. If one transaction worth of $1 then you have loose $180000
and I don't think FAST_START_MTTR_TARGET, this will make checkpoint to occur more frequent hence make overall performance degrated
ThxYes, but if you're starting to calculate in that kind of numbers, then I'm wondering why they use an active/passive config.
Regards
FJFranken

Incomplete Recovery After Drop Tablespace.

Hi...some technical help required.
I was trying a hands-on for incomplete recovery. That is drop a tablespace and then retrieve back until 1 second before drop statement.
The Steps were like this...
1) Shutdown Immediate;
2) Copy all *.ctl, *.dbf, logfiles into a different folder <nis_back>
3) Startup;
4) Enter 3-4 Records and Commit. Table is in <USER> Tablespace.
5) 3 times "alter system switch logfile;"
5) drop tablespace users;
6) shutdown;
7) Check the Alter Log and find the time when tablespace dropped.
Suppose time when dropped is -> 21-Aug 10:30:45 AM. (HH:MM:SS)
7) copy back only *.dbf, *.ctl files from backup folder <nis_back>
8) startup mount;
9) alter database recover automatic until time '2002-08-21:10:30:40';
10) <<Statement Process>> Message Comes.
11) alter database open resetlogs;
When I open the table into which I inserted records just before dropping the tablespace I dont see the records (Inseretd in Step - 4) but the tablespace is back.
Now My Concern -> Why did the 3-4 record which I inserted in step 4 did not get restored from the archieve log ?
Hope to hear from you all soon.
Thanks in advance.
Regards
Nishit

After step 5, try ALTER SYSTEM ARCHIVELOG ALL
Naveen
Hi...some technical help required.
I was trying a hands-on for incomplete recovery. That is drop a tablespace and then retrieve back until 1 second before drop statement.
The Steps were like this...
1) Shutdown Immediate;
2) Copy all *.ctl, *.dbf, logfiles into a different folder <nis_back>
3) Startup;
4) Enter 3-4 Records and Commit. Table is in <USER> Tablespace.
5) 3 times "alter system switch logfile;"
5) drop tablespace users;
6) shutdown;
7) Check the Alter Log and find the time when tablespace dropped.
Suppose time when dropped is -> 21-Aug 10:30:45 AM. (HH:MM:SS)
7) copy back only *.dbf, *.ctl files from backup folder <nis_back>
8) startup mount;
9) alter database recover automatic until time '2002-08-21:10:30:40';
10) <<Statement Process>> Message Comes.
11) alter database open resetlogs;
When I open the table into which I inserted records just before dropping the tablespace I dont see the records (Inseretd in Step - 4) but the tablespace is back.
Now My Concern -> Why did the 3-4 record which I inserted in step 4 did not get restored from the archieve log ?
Hope to hear from you all soon.
Thanks in advance.
Regards
Nishit

Finding exact time for sequence change

Hi,
for incomplete recovery purpose , i want to know the exact timing of sequence number change or SCN change...i tried some of the views like v$loghist, V$log_history..provide only date ..these didnt provide exact time...
SQL> select * from v$loghist;
THREAD# SEQUENCE# FIRST_CHANGE# FIRST_TIM SWITCH_CHANGE#
1 1 944409 31-MAY-09 945995
1 2 945995 31-MAY-09 947470
Oracle 9.3
Redhat 5.3
Thank u
selva..

Connected to:
Oracle Database 10g Release 10.2.0.4.0 - Production
SQL> alter session set nls_date_format='dd.mm.yyyy hh24:mi:ss';
Session altered.
SQL> select * from v$loghist where rownum < 10;
   THREAD# SEQUENCE# FIRST_CHANGE# FIRST_TIME          SWITCH_CHANGE#
         1       2035     760254081 28.04.2009 00:45:41      760391689
         1       2036     760391689 28.04.2009 06:30:44      760479542
         1       2037     760479542 28.04.2009 10:18:58      760566251
         1       2038     760566251 28.04.2009 11:18:23      760686034
         1       2039     760686034 28.04.2009 11:33:20      760802082
         1       2040     760802082 28.04.2009 12:00:44      760916445
         1       2041     760916445 28.04.2009 12:18:07      761027875
         1       2042     761027875 28.04.2009 12:33:28      761147250
         1       2043     761147250 28.04.2009 12:49:01      761262830
9 rows selected.

How do I send instance for manual recovery at run time.

Hi
I have a BPEL process within which I am trying to handle a business error. I understand using the default-policies on the application server I can send a message for manual recovery. But is it possible to force an instance into the manual recovery queue in the event of a handled error?
I have previosuly used the default policies to route remote/binding faults to the activities tab (manual recovery) tab and the users find this useful to adjust XM land retry, re-throw etc. But can we do the same for errors handled within the BPEL. So if I have a catch all within my process how would I send the instance to this manual recovery queue.
Thanks
Rich

I hate it when after an hour's searching I post a question
and then find the answer ten minutes later...
"Current VI's Path" on the file IO palette...
Bob

An error occurred during the process of recovery(incomplete recovery)

Hi,
I have a HP envy m6 1154ez. When I tried to restore to factory default I have an error incomplete recovery
Can someone tell me how to fix this or what needs to be done to get my Windows working again, any help would be greatly appreciated.
Report an error,
Component: Windows 8 Preinstall Diagnostic Tools - TDC
Timing: FactoryUpdate
Regional SKU: No
RCTO Image: No
Error: Mismatched option code (LOC#ACB) for dash code (-BGx)
Error: Option code LOC#ACB should use dash code -25x
Next Step: Please dash image SKU number with xxxxxx-25x
Next Step: Or change LOC# in SKU Number or CTO Localization Code via EEPROM
[ 0:17:59.87] ------------------------------------------------------------------------------------------
***CTO Error condition has been dtected in [Factory Update] phase !! ***
[ 0:17:59.87] Suggest to create PIN-log and send to TWN PDC NB-PreinPM for further analysis ...
[ 0:17:59.87] ------------------------------------------------------------------------------------------
[ 0:16:27.91] Start BBOffline.cmd...
UPDrv=[C:]
[ 0:16:27.92] Set UIA Error Code to 951
[ 0:16:28.12] Delete [FBI] folder.
[ 0:16:28.14] WinPE is 64bit.
[ 0:16:37.29] Starts [FixUps].
[ 0:16:37.34] ---------------------------------------------------------------------
[ 0:16:37.34] FixUps.cmd...
[ 0:16:40.59] FixUps.cmd completed...
[ 0:16:40.59] ---------------------------------------------------------------------
[ 0:16:40.59] Starts [Tweaks for SSRD].
[ 0:16:40.63] ---------------------------------------------------------------------
[ 0:16:40.63] SSRD Tweaks to change user default locale...
[ 0:16:40.63] Copy C:\System.sav\Util\TDC\MCPP\FBIRES\FBIGRRES.DLL.
[ 0:16:40.84] Run "Dism.exe /image:C:\ /Set-SKUIntlDefaults:de-DE ".
[ 0:16:52.90] ---------------------------------------------------------------------
[ 0:16:52.92] Launch PININST.exe for Offline ...
[ 0:16:56.54] Starts [Sleep 10 sec].
[ 0:17:06.58] Starts [Create RStoneFUpdate.INI].
[ 0:17:07.18] Starts [create 1GB Pagefile for offline].
Volume in drive C has no label.
Volume Serial Number is 8025-9CBE
Directory of C:\System.sav\bbv
04/04/2015 12:17 AM 1,073,741,824 pagefile.sys
1 File(s) 1,073,741,824 bytes
0 Dir(s) 90,616,721,408 bytes free
[ 0:17:07.28] Brand detection.
[ 0:17:07.33] Customize error handling for Specialize ~ BBV1.
0 file(s) copied.
[ 0:17:07.34] ---------------------------------------------------------------------
[ 0:17:17.11] Check Win 8 configuration...
[ 0:17:18.11] Check system ID...
[ 0:17:19.12] Check OS SKU...
[ 0:17:20.12] Check option code...
[ 0:17:21.12] Check brand name...
SKU_DEF_COUNTRY=[203]
SKU_DEF_SYS_LOC=[ru-RU]
Reset country in administrator...
Reset country in Default user...
Reset System locale
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
Reporting offline international settings.
Default system UI language : de-DE
System locale : ru-RU
Default time zone : W. Europe Standard Time
User locale for default user : de-DE
Location : Russia (GEOID = 203)
Active keyboard(s) : 0407:00000407
Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)
Installed language(s): de-DE
Type : Fully localized language.
Installed language(s): en-GB
Type : Partially localized language, MUI type.
Fallback Languages en-US
Installed language(s): fr-FR
Type : Fully localized language.
Installed language(s): it-IT
Type : Fully localized language.
The operation completed successfully.
Updated System Locale info...
[ 0:17:34.16] Start PIN Tweaks...
[ 0:17:35.20] ---------------------------------------------------------------------
[ 0:17:35.20] PIN Tweaks to hide All for BurnBoot BBV and BBV2 on restored image...
[ 0:17:35.20] ----------------------------------------
[ 0:17:35.20] Tweaks for OOBE's Unattend.xml
[ 0:17:35.20] to pick up the proper file...
[ 0:17:35.20] ----------------------------------------
[ 0:17:35.20] rename unattend.org to unattend.or_
[ 0:17:35.24] ----------------------------------------
[ 0:17:35.24] without Light Sensor..
[ 0:17:35.24] ----------------------------------------
[ 0:17:35.24] update unattend.reg for Minimized Image Recovery...
[ 0:17:35.27] This is Restored image [RImage.flg]...
[ 0:17:35.27] ---------------------------------------------------------------------
[ 0:17:36.15] Start MIR Tweaks...
[ 0:17:37.22] ---------------------------------------------------------------------
[ 0:17:37.22] [MIR Tweaks] ...
[ 0:17:37.22] ----------------------------------------
[ 0:17:37.22] apply Device Path registry for MIR image
[ 0:17:37.22] ----------------------------------------
[ 0:17:38.21] ---------------------------------------------------------------------
[ 0:17:43.18] Start Factory Update(s)...
[ 0:17:55.19] Start QFE Offline installation...
[ 0:17:59.78] PININST_OFF: PASSED...
[ 0:17:59.80] Type C:\System.sav\Logs\BBFindEr.log...
[ 0:17:59.80] Type C:\System.sav\Logs\BBFindE0.log...
---------- C:\SYSTEM.SAV\LOGS\PININST_OFF.LOG
Result=PASSED
[ 0:17:59.81] There was no QFE installation...
[ 0:17:59.81] Check FUList.log if there is duplicate Desc...
No duplication.
[ 0:17:59.86] No Duplicated Desc is found... PASSED.
[ 0:17:59.86] There was no Factory Update...

Hi @artem98765,
Welcome to the HP Forums!
It is a terrific place to find answers and suggestions.
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I grasp that when you tried to do a recovery back to factory you received the error incomplete recovery.
As you did not state if how you were doing the recovery I will include documentation for the process along with a troubleshooting document.
HP PCs - Performing an HP system recovery (Windows 8)
HP PCs - Troubleshooting HP System Recovery Problems (Windows 8)
If you are still unable to complete the recovery please contact HP support for further assistance.
Please call our technical support at 800 474 6836. If you live outside the US/Canada Region, please click the link below to get a support number for your region.
World Wide Phone Support
Good Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

A problem about incomplete recovery

All,
I'm a freshman for oracle knowledge and skill. I'm simulating the incomplete recovery for database. Here are my scenarios and steps:
1. In database "db1", there is a table named "tb1" has 2 records, the whole database running on archive log mode and has 3 redo log groups(each group contains one member) ---- status "A"
2. Make a cold backup for all datafiles, controlfiles and redo logs;
3. startup database again, and insert 3 records into "tb1", then switch log file at least 3 times. Get the frist change number form latest archived log. ---- status "B"
4. after the 3rd step over, drop a tablespace named "indx" and do a switching log file operation again.
5. shutdow database immediate and restore all the backuped datafile and controlfiles, not including the redo logs and startup database with mount option.
6. run recover command to execute the incomplete recovery to database.
whatever using "recover until time '<almost close the drop operating time>" or "recover until change number", I only got the status "A" after open the database, not status "B". But as my understanding and some reference from books, it should return to status "B" which includes the newer 3 records.
Now, I adhere some alert logs at below (the number 54878 is the latest change number in archived log files before dropping that tablespace)
alter database recover until change 54878
Tue Jul 03 17:30:34 2007
Media Recovery Start
Media Recovery Not Required
Completed: alter database recover until change 54878
Tue Jul 03 17:31:35 2007
alter database open resetlogs
Tue Jul 03 17:31:35 2007
RESETLOGS after complete recovery through change 54742
why the recovery use change number 54742 but not 54878 I expected. Did I go the correct steps for this incomplete recovery. Does anyone can give me some piece of advice to resolve this problem

Are you using 'recover using backup controlfile'...???????????
If not, it will take the restored controlfiles as the latest copy and will only recover up to the SCN in there.
Using the above, Oracle will simply ignore the SCN in the controlfile, since it knows its an old controlfile and should recover beyond the restored controfile..

Incomplete recovery in Oracle 10g

hello,
I have been trying Incomplete recovery in oracle 10g. The steps i did were.
1. Set the database in archivelog mode.
2. shutdown immediate
3. Take physical copies of control files, datafiles and redo files
4. open the database.
5. Insert three rows in test table and commit. (and note the time )
6. shutdown abort
7. copy the restored datafiles to the desired location
8. startup mount
9 recover database until time (the time noted in step 5)
10. alter database open resetlogs
After doing this, i still do not get the three records inserted in step 5.
Can anyone suggest why this is so ? am i missing something. ?
Thanx.
Trupti

Hello,
Thank you for the prompt reply.
I did what you suggested. Here are the output.
16:17:52 SQL> select * from testing.test;
NO
1
2
3
4
17:09:26 SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
*** Here i took a backup of all files.
17:10:16 SQL> startup mount;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 788224 bytes
Variable Size 66058496 bytes
Database Buffers 100663296 bytes
Redo Buffers 262144 bytes
Database mounted.
17:13:45 SQL> alter database open;
Database altered.
17:14:07 SQL> alter system switch logfile;
System altered.
17:14:17 SQL> select * from testing.test;
NO
1
2
3
4
17:14:25 SQL> insert into testing.test values(5);
1 row created.
17:14:40 SQL> insert into testing.test values(6);
1 row created.
17:14:43 SQL> insert into testing.test values(7);
1 row created.
17:14:45 SQL> commit;
Commit complete.
17:14:47 SQL> alter system switch logfile;
System altered.
17:14:50 SQL> insert into testing.test values(8);
1 row created.
17:14:55 SQL> insert into testing.test values(9);
1 row created.
17:14:57 SQL> insert into testing.test values(10);
1 row created.
17:15:00 SQL> commit;
Commit complete.
17:15:02 SQL> alter system switch logfile;
System altered.
17:15:04 SQL> shutdown abort;
ORACLE instance shut down.
*** Here i restored the datafiles
17:15:15 SQL> startup mount;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 788224 bytes
Variable Size 66058496 bytes
Database Buffers 100663296 bytes
Redo Buffers 262144 bytes
Database mounted.
17:18:09 SQL> recover database until time '2004-12-05:17:14:45';
ORA-00279: change 402561 generated at 12/05/2004 17:10:03 needed for thread 1
ORA-00289: suggestion :
G:\ORACLE10G\ORADATA\NEWTEST\ARCHIVE\ARC00002_0544119450.001
ORA-00280: change 402561 for thread 1 is in sequence #2
17:18:43 Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
Media recovery complete.
17:19:20 SQL>
17:19:51 SQL> alter database open resetlogs;
Database altered.
17:20:33 SQL> select * from testing.test;
NO
1
2
3
4

Incomplete recovery after open resetlogs

hi gurus
Every sunday,consistent backups are performed on your database.Because of a user error,you performed an incomplete recovery on Tuesday and opened the database with RESETLOGS option.
A user error occurs again on Thursday,whick necessitates an incomplete recovery.Sunday's bakcup is the most recent backup avaliable.
what would you do in this scenario？
A. recovery cannot be performed because backup was not performed after the last incomplete recovery.
B. restore all backups from Sunday's backup,and then perform an incomplete recovery up to the point in time when the user error occured Thursday.
C. restore all the files from Sunday's backup,and then recover up to the point in time when the RESETLOGS operation was performed on Tuesday.
D. restore all the file from Sunday's backup, and open the database to reset the database to the point in time when the backup was performed on Sunday.
I choose C but answer gives B. what do u think?
thank u in advance.

As of oracle 10g, it is possible to restore and recover across RESETLOGS operations: see http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/flashptr006.htm#sthref667. So B is correct for 10g or 11g.

Question on Incomplete recovery

Hello all,
I am using Oracle Enterprise edition on windows vista.
I am trying to perform an Incomplete recovery using 'recover database until time'. The format is 'YYYY-MM-DD:HH24:MI:SS'
My question is how to view the time to seconds to recover the database using archived log. Is there any v$dictionary where I can view the timestamp for archived log, i know there is v$archived_log, but don't see the relevant one?
Secondly, view a list of scn to recover the database to using 'recover database until change';?
Kindly help.
Thanks!
null
null

that only provides the date and not the time?
SQL> select first_time from v$archived_log;
FIRST_TIME
10-APR-08
12-APR-08
13-APR-08
13-APR-08
13-APR-08
13-APR-08It provides a timestamp. It is formatted according to your nls_date_format setting. to display the whole of a date you'll need to either
a) set nls_date_format appropriately
b) use a to_char function around the column.
I personally set nls_date_format to 'DD-MON-YYYY HH24:MI' in my glogin file and use a to_char for any other format.
Niall Litchfield
http://www.orawin.info/

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

Outbound Order Confirmation - Output control for incomplete sales orders

Hi EDI Folks,
I have a simple question. I want to send EDI 855 for only the completed sales orders.
Whenever inbound sales order is processed and if the order is incomplete. I don't want to send the order confirmation for the order at that point of time. When that order is made complete, then only i want to send the order confirmation (EDI 855).
How can we do it??
What is the output determination requirement for this??
Right now i am using requirement '02' which proposes EDI output for both complete and incomplete sales orders.
Please respond to the above quesition.
Thanks and waiting for your reply,
Creasy Matt

MxG,
For both plant and pricing condition functional config was already done. If any of these two fields are missing, the status of sales order will be incomplete.For incomplete orders also, the EDI output is being proposed.
Now just tell me, in which SAP program, do i have to put the break point?
Where exactly ??
Thanks and kind regards,
Creasy Matt

Time for incomplete recovery.

Similar Messages

Maybe you are looking for