{"id":202,"date":"2012-02-16T07:40:00","date_gmt":"1970-01-01T00:00:00","guid":{"rendered":"http:\/\/www.yazilimmutfagi.com\/?p=202"},"modified":"2012-02-16T07:40:00","modified_gmt":"1970-01-01T00:00:00","slug":"rman-duplicate-ile-standby-database-kurulumu","status":"publish","type":"post","link":"https:\/\/www.yazilimmutfagi.com\/index.php\/2012\/02\/16\/rman-duplicate-ile-standby-database-kurulumu\/","title":{"rendered":"RMAN DUPLICATE ILE STANDBY DATABASE KURULUMU"},"content":{"rendered":"\n

RMAN DUPLICATE ILE STANDBY DATABASE KURULUMU<\/h3>\n

Standby veritabanlari production veritabanlarinin bire bir kopyasidir ve bu databaseler genelde felaket durumlarinda kullanilmak için yedek database olarak kullanilir. Bu makalede standby veritabaninin rman duplicate ile nasil kuruldugundan bahsedecegim. Production veritabaninin birebir kopyasini olusturmak için en kolay yöntem recovery manager (RMAN) kullanmaktir. Bunun disinda fiziksel dosya kopyalama yöntemi kullanilabilir fakat bu yöntemi online yapmak mümkün degildir. RMAN ile backup alinip bu backup i restore ederek standby database olusturabiliriz fakat 11 g ile network üzerinden backup almadan duplicate yöntemi ile kopya olusturabiliyoruz. 10 g de duplicate yapilabiliyor fakat yine backup alip standby tarafinda bu dosyalari kullanmak durumunda kaliyoruz. Backupin alinmasi, standby tarafina yüklenmesi ve restore edilmesi adimlari düsünüldügünde backup-restore yönteminde epeyce vakit kaybi yasanmaktadir. Tabiki sunucular arasinda güçlü bir networkünüz yoksa duplicate de vakit alacaktir ama bana göre her halükarda bu yöntem en iyi metottur. Bu makalede Oracle ASM üzerinde çalisan bir veritabani için kurulum anlatilacaktir. \n<\/p>\n.<\/a>\n\n

\nOS = Linux\/Unix Oracle Database\/Grid Version = 11.2.0.3 PRIMARY\/PRODUCTION \nDatabase = ISTANBUL PRIMARY ASM DISKGROUP = +DATA STANDBY \nDatabase = ANKARA STANDBY ASM DISKGROUP = +DATAFKM \nStandby profile dosyasi isletim sistemi kullanicisi i\u00e7in ORACLE_BASE=\/oracle\/product;\n export ORACLE_BASE ORACLE_HOME=$ORACLE_BASE\/11.2.0\/db;\n export ORACLE_HOME ORACLE_SID=ANKARA;\n export ORACLE_SID DISPLAY=`hostname`:0.0;\n export DISPLAY PATH=$ORACLE_HOME\/bin:\/usr\/bin:\/etc:\/usr\/bin\/X11:\/usr\/local\/bin:$ORACLE_HOME\/OPatch:\/oracle\/product\/11.1.0\/crs\/bin:$PATH;\n export PATH LD_LIBRARY_PATH=$ORACLE_HOME\/lib:$ORACLE_HOME\/rdbms\/lib;\n export LD_LIBRARY_PATH SHLIB_PATH=$ORACLE_HOME\/lib32:$ORACLE_HOME\/rdbms\/lib32;\nexport SHLIB_PATH TMP=\/oracle\/oratmp;\n export TMP TMPDIR=\/oracle\/oratmp;\n export TMPDIR TEMP=\/oracle\/oratmp;\n export TEMP TEMPDIR=\/oracle\/oratmp;\n export TEMPDIR Production profile dosyasi isletim sistemi kullanicisi i\u00e7in ORACLE_BASE=\/oracle\/product;\n export ORACLE_BASE ORACLE_HOME=$ORACLE_BASE\/11.2.0\/db;\n export ORACLE_HOME ORACLE_SID=ISTANBUL;\n export ORACLE_SID DISPLAY=`hostname`:0.0;\n export DISPLAY PATH=$ORACLE_HOME\/bin:\/usr\/bin:\/etc:\/usr\/bin\/X11:\/usr\/local\/bin:$ORACLE_HOME\/OPatch:\/oracle\/product\/11.1.0\/crs\/bin:$PATH;\n export PATH LD_LIBRARY_PATH=$ORACLE_HOME\/lib:$ORACLE_HOME\/rdbms\/lib;\n export LD_LIBRARY_PATH SHLIB_PATH=$ORACLE_HOME\/lib32:$ORACLE_HOME\/rdbms\/lib32;\nexport SHLIB_PATH TMP=\/oracle\/oratmp;\n export TMP TMPDIR=\/oracle\/oratmp;\n export TMPDIR TEMP=\/oracle\/oratmp;\n export TEMP TEMPDIR=\/oracle\/oratmp;\n export TEMPDIR\n \n<\/div><\/code>\n\n

Standby Database Kurulumu 1.\tÖncelikle production veritabaninda force logging açilir. Asagidaki komutu çalistirarak force logging i açiyoruz. <\/p>\n\n\n

alter database force logging<\/div>\n<\/code> \n

2.\tStandby veritabaninda Database Software ve Grid Infrastructure kurulduktan sonra primary database den password dosyasi kopyalanir. Standby tarafinda asagidaki komut ile dosyayi kopyalayabilirsiniz. <\/p>\n\n\n

\nScp oracle\/password@production_db:$ORACLE_HOME\/dbs\/orapwISTANBUL\n$ORACLE_HOME\/dbs\/orapwANKARA Password file kopyalandiktan sonra production veritabanin init dosyasi olusturulur \n    ve standby tarafina kopyalanir. \n Production veritabaninda : \nsqlplus “\/as sysdba” SQL-> \ncreate pfile=’\/home\/oracle\/initANKARA.ora’ \nfrom spfile; daha sonra bu dosya standby tarafina kopyalanir. \nScp oracle\/password@production_db:\/home\/oracle\/initANKARA.ora \n$ORACLE_HOME\/dbs\/\n \n\n<\/div>\n<\/code>\n\n

\nInit dosyasini standby database tarafinda kullanabilmek için birkaç parametreyi degistirmemiz gerekecek. Production veritabanindan alinan parametre dosyasi asagidaki gibi olacaktir. \n\n<\/p>\n\n\n

\nISTANBUL.__db_cache_size=40533753856 \nISTANBUL.__oracle_base='\/oracle\/product' \nISTANBUL.__shared_pool_size=7784628224 \n*._ash_size=134217728 \n*.audit_file_dest='\/oracle\/product\/admin\/ISTANBUL\/adump' \n*.audit_trail='DB' \n*.compatible='11.2.0.0.0' \n*.control_files='+DATA\/ISTANBUL\/control01.ctl','+DATA\/ISTANBUL\/control02.ctl' \n*.cursor_sharing='EXACT' \n*.db_block_size=8192 \n*.db_cache_size=43622320128 \n*.db_domain='' \n*.db_file_multiblock_read_count=32 *.db_files=1000 \n*.db_name='ISTANBUL' \n*.diagnostic_dest='\/oracle\/product' \n*.dispatchers='(PROTOCOL=TCP) (SERVICE=ISTANBULXDB)' \n*.java_pool_size=78643200 \n*.job_queue_processes=50 \n*.large_pool_size=786432000 \n*.local_listener='LISTENER_ISTANBUL' \n*.log_archive_dest_1='LOCATION=+DATA' \n*.log_archive_format='%t_%s_%r.arc' \n*.log_buffer=10000000 *.open_cursors=65000 \n*.optimizer_dynamic_sampling=1 \n*.parallel_execution_message_size=65536 \n*.parallel_max_servers=32 \n*.parallel_servers_target=32 \n*.parallel_threads_per_cpu=1 \n*.pga_aggregate_target=10737418240 \n*.processes=1000 \n*.recyclebin='off' \n*.remote_login_passwordfile='EXCLUSIVE' \n*.resource_limit=FALSE \n*.sga_target=0 \n*.shared_pool_size=5368709120 \n*.star_transformation_enabled='TRUE' \n*.undo_management='AUTO' \n*.undo_tablespace='UNDO\n<\/div>\n<\/code> \n\n\n\n

\nAsagidaki gibi düzenlenir ve standby tarafinda çalisacak hale getirilir. \/oracle\/product\/admin\/ANKARA\/adump ilgili dizin standby tarafinda olusturulmus olmalidir Koyu renkli parametler disindaki parametreler ayni kalmalidir. <\/p>\n\n\n\n

\n*.audit_file_dest='\/oracle\/product\/admin\/ANKARA\/adump' \n*.audit_trail='DB' \n*.compatible='11.2.0.0.0' \n*.control_files='+DATAFKM\/ANKARA\/control01.ctl','+DATAFKM\/ANKARA\/control02.ctl' \n*.cursor_sharing='EXACT' \n*.db_block_size=8192 \n*.db_domain='' \n*.db_file_multiblock_read_count=32 \n*.db_files=1000 *.db_name='ISTANBUL' \n*.db_unique_name='ANKARA' \n*.diagnostic_dest='\/oracle\/product' \n*.dispatchers='(PROTOCOL=TCP) (SERVICE=ANKARAXDB)' \n*.job_queue_processes=50 *.log_archive_dest_1='LOCATION=+DATAFKM' \n*.log_archive_format='%t_%s_%r.arc' \n*.open_cursors=65000 \n*.optimizer_dynamic_sampling=1 \n*.parallel_execution_message_size=65536 \n*.parallel_max_servers=32 \n*.parallel_servers_target=32 \n*.parallel_threads_per_cpu=1 \n*.pga_aggregate_target=10737418240 \n*.processes=1000 \n*.recyclebin='off' \n*.remote_login_passwordfile='EXCLUSIVE' \n*.resource_limit=FALSE \n*.sga_target=24737418240 \n*.sga_max_size=24737418240 \n*.star_transformation_enabled='TRUE' \n*.undo_management='AUTO' \n*.undo_tablespace='UNDOTBS1'\n\n<\/div>\n<\/code> \n\n

\n3.\tStandby init dosyasi düzenlendikten sonra hem standby tarafinda hemde production tarafinda tnsnames.ora dosyasina her iki database için erisim bilgisi eklenir. $ORACLE_HOME\/network\/admin\/tnsnames.ora dosyasina asagidaki tns bilgileri girilir. \n<\/p>\n\n\n

\n\nISTANBUL = \n(\n   DESCRIPTION = \n   (\n      ADDRESS = \n      (PROTOCOL = TCP)\n      (HOST = istanbul_db_ip_veya_host)\n      (PORT = 1521)) \n      (CONNECT_DATA = \n      (SERVER = DEDICATED) \n      (SERVICE_NAME = ISTANBUL) \n   ) \n) \nANKARA = \n(\n   DESCRIPTION = \n   (\n      ADDRESS = \n      (PROTOCOL = TCP)\n      (HOST = ankara_db_ip_veya_host)\n      (PORT = 1521)) \n      (CONNECT_DATA = \n      (SERVER = DEDICATED) \n      (SID= ANKARA) \n   ) \n)\n\n<\/div>\n<\/code> \n\n

\n 4.\tStandby database nomount modda açilir ve database i dinleyecek listener olusturulur. <\/p>\n \n\n

\n\nSqlplus “\/as sysdba” \nSQL-> startup nomount; \n$ORACLE_HOME\/network\/admin\/listener.ora \nSID_LIST_LISTENER = \n(\n   SID_LIST = \n   (\n      SID_DESC = \n      (GLOBAL_DBNAME = ANKARA) \n      (ORACLE_HOME = $ORACLE_HOME) \n      (SID_NAME = ANKARA) \n   )\n) \nLISTENER = \n(\n   DESCRIPTION_LIST = \n   (\n      DESCRIPTION = \n      (\n         ADDRESS = \n         (PROTOCOL = IPC)\n         (KEY = EXTPROC1521)) \n         (ADDRESS = \n         (PROTOCOL = TCP)\n         (HOST = standby_ip_veya_host)(PORT = 1521)\n      ) \n   ) \n)\n\n<\/div>\n<\/code> \n\n\n

Listener dosyasi düzenlendikten sonra listener açilir.<\/p>\n \n\n\n

\nLsnrctl start LISTENER \nStandby tarafini init dosyasi ile açmistik fakat spfile ile çalismak daha kolay olacagi için spfile create edilir. \nSqlplus “\/as sysdba” \nSQL -> \ncreate spfile from pfile; \nSQL->shutdown abort; \nSQL->startup nomount; \nSQL->Show parameter spfile;\n<\/div>\n<\/code> \n.<\/a>\n

\n 5.\tSpfile create edildikten sonra standby ve primary database ler için asagidaki parametler set edilir. Standby database de sql komut satirinda çalistirilir <\/p>\n \n \n \n\n

\nALTER SYSTEM SET \nLOG_ARCHIVE_CONFIG='DG_CONFIG=( ISTANBUL, ANKARA)' \nSCOPE=BOTH; \nALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=ISTANBUL LGWR ASYNC \nVALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ISTANBUL' \nSCOPE=BOTH ; \nALTER SYSTEM SET DB_FILE_NAME_CONVERT ='+DATA\/ISTANBUL\/', '+DATAFKM\/ANKARA\/' \nSCOPE=SPFILE ; ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO SCOPE=BOTH ; \nALTER SYSTEM SET FAL_SERVER= ISTANBUL SCOPE=BOTH ;\nALTER SYSTEM SET FAL_CLIENT= ANKARA SCOPE=BOTH ;\nALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2='ENABLE' scope=BOTH; \nALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1='ENABLE' scope=BOTH;\nALTER SYSTEM SET log_file_name_convert= '+DATA\/ISTANBUL','+DATAFKM\/ANKARA' \nscope=SPFILE; \n production veritabaninda çalistirilir \nALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=( ISTANBUL, ANKARA)' \nSCOPE=BOTH ; ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=ANKARA LGWR ASYNC \nVALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ANKARA' \nSCOPE=BOTH ; ALTER SYSTEM SET DB_FILE_NAME_CONVERT ='+DATAFKM\/ANKARA\/', '+DATA\/ISTANBUL\/' SCOPE=SPFILE ;\nALTER SYSTEM SET LOG_FILE_NAME_CONVERT ='+DATAFKM\/ANKARA\/','+DATA\/ISTANBUL\/' SCOPE=SPFILE ; \nALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO SCOPE=BOTH ; \nALTER SYSTEM SET FAL_SERVER= ANKARA SCOPE=BOTH ; \nALTER SYSTEM SET FAL_CLIENT= ISTANBUL SCOPE=BOTH ; \n ----veritabani duplicate edilene kadar log akisini kesmekte fayda var duplicate sü\n--resince de production ortamdan arsiv loglar silinmezse daha sonra restore etmek zorunda kalmayiz.---- \nALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2='DEFER' scope=BOTH ;\n<\/div>\n<\/code> \n\n

\n6.\tHer iki tarafta da parametreler düzenlendikten sonra standby tarafi yeniden baslatilir. \n<\/p>\n\n\n\n

\nSqlplus “\/as sysdba” SQL -> \nshutdown abort; SQL -> startup nomount;\n<\/div>\n<\/code> \n\n

7.\tProduction veritabaninda standby log grouplar olusturulur. <\/p>\n\n\n

\nalter database add standby logfile \ngroup 29 ('+DATA') size 128M, \ngroup 30 ('+DATA') size 128M, \ngroup 31 ('+DATA') size 128M, \ngroup 32 ('+DATA') size 128M;\n<\/div>\n<\/code> \n\n

\n8.\tHer ne kadar duplicate ile controlfile kopyalansada production ortaminin controlfile backupi alinir ve standby tarafinda restore edilir. Primary database de :<\/p>\n\n \n

\n\nRman target \/ rman->\nbackup current controlfile for standby format '\/home\/oracle\/ForStbCtl_IDM_%U'; \nBackup alindiktan sonra standby tarafina kopyalanir.\nstandby da : scp oracle@production_db:\/home\/oracle\/\tForStbCtl_ISTANBUL_ \/home\/oracle \ndaha sonra standby da controlfile restore edilir.\nRman target \/ rman-> \nrestore controlfile from '\/home\/oracle\/ ForStbCtl_ISTANBUL_’;\n\n<\/div>\n<\/code> \n\n

9.\tProductionda rman e baglanip db duplicate baslatilir. Asagidaki komutlar production veritabaninda çalistirilir. Herhangi bir dizinde duplicate.rman adinda bir dosyaya kaydedecegim ve nohup ile arka planda çalismasini saglayacagim. <\/p>\n \n\n

\n\nCd \/home\/oracle Vi duplicate.rman \nconnect target \/ connect auxiliary sys\/sysIDMdb1@ANKARA; \nRUN { ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK; \nALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK; \nALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE DISK; \nALLOCATE AUXILIARY CHANNEL aux4 DEVICE TYPE DISK; \nALLOCATE AUXILIARY CHANNEL aux5 DEVICE TYPE DISK; \nALLOCATE AUXILIARY CHANNEL aux6 DEVICE TYPE DISK; \nallocate channel t1 type disk; \nallocate channel t2 type disk; \nallocate channel t3 type disk; \nallocate channel t4 type disk; \nallocate channel t5 type disk; \nallocate channel t6 type disk; \nduplicate target database for standby from active database; \nrelease channel aux1; \nrelease channel aux2; \nrelease channel aux3; \nrelease channel aux4; \nrelease channel aux5; \nrelease channel aux6; \nrelease channel t1; \nrelease channel t2; \nrelease channel t3; \nrelease channel t4; \nrelease channel t5; \nrelease channel t6; } \nProduction_db_host -> \nnohup rman cmdfile duplicate.rman log duplicate.log & \nduplicate.log dosyasi takip edilir\n\n<\/div>\n<\/code>\n\n

\n10.\t Duplicate islemi bittikten sonra primary tarafta log gönderme açilir. <\/p>\n\n\n

\nProduction veritabanin da : sqlplus “\/as sysdba” SQL-> \nALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2='ENABLE' \nscope=both; \nStandby tarafinda ise arsiv isleme prosesi baslatilir. \nSqlplus “\/as sysdba” \nSQL -> \nALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT \nLOGFILE DISCONNECT; \nAsagidaki sorgu ile standby da prosesin arsiv isleyip islemedigi kontrol edilir. \nSELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;\n\n\n<\/div>\n<\/code>\n\n

\nRMAN Duplicate yöntemi database kopyalamada kullanilabilecek en pratik ve kolay yöntemdir sadece dataguard\/standby için degil production veritabaninizin kopyasina ihtiyaciniz oldugunda da kullanabilirsiniz. Asagidaki linklerden rman duplicate ile nasil veritabani kopyasi olusturulacagi ile iligli detayli bilgiye ulasabilirsiniz. <\/p>\n\n

Standby veritabanlari production veritabanlarinin bire bir kopyasidir ve bu databaseler genelde felaket durumlarinda kullanilmak için yedek database olarak kullanilir. Bu makalede standby veritabaninin rman duplicate ile nasil kuruldugundan bahsedecegim.<\/p>\n","protected":false},"author":551,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[423],"tags":[5142,5718,5132,4383,5709,4392],"_links":{"self":[{"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/posts\/202"}],"collection":[{"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/users\/551"}],"replies":[{"embeddable":true,"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/comments?post=202"}],"version-history":[{"count":0,"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/posts\/202\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/categories?post=202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.yazilimmutfagi.com\/index.php\/wp-json\/wp\/v2\/tags?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

\nOracle 9.2 = http:\/\/docs.oracle.com\/cd\/B10501_01\/server.920\/a96566\/rcmdupdb.htm
\nOracle 10gR2 = http:\/\/docs.oracle.com\/cd\/B19306_01\/backup.102\/b14191\/rcmdupdb.htm
Oracle 11gR1= http:\/\/docs.oracle.com\/cd\/B28359_01\/backup.111\/b28270\/rcmdupdb.htm
\n<\/p>\n.<\/a>","protected":false},"excerpt":{"rendered":"