Last month my client encountered an error ORA-01547, ORA-01194 and ORA-01110 when he performed Oracle RMAN restore and recover operation to a specified time on a test server. Yes, he acquired the RMAN backupset (the full backup and cumulative incremental backup that is the closest to the specified time) from other server that saved all of RMAN backupsets with exceeding the rman retention policy, and then copied them to the test server. Hence he asked for some help from me.
Next I connected his computer by the secure remote connect tool and spent some time troubleshooting those errors. Finally I’ve recovered his oracle database successfully.
Now I’ll share how to tackle the issue mentioned previously in this blog post.
We can use OS command “oerr ora 01547” to check the related section of the Cause and Action as below.
[oracle@xxxx ~]$ oerr ora 01547
01547, 00000, "warning: RECOVER succeeded but OPEN RESETLOGS would get error below"
// *Cause: Media recovery with one of the incomplete recovery options ended
// without error. However, if the ALTER DATABASE OPEN RESETLOGS command
// were attempted now, it would fail with the specified error.
// The most likely cause of this error is forgetting to restore one or
// more datafiles from a sufficiently old backup before executing the
// incomplete recovery.
// *Action: Rerun the incomplete media recovery using different datafile
// backups, a different control file, or different stop criteria
As we can see from the above description it’s the incomplete recovery before open resetlogs. Here’re some important steps which the client has provided to me.
RMAN> run {
allocate channel c1 type disk;
allocate channel c2 type disk;
sql 'alter session set nls_date_format="yyyy-mm-dd hh24:mi:ss"';
set until time ='2022-12-31 23:00:00';
restore database;
recover database;
alter database open resetlogs;
}2> 3> 4> 5> 6> 7> 8> 9>
allocated channel: c1
channel c1: SID=541 device type=DISK
allocated channel: c2
channel c2: SID=618 device type=DISK
sql statement: alter session set nls_date_format="yyyy-mm-dd hh24:mi:ss"
executing command: SET until clause
Starting restore at 14-JAN-23
channel c1: starting datafile backup set restore
channel c1: specifying datafile(s) to restore from backup set
channel c1: restoring datafile 00003 to /XXXdata/XXX/XXXdata1/undotbs01.dbf
channel c1: restoring datafile 00006 to /XXXdata/XXX/XXXdata2/XXXdata_02.dbf
channel c1: restoring datafile 00008 to /XXXdata/XXX/XXXdata2/XXXdata_04.dbf
channel c1: restoring datafile 00010 to /XXXdata/XXX/XXXdata2/XXXdata_06.dbf
channel c1: restoring datafile 00012 to /XXXdata/XXX/XXXdata2/XXXdata_08.dbf
channel c1: restoring datafile 00014 to /XXXdata/XXX/XXXdata3/XXXdata_10.dbf
channel c1: restoring datafile 00016 to /XXXdata/XXX/XXXdata3/XXXdata_12.dbf
channel c1: restoring datafile 00018 to /XXXdata/XXX/XXXdata3/XXXdata_14.dbf
channel c1: restoring datafile 00020 to /XXXdata/XXX/XXXdata3/XXXdata_16.dbf
channel c1: restoring datafile 00022 to /XXXdata/XXX/XXXdata3/yyyyyy1.dbf
channel c1: restoring datafile 00023 to /XXXdata/XXX/XXXdata3/yyyyyy2.dbf
channel c1: restoring datafile 00024 to /XXXdata/XXX/XXXdata1/userdata1.dbf
channel c1: restoring datafile 00027 to /XXXdata/XXX/XXXdata1/bbbbb03.dbf
channel c1: restoring datafile 00028 to /XXXdata/XXX/XXXdata3/bbbbb04.dbf
channel c1: restoring datafile 00030 to /XXXdata/XXX/XXXdata3/XXXdata_18.dbf
channel c1: restoring datafile 00032 to /XXXdata/XXX/XXXdata3/yyyyyy4.dbf
channel c1: restoring datafile 00033 to /XXXdata/XXX/XXXdata3/XXXdata20.dbf
channel c1: restoring datafile 00035 to /XXXdata/XXX/XXXdata3/XXXdata_22.dbf
channel c1: restoring datafile 00037 to /XXXdata/XXX/XXXdata3/XXXdata_24.dbf
channel c1: restoring datafile 00039 to /XXXdata/XXX/XXXdata3/XXXdata_26.dbf
channel c1: restoring datafile 00041 to /XXXdata/XXX/XXXdata3/XXXdata27.dbf
channel c1: restoring datafile 00043 to /XXXdata/XXX/XXXdata3/XXXdata_29.dbf
channel c1: restoring datafile 00045 to /XXXdata/XXX/XXXdata3/XXXdata_30.dbf
channel c1: restoring datafile 00047 to /XXXdata/XXX/XXXdata3/yyyyyy6.dbf
channel c1: restoring datafile 00049 to /XXXdata/XXX/XXXdata3/bbbbb08.dbf
channel c1: restoring datafile 00051 to /XXXdata/XXX/XXXdata3/bbbbb10.dbf
channel c1: restoring datafile 00052 to /XXXdata/XXX/XXXdata2/bbbbb11.dbf
channel c1: restoring datafile 00054 to /XXXdata/XXX/XXXdata3/XXXdata_31.dbf
channel c1: restoring datafile 00056 to /XXXdata/XXX/XXXdata2/bbbbb12.dbf
channel c1: restoring datafile 00058 to /XXXdata/XXX/XXXdata2/bbbbb13.dbf
channel c1: restoring datafile 00060 to /XXXdata/XXX/XXXdata3/yyyyyy8.dbf
channel c1: restoring datafile 00062 to /XXXdata/XXX/XXXdata3/XXXdata_35.dbf
channel c1: restoring datafile 00064 to /XXXdata/XXX/XXXdata2/bbbbb16.dbf
channel c1: restoring datafile 00066 to /XXXdata/XXX/XXXdata2/bbbbb18.dbf
channel c1: restoring datafile 00068 to /XXXdata/XXX/XXXdata2/bbbbb20.dbf
channel c1: restoring datafile 00070 to /XXXdata/XXX/XXXdata3/XXXdata_37.dbf
channel c1: restoring datafile 00073 to /XXXdata/XXX/XXXdata2/bbbbb21.dbf
channel c1: restoring datafile 00074 to /XXXdata/XXX/XXXdata3/yyyyyy10.dbf
channel c1: restoring datafile 00076 to /XXXdata/XXX/XXXdata2/bbbbb23.dbf
channel c1: restoring datafile 00078 to /XXXdata/XXX/XXXdata2/bbbbb25.dbf
channel c1: restoring datafile 00080 to /XXXdata/XXX/XXXdata3/yyyyyy12.dbf
channel c1: restoring datafile 00082 to /XXXdata/XXX/XXXdata3/XXXdata_40.dbf
channel c1: restoring datafile 00084 to /XXXdata/XXX/XXXdata3/XXXdata_42.dbf
channel c1: restoring datafile 00086 to /XXXdata/XXX/XXXdata3/XXXdata_44.dbf
channel c1: restoring datafile 00089 to /XXXdata/XXX/XXXdata3/XXXdata_46.dbf
channel c1: restoring datafile 00091 to /XXXdata/XXX/XXXdata3/XXXdata_48.dbf
channel c1: restoring datafile 00093 to /XXXdata/XXX/XXXdata3/XXXdata_50.dbf
channel c1: restoring datafile 00095 to /XXXdata/XXX/XXXdata3/XXXdata_52.dbf
channel c1: restoring datafile 00097 to /XXXdata/XXX/XXXdata3/XXXdata_54.dbf
channel c1: reading from backup piece /tools/backup/FULL/XXX_L0_249543_1_1124838005
channel c2: starting datafile backup set restore
channel c2: specifying datafile(s) to restore from backup set
channel c2: restoring datafile 00001 to /XXXdata/XXX/XXXdata1/system01.dbf
channel c2: restoring datafile 00002 to /XXXdata/XXX/XXXdata1/sysaux01.dbf
channel c2: restoring datafile 00004 to /XXXdata/XXX/XXXdata1/users01.dbf
channel c2: restoring datafile 00005 to /XXXdata/XXX/XXXdata2/XXXdata_01.dbf
channel c2: restoring datafile 00007 to /XXXdata/XXX/XXXdata2/XXXdata_03.dbf
channel c2: restoring datafile 00009 to /XXXdata/XXX/XXXdata2/XXXdata_05.dbf
channel c2: restoring datafile 00011 to /XXXdata/XXX/XXXdata2/XXXdata_07.dbf
channel c2: restoring datafile 00013 to /XXXdata/XXX/XXXdata2/XXXdata_09.dbf
channel c2: restoring datafile 00015 to /XXXdata/XXX/XXXdata3/XXXdata_11.dbf
channel c2: restoring datafile 00017 to /XXXdata/XXX/XXXdata3/XXXdata_13.dbf
channel c2: restoring datafile 00019 to /XXXdata/XXX/XXXdata3/XXXdata_15.dbf
channel c2: restoring datafile 00021 to /XXXdata/XXX/XXXdata3/XXXdata_17.dbf
channel c2: restoring datafile 00025 to /XXXdata/XXX/XXXdata1/bbbbb01.dbf
channel c2: restoring datafile 00026 to /XXXdata/XXX/XXXdata2/bbbbb02.dbf
channel c2: restoring datafile 00029 to /XXXdata/XXX/XXXdata3/yyyyyy3.dbf
channel c2: restoring datafile 00031 to /XXXdata/XXX/XXXdata3/XXXdata_19.dbf
channel c2: restoring datafile 00034 to /XXXdata/XXX/XXXdata3/XXXdata_21.dbf
channel c2: restoring datafile 00036 to /XXXdata/XXX/XXXdata3/XXXdata_23.dbf
channel c2: restoring datafile 00038 to /XXXdata/XXX/XXXdata3/XXXdata_25.dbf
channel c2: restoring datafile 00040 to /XXXdata/XXX/XXXdata3/yyyyyy5.dbf
channel c2: restoring datafile 00042 to /XXXdata/XXX/XXXdata3/XXXdata_28.dbf
channel c2: restoring datafile 00044 to /XXXdata/XXX/XXXdata3/bbbbb05.dbf
channel c2: restoring datafile 00046 to /XXXdata/XXX/XXXdata3/bbbbb06.dbf
channel c2: restoring datafile 00048 to /XXXdata/XXX/XXXdata3/bbbbb07.dbf
channel c2: restoring datafile 00050 to /XXXdata/XXX/XXXdata3/bbbbb09.dbf
channel c2: restoring datafile 00053 to /XXXdata/XXX/XXXdata3/yyyyyy7.dbf
channel c2: restoring datafile 00055 to /XXXdata/XXX/XXXdata3/XXXdata_32.dbf
channel c2: restoring datafile 00057 to /XXXdata/XXX/XXXdata3/XXXdata_33.dbf
channel c2: restoring datafile 00059 to /XXXdata/XXX/XXXdata2/bbbbb14.dbf
channel c2: restoring datafile 00061 to /XXXdata/XXX/XXXdata3/XXXdata_34.dbf
channel c2: restoring datafile 00063 to /XXXdata/XXX/XXXdata2/bbbbb15.dbf
channel c2: restoring datafile 00065 to /XXXdata/XXX/XXXdata2/bbbbb17.dbf
channel c2: restoring datafile 00067 to /XXXdata/XXX/XXXdata2/bbbbb19.dbf
channel c2: restoring datafile 00069 to /XXXdata/XXX/XXXdata3/XXXdata_36.dbf
channel c2: restoring datafile 00071 to /XXXdata/XXX/XXXdata3/XXXdata_38.dbf
channel c2: restoring datafile 00072 to /XXXdata/XXX/XXXdata3/yyyyyy9.dbf
channel c2: restoring datafile 00075 to /XXXdata/XXX/XXXdata2/bbbbb22.dbf
channel c2: restoring datafile 00077 to /XXXdata/XXX/XXXdata2/bbbbb24.dbf
channel c2: restoring datafile 00079 to /XXXdata/XXX/XXXdata3/yyyyyy11.dbf
channel c2: restoring datafile 00081 to /XXXdata/XXX/XXXdata3/XXXdata_39.dbf
channel c2: restoring datafile 00083 to /XXXdata/XXX/XXXdata3/XXXdata_41.dbf
channel c2: restoring datafile 00085 to /XXXdata/XXX/XXXdata3/XXXdata_43.dbf
channel c2: restoring datafile 00087 to /XXXdata/XXX/XXXdata3/yyyyyy13.dbf
channel c2: restoring datafile 00088 to /XXXdata/XXX/XXXdata3/XXXdata_45.dbf
channel c2: restoring datafile 00090 to /XXXdata/XXX/XXXdata3/XXXdata_47.dbf
channel c2: restoring datafile 00092 to /XXXdata/XXX/XXXdata3/XXXdata_49.dbf
channel c2: restoring datafile 00094 to /XXXdata/XXX/XXXdata3/XXXdata_51.dbf
channel c2: restoring datafile 00096 to /XXXdata/XXX/XXXdata3/XXXdata_53.dbf
channel c2: restoring datafile 00098 to /XXXdata/XXX/XXXdata3/XXXdata_55.dbf
channel c2: reading from backup piece /tools/backup/FULL/XXX_L0_249544_1_1124838005
channel c1: piece handle=/tools/backup/FULL/XXX_L0_249543_1_1124838005 tag=XXX_L0_BAK
channel c1: restored backup piece 1
channel c1: restore complete, elapsed time: 05:57:38
channel c2: piece handle=/tools/backup/FULL/XXX_L0_249544_1_1124838005 tag=XXX_L0_BAK
channel c2: restored backup piece 1
channel c2: restore complete, elapsed time: 06:00:58
Finished restore at 14-JAN-23
Starting recover at 14-JAN-23
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: '/XXXdata/XXX/XXXdata1/system01.dbf'
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/14/2023 17:48:33
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 302708 and starting SCN of 26776466150 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302707 and starting SCN of 26776433473 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302706 and starting SCN of 26776433444 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302705 and starting SCN of 26776399435 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302704 and starting SCN of 26776399410 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302703 and starting SCN of 26776369626 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302702 and starting SCN of 26776369609 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302701 and starting SCN of 26776360947 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302700 and starting SCN of 26776360936 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302699 and starting SCN of 26776351505 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302698 and starting SCN of 26776351492 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302697 and starting SCN of 26776344046 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302696 and starting SCN of 26776344034 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302695 and starting SCN of 26776333909 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302694 and starting SCN of 26776333884 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302693 and starting SCN of 26776301722 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302692 and starting SCN of 26776301680 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302691 and starting SCN of 26776268739 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302690 and starting SCN of 26776268706 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302689 and starting SCN of 26776235413 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302688 and starting SCN of 26776235373 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302687 and starting SCN of 26776170046 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302686 and starting SCN of 26776170037 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302685 and starting SCN of 26776159596 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302684 and starting SCN of 26776159584 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302683 and starting SCN of 26776148399 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302682 and starting SCN of 26776148388 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302681 and starting SCN of 26776139831 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302680 and starting SCN of 26776139812 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302679 and starting SCN of 26776128484 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302678 and starting SCN of 26776128464 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302677 and starting SCN of 26776095045 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302676 and starting SCN of 26776095013 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302675 and starting SCN of 26776060452 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302674 and starting SCN of 26776060424 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302673 and starting SCN of 26776023966 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302672 and starting SCN of 26776023896 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302671 and starting SCN of 26775984796 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302670 and starting SCN of 26775984744 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302669 and starting SCN of 26775967133 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302668 and starting SCN of 26775967122 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302667 and starting SCN of 26775950637 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302666 and starting SCN of 26775950625 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302665 and starting SCN of 26775934506 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302664 and starting SCN of 26775934493 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302663 and starting SCN of 26775918627 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302662 and starting SCN of 26775918593 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302661 and starting SCN of 26775883104 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302660 and starting SCN of 26775883067 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302659 and starting SCN of 26775842285 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302658 and starting SCN of 26775842237 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302657 and starting SCN of 26775799909 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302656 and starting SCN of 26775799846 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302655 and starting SCN of 26775732483 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302654 and starting SCN of 26775732454 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302653 and starting SCN of 26775714118 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302652 and starting SCN of 26775714094 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302651 and starting SCN of 26775698437 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302650 and starting SCN of 26775698424 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302649 and starting SCN of 26775682578 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302648 and starting SCN of 26775682567 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302647 and starting SCN of 26775666207 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302646 and starting SCN of 26775666172 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302645 and starting SCN of 26775630257 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302644 and starting SCN of 26775630232 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302643 and starting SCN of 26775594492 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302642 and starting SCN of 26775594454 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302641 and starting SCN of 26775558702 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302640 and starting SCN of 26775558663 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302639 and starting SCN of 26775518973 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302638 and starting SCN of 26775518946 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302637 and starting SCN of 26775504453 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302636 and starting SCN of 26775504444 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302635 and starting SCN of 26775491401 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302634 and starting SCN of 26775491377 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302633 and starting SCN of 26775478020 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302632 and starting SCN of 26775478000 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302631 and starting SCN of 26775463475 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302630 and starting SCN of 26775463425 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302629 and starting SCN of 26775427270 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302628 and starting SCN of 26775427231 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302627 and starting SCN of 26775388068 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302626 and starting SCN of 26775388035 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302625 and starting SCN of 26775348400 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302624 and starting SCN of 26775348342 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302623 and starting SCN of 26775265222 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302622 and starting SCN of 26775265182 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302621 and starting SCN of 26775248965 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302620 and starting SCN of 26775248950 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302619 and starting SCN of 26775238030 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302618 and starting SCN of 26775238019 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302617 and starting SCN of 26775225426 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302616 and starting SCN of 26775225410 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302615 and starting SCN of 26775213300 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302614 and starting SCN of 26775213281 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302613 and starting SCN of 26775178928 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302612 and starting SCN of 26775178899 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302611 and starting SCN of 26775143517 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302610 and starting SCN of 26775143490 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302609 and starting SCN of 26775109108 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302608 and starting SCN of 26775109056 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302607 and starting SCN of 26775067925 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302606 and starting SCN of 26775067899 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302605 and starting SCN of 26775058223 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302604 and starting SCN of 26775058212 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302603 and starting SCN of 26775049001 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302602 and starting SCN of 26775048992 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302601 and starting SCN of 26775039760 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302600 and starting SCN of 26775039751 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302599 and starting SCN of 26775029331 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302598 and starting SCN of 26775029300 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302597 and starting SCN of 26774997119 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302596 and starting SCN of 26774997088 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302595 and starting SCN of 26774963869 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302594 and starting SCN of 26774963837 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302593 and starting SCN of 26774930521 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302592 and starting SCN of 26774930475 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302591 and starting SCN of 26774865974 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302590 and starting SCN of 26774865787 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302589 and starting SCN of 26774856647 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302588 and starting SCN of 26774856632 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302587 and starting SCN of 26774848060 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302586 and starting SCN of 26774848049 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302585 and starting SCN of 26774839067 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302584 and starting SCN of 26774839039 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302583 and starting SCN of 26774828736 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302582 and starting SCN of 26774828713 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302581 and starting SCN of 26774796757 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302580 and starting SCN of 26774796725 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302579 and starting SCN of 26774765397 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 302578 and starting SCN of 26774765368 found to restore
RMAN-00567: Recovery Manager could not print some error messages
As we can see from the highlight line 4-5 the specified restore and recovery point time is “2022-12-31 23:00:00”, from the highlight line 132-133 the restore operation has been finished, next encountered ORA-01547, ORA-01194 and ORA-01110 just starting the recover action from the highlight line 140-142. Since the highlight line 150 reveals that oracle rman need the backup archive logs to continue recovering database but it doesn’t found them because of missing log.
Now we have to get the sequence between XXXXXX and XXXXXX with all of backup archive logs that are able to recover to “2022-12-31 23:00:00”. In other words we have to copy the missing backup archive logs to the backup location of the test server and then perform recover operation and the final open resetlogs operation.
Firstly I check the checkpoint_change# respectively from v$datafile and v$datafile_header.
col CHECKPOINT_CHANGE# for 99999999999
select distinct checkpoint_change# from v$datafile;
CHECKPOINT_CHANGE#
------------------
26776712072
select distinct checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
------------------
26774322733
26774322752
As we can see from the previous SQL query 26774322733 and 26774322752 (checkpoint_change# from v$datafile_header) is far less than 26776712072 (checkpoint_change# from v$datafile), due to the inconsist checkpoint_change# from v$datafile and v$datafile_header oracle never has been opened successfully. By the way x$kcvfh is the base table of view gv$datafile_header (we can get it from the SQL query select view_definition from v$fixed_view_definition where view_name = ‘GV$DATAFILE_HEADER’;) so we can get min(fhrba_seq) and max(fhrba_seq) from x$kcvfh, here’s the query result.
select min(fhrba_seq), max(fhrba_seq) from X$KCVFH;
MIN(FHRBA_SEQ) MAX(FHRBA_SEQ)
------------------------------ ------------------------------
302557 302557
Based on the above query now we can infer that 302557 is the first archive log sequence that oracle will use it to perform recover action, then which is the last archive log sequence that used by oracle? We use the following sql query to determine it.
select substr(L.GROUP#,1,6) GROUP#,
substr(L.THREAD#,1,7) THREAD#,
substr(L.SEQUENCE#,1,10) SEQUENCE#,
substr(L.MEMBERS,1,7) MEMBERS,
substr(L.ARCHIVED,1,8) ARCHIVED,
substr(L.STATUS,1,10) STATUS,
substr(L.FIRST_CHANGE#,1,16) FIRST_CHANGE#,
substr(LF.member,1,60) REDO_LOGFILE
from GV$LOG L, GV$LOGFILE LF
where L.GROUP# = LF.GROUP#;
GROUP# THREAD# SEQUENCE# MEMBERS ARCHIV STATUS FIRST_CHANGE# REDO_LOGFILE
------------ -------------- -------------------- -------------- ------ -------------------- -------------------------------- ------------------------------------
1 1 302729 2 NO CURRENT 26776719932 /XXXdata/XXX/mirrlogA/log_g1m2.dbf
1 1 302729 2 NO CURRENT 26776719932 /XXXdata/XXX/origlogA/log_g1m1.dbf
2 1 302726 2 YES INACTIVE 26776657056 /XXXdata/XXX/origlogA/log_g2m1.dbf
4 1 302728 2 YES ACTIVE 26776719922 /XXXdata/XXX/mirrlogB/log_g4m2.dbf
3 1 302727 2 YES ACTIVE 26776712072 /XXXdata/XXX/origlogB/log_g3m1.dbf
3 1 302727 2 YES ACTIVE 26776712072 /XXXdata/XXX/mirrlogB/log_g3m2.dbf
4 1 302728 2 YES ACTIVE 26776719922 /XXXdata/XXX/origlogB/log_g4m1.dbf
2 1 302726 2 YES INACTIVE 26776657056 /XXXdata/XXX/mirrlogA/log_g2m2.dbf
8 rows selected.
As we can see from the highlight line 14-15, 302729 is the last log sequence by redo which we have to recover to by using the current redo log.
Now we have to find out all of the backup archive log file location we can use the following RMAN command to check it.
RMAN> list backup of archivelog sequence between 302557 and 302729;
Now oracle lists archivelog backupset file location we tidies up them to a regular file. Here’s the result.
/backup/LOG/XXX_arc_249545_1_1124852404
/backup/LOG/XXX_arc_249547_1_1124853304
/backup/LOG/XXX_arc_249549_1_1124854203
/backup/LOG/XXX_arc_249553_1_1124854910
/backup/LOG/XXX_arc_249552_1_1124854910
/backup/LOG/XXX_arc_249555_1_1124855104
/backup/LOG/XXX_arc_249557_1_1124856003
/backup/LOG/XXX_arc_249559_1_1124856903
/backup/LOG/XXX_arc_249561_1_1124857803
/backup/LOG/XXX_arc_249563_1_1124858703
/backup/LOG/XXX_arc_249565_1_1124859603
/backup/LOG/XXX_arc_249567_1_1124860504
/backup/LOG/XXX_arc_249569_1_1124861402
/backup/LOG/XXX_arc_249571_1_1124862302
/backup/LOG/XXX_arc_249573_1_1124863203
/backup/LOG/XXX_arc_249575_1_1124864103
/backup/LOG/XXX_arc_249577_1_1124865003
/backup/LOG/XXX_arc_249579_1_1124865903
/backup/LOG/XXX_arc_249581_1_1124866803
/backup/LOG/XXX_arc_249583_1_1124867702
/backup/LOG/XXX_arc_249585_1_1124868603
/backup/LOG/XXX_arc_249587_1_1124869503
/backup/LOG/XXX_arc_249589_1_1124870403
/backup/LOG/XXX_arc_249591_1_1124871303
/backup/LOG/XXX_arc_249593_1_1124872203
/backup/LOG/XXX_arc_249595_1_1124873102
/backup/LOG/XXX_arc_249597_1_1124874003
/backup/LOG/XXX_arc_249599_1_1124874903
/backup/LOG/XXX_arc_249601_1_1124875803
/backup/LOG/XXX_arc_249603_1_1124876703
/backup/LOG/XXX_arc_249605_1_1124877603
/backup/LOG/XXX_arc_249607_1_1124878503
/backup/LOG/XXX_arc_249609_1_1124879402
/backup/LOG/XXX_arc_249611_1_1124880303
/backup/LOG/XXX_arc_249613_1_1124881203
/backup/LOG/XXX_arc_249615_1_1124882103
/backup/LOG/XXX_arc_249617_1_1124883003
/backup/LOG/XXX_arc_249619_1_1124883902
/backup/LOG/XXX_arc_249621_1_1124884803
/backup/LOG/XXX_arc_249623_1_1124885703
/backup/LOG/XXX_arc_249625_1_1124886603
/backup/LOG/XXX_arc_249627_1_1124887504
/backup/LOG/XXX_arc_249629_1_1124888404
/backup/LOG/XXX_arc_249631_1_1124889302
/backup/LOG/XXX_arc_249633_1_1124890202
/backup/LOG/XXX_arc_249635_1_1124891103
/backup/LOG/XXX_arc_249637_1_1124892003
/backup/LOG/XXX_arc_249639_1_1124892905
/backup/LOG/XXX_arc_249641_1_1124893804
/backup/LOG/XXX_arc_249643_1_1124894702
/backup/LOG/XXX_arc_249645_1_1124895603
/backup/LOG/XXX_arc_249647_1_1124896503
/backup/LOG/XXX_arc_249649_1_1124897403
/backup/LOG/XXX_arc_249651_1_1124898303
/backup/LOG/XXX_arc_249653_1_1124899203
/backup/LOG/XXX_arc_249655_1_1124900102
/backup/LOG/XXX_arc_249657_1_1124901003
/backup/LOG/XXX_arc_249659_1_1124901903
/backup/LOG/XXX_arc_249661_1_1124902803
/backup/LOG/XXX_arc_249663_1_1124903704
/backup/LOG/XXX_arc_249665_1_1124904603
/backup/LOG/XXX_arc_249667_1_1124905502
/backup/LOG/XXX_arc_249669_1_1124906403
/backup/LOG/XXX_arc_249671_1_1124907303
/backup/LOG/XXX_arc_249673_1_1124908203
/backup/LOG/XXX_arc_249675_1_1124909104
/backup/LOG/XXX_arc_249677_1_1124910003
/backup/LOG/XXX_arc_249679_1_1124910902
/backup/LOG/XXX_arc_249681_1_1124911803
/backup/LOG/XXX_arc_249683_1_1124912703
/backup/LOG/XXX_arc_249685_1_1124913603
/backup/LOG/XXX_arc_249687_1_1124914503
/backup/LOG/XXX_arc_249689_1_1124915403
/backup/LOG/XXX_arc_249691_1_1124916302
At this moment I tell my client there has not existed the preceding archivelog backupset file on the test server, waiting for a while he finished copying those files to the location of RMAN backupset on the test server and executed “catalog start with …”, then I performs the action of recover database on RMAN command line (no shown any error) now open resetlogs oracle database is ok!
P.S.: Before oracle use rman backupset to restore and recover database to a specified time we must ensure the backupset is completed, including the rman full backup, cumulative rman incremental backup, archive log backup, the latest current file backup. Apart from using set until time = ‘2022-12-31 23:00:00’; we can add time point to restore database and recover database clause as well, e.g. restore database until time “to_date(‘2022-12-31 23:00:00’, ‘yyyy-mm-dd hh24:mi:ss’)”; and recover database until time “to_date(‘2022-12-31 23:00:00’, ‘yyyy-mm-dd hh24:mi:ss’)”;.
Before “alter database open resetlogs;” we can also check the final oracle database recover time point by an interesting sql query as below (next it’s the query result).
set linesize 400
set pagesize 400
col name for a50
select d.name,
d.checkpoint_change#,
to_char(d.checkpoint_time, 'yyyy-mm-dd hh24:mi:ss'),
h.checkpoint_change#,
to_char(h.checkpoint_time, 'yyyy-mm-dd hh24:mi:ss')
from v$datafile_header h, v$datafile d
where h.file# = d.file#
order by 1;
NAME CHECKPOINT_CHANGE# TO_CHAR(D.CHECKPOIN CHECKPOINT_CHANGE# TO_CHAR(H.CHECKPOIN
-------------------------------------------------- ------------------ ------------------- ------------------ -------------------
/xxxdata/xxx/xxxdata1/bbbbb01.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata1/bbbbb03.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata1/sysaux01.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata1/system01.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata1/undotbs01.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata1/userdata1.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata1/users01.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb02.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb11.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb12.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb13.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb14.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb15.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb16.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb17.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb18.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb19.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb20.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb21.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb22.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb23.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb24.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/bbbbb25.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_01.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_02.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_03.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_04.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_05.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_06.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_07.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_08.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata2/xxxdata_09.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb08.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_34.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_35.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb04.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb05.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb06.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb07.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb09.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/bbbbb10.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy1.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy10.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy11.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy12.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy13.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy2.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy3.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy4.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy5.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy6.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy7.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy8.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/yyyyyy9.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata20.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata27.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_10.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_11.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_12.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_13.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_14.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_15.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_16.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_17.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_18.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_19.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_21.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_22.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_23.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_24.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_25.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_26.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_28.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_29.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_30.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_31.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_32.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_33.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_36.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_37.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_38.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_39.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_40.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_41.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_42.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_43.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_44.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_45.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_46.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_47.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_48.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_49.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_50.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_51.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_52.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_53.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_54.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
/xxxdata/xxx/xxxdata3/xxxdata_55.dbf 2.6777E+10 2022-12-31 23:39:00 2.6777E+10 2022-12-31 23:00:00
Focusing and Concentrating Oracle Recipes, Tips and Techniques 