cancel
Showing results for 
Search instead for 
Did you mean: 

blockrecover datafile wants more and more redologs

Former Member
0 Kudos

Hello,


in our prod. system we have a block corruption at datafile 5 block 988626; It's Oracle 11.2.0.2.

DBV at 10.03.2012 was red.

DBV at 03.03.2012 was green.

We have tried a blockrecover like discribed in sap note 540463 with a copy

of affected datafile from 07.03.2012.

But the recovery process wants more and more redologs. Not only these

up to this backup time. The last redolog in the list is from 01.12.2011.

Have anyone a suggestion, why?

RMAN> blockrecover datafile 5 block 988626;


Starting recover at 13-MAR-12

using channel ORA_DISK_1


channel ORA_DISK_1: restoring block(s) from datafile copy /oracle/ABP/sapbackup/beibwemz.spa/sr4.data2

ORA-19505: failed to identify file "/oracle/ABP/sapbackup/beibwemz.spa/sr4.data2"

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

Additional information: 3

ORA-19600: input file is datafile copy 0 (/oracle/ABP/sapbackup/beibwemz.spa/sr4.data2)


failover to previous backup


channel ORA_DISK_1: restoring block(s) from datafile copy /oracle/ABP/sapbackup/beibmiwu.spa/sr4.data2

ORA-19505: failed to identify file "/oracle/ABP/sapbackup/beibmiwu.spa/sr4.data2"

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

Additional information: 3

ORA-19600: input file is datafile copy 0 (/oracle/ABP/sapbackup/beibmiwu.spa/sr4.data2)


failover to previous backup


channel ORA_DISK_1: restoring block(s) from datafile copy /oracle/ABP/sapbackup/beibhlbt.spa/sr4.data2

ORA-19505: failed to identify file "/oracle/ABP/sapbackup/beibhlbt.spa/sr4.data2"

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

Additional information: 3

ORA-19600: input file is datafile copy 0 (/oracle/ABP/sapbackup/beibhlbt.spa/sr4.data2)


failover to previous backup


channel ORA_DISK_1: restoring block(s) from datafile copy /oracle/ABP/sapbackup/beibcngr.spa/sr4.data2

ORA-19505: failed to identify file "/oracle/ABP/sapbackup/beibcngr.spa/sr4.data2"

ORA-27037: unable to obtain file status

IBM AIX RISC System/6000 Error: 2: No such file or directory

Additional information: 3

ORA-19600: input file is datafile copy 0 (/oracle/ABP/sapbackup/beibcngr.spa/sr4.data2)


failover to previous backup


channel ORA_DISK_1: restoring block(s) from datafile copy /oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2


starting media recovery


archived log for thread 1 with sequence 746 is already on disk as file /oracle/ABP/oraarch/ABParch1_746_762960509.dbf

archived log for thread 1 with sequence 747 is already on disk as file /oracle/ABP/oraarch/ABParch1_747_762960509.dbf

archived log for thread 1 with sequence 748 is already on disk as file /oracle/ABP/oraarch/ABParch1_748_762960509.dbf

archived log for thread 1 with sequence 749 is already on disk as file /oracle/ABP/oraarch/ABParch1_749_762960509.dbf

archived log for thread 1 with sequence 750 is already on disk as file /oracle/ABP/oraarch/ABParch1_750_762960509.dbf

archived log for thread 1 with sequence 751 is already on disk as file /oracle/ABP/oraarch/ABParch1_751_762960509.dbf

archived log for thread 1 with sequence 752 is already on disk as file /oracle/ABP/oraarch/ABParch1_752_762960509.dbf

archived log for thread 1 with sequence 753 is already on disk as file /oracle/ABP/oraarch/ABParch1_753_762960509.dbf

archived log for thread 1 with sequence 754 is already on disk as file /oracle/ABP/oraarch/ABParch1_754_762960509.dbf

archived log for thread 1 with sequence 755 is already on disk as file /oracle/ABP/oraarch/ABParch1_755_762960509.dbf

archived log for thread 1 with sequence 756 is already on disk as file /oracle/ABP/oraarch/ABParch1_756_762960509.dbf

archived log for thread 1 with sequence 757 is already on disk as file /oracle/ABP/oraarch/ABParch1_757_762960509.dbf

archived log for thread 1 with sequence 758 is already on disk as file /oracle/ABP/oraarch/ABParch1_758_762960509.dbf

archived log for thread 1 with sequence 759 is already on disk as file /oracle/ABP/oraarch/ABParch1_759_762960509.dbf

archived log for thread 1 with sequence 760 is already on disk as file /oracle/ABP/oraarch/ABParch1_760_762960509.dbf

archived log for thread 1 with sequence 761 is already on disk as file /oracle/ABP/oraarch/ABParch1_761_762960509.dbf

archived log for thread 1 with sequence 762 is already on disk as file /oracle/ABP/oraarch/ABParch1_762_762960509.dbf

archived log for thread 1 with sequence 763 is already on disk as file /oracle/ABP/oraarch/ABParch1_763_762960509.dbf

archived log for thread 1 with sequence 764 is already on disk as file /oracle/ABP/oraarch/ABParch1_764_762960509.dbf

archived log for thread 1 with sequence 765 is already on disk as file /oracle/ABP/oraarch/ABParch1_765_762960509.dbf

archived log for thread 1 with sequence 766 is already on disk as file /oracle/ABP/oraarch/ABParch1_766_762960509.dbf

archived log for thread 1 with sequence 767 is already on disk as file /oracle/ABP/oraarch/ABParch1_767_762960509.dbf

archived log for thread 1 with sequence 768 is already on disk as file /oracle/ABP/oraarch/ABParch1_768_762960509.dbf

archived log for thread 1 with sequence 769 is already on disk as file /oracle/ABP/oraarch/ABParch1_769_762960509.dbf

archived log for thread 1 with sequence 770 is already on disk as file /oracle/ABP/oraarch/ABParch1_770_762960509.dbf

archived log for thread 1 with sequence 771 is already on disk as file /oracle/ABP/oraarch/ABParch1_771_762960509.dbf

archived log for thread 1 with sequence 772 is already on disk as file /oracle/ABP/oraarch/ABParch1_772_762960509.dbf

archived log for thread 1 with sequence 773 is already on disk as file /oracle/ABP/oraarch/ABParch1_773_762960509.dbf

archived log for thread 1 with sequence 774 is already on disk as file /oracle/ABP/oraarch/ABParch1_774_762960509.dbf

archived log for thread 1 with sequence 775 is already on disk as file /oracle/ABP/oraarch/ABParch1_775_762960509.dbf

archived log for thread 1 with sequence 776 is already on disk as file /oracle/ABP/oraarch/ABParch1_776_762960509.dbf

archived log for thread 1 with sequence 777 is already on disk as file /oracle/ABP/oraarch/ABParch1_777_762960509.dbf

archived log for thread 1 with sequence 778 is already on disk as file /oracle/ABP/oraarch/ABParch1_778_762960509.dbf

archived log for thread 1 with sequence 779 is already on disk as file /oracle/ABP/oraarch/ABParch1_779_762960509.dbf

archived log for thread 1 with sequence 780 is already on disk as file /oracle/ABP/oraarch/ABParch1_780_762960509.dbf

archived log for thread 1 with sequence 781 is already on disk as file /oracle/ABP/oraarch/ABParch1_781_762960509.dbf

archived log for thread 1 with sequence 782 is already on disk as file /oracle/ABP/oraarch/ABParch1_782_762960509.dbf

archived log for thread 1 with sequence 783 is already on disk as file /oracle/ABP/oraarch/ABParch1_783_762960509.dbf

archived log for thread 1 with sequence 784 is already on disk as file /oracle/ABP/oraarch/ABParch1_784_762960509.dbf

archived log for thread 1 with sequence 785 is already on disk as file /oracle/ABP/oraarch/ABParch1_785_762960509.dbf

archived log for thread 1 with sequence 786 is already on disk as file /oracle/ABP/oraarch/ABParch1_786_762960509.dbf

archived log for thread 1 with sequence 787 is already on disk as file /oracle/ABP/oraarch/ABParch1_787_762960509.dbf

archived log for thread 1 with sequence 788 is already on disk as file /oracle/ABP/oraarch/ABParch1_788_762960509.dbf

archived log for thread 1 with sequence 789 is already on disk as file /oracle/ABP/oraarch/ABParch1_789_762960509.dbf

archived log for thread 1 with sequence 790 is already on disk as file /oracle/ABP/oraarch/ABParch1_790_762960509.dbf

archived log for thread 1 with sequence 791 is already on disk as file /oracle/ABP/oraarch/ABParch1_791_762960509.dbf

archived log for thread 1 with sequence 792 is already on disk as file /oracle/ABP/oraarch/ABParch1_792_762960509.dbf

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 03/13/2012 15:09:22

RMAN-06053: unable to perform media recovery because of missing log

RMAN-06025: no backup of archived log for thread 1 with sequence 745 and starting SCN of 142871345 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 744 and starting SCN of 142857584 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 743 and starting SCN of 142610445 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 742 and starting SCN of 142603818 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 741 and starting SCN of 142251070 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 740 and starting SCN of 142208140 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 739 and starting SCN of 141900635 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 738 and starting SCN of 141801729 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 737 and starting SCN of 141456008 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 736 and starting SCN of 141317333 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 735 and starting SCN of 141011498 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 734 and starting SCN of 140788707 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 733 and starting SCN of 140456236 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 732 and starting SCN of 140092943 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 731 and starting SCN of 139966473 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 730 and starting SCN of 139696804 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 729 and starting SCN of 139315095 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 728 and starting SCN of 138927651 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 727 and starting SCN of 138554231 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 726 and starting SCN of 138162447 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 725 and starting SCN of 137802351 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 724 and starting SCN of 137373198 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 723 and starting SCN of 137255943 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 722 and starting SCN of 136991580 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 721 and starting SCN of 136597023 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 720 and starting SCN of 136580858 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 719 and starting SCN of 136189970 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 718 and starting SCN of 136133619 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 717 and starting SCN of 135766210 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 716 and starting SCN of 135392432 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 715 and starting SCN of 135082730 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 714 and starting SCN of 134596523 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 713 and starting SCN of 134575210 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 712 and starting SCN of 134190321 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 711 and starting SCN of 133795473 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 710 and starting SCN of 133727100 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 709 and starting SCN of 133390114 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 708 and starting SCN of 133373937 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 707 and starting SCN of 132974335 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 706 and starting SCN of 132547468 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 705 and starting SCN of 132122752 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 704 and starting SCN of 131577534 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 703 and starting SCN of 131537977 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 702 and starting SCN of 131026543 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 701 and starting SCN of 130595253 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 700 and starting SCN of 130194501 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 699 and starting SCN of 129782971 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 698 and starting SCN of 129727897 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 697 and starting SCN of 129362109 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 696 and starting SCN of 128921639 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 695 and starting SCN of 128523499 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 694 and starting SCN of 128397227 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 693 and starting SCN of 128014237 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 692 and starting SCN of 127938320 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 691 and starting SCN of 127563046 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 690 and starting SCN of 127534952 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 689 and starting SCN of 127161442 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 688 and starting SCN of 126745054 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 687 and starting SCN of 126744547 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 686 and starting SCN of 126340344 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 685 and starting SCN of 125912026 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 684 and starting SCN of 125507870 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 683 and starting SCN of 125373198 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 682 and starting SCN of 125097576 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 681 and starting SCN of 125077928 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 680 and starting SCN of 124690471 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 679 and starting SCN of 124267563 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 678 and starting SCN of 124230819 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 677 and starting SCN of 123840628 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 676 and starting SCN of 123441068 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 675 and starting SCN of 123415609 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 674 and starting SCN of 122950744 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 673 and starting SCN of 122556598 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 672 and starting SCN of 122430129 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 671 and starting SCN of 122149270 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 670 and starting SCN of 122085303 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 669 and starting SCN of 121737110 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 668 and starting SCN of 121321405 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 667 and starting SCN of 121293299 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 666 and starting SCN of 120892235 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 665 and starting SCN of 120750679 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 664 and starting SCN of 120464633 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 663 and starting SCN of 120187281 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 662 and starting SCN of 119993667 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 661 and starting SCN of 119596331 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 660 and starting SCN of 119470712 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 659 and starting SCN of 119169365 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 658 and starting SCN of 119121238 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 657 and starting SCN of 118607425 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 656 and starting SCN of 118564465 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 655 and starting SCN of 118002497 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 654 and starting SCN of 117907719 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 653 and starting SCN of 117587712 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 652 and starting SCN of 117162707 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 651 and starting SCN of 116706893 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 650 and starting SCN of 116316027 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 649 and starting SCN of 116229494 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 648 and starting SCN of 115930397 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 647 and starting SCN of 115885601 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 646 and starting SCN of 115522122 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 645 and starting SCN of 115434304 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 644 and starting SCN of 115013992 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 643 and starting SCN of 114755115 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 642 and starting SCN of 114548484 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 641 and starting SCN of 114502983 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 640 and starting SCN of 114454681 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 639 and starting SCN of 114426164 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 638 and starting SCN of 114397043 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 637 and starting SCN of 114371074 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 636 and starting SCN of 114345017 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 635 and starting SCN of 114317260 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 634 and starting SCN of 114289017 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 633 and starting SCN of 114259554 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 632 and starting SCN of 114231181 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 631 and starting SCN of 114149584 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 630 and starting SCN of 114073784 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 629 and starting SCN of 113996145 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 628 and starting SCN of 113958802 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 627 and starting SCN of 113938233 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 626 and starting SCN of 113923193 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 625 and starting SCN of 113908773 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 624 and starting SCN of 113889975 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 623 and starting SCN of 113847827 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 622 and starting SCN of 113781007 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 621 and starting SCN of 113715692 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 620 and starting SCN of 113639496 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 619 and starting SCN of 113565059 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 618 and starting SCN of 113514947 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 617 and starting SCN of 113422709 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 616 and starting SCN of 113315273 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 615 and starting SCN of 113281018 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 614 and starting SCN of 113235876 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 613 and starting SCN of 113194388 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 612 and starting SCN of 113150748 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 611 and starting SCN of 113119377 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 610 and starting SCN of 113090724 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 609 and starting SCN of 113056412 found to restore

RMAN-00567: Recovery Manager could not print some error messages

----


kind regards


Ch.Fischer


View Entire Topic
Former Member
0 Kudos

Hello, in SAP note 540463 point 12. is discribed, that RMAN can do blockrecover without any preconfiguration of RMAN. Even if the backup are NOT done with RMAN.

With the command "copy list;" in RMAN we get all datafiles and redologs listed. So RMAN is knowing them. But i don't understand, why he request redologs up to 01.12.2011 if we try to recover from a datafile from 07.03.2012.

regards
Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

yes you are right about the sapnote, but it hides a lot of information. Let me put some light into it.

At first the sapnote states "restore ALL archives from the restored backup up to now to oraarch.". This only works, because of if you perform an old fashion backup - the BR*Tools do not remove the archive log meta data information from the control files. So you need to copy all of these archive log files back to the same location with the same name. Aftter that RMAN can still rely on that meta data information. This is also mentioned in the next part of the sapnote - if you have not enough space for all the archive logs - you need to register them manually with the provided script. Pretty much effort and manual tasks in my opinion.

If you have manually provided all the necessary archive logs in the original location you just need to perform a block recovery (in case of the data file copy is also available - this can be verified with by RMAN crosscheck). The sapnote contains only one sentence about the  data file copy ("restore the files having corrupt blocks from a good backup to ANOTHER  location on disk (e.g. sapreorg)") - that is the same procedure and the same prerequisite as with the archive logs. With your provided RMAN errors (ORA-19505) you can see that the prerequisites are not fulfilled in your case.

In your case RMAN can only find a previous data file copy (/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2) and it seems like this is much older and more archive logs are needed for recovery.

If i get you right - you have done one fatal error before executing the RMAN block recovery. You have restored an old data file with brbackup and have overwritten the whole original data file right? In this case you need to recover the whole data file the old fashion way too and not just one block.

Regards

Stefan

Former Member
0 Kudos

If i get you right - you have done one fatal error before executing the RMAN block recovery. You have      restored an old data file with brbackup and have overwritten the whole original data file right?

No. You can see that i have restored the affected Datafile from Backup "beiaxplp" to
the copy place /oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2. The corrupted datafile is still present.
I start the blockrecovery as discribed in note. RMAN is knowing all datafiles and logs like discribed in note. The archivlogs we have resored in original directory /oracle/ABP/oraarch . RMAN is knowing and finding them (look at first post). So i think all prerequisites are fulfilled in my case.

regards
Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

ok now i get it. I assumed that you have overwritten the original file, because you have wrote "I restored it from a successful backup with brbackup.".

However in this case you have fulfilled all the prerequisites for a block recovery by RMAN, but the backup from "beiaxplp.spa" is not your latest one. You get several ORA-19505 errors and corresponding fail overs to previous backups (and of course more archive logs are needed then). It seems like your newest backup is the "beibwemz.spa" one. You can check this with the following query:

SQL> alter session set nls_date_format = 'dd.mm.yyyy hh24:mi:ss';

SQL> select NAME, STAMP, CREATION_TIME, COMPLETION_TIME from V$DATAFILE_COPY where FILE# = 5;

Regards

Stefan

P.S.: RMAN is also not able to find all archive log files (files with the sequence number 609 to 745 are missing) - however the reason for the need of these archive logs seems to be the old data file copy.

Former Member
0 Kudos
  1. SQL> alter session set nls_date_format = 'dd.mm.yyyy hh24:mi:ss'
  2. SQL> select NAME, STAMP, CREATION_TIME, COMPLETION_TIME from V$DATAFILE_COPY where FILE# = 5; 

NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behvgddh.spa/sr4.data2

774549502 18.07.2011 15:50:51 06.02.2012 16:38:22

/oracle/ABP/sapbackup/behvlayk.spa/sr4.data2

774635589 18.07.2011 15:50:51 07.02.2012 16:33:09

/oracle/ABP/sapbackup/behvpytm.spa/sr4.data2

774722973 18.07.2011 15:50:51 08.02.2012 16:49:33

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behvuwon.spa/sr4.data2

774808445 18.07.2011 15:50:51 09.02.2012 16:34:05

/oracle/ABP/sapbackup/behvzujp.spa/sr4.data2

774894663 18.07.2011 15:50:51 10.02.2012 16:31:03

/oracle/ABP/sapbackup/behweser.spa/sr4.data2

774982008 18.07.2011 15:50:51 11.02.2012 16:46:48

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behwonuv.spa/sr4.data2

775154016 18.07.2011 15:50:51 13.02.2012 16:33:36

/oracle/ABP/sapbackup/behwtlpx.spa/sr4.data2

775240368 18.07.2011 15:50:51 14.02.2012 16:32:48

/oracle/ABP/sapbackup/behwyjlb.spa/sr4.data2

775329379 18.07.2011 15:50:51 15.02.2012 17:16:19

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behxdhgc.spa/sr4.data2

775413594 18.07.2011 15:50:51 16.02.2012 16:39:54

/oracle/ABP/sapbackup/behxifbe.spa/sr4.data2

775500311 18.07.2011 15:50:51 17.02.2012 16:45:11

/oracle/ABP/sapbackup/behxncwg.spa/sr4.data2

775587157 18.07.2011 15:50:51 18.02.2012 16:52:37

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behxwymk.spa/sr4.data2

775760488 18.07.2011 15:50:51 20.02.2012 17:01:28

/oracle/ABP/sapbackup/behybwhl.spa/sr4.data2

775846628 18.07.2011 15:50:51 21.02.2012 16:57:08

/oracle/ABP/sapbackup/behygucn.spa/sr4.data2

775932807 18.07.2011 15:50:51 22.02.2012 16:53:27

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behylrxq.spa/sr4.data2

776020428 18.07.2011 15:50:51 23.02.2012 17:13:48

/oracle/ABP/sapbackup/behyqpsr.spa/sr4.data2

776104522 18.07.2011 15:50:51 24.02.2012 16:35:22

/oracle/ABP/sapbackup/behyvnnt.spa/sr4.data2

776191572 18.07.2011 15:50:51 25.02.2012 16:46:12

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behzfjdx.spa/sr4.data2

776364710 18.07.2011 15:50:51 27.02.2012 16:51:50

/oracle/ABP/sapbackup/behzpfhp.spa/sr4.data2

776532716 18.07.2011 15:50:51 29.02.2012 15:31:56

/oracle/ABP/sapbackup/behzudis.spa/sr4.data2

776792057 18.07.2011 15:50:51 01.03.2012 15:34:17

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/behzzakf.spa/sr4.data2

776877870 18.07.2011 15:50:51 02.03.2012 15:24:30

/oracle/ABP/sapbackup/beiadyfh.spa/sr4.data2

776964568 18.07.2011 15:50:51 03.03.2012 15:29:28

/oracle/ABP/sapbackup/beiantvl.spa/sr4.data2

777137097 18.07.2011 15:50:51 05.03.2012 15:24:57

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/beiasrqn.spa/sr4.data2

777223491 18.07.2011 15:50:51 06.03.2012 15:24:51

   777309916 18.07.2011 15:50:51 07.03.2012 15:25:16

/oracle/ABP/sapbackup/beibcngr.spa/sr4.data2

777396314 18.07.2011 15:50:51 08.03.2012 15:25:14

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/beibhlbt.spa/sr4.data2

777482649 18.07.2011 15:50:51 09.03.2012 15:24:09

/oracle/ABP/sapbackup/beibmiwu.spa/sr4.data2

777569235 18.07.2011 15:50:51 10.03.2012 15:27:15

/oracle/ABP/sapbackup/beibwemz.spa/sr4.data2

777741972 18.07.2011 15:50:51 12.03.2012 15:26:12

  NAME

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

     STAMP CREATION_TIME       COMPLETION_TIME

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

/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2

777827167 18.07.2011 15:50:51 13.03.2012 15:06:07

/oracle/ABP/sapbackup/beicbcic.spa/sr4.data2

777828270 18.07.2011 15:50:51 13.03.2012 15:24:30

/oracle/ABP/sapbackup/beicgadd.spa/sr4.data2

777914689 18.07.2011 15:50:51 14.03.2012 15:24:49

RMAN has do a failover of the restored datafiles before "beiaxplp", so i think this is the file where the corruption does not exist. Must we restore all the other backups of datafile 5 for recovery?

regards
Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

hmm i am confused right now ... you said ...

have tried a blockrecover like discribed in sap note 540463 with a copy of affected datafile from 07.03.2012.

But you restored and use a copy of the data file out of backup "beiaxplp.spa"  from "13.03.2012 15:06:07". It seems like you are using the backup, that you have done right before you tried to restore the corrupted data block. If you really want to use the physical backup from 07.03.2012 you need the data file copy from backup "beiasrqn.spa" or "beibcngr.spa" and these files are not available in the filesystem right now - as you can see from the RMAN errors (ORA-19505: failed to identify file "/oracle/ABP/sapbackup/beibcngr.spa/sr4.data2"). So you have not fulfilled the prerequisite from sapnote #540463.

I really dislike that manual activities by BR*Tools in such a backup procedure.

Regards

Stefan

Former Member
0 Kudos

Mhm, in SAP the beiaxplp is from 7.03.2012 now i'am confused.

Has RMAN other logs and timestamps?

regards
Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

now it is getting tricky, but i like it that way

The RMAN time stamp has to be the same (or better said the SCN information). As i have never traced that manual (under the hood) tasks by BR*Tools, we need to do some additional research to figure it out. That's the problem with the BR*Tools - you really don't know what they exactly do (until you trace them). If you  do native RMAN backup it would be well known.

Please execute the following queries (and OS commands) and post the output as attached text file (the unformatted copy & paste output is nearly unreadable).

SQL> set linesize 500

SQL> alter session set nls_date_format = 'dd.mm.yyyy hh24:mi:ss';

SQL> select STAMP, CHECKPOINT_TIME, CHECKPOINT_CHANGE#, COMPLETION_TIME from V$DATAFILE_COPY where NAME = '/oracle/ABP/sapbackup/beiasrqn.spa/sr4.data2';

SQL> select STAMP, CHECKPOINT_TIME, CHECKPOINT_CHANGE#, COMPLETION_TIME from V$DATAFILE_COPY where NAME = '/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2';

SQL> select STAMP, CHECKPOINT_TIME, CHECKPOINT_CHANGE#, COMPLETION_TIME from V$DATAFILE_COPY where NAME = '/oracle/ABP/sapbackup/beibcngr.spa/sr4.data2';

SQL> select SEQUENCE#, FIRST_CHANGE#, FIRST_TIME, NEXT_CHANGE#, NEXT_TIME from V$ARCHIVED_LOG where SEQUENCE# between 609 and 745 order by SEQUENCE#;

shell> dd if='/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2' of='/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2.hd.dump' bs=8192 count=2

shell> cat /oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2.hd.dump

Regards

Stefan

Former Member
0 Kudos

swe132053:/>dd if='/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2' of='/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2.hd.dump' bs=8192 count=2

2+0 records in.

2+0 records out.

swe132053:/>cat /oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2.hd.dump

¢ÿÀñÑ ©z{|}

            ¢@/»           b-a[-yÚ}.ð.TÈëÀÆ.H½lëÀ.TÈÿ

                 F,YABPny©                           Ï©PSAPSR4-ëÀ.TÈÿ

                                                                     Ï@

regards
Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

thank you for the output. I was not sure about the dd and header dump on AIX, but i don't need it to verify my assumption. So here we go with the analysis.

  1. The data file copy '/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2' is the correct one (verified by CHECKPOINT_TIME). The COMPLETION_TIME (= Time when the copy was completed) is updated by the BR*Tools restore operation, so no need to look deeper into this.
  2. The checkpoint scn for data file copy '/oracle/ABP/sapbackup/beiaxplp.spa/sr4.data2' is 149667987. But the listed archive logs (sequence 609 to 745) are not needed for recovery of that particular data file copy (or block recovery) at all. The latest SCN of archive log sequence 745 is 142970122, but you need the archive logs starting from 149667987.
  3. Please run the following query to get the needed archive logs (and post the text file again):

SQL> set linesize 500 

SQL> alter session set nls_date_format = 'dd.mm.yyyy hh24:mi:ss';  

SQL> select SEQUENCE#, FIRST_CHANGE#, FIRST_TIME, NEXT_CHANGE#, NEXT_TIME from V$ARCHIVED_LOG where SEQUENCE# => 745 order by SEQUENCE#; 

After identifying the needed archive logs, i would suggest to restore only these few archive log files, run a crosscheck for all archive logs and run the block recovery again. As i already mentioned the meta data information for the archive log files is not updated by BR*Tools backup, so RMAN still thinks, that these files should be there. After the restore of the needed archive logs and a crosscheck - they are marked as expired.

Regards

Stefan

Former Member
0 Kudos

Hello,

i know the needed archivelogs. SAP has a good overall view for it.
How i do a crosscheck?

regards
Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

ok just to be complete. You need all archive logs starting from sequence 779 until now. If all of these archive logs are present in the archive log destination - execute the following commands:

shell> rman target /

RMAN> crosscheck archivelog all;

RMAN> blockrecover datafile 5 block 988626;

Let's see what is happening

Regards

Stefan

Former Member
0 Kudos

Yippie, he got it.

after the crosscheck, he made the recovery.
Now the consistence check of the file is without any corruption.

Thank you very much for your patience and help.

regards
Chris

Former Member
0 Kudos

Hello,

we want to recover a other block now, and the error is thera again.
The crosscheck do not solve it.
Why RMAN do this?
We have restored all needed redologs. Checked the TIMESTAMP and SEQUENCE. All is right.

regadrs

Chris

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

we would need to go through the previous procedure again to identify the root cause. Maybe it is another issue (now) and need to do some RMAN tracing as well.

Regards

Stefan

Former Member
0 Kudos

We have checked the steps.
But all is right, we think.

Have a look at attached file.

regards

Ch.Fischer

stefan_koehler
Active Contributor
0 Kudos

Hello Christian,

that looks kind of strange indeed (on the first view). 2 notes without doing a deeper investigations:

  1. You are using a deprecated syntax (http://docs.oracle.com/cd/E11882_01/backup.112/e10643/obs_comm.htm#RCMRF910)
  2. Do you fullfil  the prerequisites for block  recovery (http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta2001.htm#i84135) - especially point 2.

For any further investigations we need to do some RMAN tracing. If you need further assistance - you already have my contact data.

Regards

Stefan