{"id":5052,"date":"2013-08-01T10:43:58","date_gmt":"2013-08-01T07:43:58","guid":{"rendered":"http:\/\/www.koraykey.com\/?p=5052"},"modified":"2013-08-01T10:43:58","modified_gmt":"2013-08-01T07:43:58","slug":"oracle-veritabanini-dosya-sisteminden-asm-dosya-sistemine-tasima-yapilandirmasi-file-system-to-asm","status":"publish","type":"post","link":"https:\/\/www.koraykey.com\/?p=5052","title":{"rendered":"Oracle Veritaban\u0131n\u0131 Dosya Sisteminden ASM Dosya Sistemine Ta\u015f\u0131ma Yap\u0131land\u0131rmas\u0131 (File System to ASM)"},"content":{"rendered":"

\"OracleDbEnt\"<\/a>Bu makalemizde “Oracle Veritaban\u0131n\u0131 Dosya Sisteminden ASM Dosya Sistemine Ta\u015f\u0131ma Yap\u0131land\u0131rmas\u0131” konusunu inceleyece\u011fiz. Veritaban\u0131m\u0131z\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucuda bulunan veri dosyalar\u0131m\u0131z\u0131 i\u015fletim sistemi dosya sisteminden ASM dosya sistemine (File System to ASM) ta\u015f\u0131yaca\u011f\u0131z. Senaryomuza g\u00f6re \u00f6nceden dosya sistemine kurulmu\u015f bir veritaban\u0131 sunucumuza \u00f6ncelikle atanm\u0131\u015f olan iki diskimizi “DATA” ve “FRA” olarak “ASM Library” ile damgalayaca\u011f\u0131z ve sonras\u0131nda “Grid Infrastructure” yaz\u0131l\u0131m\u0131n\u0131 kuraca\u011f\u0131z.<\/span><\/p>\n

1. \u0130\u015flemlerimiz boyunca bir sorun olmamas\u0131 i\u00e7in sunucumuzda \u00e7al\u0131\u015fan veritaban\u0131 ve ilgili servislerimizi durduruyoruz. Ayr\u0131ca bu i\u015flemlere ba\u015flamadan \u00f6nce t\u00fcm veritaban\u0131m\u0131z\u0131n bir yede\u011fini almal\u0131y\u0131z.<\/span><\/p>\n

-- A\u015fa\u011f\u0131daki i\u015flemleri \"oracle\" kullan\u0131c\u0131m\u0131z ile yap\u0131yoruz.<\/span>\r\n\r\n# su - oracle<\/span>\r\n\r\n-- Oracle Enterprise Manager konsolumuzu durduruyoruz.<\/span>\r\n\r\n$ emctl stop dbconsole<\/span>\r\n\r\n-- Veritaban\u0131 ve network servislerimizi durduruyoruz.<\/span>\r\n\r\n$ dbshut $ORACLE_HOME<\/span><\/pre>\n
2.\u00a0Sunucumuza veri depolama \u00fcnitemizden atanm\u0131\u015f olan iki adet diskimizi belirleyip bunlar\u0131 “ASM Library” ile damgal\u0131yoruz. E\u011fer disklerimiz i\u00e7in “Multipath” yap\u0131land\u0131rmas\u0131 yapmam\u0131z gerekiyorsa “Linux \u0130\u015fletim Sistemlerinde Multipath Yap\u0131land\u0131rmas\u0131”<\/a> yaz\u0131m\u0131z\u0131 inceleyebilirsiniz.<\/span><\/p>\n
-- Sunucumuzda bulunan disklerimizi listeliyoruz.<\/span>\r\n\r\n# ll \/dev\/sd*<\/span>\r\nbrw-rw---- 1 root disk 8,  0 Jul 31 18:47 \/dev\/sda<\/span>\r\nbrw-rw---- 1 root disk 8,  1 Jul 31 18:47 \/dev\/sda1<\/span>\r\nbrw-rw---- 1 root disk 8,  2 Jul 31 18:47 \/dev\/sda2<\/span>\r\nbrw-rw---- 1 root disk 8, 16 Jul 31 18:47 \/dev\/sdb<\/span>\r\nbrw-rw---- 1 root disk 8, 32 Jul 31 18:47 \/dev\/sdc<\/span>\r\n\r\n-- Sistem disklerimiz a\u015fa\u011f\u0131daki gibi,<\/span>\r\nbrw-rw---- 1 root disk 8,  0 Jul 31 18:47 \/dev\/sda<\/span>\r\nbrw-rw---- 1 root disk 8,  1 Jul 31 18:47 \/dev\/sda1<\/span>\r\nbrw-rw---- 1 root disk 8,  2 Jul 31 18:47 \/dev\/sda2<\/span>\r\n\r\n-- ASM i\u00e7in kullanaca\u011f\u0131m\u0131z disklerimizse a\u015fa\u011f\u0131daki gibidir.<\/span>\r\nbrw-rw---- 1 root disk 8, 16 Jul 31 18:47 \/dev\/sdb<\/span>\r\nbrw-rw---- 1 root disk 8, 32 Jul 31 18:47 \/dev\/sdc<\/span><\/pre>\n
2. Sunucumuzda ASM i\u00e7in kullanaca\u011f\u0131m\u0131z disklerde partition table olu\u015fturuyoruz.<\/span><\/p>\n
# fdisk \/dev\/sdb<\/span>\r\n\r\nWARNING: DOS-compatible mode is deprecated. It's strongly recommended to<\/span>\r\n         switch off the mode (command 'c') and change display units to<\/span>\r\n         sectors (command 'u').<\/span>\r\n\r\nCommand (m for help): n<\/span>\r\nCommand action<\/span>\r\n   e   extended<\/span>\r\n   p   primary partition (1-4)<\/span>\r\np<\/span>\r\nPartition number (1-4): 1<\/span>\r\nFirst cylinder (1-1305, default 1): <\/span>\r\nUsing default value 1<\/span>\r\nLast cylinder, +cylinders or +size{K,M,G} (1-1305, default 1305): <\/span>\r\nUsing default value 1305<\/span>\r\n\r\nCommand (m for help): w<\/span>\r\nThe partition table has been altered!<\/span>\r\n\r\nCalling ioctl() to re-read partition table.<\/span>\r\nSyncing disks.<\/span>\r\n\r\n1. soruda \"n\" se\u00e7ene\u011fini veriyoruz.<\/span>\r\n2. soruda t\u00fcr\u00fcn\u00fc soruyor \u201cp\u201d se\u00e7ene\u011fini veriyoruz primary olarak<\/span>\r\nolu\u015fturuyoruz.<\/span>\r\n3. soruda enter diyerek default se\u00e7ene\u011fi veriyoruz.<\/span>\r\nD\u00f6rd\u00fcnc\u00fc ve Be\u015finci sorular\u0131 enter diyerek default se\u00e7ene\u011finde b\u0131rak\u0131yoruz.<\/span>\r\n\r\n-- Ayn\u0131 i\u015flemi di\u011fer diskimiz i\u00e7inde yap\u0131yoruz.<\/span>\r\n\r\n# fdisk \/dev\/sdc<\/span>\r\n\r\nWARNING: DOS-compatible mode is deprecated. It's strongly recommended to<\/span>\r\n         switch off the mode (command 'c') and change display units to<\/span>\r\n         sectors (command 'u').<\/span>\r\n\r\nCommand (m for help): n<\/span>\r\nCommand action<\/span>\r\n   e   extended<\/span>\r\n   p   primary partition (1-4)<\/span>\r\np<\/span>\r\nPartition number (1-4): 1<\/span>\r\nFirst cylinder (1-1305, default 1): <\/span>\r\nUsing default value 1<\/span>\r\nLast cylinder, +cylinders or +size{K,M,G} (1-1305, default 1305): <\/span>\r\nUsing default value 1305<\/span>\r\n\r\nCommand (m for help): w<\/span>\r\nThe partition table has been altered!<\/span>\r\n\r\nCalling ioctl() to re-read partition table.<\/span>\r\nSyncing disks.<\/span>\r\n\r\n-- Art\u0131k disklerimiz haz\u0131r.<\/span>\r\n\r\n# ll \/dev\/sd*<\/span>\r\nbrw-rw---- 1 root disk 8, 16 Mar 10 23:00 \/dev\/sdb<\/span>\r\nbrw-rw---- 1 root disk 8, 17 Mar 10 23:00 \/dev\/sdb1<\/span>\r\nbrw-rw---- 1 root disk 8, 32 Mar 10 23:03 \/dev\/sdc<\/span>\r\nbrw-rw---- 1 root disk 8, 33 Mar 10 23:03 \/dev\/sdc1<\/span>\r\n\r\n-- Komutunu \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131m\u0131zda  sdb1 ve sdc1 olarak disklerimizin olu\u015ftu\u011funu\r\ng\u00f6r\u00fcyoruz.<\/span><\/pre>\n
3. Sunucumuzda \u201cOracle ASM Library\u201d ile disklerimizi ASM Dosya Sistemi i\u00e7in damgalayabiliriz.<\/span><\/p>\n
-- \u00d6ncelikle ASM Library i\u00e7in yetkilendirme ve yap\u0131land\u0131rma ayar\u0131m\u0131z\u0131<\/span>\r\nyap\u0131yoruz.<\/span>\r\n\r\n# oracleasm configure -I<\/span>\r\nConfiguring the Oracle ASM library driver.<\/span>\r\n\r\nThis will configure the on-boot properties of the Oracle ASM library<\/span>\r\ndriver.  The following questions will determine whether the driver is<\/span>\r\nloaded on boot and what permissions it will have.  The current values<\/span>\r\nwill be shown in brackets ('[]').  Hitting <ENTER> without typing an<\/span>\r\nanswer will keep that current value.  Ctrl-C will abort.<\/span>\r\n\r\nDefault user to own the driver interface []: oracle<\/span>\r\nDefault group to own the driver interface []: dba<\/span>\r\nStart Oracle ASM library driver on boot (y\/n) [n]: y<\/span>\r\nScan for Oracle ASM disks on boot (y\/n) [y]: y<\/span>\r\n\r\nThe next two configuration options take substrings to match device names.<\/span>\r\nThe substring \"sd\" (without the quotes), for example, matches \"sda\", \"sdb\",<\/span>\r\netc.  You may enter more than one substring pattern, separated by spaces.<\/span>\r\nThe special string \"none\" (again, without the quotes) will clear the value.<\/span>\r\n\r\nDevice order to scan for ASM disks []: <\/span>\r\nDevices to exclude from scanning []: <\/span>\r\nUse device logical block size for ASM (y\/n) [n]: y<\/span>\r\nWriting Oracle ASM library driver configuration: done<\/span>\r\n\r\n-- \u015eimdi Oracle ASM Kernel mod\u00fcl\u00fcn\u00fc aktif edelim.<\/span>\r\n\r\n# oracleasm init<\/span>\r\nCreating \/dev\/oracleasm mount point: \/dev\/oracleasm<\/span>\r\nLoading module \"oracleasm\": oracleasm<\/span>\r\nConfiguring \"oracleasm\" to use device logical block size <\/span>\r\nMounting ASMlib driver filesystem: \/dev\/oracleasm<\/span>\r\n\r\nBu i\u015flemlerden sonra art\u0131k ASM i\u00e7in disklerimizi olu\u015fturup<\/span>\r\ndamgalayabiliriz.<\/span>\r\n\r\n# oracleasm createdisk data1 \/dev\/sdb1<\/span>\r\nWriting disk header: done<\/span>\r\nInstantiating disk: done<\/span>\r\n\r\n# oracleasm createdisk fra1 \/dev\/sdc1<\/span>\r\nWriting disk header: done<\/span>\r\nInstantiating disk: done<\/span>\r\n\r\n-- Olu\u015fturdu\u011fumuz disklerimizi listelemek i\u00e7in<\/span>\r\n\r\n# ll \/dev\/oracleasm\/disks\/<\/span>\r\ntotal 0<\/span>\r\nbrw-rw---- 1 oracle dba 8, 17 Mar 10 23:11 DATA1<\/span>\r\nbrw-rw---- 1 oracle dba 8, 33 Mar 10 23:12 FRA1<\/span>\r\n\r\nveya<\/span>\r\n\r\n# oracleasm listdisks<\/span>\r\nDATA1<\/span>\r\nFRA1<\/span>\r\n\r\n-- Yukar\u0131da g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi \"DATA\" ve \"FRA\" ad\u0131nda 2 diskimiz olu\u015fmu\u015f ve<\/span>\r\nASM i\u00e7in damgalanm\u0131\u015f durumda.<\/span><\/pre>\n
4. Oracle\u00a0Grid Infrastructure kurulumunu yapabilmek, kurulum ve patch dosyalar\u0131m\u0131z\u0131 koyabilmek i\u00e7in gerekli olan dizinleri yarat\u0131p haklar\u0131 at\u0131yoruz.<\/span><\/p>\n
# mkdir -p \/u01\/app\/11.2.0.3\/grid\r\n# mkdir -p \/u01\/orainstall\r\n# mkdir -p \/u01\/orainstall\/opatch\r\n# mkdir -p \/u01\/orainstall\/patchset\r\n# chown -R oracle:oinstall \/u01\/app\/11.2.0.3\/grid\r\n# chmod -R 775 \/u01\/app\/11.2.0.3\/grid\r\n\r\n\/u01\/app\/11.2.0.3\/grid\r\nGrid Infrastructure kurulum dizini.\r\n\r\n\/u01\/orainstall\r\nOracle kurulum dosyalar\u0131n\u0131 ataca\u011f\u0131m\u0131z dizin.\r\n<\/span><\/pre>\n
5. Kuruluma ge\u00e7ebilmemiz i\u00e7in ftp yada ba\u015fka bir y\u00f6ntem ile kurulum dosyalar\u0131m\u0131z\u0131 olu\u015fturdu\u011fumuz \u201c\/u01\/orainstall\/\u201d dizini alt\u0131na at\u0131yoruz. E\u011fer sunucumuzda ftp server \u00f6zelli\u011fi aktif edilmemi\u015fse \u201cLinux \u0130\u015fletim Sistemlerinde HTTP ve FTP Server Yap\u0131land\u0131rmas\u0131\u201d<\/a>\u00a0makalemizden faydalanarak gerekli ayarlar\u0131 yapabiliriz<\/span>. Oracle kullan\u0131c\u0131s\u0131 ile kopyalama i\u015flemimiz bitti\u011finde kurulum dosyalar\u0131m\u0131z\u0131 kontrol ediyoruz.<\/span><\/p>\n
# su - oracle<\/span>\r\n\r\n$ ls<\/span>\r\np10404530_112030_Linux-x86-64_3of7.zip<\/span><\/pre>\n
6. Oracle Grid Infrastructure kurulumu i\u00e7in ilk 3. zip dosyas\u0131na ihtiyac\u0131m\u0131z var. Bu kurulum dosyalar\u0131m\u0131z\u0131 OTN veya MOS hesaplar\u0131m\u0131z ile indirebiliriz. E\u011fer son versiyon kurulumu yapabilmek istiyorsak (11.2.0.3.0 gibi) MOS dedi\u011fimiz Oracle Support \u00fcyeli\u011fimizin olmas\u0131 gerekmektedir. E\u011fer buna sahip de\u011filsek o zaman OTN hesab\u0131m\u0131z ile \u00e7\u0131km\u0131\u015f olan ilk versiyonu (11.2.0.1.0 gibi) indirebiliriz. Burada dikkat edece\u011fimiz veritaban\u0131 versiyonumuz ile Grid versiyonumuzun uyumlu bir versiyonda olmas\u0131. Bunun i\u00e7in kurulum sonras\u0131 gerekli kontrolleri yaparak gerekiyorsa\u00a0patch ge\u00e7me <\/a>i\u015flemini uygulamal\u0131y\u0131z. \u015eimdi bu s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f dosyalar\u0131m\u0131z\u0131 oracle kullan\u0131c\u0131s\u0131 ile a\u00e7\u0131yoruz.<\/span><\/p>\n
-- S\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f dosyam\u0131z\u0131 a\u00e7\u0131yoruz.\r\n\r\n$ cd \/u01\/orainstall<\/span>\r\n$ unzip p10404530_112030_Linux-x86-64_3of7.zip\r\n\r\nAy\u0131klama i\u015flemi tamamland\u0131\u011f\u0131nda yer kaplamamas\u0131 i\u00e7in istersek .zip dosyalar\u0131n\u0131\r\ntemizleyebiliriz.\r\n\r\n$ rm p10404530_112030_Linux-x86-64_*<\/span><\/pre>\n
7. Veritaban\u0131m\u0131z\u0131 \u201cdbca\u201d\u00a0arac\u0131 ile sunucu \u00fczerinde de\u011filde uzaktan kendi bilgisayar\u0131m\u0131zda yap\u0131lacaksa ekran\u0131 export edebiliriz. Bunun i\u00e7in \u201cXmanager\u201d<\/a>\u00a0vb. em\u00fclat\u00f6r yaz\u0131l\u0131mlar\u0131 kullan\u0131labilir. Bu yaz\u0131l\u0131m\u0131 bilgisayar\u0131m\u0131za kurdu\u011fumuzda \u201cXmanager \u2013 Passive\u201d program\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmal\u0131y\u0131z. G\u00f6rev \u00e7ubu\u011funda yaz\u0131l\u0131m \u00e7al\u0131\u015facak ve export etti\u011fimiz ekran\u0131 kendi bilgisayar\u0131m\u0131zdan y\u00f6netebilece\u011fiz. Bununla beraber \u201cVNC Server\u201d arac\u0131l\u0131\u011f\u0131 ile de sunucuya ba\u011flanabilir ve kurulumu direk sunucu \u00fczerinden yapabiliriz. Bunun i\u00e7in \u201cLinux \u0130\u015fletim Sistemlerinde VNC Server Yap\u0131land\u0131rmas\u0131\u201d<\/a>\u00a0makalemizden yararlanabilirsiniz. \u00d6nerilen kurulumu VNC Server veya sunucu \u00fczerinden yapman\u0131z \u00e7\u00fcnk\u00fc kurulum a\u015famas\u0131nda network vb. kesintide kurulumunuz yar\u0131m kalabilir.<\/span><\/p>\n
-- A\u015fa\u011f\u0131daki i\u015flemleri \"oracle\" kullan\u0131c\u0131s\u0131 ile yapmal\u0131y\u0131z.<\/span>\r\n\r\n-- \u00d6ncelikle Xmanager vb. Em\u00fclat\u00f6r program\u0131n\u0131 bilgisayar\u0131m\u0131zda \u00e7al\u0131\u015ft\u0131rmal\u0131y\u0131z.<\/span>\r\nArd\u0131ndan a\u015fa\u011f\u0131daki komut ile g\u00f6r\u00fcnt\u00fcy\u00fc export etmeliyiz.<\/span>\r\n\r\n$ DISPLAY=<machine-name>:0.0; export DISPLAY<\/span>\r\n\r\n\u00d6rnek;<\/span>\r\n\r\n$ DISPLAY=192.168.2.83:0.0; export DISPLAY<\/span>\r\n\r\nTest i\u00e7in;<\/span>\r\n\r\n$ xclock<\/span>\r\n\r\n-- Yazd\u0131\u011f\u0131m\u0131zda ekran\u0131m\u0131zda bir saat yaz\u0131l\u0131m\u0131n\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6rmeliyiz. E\u011fer<\/span>\r\na\u00e7\u0131lm\u0131yorsa ayarlarda bir sorun var demektir. Firewall vb. ayarlar\u0131m\u0131z\u0131 kontrol<\/span>\r\netmeliyiz.<\/span><\/pre>\n
8. Bu i\u015flemlerin tamam\u0131 bitti\u011finde kuruluma ge\u00e7ebiliriz. \u201cOracle Grid Infrastructure\u201d yaz\u0131l\u0131m\u0131n\u0131n kurulumuna ba\u015fl\u0131yoruz.<\/span><\/p>\n
-- Oracle kullan\u0131c\u0131s\u0131 ile sistemimize ba\u011fl\u0131yken<\/span>\r\n\r\n$ cd \/u01\/orainstall\/grid\/<\/span>\r\n\r\nkurulum dizininde bulunan<\/span>\r\n\r\n$ .\/runInstaller<\/span>\r\n\r\nuygulamas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131yoruz.<\/span><\/pre>\n
9. A\u00e7\u0131lan kar\u015f\u0131lama ekran\u0131nda g\u00fcncellemeler i\u00e7in bizden \u201cOracle Support MOS\u201d hesab\u0131n\u0131 istiyor bu ad\u0131m\u0131 \u201cSkip software updates\u201d se\u00e7ene\u011fini se\u00e7erek \u201cNext\u201d\u00a0d\u00fc\u011fmesine t\u0131kl\u0131yoruz.<\/span><\/p>\n
\"DB_Install_1\"<\/a><\/p>\n
10. Kurulumumuzu \u201cStandalone\u201d olarak yapaca\u011f\u0131m\u0131z i\u00e7in \u201cConfigure Oracle Grid Infrastructure for a Standalone Server\u201d se\u00e7ene\u011fini se\u00e7erek \u201cNext\u201d d\u00fc\u011fmesine t\u0131kl\u0131yoruz.<\/span><\/p>\n
\"DB_Install_2\"<\/a><\/p>\n
11. Dil se\u00e7ene\u011fimizi varsay\u0131lan olarak \u201cEnglish\u201d olarak se\u00e7ili b\u0131rak\u0131yoruz ve \u201cNext\u201d d\u00fc\u011fmesine t\u0131kl\u0131yoruz.<\/span><\/p>\n
\"DB_Install_3\"<\/a><\/p>\n
12. Daha \u00f6nce olu\u015fturdu\u011fumuz ASM Disklerimizi burada kullan\u0131ma sunuyoruz. \u201cDisk Group Name\u201d olarak DATA yaz\u0131yoruz ve \u201cRedundancy\u201d olarak \u201cExternal\u201d se\u00e7iyoruz ve \u201cNext\u201d d\u00fc\u011fmesine t\u0131kl\u0131yoruz. Buradaki se\u00e7enekleri a\u00e7\u0131klayacak olursak.<\/span><\/p>\n
External\u00a0 : <\/strong>Yede\u011fi yoktur.Ancak en performansl\u0131 moddur. Genelde hardware mirror varsa kullan\u0131l\u0131r ve varsay\u0131lan se\u00e7enektir. Burada \u015f\u00f6yle d\u00fc\u015f\u00fcnebiliriz. Bir veri depolama (storage) \u00fcnitemiz var ve oradan sunucumuza disk atan\u0131yor ve mirror orada veri depolama \u00fcnitesi katman\u0131nda yap\u0131ld\u0131\u011f\u0131 i\u00e7in bizim ayr\u0131ca oracle asm taraf\u0131nda bir mirror olu\u015fturmam\u0131za gerek kalm\u0131yor.<\/span><\/p>\n
Normal\u00a0 : <\/strong>ASM\u2019nin 2 y\u00f6nl\u00fc mirroring yapt\u0131\u011f\u0131 konfig\u00fcrasyondur. Bu durumda veri tutarl\u0131l\u0131\u011f\u0131 artar ancak disk alan\u0131ndan taviz verilir.<\/span><\/p>\n
High\u00a0 : <\/strong>ASM\u2019nin 3 y\u00f6nl\u00fc mirroring yapt\u0131\u011f\u0131 konfig\u00fcrasyondur. Bu durumda veri tutarl\u0131l\u0131\u011f\u0131 artar ancak disk alan\u0131ndan taviz verilir. Daha fazla veri sa\u011flaml\u0131\u011f\u0131 tesis edilmektedir.<\/span><\/p>\n
\"DB_Install_4\"<\/a><\/p>\n
13. Asm Library alt\u0131nda olu\u015fan disklerin yolunu sisteme tan\u0131t\u0131yoruz \u201cChange Discovery Path\u201d d\u00fc\u011fmesine t\u0131klayarak a\u00e7\u0131lan pencerede disklerin yolu olan \u201c\/dev\/oracleasm\/disks\u201d yolunu yaz\u0131yoruz.<\/span><\/p>\n
\"DB_Install_5\"<\/a><\/p>\n
14. Sistemimizdeki Oracle ASM damgal\u0131 \u00fcye diskleri art\u0131k\u00a0\u201dCandidate Disks\u201d se\u00e7ene\u011fi se\u00e7iliyken g\u00f6rebiliyoruz. \u201cDATA\u201d disk grubunu yap\u0131land\u0131rd\u0131\u011f\u0131m\u0131z i\u00e7in a\u015fa\u011f\u0131daki alandan \u201cDATA1\u2033 yaz\u0131l\u0131 diskimizi se\u00e7iyoruz. ASM \u201cAllocation Units\u201d konusundan bahsedecek olursak e\u011fer bunlar\u0131 veritaban\u0131 instance\u2019\u0131n\u0131n bloklar\u0131 veya extent\u2019leri olarak d\u00fc\u015f\u00fcnebilirsiniz. Ama\u00e7lar\u0131 bu miktar kadar alan\u0131n tahsis edilerek ilerlenmesini g\u00f6stermektir. Disk gruplar\u0131 yarat\u0131l\u0131rken tan\u0131mlanabilirler ve varsay\u0131lan olarak 1 MB olurlar. 11g ile birlikte bu miktar da de\u011fi\u015febilmektedir ve 2, 4, 8, 16, 32 ve en fazla 64 MB olarak yeniden tan\u0131mlanabilmektedirler. Ayn\u0131 db_block_size\u2019da oldu\u011fu gibi d\u00fc\u015f\u00fck olursa daha h\u0131zl\u0131 cache\u2019lenecek ve b\u00fcy\u00fck olursa da arka arkaya okuma yap\u0131ld\u0131\u011f\u0131 zaman daha efektif olacakt\u0131r. VLDB (Very Large Database) tipi veri ambarlar\u0131nda y\u00fcksek AU kullanmak faydal\u0131 olacakt\u0131r. AU\u2019nun miktar\u0131n\u0131 disk grup yarat\u0131l\u0131rken g\u00f6sterebiliyoruz ancak sonradan de\u011fi\u015ftiremiyoruz. ASM \u201cFiles\u201d ise AU\u2019lardan olu\u015fan extent\u2019lerdir. Dosya adlar\u0131 + ile ba\u015flarlar ve ASM instance\u2019\u0131 taraf\u0131ndan y\u00f6netilirler. Dosya isimleri genelde de\u011fi\u015fken say\u0131lardan olu\u015fmaktad\u0131r ancak bu dosya isimlerine (\u00f6rne\u011fin bir datafile) alias verme \u015fans\u0131m\u0131z bulunmaktad\u0131r. Bu dosya isimleri benzersizdir ve hi\u00e7bir zaman ba\u015fka bir datafile ismi ile \u00e7ak\u0131\u015fmaz. Bu da yine ASM\u2019nin bize sa\u011flad\u0131\u011f\u0131 faydalardan yaln\u0131zca bir tanesidir. ASM\u2019nin y\u00f6netti\u011fi dosyalar disk\u2019ler \u00fczerinde SAME metodolojisi ile tutulmaktad\u0131r (Stripe-And-Mirror Everything). ASM dosyalar\u0131ndan kast\u0131m\u0131z nedir? Datafile, kontrol dosyas\u0131, redolog dosyas\u0131, RMAN yedekleri gibi. Buras\u0131 \u00f6nemli, 11g Release 2\u2032ye kadar ASM, OCR dosyalar\u0131, cluster-voting disk, alert log dosyalar\u0131, trace dosyalar\u0131 ve Oracle binary\u2019leri gibi dosyalar\u0131 desteklemiyordu ancak 11gR2 bu k\u0131s\u0131t\u0131 ortadan kald\u0131rarak, bu tipte dosyalar\u0131n da ASM taraf\u0131ndan desteklenmesini sa\u011flad\u0131. 11gR2\u2032yi tercih etmek ve kullanmak i\u00e7in yine \u00e7ok ufak ama b\u00fcy\u00fck bir neden. Yaz\u0131m\u0131n ba\u015f\u0131nda belirtti\u011fim \u201cExtent Map\u201d ile ilgili de \u015funlar\u0131 ifade edebilirim. Extent map, ASM\u2019nin y\u00f6netti\u011fi dosyalar\u0131n disk \u00fczerinde nerede oldu\u011fu bilgisine sahiptir. Tabii tablolar\u0131n veya objelerin nerede oldu\u011fundan \u00f6te bu objelerin bulundu\u011fu extent\u2019lerin nerede durdu\u011funun bilgisine sahiptir.<\/span><\/p>\n
\"DB_Install_6\"<\/a><\/p>\n
15. Oracle ASM kullan\u0131c\u0131lar\u0131 i\u00e7in bir parola belirliyoruz. Bu parolay\u0131 asla unutmamal\u0131y\u0131z. Daha sonra veritaban\u0131 kurulum a\u015famas\u0131nda bu parola ASM disk grubuna eri\u015febilmek i\u00e7in gerekli olacakt\u0131r. Her iki kullan\u0131c\u0131ya ayn\u0131 parolay\u0131 atamak i\u00e7in \u201cUse same passwords for these accounts\u201d se\u00e7ene\u011fini se\u00e7erek her iki kullan\u0131c\u0131ya ayn\u0131 parolay\u0131 at\u0131yoruz.<\/span><\/p>\n
\"DB_Install_7\"<\/a><\/p>\n
16. Atam\u0131\u015f oldu\u011fumuz parola e\u011fer oracle \u00f6nerilen parola politikas\u0131na uygun de\u011filse a\u015fa\u011f\u0131daki gibi uyar\u0131 veriyor. Burada \u201cYes\u201d d\u00fc\u011fmesine t\u0131klayarak devam ediyoruz.<\/span><\/p>\n
\"DB_Install_8\"<\/a><\/p>\n
17. Kurulumlar\u0131n hangi i\u015fletim sistemi gruplar\u0131 ile yap\u0131laca\u011f\u0131n\u0131 soruyor burada \u201coinstall\u201d veya \u201cdba\u201d gruplar\u0131 se\u00e7ilerek kurulum yap\u0131labilir. Tek olmas\u0131 d\u00fc\u015f\u00fcncesiyle \u201cdba\u201d olarak se\u00e7iyoruz ve \u201cNext\u201d d\u00fc\u011fmesine t\u0131kl\u0131yoruz.<\/span><\/p>\n
\"DB_Install_9\"<\/a>18. Kurulum sihirbaz\u0131 bu se\u00e7imlerinde standart d\u0131\u015f\u0131 oldu\u011funu s\u00f6yl\u00fcyor burada verdi\u011fi uyar\u0131ya\u00a0ekran\u0131na\u00a0\u201dYes\u201d d\u00fc\u011fmesini t\u0131klayarak devam ediyoruz.<\/span><\/p>\n
\"DB_Install_10\"<\/a><\/p>\n
19. Oracle grid kurulumunun yap\u0131laca\u011f\u0131 dizinleri se\u00e7iyoruz. Dizinleri a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcndeki gibi se\u00e7iyoruz ve daha \u00f6nce yaratt\u0131\u011f\u0131m\u0131z dizinlere kurulumun yap\u0131lmas\u0131n\u0131 sa\u011fl\u0131yoruz.<\/span><\/p>\n
\"DB_Install_11\"<\/a><\/p>\n
20. Grid home dizinimizin Oracle Base dizini d\u0131\u015f\u0131nda oldu\u011fu konusunda bizi uyar\u0131yor. Bu uyar\u0131 ekran\u0131na \u201cYes\u201d d\u00fc\u011fmesini t\u0131klayarak devam ediyoruz.<\/span><\/p>\n
\"DB_Install_12\"<\/a><\/p>\n
21. Oracle Inventory dizini nereye yarataca\u011f\u0131 konusunda bilgi veriyor burada \u201cNext\u201d d\u00fc\u011fmesini t\u0131klayarak devam ediyoruz.<\/span><\/p>\n
\"DB_Install_13\"<\/a><\/p>\n
22. Kurulumumuzda herhangi bir sorun yoksa \u00f6ngereksinimlerin tamam\u0131 uygunsa kurulum i\u00e7in \u00f6zet bilgi ekran\u0131 kar\u015f\u0131m\u0131za gelecektir. Kuruluma ba\u015flamak i\u00e7in \u201cInstall\u201d d\u00fc\u011fmesini t\u0131kl\u0131yoruz.<\/span><\/p>\n
\"DB_Install_14\"<\/a><\/p>\n
23. Kurulum a\u015famalar\u0131n\u0131 a\u015fa\u011f\u0131daki ekrandan takip edebiliriz.<\/span><\/p>\n
\"DB_Install_15\"<\/a><\/p>\n
24. Kurulum sonuna do\u011fru bizden \u201croot\u201d kullan\u0131c\u0131s\u0131 ile 2 adet .sh scripti \u00e7al\u0131\u015ft\u0131rmam\u0131z\u0131 istiyor. Bu scriptler Inventory ve haklar\u0131n ayarlanmas\u0131 i\u00e7in gerekli e\u011fer atlarsak kurulum ba\u015far\u0131s\u0131z olacakt\u0131r.<\/span><\/p>\n
\"GridtoAsm_1\"<\/a><\/p>\n
Script’i \u201droot\u201d kullan\u0131c\u0131s\u0131 ile a\u00e7\u0131lm\u0131\u015f bir terminal penceresinden \u00e7al\u0131\u015ft\u0131rmal\u0131y\u0131z.\u00a0Script’i \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131m\u0131zda a\u015fa\u011f\u0131daki gibi \u00e7\u0131kt\u0131lar olu\u015facakt\u0131r. Gerekli script\u2019i \u00e7al\u0131\u015ft\u0131rd\u0131ktan sonra \u201cOK\u201d d\u00fc\u011fmesine t\u0131klayarak devam ediyoruz.\u00a0<\/strong>Script’i \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131 a\u015famas\u0131nda hata verirse ve yeniden kurma i\u015flemi yapacaksak hatal\u0131 kurulumun temizlenmesiyle ilgili \u201cOracle Grid Infrastructure Kurulumunun Ba\u015far\u0131s\u0131z Olmas\u0131 Durumunda Sistemin Temizlenmesi\u201d<\/a> makalemizi inceleyebilirsiniz.<\/span><\/p>\n
# cd \/u01\/app\/11.2.0.3\/grid\/<\/span>\r\n# .\/root.sh<\/span>\r\n\r\nPerforming root user operation for Oracle 11g \r\n\r\nThe following environment variables are set as:\r\n\u00a0\u00a0\u00a0 ORACLE_OWNER= oracle\r\n\u00a0\u00a0\u00a0 ORACLE_HOME=\u00a0 \/u01\/app\/11.2.0.3\/grid\r\n\r\nEnter the full pathname of the local bin directory: [\/usr\/local\/bin]: \r\nThe contents of \"dbhome\" have not changed. No need to overwrite.\r\nThe contents of \"oraenv\" have not changed. No need to overwrite.\r\nThe contents of \"coraenv\" have not changed. No need to overwrite.\r\n\r\nEntries will be added to the \/etc\/oratab file as needed by\r\nDatabase Configuration Assistant when a database is created\r\nFinished running generic part of root script.\r\nNow product-specific root actions will be performed.\r\nCreating trace directory\r\nLOCAL ADD MODE \r\nCreating OCR keys for user 'oracle', privgrp 'oinstall'..\r\nOperation successful.\r\nLOCAL ONLY MODE \r\nSuccessfully accumulated necessary OCR keys.\r\nCreating OCR keys for user 'root', privgrp 'root'..\r\nOperation successful.\r\nCRS-4664: Node koraykey-db1 successfully pinned.\r\nAdding Clusterware entries to upstart<\/span><\/pre>\n
25.\u00a0 Script’imizi \u00e7al\u0131\u015ft\u0131rd\u0131ktan sonra \u201cOk\u201d d\u00fc\u011fmesine basarak kuruluma devam ediyoruz.<\/span><\/p>\n
\"DB_Install_17\"<\/a><\/p>\n
26. Kurulum ba\u015far\u0131l\u0131 bir \u015fekilde tamamland\u0131ktan sonra \u201cClose\u201d d\u00fc\u011fmesine basarak kurulumu bitiriyoruz.<\/span><\/p>\n
\"DB_Install_18\"<\/a><\/p>\n
27. Oracle Veritaban\u0131 ve Grid i\u00e7in de\u011fi\u015fkenlerimizi \u201c.bash_profile\u201d dosyam\u0131za yaz\u0131yoruz.<\/span><\/p>\n
-- Oracle kullan\u0131c\u0131s\u0131na ge\u00e7i\u015f yap\u0131yoruz.<\/span>\r\n\r\n# su - oracle<\/span>\r\n\r\n$ vim \/home\/oracle\/.bash_profile<\/span>\r\n\r\n-- Dosyas\u0131na a\u015fa\u011f\u0131daki de\u011fi\u015fkenleri giriyoruz.<\/span>\r\n\r\n# Oracle bash_profile Environment Settings<\/span>\r\n\r\nTMP=\/tmp; export TMP<\/span>\r\nTMPDIR=$TMP; export TMPDIR<\/span>\r\n\r\nORACLE_HOSTNAME=koraykey-db1.localdomain; export ORACLE_HOSTNAME<\/span>\r\nORACLE_UNQNAME=orcl; export ORACLE_UNQNAME<\/span>\r\nORACLE_BASE=\/u01\/app\/oracle; export ORACLE_BASE<\/span>\r\nGRID_HOME=\/u01\/app\/11.2.0.3\/grid; export GRID_HOME<\/span>\r\nDB_HOME=$ORACLE_BASE\/product\/11.2.0.3\/db; export DB_HOME<\/span>\r\nORACLE_HOME=$DB_HOME; export ORACLE_HOME<\/span>\r\nORACLE_SID=orcl; export ORACLE_SID<\/span>\r\nORACLE_HOME_LISTNER=$ORACLE_HOME export ORACLE_HOME_LISTNER<\/span>\r\nORACLE_TERM=xterm; export ORACLE_TERM<\/span>\r\nBASE_PATH=\/usr\/sbin:$PATH; export BASE_PATH<\/span>\r\nPATH=$ORACLE_HOME\/bin:$BASE_PATH; export PATH<\/span>\r\n\r\nLD_LIBRARY_PATH=$ORACLE_HOME\/lib:\/lib:\/usr\/lib; export LD_LIBRARY_PATH<\/span>\r\nCLASSPATH=$ORACLE_HOME\/JRE:$ORACLE_HOME\/jlib:$ORACLE_HOME\/rdbms\/jlib; export CLASSPATH<\/span>\r\n\r\nif [ $USER = \"oracle\" ]; then<\/span>\r\n  if [ $SHELL = \"\/bin\/ksh\" ]; then<\/span>\r\n    ulimit -p 16384<\/span>\r\n    ulimit -n 65536<\/span>\r\n  else<\/span>\r\n    ulimit -u 16384 -n 65536<\/span>\r\n  fi<\/span>\r\nfi<\/span>\r\n\r\nalias grid_env='. \/home\/oracle\/.grid'<\/span>\r\nalias db_env='. \/home\/oracle\/.db'<\/span>\r\n\r\n-- Daha sonra grid ve db de\u011fi\u015fkenleri aras\u0131nda ge\u00e7i\u015f yapabilmek i\u00e7in <\/span>\r\n\".grid\" ve \".db\" profil dosyalar\u0131m\u0131z\u0131 olu\u015fturuyoruz.<\/span>\r\n\r\n$ vim \/home\/oracle\/.grid<\/span>\r\n\r\n-- Dosyas\u0131na a\u015fa\u011f\u0131daki de\u011fi\u015fkenleri giriyoruz.<\/span>\r\n\r\n# Oracle \"grid\" Environment Settings<\/span>\r\n\r\nORACLE_SID=+ASM; export ORACLE_SID<\/span>\r\nORACLE_HOME=$GRID_HOME; export ORACLE_HOME<\/span>\r\nPATH=$ORACLE_HOME\/bin:$BASE_PATH; export PATH<\/span>\r\n\r\nLD_LIBRARY_PATH=$ORACLE_HOME\/lib:\/lib:\/usr\/lib; export LD_LIBRARY_PATH<\/span>\r\nCLASSPATH=$ORACLE_HOME\/JRE:$ORACLE_HOME\/jlib:$ORACLE_HOME\/rdbms\/jlib; export CLASSPATH<\/span>\r\n\r\n$ vim \/home\/oracle\/.db<\/span>\r\n\r\n-- Dosyas\u0131na a\u015fa\u011f\u0131daki de\u011fi\u015fkenleri giriyoruz.<\/span>\r\n\r\n# Oracle \"db\" Environment Settings<\/span>\r\n\r\nORACLE_SID=orcl; export ORACLE_SID<\/span>\r\nORACLE_HOME=$DB_HOME; export ORACLE_HOME<\/span>\r\nPATH=$ORACLE_HOME\/bin:$BASE_PATH; export PATH<\/span>\r\n\r\nLD_LIBRARY_PATH=$ORACLE_HOME\/lib:\/lib:\/usr\/lib; export LD_LIBRARY_PATH<\/span>\r\nCLASSPATH=$ORACLE_HOME\/JRE:$ORACLE_HOME\/jlib:$ORACLE_HOME\/rdbms\/jlib; export CLASSPATH<\/span><\/pre>\n
28. Kurulum s\u0131ras\u0131nda \u201cDATA\u201d disk\u00a0grubumuzu\u00a0olu\u015fturmu\u015ftuk. \u015eimdi \u201casmca\u201d komutunu kullanarak \u201cFRA\u201d disk grubumuzu olu\u015fturaca\u011f\u0131z.<\/span><\/p>\n
-- Oracle kullan\u0131c\u0131s\u0131 ile a\u00e7\u0131lm\u0131\u015f bir terminal ekran\u0131nda daha \u00f6nce<\/span>\r\nolu\u015fturmu\u015f oldu\u011fumuz \"grid\" de\u011fi\u015fken dosyam\u0131z\u0131 \u00e7al\u0131\u015ft\u0131r\u0131yoruz.<\/span>\r\n\r\n$ cd<\/span>\r\n$ . .bash_profile<\/span>\r\n$ . .grid<\/span>\r\n\r\n-- Ard\u0131ndan a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131rarak \"ASM Configuration Assistant\" a\u00e7\u0131yoruz.<\/span>\r\n\r\n$ asmca<\/span><\/pre>\n
29. A\u00e7\u0131lan pencerede \u201cCreate\u201d d\u00fc\u011fmesine t\u0131kl\u0131yoruz ve a\u015fa\u011f\u0131daki pencerede g\u00f6sterildi\u011fi gibi ayarlar\u0131 yap\u0131yoruz. Ard\u0131ndan \u201cOK\u201d d\u00fc\u011fmesine t\u0131klayarak \u201cFRA\u201d diskimizi olu\u015fturuyoruz.<\/span><\/p>\n
\"DB_Install_20\"<\/a><\/p>\n
30. Disk grubumuzu ba\u015far\u0131l\u0131 bir \u015fekilde olu\u015fturdu\u011fumuzda a\u015fa\u011f\u0131daki gibi uyar\u0131 al\u0131yoruz.<\/span><\/p>\n
\"DB_Install_21\"<\/a><\/p>\n
31. A\u015fa\u011f\u0131daki ekranda g\u00f6r\u00fcld\u00fc\u011f\u00fc gibi art\u0131k \u201cDATA\u201d ve \u201cFRA\u201d disk gruplar\u0131m\u0131z haz\u0131r durumdad\u0131r. Art\u0131k veritaban\u0131 kurulumumuzda bu disklerimizi atayabilece\u011fiz.<\/span><\/p>\n
\"DB_Install_22\"<\/a><\/p>\n
32. ASM yap\u0131land\u0131rma ekran\u0131ndan \u00e7\u0131kmak i\u00e7in \u201cExit\u201d d\u00fc\u011fmesine bas\u0131yoruz ard\u0131ndan gelen ekrandaki uyar\u0131ya \u201cYes\u201d d\u00fc\u011fmesini t\u0131klayarak \u00e7\u0131k\u0131yoruz.<\/span><\/p>\n
\"DB_Install_23\"<\/a><\/p>\n
33. Veritaban\u0131m\u0131z\u0131 dosya sistemden (File System to ASM) ASM dosya sistemine ta\u015f\u0131ma i\u015flemlerine ba\u015flamak i\u00e7in veritban\u0131m\u0131z\u0131 ba\u015flat\u0131yoruz ve gerekli kontrolleri yap\u0131yoruz. Ayr\u0131ca i\u015fleme ba\u015flamadan \u00f6nce e\u011fer a\u00e7\u0131ksa i\u015flem sonunda tekrar a\u00e7mak \u00fczere “Archive Mod”u kapat\u0131yoruz.
\n<\/span><\/p>\n
-- \u0130\u015flemlerimize ba\u015flamak i\u00e7in veritaban\u0131m\u0131z\u0131 ba\u015flat\u0131yoruz.<\/span>\r\n\r\n$ . .db<\/span>\r\n$ dbstart $ORACLE_HOME<\/span>\r\n\r\n--  Veritaban\u0131 durumumuzu sorguluyoruz.<\/span>\r\n\r\nSQL> select instance_name,version,database_status from v$instance;<\/span>\r\n\r\n-- ASM disklerimizin durumunu sorguluyoruz.<\/span>\r\n\r\nSQL> select NAME,STATE,TOTAL_MB,PATH from v$asm_disk;<\/span>\r\n\r\nNAME                           STATE      TOTAL_MB<\/span>\r\n------------------------------ -------- ----------<\/span>\r\nPATH<\/span>\r\n--------------------------------------------------<\/span>\r\nFRA_0000                       NORMAL         5114<\/span>\r\n\/dev\/oracleasm\/disks\/FRA1<\/span>\r\n\r\nDATA_0000                      NORMAL         5114<\/span>\r\n\/dev\/oracleasm\/disks\/DATA1\r\n\r\n-- Veritaban\u0131m\u0131zda \"Archive Mod\"u kapatmak i\u00e7in a\u015fa\u011f\u0131daki i\u015flemleri yap\u0131yoruz.\r\n\r\n$ sqlplus \/ as sysdba\r\n\r\nSQL> shutdown immediate;\r\nDatabase closed.\r\nDatabase dismounted.\r\nORACLE instance shut down.\r\n\r\nSQL> startup mount;\r\nORACLE instance started.\r\n\r\nTotal System Global Area 1043886080 bytes\r\nFixed Size\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2234960 bytes\r\nVariable Size\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 624952752 bytes\r\nDatabase Buffers\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 411041792 bytes\r\nRedo Buffers\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5656576 bytes\r\nDatabase mounted.\r\n\r\nSQL> alter database noarchivelog;\r\n\r\nDatabase altered.\r\n\r\nSQL> exit\r\n<\/span><\/pre>\n
34. Sunucumuzda kullan\u0131yorsak mevcut “spfile” dosyam\u0131z\u0131 ASM dosya sistemine ta\u015f\u0131yoruz ve gerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span><\/p>\n
-- Sunucumuzda \"spfile\" dosyam\u0131z\u0131n yede\u011fini \"RMAN\" arac\u0131 ile al\u0131yoruz.<\/span>\r\n\r\n$ rman target \/<\/span>\r\n\r\nconnected to target database: ORCL (DBID=1350027477)<\/span>\r\n\r\nRMAN> backup as backupset spfile;<\/span>\r\n\r\nRMAN> exit<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131 kapat\u0131p \"mount\" modda a\u00e7\u0131yoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba<\/span>\r\n\r\nSQL> shutdown immediate;<\/span>\r\nDatabase closed.<\/span>\r\nDatabase dismounted.<\/span>\r\nORACLE instance shut down.<\/span>\r\n\r\nSQL> startup mount;<\/span>\r\n\r\nORACLE instance started.<\/span>\r\nTotal System Global Area 1043886080 bytes<\/span>\r\nFixed Size                  2234960 bytes<\/span>\r\nVariable Size             624952752 bytes<\/span>\r\nDatabase Buffers          411041792 bytes<\/span>\r\nRedo Buffers                5656576 bytes<\/span>\r\nDatabase mounted.<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- Sunucumuzda \"RMAN\" arac\u0131 ile \"spfile\" yede\u011fimizi ASM dosya sistemimize d\u00f6n\u00fcyoruz.<\/span>\r\n\r\n$ rman target \/ <\/span>\r\n\r\nconnected to target database: ORCL (DBID=1350027477, not open)<\/span>\r\n\r\nRMAN> restore spfile to '+DATA\/spfileorcl.ora';<\/span>\r\n\r\nRMAN> exit<\/span>\r\n\r\n-- ASM dosya sistemine ta\u015f\u0131d\u0131\u011f\u0131m\u0131z \"spfile\" dosyas\u0131n\u0131 veritaban\u0131m\u0131za tan\u0131tmak i\u00e7in\r\ngerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131n kulland\u0131\u011f\u0131 \"spfile\" yolunu sorguluyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> show parameter spfile;<\/span>\r\n\r\nNAME                                 TYPE        VALUE<\/span>\r\n------------------------------------ ----------- ------------------------------<\/span>\r\nspfile                               string      \/u01\/app\/oracle\/product\/11.2.0<\/span>\r\n                                                 .3\/db\/dbs\/spfileorcl.ora<\/span>\r\n\r\n-- ASM dosya sistemine ta\u015f\u0131d\u0131\u011f\u0131m\u0131z yeni \"spfile\" dosyam\u0131z i\u00e7in gerekli d\u00fczenlemeleri\r\nyap\u0131yoruz.<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131 kapat\u0131yoruz.<\/span>\r\n\r\nSQL> shutdown immediate;<\/span>\r\n\r\nORA-01109: database not open<\/span>\r\nDatabase dismounted.<\/span>\r\nORACLE instance shut down.<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- Spfile dosyam\u0131z\u0131n bulundu\u011fu dizine ge\u00e7iyoruz ve eski \"spfile\" dosyam\u0131z\u0131 ba\u015fka\r\nbir isimle adland\u0131r\u0131yoruz.<\/span>\r\n\r\n$ cd $ORACLE_HOME\/dbs<\/span>\r\n$ mv spfileorcl.ora spfileorcl.ora.bak<\/span>\r\n\r\n-- Sunucumuzda bulunan \"init.ora\" dosyam\u0131za yeni \"spfile\" dosyam\u0131z\u0131n yolunu\r\nyaz\u0131yoruz.<\/span>\r\n\r\n$ vim initorcl.ora<\/span>\r\n\r\n*.spfile='+DATA\/spfileorcl.ora'<\/span>\r\n\r\n-- \u0130\u015flemlerimizi tamamlad\u0131ktan sonra veritaban\u0131m\u0131z\u0131 a\u00e7\u0131p \"spfile\" parametremizi\r\nkontrol ediyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> startup;<\/span>\r\n\r\nORACLE instance started.<\/span>\r\nTotal System Global Area 1043886080 bytes<\/span>\r\nFixed Size                  2234960 bytes<\/span>\r\nVariable Size             624952752 bytes<\/span>\r\nDatabase Buffers          411041792 bytes<\/span>\r\nRedo Buffers                5656576 bytes<\/span>\r\nDatabase mounted.<\/span>\r\nDatabase opened.<\/span>\r\n\r\nSQL> show parameter spfile;<\/span>\r\n\r\nNAME                                 TYPE        VALUE<\/span>\r\n------------------------------------ ----------- ------------------------------<\/span>\r\nspfile                               string      +DATA\/spfileorcl.ora<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"spfile\" dosya yolumuz ASM olarak de\u011fi\u015fmi\u015f durumda.<\/span><\/pre>\n
35. Sunucumuzda mevcut “controlfile” dosyam\u0131z\u0131 ASM dosya sistemine ta\u015f\u0131yoruz ve gerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span><\/p>\n
-- Mevcut \"Control File\" durumumuzu sorguluyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> show parameter control_files;<\/span>\r\n\r\nNAME                                 TYPE        VALUE<\/span>\r\n------------------------------------ ----------- ------------------------------<\/span>\r\ncontrol_files                        string      \/u01\/app\/oracle\/oradata\/ORCL\/c<\/span>\r\n                                                 ontrolfile\/o1_mf_8zl9554m_.ctl<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131 kapat\u0131p \"mount\" modda a\u00e7\u0131yoruz.<\/span>\r\n\r\nSQL> shutdown immediate;<\/span>\r\n\r\nDatabase closed.<\/span>\r\nDatabase dismounted.<\/span>\r\nORACLE instance shut down.<\/span>\r\n\r\nSQL> startup mount;<\/span>\r\n\r\nORACLE instance started.<\/span>\r\nTotal System Global Area 1043886080 bytes<\/span>\r\nFixed Size                  2234960 bytes<\/span>\r\nVariable Size             624952752 bytes<\/span>\r\nDatabase Buffers          411041792 bytes<\/span>\r\nRedo Buffers                5656576 bytes<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- RMAN arac\u0131m\u0131z\u0131n copy komutu ile ge\u00e7erli \"control file\" dosyam\u0131z\u0131 ASM dosya\r\nsistemine kopyal\u0131yoruz.<\/span>\r\n\r\n$ rman target \/ <\/span>\r\n\r\nconnected to target database: ORCL (DBID=1350027477, not open)<\/span>\r\n\r\nRMAN> copy current controlfile to '+DATA\/control01.ctl';<\/span>\r\n\r\nRMAN> exit<\/span>\r\n\r\n-- Veritaban\u0131m\u0131za yeni \"controlfile\" yolumuzu tan\u0131t\u0131yoruz.<\/span>\r\n\r\nSQL> alter system set control_files='+DATA\/control01.ctl' scope=spfile;<\/span>\r\n\r\nSystem altered.<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131 yeniden ba\u015flat\u0131p \"control file\" parametremizin durumunu kontrol\r\nediyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> shu immediate;<\/span>\r\nORA-01109: database not open<\/span>\r\n\r\nSQL> startup mount;<\/span>\r\n\r\nSQL> alter database open resetlogs;<\/span>\r\n\r\nDatabase altered.<\/span>\r\n\r\nSQL> show parameter control_files;<\/span>\r\n\r\nNAME                                 TYPE        VALUE<\/span>\r\n------------------------------------ ----------- -------------------<\/span>\r\ncontrol_files                        string      +DATA\/control01.ctl<\/span>\r\n\r\nSQL> exit<\/span><\/pre>\n
36. Sunucumuzda mevcut “datafile” dosyalar\u0131m\u0131z\u0131 ASM dosya sistemine ta\u015f\u0131yoruz ve gerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span><\/p>\n
-- Sunucumuzda \"datafile\" dosyalar\u0131m\u0131z\u0131 ta\u015f\u0131mak i\u00e7in veritaban\u0131m\u0131z\u0131 kapat\u0131p \"mount\"\r\nmodda a\u00e7\u0131yoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> shutdown immediate;<\/span>\r\n\r\nSQL> startup mount;<\/span>\r\n\r\nORACLE instance started.<\/span>\r\n\r\nTotal System Global Area 1043886080 bytes<\/span>\r\nFixed Size                  2234960 bytes<\/span>\r\nVariable Size             624952752 bytes<\/span>\r\nDatabase Buffers          411041792 bytes<\/span>\r\nRedo Buffers                5656576 bytes<\/span>\r\nDatabase mounted.<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131n \"data file\" dosyalar\u0131n\u0131 ta\u015f\u0131mak i\u00e7in RMAN arac\u0131m\u0131z\u0131 kullan\u0131yoruz.<\/span>\r\n\r\n$ rman target \/ <\/span>\r\n\r\nconnected to target database: ORCL (DBID=1350027477, not open)<\/span>\r\n\r\nRMAN> backup as copy database format '+DATA';<\/span>\r\n\r\nStarting backup at 01-AUG-13<\/span>\r\n.<\/span>\r\n.<\/span>\r\n.<\/span>\r\nFinished backup at 01-AUG-13<\/span>\r\n\r\nRMAN> switch database to copy;<\/span>\r\n\r\ndatafile 1 switched to datafile copy \"+DATA\/orcl\/datafile\/system.258.822268909\"<\/span>\r\ndatafile 2 switched to datafile copy \"+DATA\/orcl\/datafile\/sysaux.259.822268945\"<\/span>\r\ndatafile 3 switched to datafile copy \"+DATA\/orcl\/datafile\/undotbs1.260.822268969\"<\/span>\r\ndatafile 4 switched to datafile copy \"+DATA\/orcl\/datafile\/users.262.822268999\"<\/span>\r\n\r\n-- Veritaban\u0131m\u0131z\u0131n \"tempfile\" dosyas\u0131n\u0131 ta\u015f\u0131mak i\u00e7in RMAN arac\u0131m\u0131z\u0131 kullan\u0131yoruz.<\/span>\r\n\r\nRMAN> run<\/span>\r\n{<\/span>\r\nset newname for tempfile '\/u01\/data\/testdb\/temp01.dbf' to '+DATA';<\/span>\r\nswitch tempfile all;<\/span>\r\n}<\/span>\r\n\r\nRMAN> exit<\/span>\r\n\r\n-- Ta\u015f\u0131ma i\u015flemleri sonras\u0131 veritaban\u0131m\u0131z\u0131 \"open\" modda a\u00e7abiliriz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> alter database open;<\/span>\r\n\r\nDatabase altered.<\/span>\r\n\r\n-- Veritaban\u0131m\u0131zda ta\u015f\u0131ma i\u015flemi sonras\u0131 \"datafile\" durumunu kontrol ediyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> select FILE_NAME from dba_data_files;<\/span>\r\n\r\nFILE_NAME<\/span>\r\n--------------------------------------------------------------------------------<\/span>\r\n+DATA\/orcl\/datafile\/system.258.822268909<\/span>\r\n+DATA\/orcl\/datafile\/sysaux.259.822268945<\/span>\r\n+DATA\/orcl\/datafile\/undotbs1.260.822268969<\/span>\r\n+DATA\/orcl\/datafile\/users.262.822268999<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"datafile\" dosyalar\u0131m\u0131z ASM dosya sistemine ta\u015f\u0131nm\u0131\u015f durumda.<\/span><\/pre>\n
37. Sunucumuzda mevcut “redolog” dosyalar\u0131m\u0131z\u0131 ASM dosya sistemine ta\u015f\u0131yoruz ve gerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span><\/p>\n
-- Sunucumuzda bulunan \"redolog\" dosyalar\u0131m\u0131z\u0131 sorgulay\u0131p bunlar\u0131n yollar\u0131n\u0131 silmek\r\n\u00fczere not al\u0131yoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> SELECT MEMBER FROM v$logfile;<\/span>\r\n\r\n-- Bu i\u015flem s\u0131ras\u0131nda veritaban\u0131m\u0131z \"open\" modda olmal\u0131d\u0131r. \u00d6ncelikle bunu kontrol\r\nediyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> select status from v$instance;<\/span>\r\n\r\nSTATUS<\/span>\r\n------------<\/span>\r\nOPEN<\/span>\r\n\r\n-- Sunucumuzda \"Redolog\" dosyalar\u0131m\u0131z\u0131n yenilerini ASM dosya sisteminde yarat\u0131yoruz.<\/span>\r\n\r\nSQL> alter database add logfile member '+DATA' to group 1;<\/span>\r\nSQL> alter database add logfile member '+DATA' to group 2;<\/span>\r\nSQL> alter database add logfile member '+DATA' to group 3;<\/span>\r\nSQL> alter database add logfile member '+DATA' to group 4;<\/span>\r\n\r\n-- Sunucumuzda bulunan eski \"redolog\" dosyalar\u0131m\u0131z\u0131 siliyoruz ve yeni\r\nolu\u015fturduklar\u0131m\u0131zla de\u011fi\u015ftiriyoruz. <\/span>Silme i\u015flemi i\u00e7in yukar\u0131daki sorgu\r\nsonucu not ald\u0131\u011f\u0131m\u0131z \"redolog\" dosyalar\u0131m\u0131z\u0131n yollar\u0131n\u0131 yaz\u0131yoruz. <\/span>Ayr\u0131ca\r\nsilmek istedi\u011fimizde kullan\u0131lan bir dosyaya denk geldi\u011fimizde \"switch\" ederek\r\nsilebiliriz.<\/span>\r\n\r\nSQL> ALTER DATABASE DROP LOGFILE MEMBER<\/span>\r\n\u00a0 2\u00a0 '\/u01\/app\/oracle\/oradata\/ORCL\/onlinelog\/o1_mf_1_8zl955go_.log';<\/span>\r\n\r\nSQL> ALTER SYSTEM SWITCH LOGFILE;<\/span>\r\n\r\nSQL> ALTER DATABASE DROP LOGFILE MEMBER \r\n  2 '\/u01\/app\/oracle\/oradata\/ORCL\/onlinelog\/o1_mf_2_8zl95fm1_.log';<\/span>\r\n\r\nSQL> ALTER SYSTEM SWITCH LOGFILE;<\/span>\r\n\r\nSQL> ALTER DATABASE DROP LOGFILE MEMBER\r\n  2 '\/u01\/app\/oracle\/oradata\/ORCL\/onlinelog\/o1_mf_3_8zl95plx_.log';<\/span>\r\n\r\nSQL> ALTER SYSTEM SWITCH LOGFILE;<\/span>\r\n\r\nSQL> ALTER DATABASE DROP LOGFILE MEMBER\r\n  2 '\/u01\/app\/oracle\/oradata\/ORCL\/onlinelog\/o1_mf_4_8zl962r2_.log';<\/span>\r\n\r\nSQL> ALTER SYSTEM SWITCH LOGFILE;<\/span>\r\n\r\n-- Sunucumuzda i\u015flemlerimiz tamamland\u0131\u011f\u0131nda \"redolog\" dosyalar\u0131m\u0131z\u0131n durumunu\r\nkontrol ediyoruz.<\/span>\r\n\r\nSQL> SELECT MEMBER FROM v$logfile;<\/span>\r\n\r\nMEMBER<\/span>\r\n--------------------------------------------------------------------------------<\/span>\r\n+DATA\/orcl\/onlinelog\/group_1.264.822270491<\/span>\r\n+DATA\/orcl\/onlinelog\/group_2.265.822270497<\/span>\r\n+DATA\/orcl\/onlinelog\/group_3.266.822270503<\/span>\r\n+DATA\/orcl\/onlinelog\/group_4.267.822270509<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"redolog\" dosyalar\u0131m\u0131z ASM dosya sistemimize ta\u015f\u0131nm\u0131\u015f durumda.<\/span><\/pre>\n
38. Veritaban\u0131m\u0131zda “OMF” (Oracle Managed File) kullan\u0131yorsak bu parametremizide ASM dosya sistemine g\u00f6re ayarlamam\u0131z gerekmektedir. Ayr\u0131ca “FRA” (Fast Recovery Area) alan\u0131m\u0131z\u0131da ASM dosya sistemine g\u00f6re ayarlamal\u0131y\u0131z. Bunun i\u00e7in a\u015fa\u011f\u0131daki i\u015flemleri uyguluyoruz.<\/span><\/p>\n
-- Veritaban\u0131m\u0131zda \"OMF\" i\u00e7in parametremizi sorguluyoruz.<\/span>\r\n\r\n$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> show parameter DB_CREATE_FILE_DEST;<\/span>\r\n\r\nNAME                                 TYPE        VALUE<\/span>\r\n------------------------------------ ----------- ------------------------------<\/span>\r\ndb_create_file_dest                  string      \/u01\/app\/oracle\/oradata<\/span>\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"file system\" ayarlanm\u0131\u015f durumda.<\/span>\r\n\r\n-- Veritaban\u0131m\u0131zda \"OMF\" parametremizi ASM dosya sistemine g\u00f6re ayarl\u0131yoruz.<\/span>\r\n\r\nSQL> alter system set db_create_file_dest='+DATA';<\/span>\r\n\r\nSystem altered.<\/span>\r\n\r\n-- De\u011fi\u015fiklik sonras\u0131 \"OMF\" parametremizin durumunu sorguluyoruz.<\/span>\r\n\r\nSQL> show parameter DB_CREATE_FILE_DEST;<\/span>\r\n\r\nNAME                                 TYPE        VALUE<\/span>\r\n------------------------------------ ----------- ------------------------------<\/span>\r\ndb_create_file_dest                  string      +DATA<\/span>\r\n\r\nSQL> exit<\/span>\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"OMF\" parametremiz ASM dosya sistemine g\u00f6re ayarlanm\u0131\u015f durumda.\r\n\r\n-- Veritaban\u0131m\u0131zda \"FRA\" (Fast Recovery Area) alan\u0131m\u0131z\u0131 ASM dosya sistemine g\u00f6re\r\nayarl\u0131yoruz.\r\n\r\n-- Veritaban\u0131m\u0131zda \"FRA\" alan\u0131m\u0131z\u0131 sorguluyoruz.\r\n\r\n$ sqlplus \/ as sysdba\r\n\r\nSQL> show parameter recovery_file_dest\r\n\r\nNAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndb_recovery_file_dest\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 \/u01\/app\/oracle\/fast_recovery_\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 area\r\ndb_recovery_file_dest_size\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 big integer 4977M\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"file system\" olarak g\u00f6z\u00fckmekte bu alan\u0131m\u0131z\u0131 ASM dosya\r\nsistemimizde olu\u015fturdu\u011fumuz \"FRA\" alan\u0131 olarak ayarl\u0131yoruz.\r\n\r\nSQL> show parameter recovery_file_dest\r\n\r\nNAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndb_recovery_file_dest\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 \/u01\/app\/oracle\/fast_recovery_\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 area\r\ndb_recovery_file_dest_size\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 big integer 4977M\r\n\r\nSQL> alter system set db_recovery_file_dest='+FRA';\r\n\r\nSystem altered.\r\n\r\nSQL> alter system set db_recovery_file_dest_size=4977M scope=both;\r\n\r\nSystem altered.\r\n\r\n-- De\u011fi\u015fiklik sonras\u0131 \"FRA\" parametrelerimizi sorguluyoruz.\r\n\r\nSQL> show parameter recovery_file_dest\r\n\r\nNAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TYPE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndb_recovery_file_dest\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 string\u00a0\u00a0\u00a0\u00a0\u00a0 +FRA\r\ndb_recovery_file_dest_size\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 big integer 4977M\r\n\r\nSQL> exit\r\n\r\n-- G\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi \"FRA\" alan\u0131m\u0131z ASM dosya sistemimiz olarak ayarlanm\u0131\u015f durumda.\r\n<\/span><\/pre>\n
39. Bu i\u015flemler sonras\u0131nda sunucumuzu yeniden ba\u015flat\u0131yoruz ve patch ge\u00e7me i\u015flemi \u00f6ncesi t\u00fcm veritaban\u0131 ve servislerin ayakda oldu\u011funu kontrol ediyoruz. (Enterprise Manager Servisi hari\u00e7)<\/span><\/p>\n
# shutdown -r now<\/span><\/pre>\n
40. Veritaban\u0131 dosyalar\u0131m\u0131z\u0131 ta\u015f\u0131ma i\u015flemimiz tamamland\u0131. \u015eimdi e\u011fer “Grid” ve “Database” versiyonlar\u0131m\u0131z uyumlu de\u011filse “patch” ge\u00e7erek bunlar\u0131 uyumlu hale getirebiliriz. Bu durumu \u015fu \u015fekilde d\u00fc\u015f\u00fcnebiliriz. Veritaban\u0131m\u0131z\u0131 ilk olarak “file system” se\u00e7erek kurulum yapm\u0131\u015f ve kurulum sonras\u0131 veritaban\u0131m\u0131za patch ge\u00e7me i\u015flemi yapm\u0131\u015fsak ve veritaban\u0131 versiyonumuz grid versiyonumuzdan ileri bir duruma gelmi\u015fse patch i\u015fleminini uygulayarak “grid” ve “database” versiyonlar\u0131m\u0131z\u0131 ayn\u0131 veya uyumlu versiyona \u00e7ekmeliyiz. \u015eimdi bu patch ge\u00e7me i\u015flemini uygulayal\u0131m. Sistemimiz i\u00e7in \u201cMy Oracle Support\u201d<\/a> hesab\u0131m\u0131zla giri\u015f yaparak veritaban\u0131m\u0131za uygun indirmi\u015f oldu\u011fumuz \u201cGRID INFRASTRUCTURE PATCH SET UPDATE xxxx (INCLUDES DB PSU)\u201d dosyas\u0131n\u0131 ve yenilenmi\u015f \u201cOPatch\u201d<\/a> yaz\u0131l\u0131m\u0131n\u0131 ftp yada ba\u015fka bir y\u00f6ntem ile olu\u015fturdu\u011fumuz \u201c\/u01\/orainstall\/opatch\u201d ve\u00a0 \u201c\/u01\/orainstall\/patchset\u201d dizini alt\u0131na at\u0131yoruz. E\u011fer sunucumuzda ftp server \u00f6zelli\u011fi aktif edilmemi\u015fse \u201cLinux \u0130\u015fletim Sistemlerinde FTP Server Yap\u0131land\u0131rmas\u0131\u201d<\/a> makalemizden faydalanarak gerekli ayarlar\u0131 yapabiliriz. Sunucular\u0131m\u0131zda \u201cOpatch\u201d ve \u201cPatchset Update\u201d dosyalar\u0131m\u0131z\u0131n bulundu\u011fu dizine ge\u00e7erek s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f dosyalar\u0131m\u0131z\u0131 a\u00e7\u0131yoruz.<\/span><\/p>\n
Not:<\/strong> E\u011fer “grid” ve “veritaban\u0131” versiyonumuz uygunsa veya “patchset” ge\u00e7meyeceksek bu ad\u0131m\u0131 atlayabiliriz.<\/span><\/p>\n
-- Patch dosyalar\u0131m\u0131z\u0131 kopyalad\u0131\u011f\u0131m\u0131z dizinelere ge\u00e7iyoruz <\/span>ve s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f\r\ndosyalar\u0131m\u0131z\u0131 a\u00e7\u0131yoruz.<\/span>\r\n\r\n-- OPatch yaz\u0131l\u0131m\u0131n\u0131 \"unzip\" komutu ile a\u00e7\u0131yoruz.<\/span>\r\n\r\n$ cd \/u01\/orainstall\/opatch<\/span>\r\n$ unzip p6880880_112000_Linux-x86-64.zip<\/span>\r\n\r\n-- Patchset Update yaz\u0131l\u0131m\u0131n\u0131 \"unzip\" komutu ile a\u00e7\u0131yoruz.<\/span>\r\n\r\n$ cd \/u01\/orainstall\/patchset<\/span>\r\n$ unzip p16742216_112030_Linux-x86-64.zip<\/span><\/pre>\n
41.\u00a0Sunucumuzda patch ge\u00e7mek i\u00e7in kulland\u0131\u011f\u0131m\u0131z \u201cOPatch\u201d yaz\u0131l\u0131m\u0131n\u0131 g\u00fcncelliyoruz ve otomatik patch i\u015flemi i\u00e7in yan\u0131t dosyam\u0131z\u0131 (response file) olu\u015fturuyoruz.<\/span><\/p>\n
-- \"root\" kullan\u0131c\u0131s\u0131na ge\u00e7iyoruz.<\/span>\r\n\r\n-- A\u015fa\u011f\u0131daki i\u015flemleri her iki \u00fcyede uyguluyoruz. Sorun olmamas\u0131 i\u00e7in<\/span>\r\ni\u015flemi bir \u00fcyede ba\u015flat\u0131p bittince di\u011fer \u00fcyede ba\u015flatabiliriz.<\/span>\r\nBu i\u015flem s\u0131ras\u0131nda cluster servisimiz ve veritaban\u0131m\u0131z a\u00e7\u0131k durumda<\/span>\r\nolmal\u0131d\u0131r. Sadece sistemimizin bo\u015f bir zaman\u0131nda yapmak kullan\u0131c\u0131lar\u0131m\u0131z\u0131n<\/span>\r\netkilenmesini \u00f6nleyecektir. Patch i\u015flemi sonras\u0131 cluster servisimiz<\/span>\r\notomatik kapan\u0131p a\u00e7\u0131lacakt\u0131r.<\/span>\r\n\r\n$ su - root<\/span>\r\n\r\n-- G\u00fcncellemeyi uygulamak i\u00e7in \"root\" kullan\u0131c\u0131s\u0131na ge\u00e7i\u015f yap\u0131yoruz.<\/span>\r\nDaha sonra OPatch yaz\u0131l\u0131m\u0131n\u0131n yeni versiyonunu Grid ve Database<\/span>\r\nHome dizinlerinde yerlerine ta\u015f\u0131yoruz. Sonras\u0131nda otomatik patch<\/span>\r\nge\u00e7ebilmek i\u00e7in Auto Response dosyam\u0131z\u0131 olu\u015fturuyoruz.<\/span>\r\n\r\n-- Grid dizini i\u00e7in OPatch yaz\u0131l\u0131m\u0131n\u0131 g\u00fcncelliyoruz.<\/span>\r\n\r\n# cd \/u01\/app\/11.2.0.3\/grid\/<\/span>\r\n# mv OPatch OPatch_x<\/span>\r\n# cd \/u01\/orainstall\/opatch<\/span>\r\n# mv OPatch\/ \/u01\/app\/11.2.0.3\/grid<\/span>\r\n# cd \/u01\/app\/11.2.0.3\/grid\/OPatch\/ocm\/bin\/<\/span>\r\n# .\/emocmrsp\r\n<\/span>\r\nOCM Installation Response Generator 10.3.4.0.0 - Production<\/span>\r\nCopyright (c) 2005, 2010, Oracle and\/or its affiliates.<\/span>\r\nAll rights reserved.<\/span>\r\n\r\nProvide your email address to be informed of security issues, install and<\/span>\r\ninitiate Oracle Configuration Manager. Easier for you if you use your My<\/span>\r\nOracle Support Email address\/User Name.<\/span>\r\nVisit http:\/\/www.oracle.com\/support\/policies.html for details.<\/span>\r\nEmail address\/User Name: <\/span>\r\n\r\nYou have not provided an email address for notification of security issues.<\/span>\r\nDo you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  y<\/span>\r\nThe OCM configuration response file (ocm.rsp) was successfully created.<\/span>\r\n\r\n-- Grid dizini i\u00e7in OPatch yaz\u0131l\u0131m\u0131n\u0131 g\u00fcncelleyip<\/span>\r\nAuto Response dosyam\u0131z\u0131 olu\u015fturduk.<\/span>\r\n\r\n-- E\u011fer Database dizini i\u00e7indeki \"OPatch\" yaz\u0131l\u0131m\u0131n\u0131 g\u00fcncelleyceksek ayn\u0131<\/span>\r\ni\u015flemi onun i\u00e7inde yap\u0131yoruz.<\/span>\r\n\r\n-- Dosyalarda yetki problemi ya\u015famamak i\u00e7in oracle kullan\u0131c\u0131s\u0131na ge\u00e7iyoruz.<\/span>\r\n\r\n# su - oracle<\/span>\r\n$ cd \/u01\/orainstall\/opatch<\/span>\r\n$ unzip p6880880_112000_Linux-x86-64.zip<\/span>\r\n\r\n-- \"root\" kullan\u0131c\u0131s\u0131na ge\u00e7iyoruz.<\/span>\r\n\r\n$ su - root<\/span>\r\n\r\n# cd \/u01\/app\/oracle\/product\/11.2.0.3\/db<\/span>\r\n# mv OPatch OPatch_x<\/span>\r\n# cd \/u01\/orainstall\/opatch<\/span>\r\n# mv OPatch\/ \/u01\/app\/oracle\/product\/11.2.0.3\/db<\/span>\r\n# cd \/u01\/app\/oracle\/product\/11.2.0.3\/db\/OPatch\/ocm\/bin<\/span>\r\n# .\/emocmrsp\r\n<\/span>\r\nOCM Installation Response Generator 10.3.4.0.0 - Production<\/span>\r\nCopyright (c) 2005, 2010, Oracle and\/or its affiliates. <\/span>\r\nAll rights reserved.<\/span>\r\n\r\nProvide your email address to be informed of security issues, install and<\/span>\r\ninitiate Oracle Configuration Manager. Easier for you if you use your My<\/span>\r\nOracle Support Email address\/User Name.<\/span>\r\nVisit http:\/\/www.oracle.com\/support\/policies.html for details.<\/span>\r\nEmail address\/User Name: <\/span>\r\n\r\nYou have not provided an email address for notification of security issues.<\/span>\r\nDo you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  y<\/span>\r\nThe OCM configuration response file (ocm.rsp) was successfully created.<\/span><\/pre>\n
42. Sunucumuzda patch ge\u00e7me i\u015flemini ba\u015flat\u0131yoruz.<\/span><\/p>\n
-- A\u015fa\u011f\u0131daki i\u015flemi \"root\" kullan\u0131c\u0131s\u0131 ile yapmal\u0131y\u0131z.<\/span>\r\n\r\n# opatch auto <Zip'ten a\u00e7\u0131lm\u0131\u015f dizin yolu> -ocmrf <ocm yan\u0131t dosyas\u0131><\/span>\r\n\r\n\u00d6rnek;<\/span>\r\n\r\n# cd \/u01\/app\/11.2.0.3\/grid\/OPatch<\/span>\r\n# .\/<\/span>opatch auto \/u01\/orainstall\/patchset -ocmrf \/u01\/app\/11.2.0.3\/grid\/OPatch\/ocm\/bin\/ocm.rsp<\/span>\r\n\r\n-- A\u015fa\u011f\u0131daki i\u015flemleri yapmak i\u00e7in \"oracle\" kullan\u0131c\u0131s\u0131na ge\u00e7iyoruz.<\/span>\r\ni\u015flemler s\u0131ras\u0131nda veritabanlar\u0131m\u0131z a\u00e7\u0131k durumda olmal\u0131d\u0131r.<\/span>\r\n\r\n# su - oracle<\/span>\r\n$ . .db<\/span>\r\n\r\n$ cd $ORACLE_HOME\/rdbms\/admin<\/span>\r\n$ sqlplus \/nolog<\/span>\r\n\r\nSQL> CONNECT \/ AS SYSDBA<\/span>\r\n\r\n-- E\u011fer veritaban\u0131m\u0131z kapal\u0131 ise a\u00e7\u0131yoruz.<\/span>\r\n-- De\u011filse direk bir sonras\u0131 komutu kullanabiliriz.<\/span>\r\n\r\nSQL> STARTUP<\/span>\r\n\r\n-- \"Patch Post-Installation\" i\u015flemini ba\u015flat\u0131yoruz ve bitti\u011finde \u00e7\u0131k\u0131yoruz.<\/span>\r\n\r\nSQL> @catbundle.sql psu apply<\/span>\r\nSQL> QUIT<\/span><\/pre>\n
43. Sunucumuzda “patchset” i\u015flemi sonras\u0131 durumu kontrol ediyoruz.<\/span><\/p>\n
-- Oracle Patchset Update i\u015flemi sonras\u0131 grid ve veritaban\u0131 versiyonlar\u0131m\u0131z\u0131\r\nkontrol ediyoruz.<\/span>\r\n\r\n# su - oracle<\/span>\r\n\r\n-- Grid patch durumu i\u00e7in\r\n<\/span>\r\n$ . .grid<\/span>\r\n$ cd \/u01\/app\/11.2.0.3\/grid\/OPatch<\/span>\r\n$ .\/opatch lsinventory<\/span>\r\n\r\n-- Database patch durumu i\u00e7in\r\n<\/span>\r\n$ . .db<\/span>\r\n$ cd \/u01\/app\/oracle\/product\/11.2.0.3\/db\/OPatch<\/span>\r\n$ .\/opatch lsinventory<\/span><\/pre>\n
44. Veritaban\u0131m\u0131zda bu i\u015flemler sonras\u0131nda kapatm\u0131\u015f oldu\u011fumuz “Archive Log” modunu a\u00e7\u0131k duruma getiriyoruz.<\/span><\/p>\n
$ sqlplus \/ as sysdba <\/span>\r\n\r\nSQL> shutdown immediate;<\/span>\r\nDatabase closed.<\/span>\r\nDatabase dismounted.<\/span>\r\nORACLE instance shut down.<\/span>\r\n\r\nSQL> startup mount;<\/span>\r\n\r\nSQL> alter database archivelog;<\/span>\r\n\r\nDatabase altered.<\/span>\r\n\r\nSQL> alter database open;<\/span>\r\n\r\nDatabase altered.<\/span>\r\n\r\nSQL> archive log list;<\/span>\r\nDatabase log mode              Archive Mode<\/span>\r\nAutomatic archival             Enabled<\/span>\r\nArchive destination            USE_DB_RECOVERY_FILE_DEST<\/span>\r\nOldest online log sequence     8<\/span>\r\nNext log sequence to archive   11<\/span>\r\nCurrent log sequence           11<\/span>\r\n\r\nSQL> exit<\/span><\/pre>\n
45. Son olarak sistemimizi yeniden ba\u015flat\u0131yoruz ve t\u00fcm servislerimizin sorunsuzca do\u011fru bir \u015fekilde ba\u015flad\u0131\u011f\u0131ndan emin oluyoruz.<\/span><\/p>\n
# shutdown -r now<\/span><\/pre>\n
46. Bu i\u015flemler sonras\u0131nda veritaban\u0131m\u0131zda herhangi bir sorun yoksa ve sa\u011fl\u0131kl\u0131 \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin oldu\u011fumuzda dosya sisteminde tuttu\u011fumuz eski “data file” vb. dosyalar\u0131m\u0131z\u0131 silebiliriz. <\/span><\/p>\n
# cd \/u01\/app\/oracle\r\n# rm -rf fast_recovery_area\/ oradata\/<\/span><\/pre>\n
Bu makalemizde “Oracle Veritaban\u0131n\u0131 Dosya Sisteminden ASM Dosya Sistemine Ta\u015f\u0131ma Yap\u0131land\u0131rmas\u0131 (File System to ASM)” inceledik. Bu yap\u0131land\u0131rma sayesinde dosya sisteminde \u00e7al\u0131\u015fan veritabanlar\u0131m\u0131z\u0131 sorunsuzca yeniden kurmadan h\u0131zl\u0131 bir \u015fekilde “ASM” dosya sistemine ta\u015f\u0131yabiliriz. Bu makalemizde ad\u0131mlar “Oracle Enterprise Linux” i\u015fletim sistemi \u00fczerinde \u00e7al\u0131\u015fan “Oracle 11g R2” veritaban\u0131nda denenmi\u015ftir ve Red Hat t\u00fcrevi (CentOS vb.) i\u015fletim sistemlerinde ge\u00e7erlidir.<\/span><\/p>\n
Bir sonraki makalemizde g\u00f6r\u00fc\u015fmek dile\u011fiyle\u2026<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"
Bu makalemizde “Oracle Veritaban\u0131n\u0131 Dosya Sisteminden ASM Dosya Sistemine Ta\u015f\u0131ma Yap\u0131land\u0131rmas\u0131” konusunu inceleyece\u011fiz. Veritaban\u0131m\u0131z\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucuda bulunan veri dosyalar\u0131m\u0131z\u0131 i\u015fletim sistemi dosya sisteminden ASM dosya sistemine (File System to ASM) ta\u015f\u0131yaca\u011f\u0131z. Senaryomuza g\u00f6re \u00f6nceden dosya sistemine kurulmu\u015f bir veritaban\u0131 sunucumuza … Okumaya devam et →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[771,772,21,290,20,19,777,778,776,775,774,773],"class_list":["post-5052","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-asm-yapisina-database-tasima","tag-asm-yapisina-veritabani-tasima","tag-h-koray-gunduz","tag-halil-koray-gunduz","tag-koray-gunduz","tag-koraykey","tag-oracle-dosya-sisteminden-asm-dosya-sistemine-tasima","tag-oracle-file-system-tasima","tag-oracle-file-system-to-asm","tag-oracle-file-system-to-asm-migration","tag-oracle-file-systemden-asme-database-tasima","tag-oracle-file-systemden-asme-veritabani-tasima"],"_links":{"self":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/posts\/5052","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5052"}],"version-history":[{"count":0,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/posts\/5052\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5052"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5052"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5052"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}