\n\tFetching gap sequence in thread 1, gap sequence 41842-41873
\n\tFAL[client]: Trying FAL server: XDSL
\n\tTue Dec 18 13:44:03 2012
\n\tFAL[client]: Failed to request gap sequence for thread 1 gap sequence 41842-41873
\n\tFAL[client]: All defined FAL servers have been attempted.
\n\t————————————————————-
\n\tCheck that the CONTROL_FILE_RECORD_KEEP_TIME initialization
\n\tparameter is defined to a value that is sufficiently large
\n\tenough to maintain adequate log switch information to resolve
\n\tarchivelog gaps.<\/p>\n
\n\tAlert log da yukardaki gibi bir uyari alindiginda, bazi archive loglarin alinamadigini veya standby tarafina alinmissa bile bozuldugu için apply edilemedigi sonucunu çikarabiliriz.<\/p>\n
\n\tÖncelikle kontrollerimizi yapalim;<\/p>\n
\nSQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;<\/pre>\n\nPROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS\n--------- ------------ ---------- ---------- ---------- ----------\nARCH CONNECTED 0 0 0 0\nARCH CONNECTED 0 0 0 0\nARCH CONNECTED 0 0 0 0\nARCH CONNECTED 0 0 0 0\nMRP0 WAIT_FOR_GAP 1 41842 0 0\nRFS WRITING 1 41963 538625 2048\nRFS WRITING 1 41965 458753 2048\nRFS WRITING 1 41964 516097 2048\nRFS RECEIVING 0 0 0 0\n<\/pre>\n\n\tDurumu WAIT_FOR_GAP olan v$archived_log tablosunda görünmeyecektir.<\/p>\n
\nselect THREAD#, DEST_ID, SEQUENCE#, applied, archived from v$archived_log where dest_id=3 and applied='NO' order by SEQUENCE#;\n<\/pre>\n\n THREAD# DEST_ID SEQUENCE# APP ARC\n---------- ---------- ---------- --- ---\n 1 3 41874 NO YES\n 1 3 41875 NO YES\n 1 3 41876 NO YES\n 1 3 41877 NO YES\n 1 3 41878 NO YES\n 1 3 41879 NO YES\n 1 3 41880 NO YES\n 1 3 41881 NO YES\n 1 3 41882 NO YES\n 1 3 41883 NO YES\n 1 3 41884 NO YES\n 1 3 41885 NO YES\n 1 3 41886 NO YES\n 1 3 41887 NO YES\n 1 3 41888 NO YES\n 1 3 41889 NO YES\n 1 3 41890 NO YES\n 1 3 41891 NO YES\n 1 3 41892 NO YES\n 1 3 41893 NO YES\n 1 3 41894 NO YES\n 1 3 41895 NO YES\n 1 3 41896 NO YES\n 1 3 41897 NO YES\n 1 3 41898 NO YES\n 1 3 41899 NO YES\n 1 3 41900 NO YES\n 1 3 41901 NO YES\n 1 3 41902 NO YES\n 1 3 41903 NO YES\n 1 3 41904 NO YES\n 1 3 41905 NO YES\n 1 3 41906 NO YES\n 1 3 41907 NO YES\n 1 3 41908 NO YES\n\n35 rows selected.\n<\/pre>\n\n\t–yukardaki hata, bazi loglarin arsivlnemedigini gösteriir. Bunun birkaç nedeni olabilir aslinda.
\n\t*prod tarafinda archive loglar olmayabilir.
\n\t*standby tarafina loglar eksik veya yanlis gelmis olabilir.
\n\t*loglar CONTROL_FILE_RECORD_KEEP_TIME degerinden eski olabilir.<\/p>\n\n\tBu durumu çözmek için,
\n\t*eger loglar standby’da yoksa, baska bir ortamdan scp ile standbya kopyalanir veya backuptan restore edilir.<\/p>\n\n\tGap’taki eksik archiveloglar kopyalandiktan sonra veya restore edildikten sonra standby’da asagidaki komut gapteki her archivelog için çalistirilir.<\/p>\n
\n\talter database register or replace logfile '\/arcdsl11\/XDSL\/1_41842_751682847.arc';<\/p>\n
\n\tgap durmunu kontrol için asagidaki sorgu da kullanilabilir.<\/p>\n
\nSQL> select * from v$archive_gap ;\t\n<\/pre>\n