大并發(fā)高可用負載均衡系統(tǒng)部署方案.doc

大并發(fā)高可用負載均衡系統(tǒng)（實施部署方案）目錄一、 方案說明2二、 系統(tǒng)架構描述21、 系統(tǒng)整體結構圖22、 WEB端高可用負載均衡32.1 Nginx負載均衡簡介32.2 高可用方案簡介43、 數(shù)據(jù)庫高可用方案介紹5三、 WEB端負載均衡及高可用系統(tǒng)部署53.1 前端調度服務器Nginx部署53.1.1 安裝說明53.1.2 Nginx安裝53.1.3 啟動配置63.1.4 測試、維護73.2 高可用keepalive部署7四、 數(shù)據(jù)高可用方案部署7五、 運行維護事項8上?？?20151、 方案說明 為滿足公司業(yè)務平臺的發(fā)展需要，應對業(yè)務平臺的多用戶大并發(fā)量的訪問請求，需要一套高效可靠的系統(tǒng)部署方案。 目前各業(yè)務平臺存在的問題有，業(yè)務系統(tǒng)（web數(shù)據(jù)庫）單機運行，單臺應用服務器提供的訪問能力有限，存在單點故障，雖然現(xiàn)在能做到故障急時報警，但出現(xiàn)故障后恢復時間較見；另外業(yè)務數(shù)據(jù)存在安全隱患，數(shù)據(jù)定時備份，數(shù)據(jù)庫或數(shù)據(jù)庫服務器故障后存在數(shù)據(jù)留失風險，僅故障恢復時間較常等。 本套部署方案旨在加固業(yè)務系統(tǒng)的可靠性、可擴展性，提高業(yè)務系統(tǒng)的并發(fā)訪問，提高業(yè)務數(shù)據(jù)安全性。2、 系統(tǒng)架構描述1、 系統(tǒng)整體結構圖2、 WEB端高可用負載均衡2.1 Nginx負載均衡簡介 nginx是一款高性能的HTTP和反向代理服務器軟件，截止到2014年底,Nginx僅次于apache成為第二大web服務器軟件,而在全球最忙碌top10000網站中使用比例更是高達42.7%。其發(fā)展速度和流行程度已經遠遠超過其它同類軟件,成為大型網站和高并發(fā)網站的首選。Nginx的優(yōu)勢l 輕量級 安裝文件小 運行時CPU內存使用率低l 性能強，支持多核心，處理靜態(tài)文件效率高，內核采用 的poll模型最大可以支持50K并發(fā)連接l 支持熱部署，同時啟動速度快，可以不間斷服務的情況下對軟件和配置進行升級l 支持負載均衡，支持容錯和健康檢查l 代理功能強大，支持無緩存的反向代理。主流的負載均衡方案優(yōu)缺點參考：/uid-27022856-id-3236257.html2.2 高可用方案簡介 單臺調度服務器如果出現(xiàn)故障就會造成業(yè)務不可訪問，在關鍵的業(yè)務環(huán)境里通常都會提供一臺備用調度服務器，用來降低單點故障給業(yè)務系統(tǒng)帶來的風險。這里推薦使用開源軟件Keepalive來提供nginx調度服務器的高可用，當主nginx宕機后，keepalive會將調度業(yè)務切換至備用調度主機，繼續(xù)提供用戶訪問。 Keepalived的作用是檢測web服務器的狀態(tài)，如果有一臺web服務器死機，或工作出現(xiàn)故障，Keepalived將檢測到，并將有故障的web服務器從系統(tǒng)中剔除，當web服務器工作正常后Keepalived自動將web服務器加入到服務器群中，這些工作全部自動完成，不需要人工干涉，需要人工做的只是修復故障的web服務器。官方網址：/download.html3、 數(shù)據(jù)庫高可用方案介紹3、 WEB端負載均衡及高可用系統(tǒng)部署3.1 前端調度服務器Nginx部署3.1.1 安裝說明nginx安裝有源碼安裝和系統(tǒng)匹配的安裝包安裝，這里為了方便采用redhat下的RPM包安裝。3.1.2 Nginx安裝1） nginx下載地址/en/linux_packages.html2） 下載相關的安裝包wget /packages/rhel/6/noarch/RPMS/nginx-release-rhel-6-0.el6.ngx.noarch.rpm3）安裝nginx官方提供的yum源，用yum安裝rpm -ivh nginx-release-rhel-6-0.el6.ngx.noarch.rpmyum install nginx4） 查看安裝文件rootRH01 # rpm -ql nginx-1.8.0-1.el6.ngx.x86_64/etc/logrotate.d/nginx/etc/nginx/etc/nginx/conf.d/etc/nginx/conf.d/default.conf/etc/nginx/conf.d/example_ssl.conf/etc/nginx/fastcgi_params/etc/nginx/koi-utf/etc/nginx/koi-win/etc/nginx/mime.types/etc/nginx/nginx.conf/etc/nginx/scgi_params/etc/nginx/uwsgi_params/etc/nginx/win-utf/etc/rc.d/init.d/nginx/etc/sysconfig/nginx/usr/sbin/nginx/usr/share/nginx/usr/share/nginx/html/usr/share/nginx/html/50x.html/usr/share/nginx/html/index.html/var/cache/nginx/var/log/nginx3.1.3 啟動配置1） 啟動服務# service nginx start 2） 查看進程rootRH01 # ps -ef|grep nginx root 30622 1 0 10:56 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.confnginx 30623 30622 0 10:56 ? 00:00:00 nginx: worker process 以上信息顯示一個主進程和一個工作進程rootRH01 # lsof -i:80COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEnginx 30622 root 6u IPv4 70955 0t0 TCP *:http (LISTEN)nginx 30623 nginx 6u IPv4 70955 0t0 TCP *:http (LISTEN)3） 刪除或重命名默認配置文件#mv /etc/nginx/conf.d/default.conf /etc/nginx/conf.d/default.conf.bak4) 修改配置文件rootRH01 # vim /etc/nginx/nginx.conf default_type application/octet-stream; log_format main $remote_addr - $remote_user $time_local $request $status $body_bytes_sent $http_referer $http_user_agent $http_x_forwarded_for; access_log /var/log/nginx/access.log main; sendfile on; #tcp_nopush on; keepalive_timeout 65; #gzip on; include /etc/nginx/conf.d/*.conf;upstream tomcat ip_hash; server :80 weight=10; server :8080 weight=10; server listen 80; server_name locahost;location / proxy_pass http:/tomcat; 3.1.4 測試、維護3.2 高可用keepalive部署3.2.1 keepalive安裝1） 安裝前請配置yum源2） yum install -y keepalived 3） 查看安裝文件路徑# rpm -ql keepalived/etc/keepalived/etc/keepalived/keepalived.conf/etc/rc.d/init.d/keepalived/etc/sysconfig/keepalived/usr/bin/genhash/usr/libexec/keepalived/usr/sbin/keepalived/usr/share/doc/keepalived-1.2.13/usr/share/doc/keepalived-1.2.13/AUTHOR/usr/share/doc/keepalived-1.2.13/CONTRIBUTORS/usr/share/doc/keepalived-1.2.13/COPYING/usr/share/doc/keepalived-1.2.13/ChangeLog/usr/share/doc/keepalived-1.2.13/NOTE_vrrp_vmac.txt/usr/share/doc/keepalived-1.2.13/README/usr/share/doc/keepalived-1.2.13/TODO/usr/share/doc/keepalived-1.2.13/VERSION/usr/share/doc/keepalived-1.2.13/keepalived.conf.SYNOPSIS/usr/share/doc/keepalived-1.2.13/samples/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.HTTP_GET.port/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.IPv6/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.SMTP_CHECK/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.SSL_GET/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.fwmark/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.inhibit/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.misc_check/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.misc_check_arg/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.quorum/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.sample/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.status_code/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.track_interface/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.virtual_server_group/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.virtualhost/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp.localcheck/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp.lvs_syncd/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp.routes/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp.scripts/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp.static_ipaddress/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.vrrp.sync/usr/share/doc/keepalived-1.2.13/samples/sample.misccheck.smbcheck.sh/usr/share/man/man1/genhash.1.gz/usr/share/man/man5/keepalived.conf.5.gz/usr/share/man/man8/keepalived.8.gz/usr/share/snmp/mibs/KEEPALIVED-MIB.txt4） 修改配置文件主調度主機配置文件rootRH01 # cat /etc/keepalived/keepalived.conf! Configuration File for keepalivedglobal_defs notification_email notification_email_from smtp_server smtp_connect_timeout 30 router_id #對端主機IPvrrp_instance VI_1 state MASTER #主調度服務器 interface eth0 virtual_router_id 51 priority 100 # 主調度服務器使用高優(yōu)先級 advert_int 1 authentication auth_type PASS auth_pass 1111 #交互密碼 virtual_ipaddress # 虛擬IP地址 備機配置文件：rootRH04 # cat /etc/keepalived/keepalived.conf ! Configuration File for keepalivedglobal_defs notification_email notification_email_from smtp_server smtp_connect_timeout 30 router_id vrrp_instance VI_1 state BACKUP interface eth0 virtual_router_id 51 priority 90 advert_int 1 authentication auth_type PASS auth_pass 1111 virtual_ipaddress 5） 啟動服務# /etc/init.d/keepalived start 在主備機同時啟動服務，查看主機是否掛載浮動IP6） 測試查看主機是否掛載浮動IP，停止主機keepalivd進程，查看備機是否掛載浮動IP，再恢復主機進程，查看浮動IP是否又回到主機。3.2.2 配置監(jiān)控nginx進程1） 經過前面的配置，如果主服務器的keepalived停止服務，備服務器會自動接管VIP對外服務；一旦主服務器的keepalived恢復，會重新接管VIP。 但如果nginx服務故障，備用調度服務器將無法發(fā)覺，所以我們要做到當主服務器故障或nginx進程停止，備機能全權接管提供對處服務。2）使用nmap檢查nginx端口來判斷nginx的狀態(tài)，記得要首先安裝nmap，#yum install nmap -y 3）加入監(jiān)控腳本如下：rootRH01 # vim /etc/keepalived/nginx_chk.sh#!/bin/sh#check nginx server status#NGINX=/usr/sbin/nginx#如果發(fā)現(xiàn)nginx不正常，先重啟進程，等3秒再檢查，仍然失敗不再嘗試！PORT=80nmap localhost -p $PORT |grep $PORT/tcp openif $? -ne 0 ;then /etc/init.d/nginx restart sleep 3 nmap localhost -p $PORT |grep $PORT/tcp open $? -ne 0 & /etc/init.d/keepalived stopfi*主備機都要添加4） 為腳本添加執(zhí)行權限chmod +x /etc/keepalived/nginx_chk.sh 5） 在keepalive中加入腳本配置vim /etc/keepalived/keepalived.confvrrp_script chk_http_port script /etc/keepalived/nginx_chk.sh #監(jiān)控腳本 interval 2 #時間 weight 2track_script chk_http_port全部配置文件如：global_defs notification_email notification_email_from smtp_server smtp_connect_timeout 30 router_id vrrp_script chk_http_port script /etc/keepalived/nginx_chk.sh interval 2 weight 2vrrp_instance VI_1 state MASTER interface eth0 virtual_router_id 51 priority 100 advert_int 1 authentication auth_type PASS auth_pass 1111 virtual_ipaddress track_script chk_http_port 6)更進一步，為了避免啟動keepalived之前沒有啟動nginx , 可以在/etc/init.d/keepalived的start中首先啟動nginx:start() /etc/init.d/nginx start sleep 3 -x $exec | exit 5 -e $config | exit 6 echo -n $Starting $prog: daemon $exec $KEEPALIVED_OPTIONS retval=$? echo $retval -eq 0 & touch $lockfile return $retval6） 測試維護查看檢測日志：# tail -f /var/log/messages4、 數(shù)據(jù)高可用方案部署1、主庫準備工作Host IP DB_NAME DB_UNIQUE_NAME Net Service Name(網絡服務名)主庫28 ORCLDB WENDING db_wending備庫29 ORCLDB PHYSTDBY db_phystdby保護模式：默認最大性能模式注意DataGuard啟動順序：啟動順序： 先standby ,后primary;關閉順序： 先primary ,后standby;1.1、檢查數(shù)據(jù)庫是否支持Data Guard(企業(yè)版才支持),是否歸檔模式，Enable force logging$ sqlplus /as sysdbaSQL select * from v$option where parameter = Managed Standby; 確認主庫處于歸檔模式 SQL archive log list （先檢查是否歸檔模式，不是則修改） startup mount alter database archivelog; alter database open; 將primary數(shù)據(jù)庫置為FORCE LOGGING模式 SQL alter database force logging; (強制產生日志)1.2、如果主庫沒有密碼文件則建立密碼文件，從而可以OS驗證的方式登陸$ orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=iamwangnc entries=51.3、配置standby redolog（最佳性能模式可以忽略，如果將來變成備庫且要轉為其它兩種模式則要建立）SQL alter database add standby logfile group 4 (/orahome/oradata/WENDING/stdby_redo04.log) size 50m, group 5 (/orahome/oradata/WENDING/stdby_redo05.log) size 50m, group 6 (/orahome/oradata/WENDING/stdby_redo06.log) size 50m, group 7 (/orahome/oradata/WENDING/stdby_redo07.log) size 50m;standby redolog的組數(shù)參考公式：(online redolog組數(shù) + 1) * 數(shù)據(jù)庫線程數(shù)；單機線程數(shù)為1，RAC一般為2。standby redolog的組成員數(shù)和大小也盡量和online redolog一樣。1.4、設置主庫初始化參數(shù)$ sqlplus /as sysdbaSQL create pfile=/home/oracle/pfile.ora from spfile; (備份參數(shù)文件)SQL alter system set LOG_ARCHIVE_CONFIG=DG_CONFIG=(WENDING,PHYSTDBY) scope=spfile; （啟動db接受或發(fā)送redo data，包括所有庫的db_unique_name）SQL alter system set LOG_ARCHIVE_DEST_1=LOCATION=/orahome/arch1/WENDING VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=WENDING scope=spfile; （主庫歸檔目的地）SQL alter system set LOG_ARCHIVE_DEST_2=SERVICE=db_phystdby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PHYSTDBY scope=spfile; (當該庫充當主庫角色時，設置物理備庫redo data的傳輸目的地)SQL alter system set LOG_ARCHIVE_MAX_PROCESSES=5 scope=spfile; （最大ARCn進程數(shù)）SQL alter system set LOG_ARCHIVE_DEST_STATE_1=ENABLE scope=spfile; （允許redo傳輸服務傳輸數(shù)據(jù)到目的地，默認是enable）SQL alter system set LOG_ARCHIVE_DEST_STATE_2=ENABLE scope=spfile; （同上）SQL alter system set REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE scope=spfile; （exclusive or shared，所有庫sys密碼要一致，默認是exclusive）-以下是主庫切換為備庫，充當備庫角色時的一些參數(shù)設置，如果不打算做數(shù)據(jù)庫切換就不用設置了SQL alter system set FAL_SERVER=db_phystdby scope=spfile; （配置網絡服務名，假如轉換為備庫角色時，從這里獲取丟失的歸檔文件）SQL alter system set FAL_CLIENT=db_wending scope=spfile; （配置網絡服務名，fal_server拷貝丟失的歸檔文件到這里）SQL alter system set DB_FILE_NAME_CONVERT=PHYSTDBY,WENDING scope=spfile; （前為切換后的主庫路徑，后為切換后的備庫路徑，如果主備庫目錄結構完全一樣，則無需設定）SQL alter system set LOG_FILE_NAME_CONVERT=PHYSTDBY,WENDING scope=spfile; （同上，這兩個名字轉換參數(shù)是主備庫的路徑映射關系，可能會是路徑全名，看情況而定）SQL alter system set STANDBY_FILE_MANAGEMENT=auto scope=spfile; （auto后當主庫的datafiles增刪時備庫也同樣自動操作，且會把日志傳送到備庫standby_archive_dest參數(shù)指定的目錄下，確保該目錄存在，如果你的存儲采用文件系統(tǒng)沒有問題，但是如果采用了裸設備，你就必須將該參數(shù)設置為manual）SQL alter system set STANDBY_ARCHIVE_DEST=LOCATION=/orahome/arch1/WENDING scope=spfile; （一般和LOG_ARCHIVE_DEST_1的位置一樣，如果備庫采用ARCH傳輸方式，那么主庫會把歸檔日志傳到該目錄下）有了以上參數(shù)設置，則無論該庫充當主庫角色還是備庫角色都無需再修改了。然后重啟數(shù)據(jù)庫：SQL shutdown immediateSQL startup;1.5、備份主庫數(shù)據(jù)文件關閉應用服務器，停止監(jiān)聽，開始rman備份：$ lsnrctl stop$ rman target /RMAN backup full database format /backup/backup_%T_%s_%p.bak;#RMAN sql alter system archive log current;#RMAN backup archive log all format=/backup/arch_%T_%s_%p.bak;1.6、在主庫上建立備庫控制文件（控制文件通常需要有多份，手工將文件復制幾份）$ sqlplus /as sysdbaSQL alter database create standby controlfile as /backup/stdby_control01.ctl;$ cd /backup/$ cp sdtby_control01.ctl stdby_control02.ctl$ cp sdtby_control01.ctl stdby_control03.ctl1.7、為備庫準備init參數(shù)$ sqlplus /as sysdbaSQL create pfile = /backup/initPHYSTDBY.ora from spfile;$ cd /backup/$ vi initPHYSTDBY.ora 注意主備庫不同角色的屬性配置，注意文件路徑等，注意db_name要和主庫一致，主要是以下參數(shù)：audit_file_dest=/u01/app/oracle/admin/PHYSTDBY/adumpbackground_dump_dest=/u01/app/oracle/admin/PHYSTDBY/bdumpcore_dump_dest=/u01/app/oracle/admin/PHYSTDBY/bdumpuser_dump_dest=/u01/app/oracle/admin/PHYSTDBY/udump-control_files=/orahome/oradata/stdby_control01.ctl,/orahome/oradata/stdby_control02.ctl,/orahome/oradata/stdby_control03.ctldb_unique_name=PHYSTDBYlog_archive_config=DG_CONFIG=(PHYSTDBY,WENDING)log_archive_dest_1=LOCATION=/orahome/arch1/PHYSTDBY VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PHYSTDBYlog_archive_dest_2=SERVICE=db_wending LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=WENDING-fal_client=DB_PHYSTDBYfal_server=DB_WENDINGdb_file_name_convert=WENDING,PHYSTDBYlog_file_name_convert=WENDING,PHYSTDBYstandby_archive_dest=LOCATION=/orahome/arch1/PHYSTDBY另外，如果備庫將來要打開成只讀模式，需要確認audit_trail參數(shù)不是含db，應該設成os或none。1.8、拷貝上面生成的文件backup_%T.bak、stdby_control01/02/03.ctl、initPHYSTDBY.ora到備庫所在主機注意rman備份的文件在主備庫主機上目錄要一致。$ scp backup*.bak 29:/backup/$ scp initPHYSTDBY.ora 29:$ORACLE_HOME/dbs/$ scp stdby_control*.ctl 29:/orahome/oradata/1.9、建立主庫監(jiān)聽和主備庫的網絡服務名（必須是dedicated的），并啟動監(jiān)聽$ netca (是圖形界面，或者手工從別的庫把listener.ora和tnsnames.ora拷過來修改也行)$ lsnrctl start$ tnsping db_wending$ tnsping db_phystdby （此時tnsping還不通物理備庫）tnsping對方的時候，有可能linux防火墻限制了，會提示TNS-12560: TNS: 協(xié)議適配器錯誤。臨時禁用防火墻方法：# service iptables stop永久禁用防火墻方法：# chkconfig -list iptables# chkconfig -level 345 iptables off2、建立備庫2.1、設置環(huán)境變量并建立備庫一些必需目錄$ export ORACLE_BASE=/u01/app/oracle$ export ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1$ export ORACLE_SID=PHYSTDBY$ mkdir -p $ORACLE_BASE/admin/$ORACLE_SID/adump$ mkdir -p $ORACLE_BASE/admin/$ORACLE_SID/bdump$ mkdir -p $ORACLE_BASE/admin/$ORACLE_SID/cdump$ mkdir -p $ORACLE_BASE/admin/$ORACLE_SID/udump-以下目錄要看哪些地方可能會存放數(shù)據(jù)庫文件，注意不能少建$ mkdir -p /orahome/oradata/$ORACLE_SID$ mkdir -p /u01/app/oracle/oradata/$ORACLE_SID$ mkdir -p /orahome/arch1/$ORACLE_SID2.2、在備庫主機上生成密碼文件，且sys密碼和主庫得一致$ orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=iamwangnc entries=52.3、在備庫上建立監(jiān)聽，和主備庫網絡服務名（必須是dedicated的），并啟動監(jiān)聽$ netca (是圖形界面，或者手工從別的庫把listener.ora和tnsnames.ora拷過來修改也行)$ lsnrctl start$ tnsping db_wending$ tnsping db_phystdby2.4、在備庫上建立spfile$ sqlplus /as sysdbaSQL create spfile from pfile;如果pfile沒有放到$ORACLE_HOME/dbs/下，而是放在別的位置：SQL create spfile from pfile=/backup/initPHYSTDBY.ora;2.5、啟動物理備庫SQL startup nomountSQL alter database mount standby database;2.6、備庫做rman恢復$ rman target / (要求主備庫rman備份文件的存放路徑和文件名一致)RMAN restore database;#RMAN restore archivelog all;介質恢復后，rman 自動將standby 數(shù)據(jù)庫打開到mount 狀態(tài)。2.7、配置standby redolog（最佳性能模式可以忽略，如果要轉為其它兩種模式則要建立）SQL alter database add standby logfile group 4 (/orahome/oradata/PHYSTDBY/stdby_redo04.log) size 50m, group 5 (/orahome/oradata/PHYSTDBY/stdby_redo05.log) size 50m, group 6 (/orahome/oradata/PHYSTDBY/stdby_redo06.log) size 50m, group 7 (/orahome/oradata/PHYSTDBY/stdby_redo07.log) size 50m;standby redolog的組數(shù)參考公式：(online redolog組數(shù) + 1) * 數(shù)據(jù)庫線程數(shù)；單機線程數(shù)為1，RAC一般為2。standby redolog的組成員數(shù)和大小也盡量和online redolog一樣。2.8、在備庫上,啟動redo applySQL alter database recover managed standby database disconnect from session;到此物理備庫創(chuàng)建完畢！3、主備庫各參數(shù)文件內容3.1、主備庫listener.ora一樣，如果有不一樣也是host不一樣-SID_LIST_LISTENER =(SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1) (PROGRAM = extproc) )LISTENER =(DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0) )-3.2、主備庫tnsnames.ora一樣，如果有不一樣也是host和port不一樣-DB_WENDING =(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 28)(PORT = 1521) ) (CONNECT_DATA = (SERVICE_NAME = wending.lk) )DB_PHYSTDBY =(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 29)