DM8 DMDSC動態擴充套件節點
DMDSC動態擴充套件節點
DMDSC叢集支援動態擴充套件節點，每次擴充套件可以在原有基礎上增加一個節點。動態擴充套件節點要求當前DMDSC叢集的所有節點都為OK狀態，所有dmserver例項都處於OPEN狀態，且可以正常訪問。
注意:擴充套件節點過程中，不應該有修改資料庫狀態或模式的操作
一. 環境說明
新增節點環境為： 作業系統：RedHat Linux 64位。
網路配置：eth0網路卡為10.10.13.0外網網段，該機器為10.10.13.203；eth1為11.11.11.0內網網段，該機器為11.11.11.5內網網段用於MAL通訊。
DM各種工具位於目錄：/dm8/bin。
配置檔案位於目錄：/dm8/data。
二、作業系統配置
1、關閉防火牆和SELINUX
[root@dm8rac3 ~]# systemctl stop firewalld [root@dm8rac3 ~]# systemctl disable firewalld Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service. Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. [root@dm8rac3 ~]# systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:firewalld(1) Dec 09 17:28:02 dm8rac3 systemd[1]: Starting firewalld - dynamic firewall daemon... Dec 09 17:28:04 dm8rac3 systemd[1]: Started firewalld - dynamic firewall daemon. Dec 10 08:29:20 dm8rac3 systemd[1]: Stopping firewalld - dynamic firewall daemon... Dec 10 08:29:21 dm8rac3 systemd[1]: Stopped firewalld - dynamic firewall daemon. [root@dm8rac3 ~]# setenforce 0 [root@dm8rac3 ~]# sed -i s:^SELINUX=.*$:SELINUX=disabled:g /etc/selinux/config [root@dm8rac3 ~]# cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
2、修改主機名
[root@dm8rac3 ~]# hostnamectl set-hostname dm8rac3 [root@dm8rac3 ~]# sed -i s:^HOSTNAME=.*$:HOSTNAME=dm8rac3:g /etc/sysconfig/network [root@dm8rac3 ~]# echo " > 10.10.13.201 dm8rac1 > 10.10.13.202 dm8rac2 > 10.10.13.203 dm8rac3" >> /etc/hosts [root@dm8rac3 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.10.13.201 dm8rac1 10.10.13.202 dm8rac2 10.10.13.203 dm8rac3 [root@dm8rac1 ~]# vi /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.10.13.201 dm8rac1 10.10.13.202 dm8rac2 10.10.13.203 dm8rac3 [root@dm8rac2 ~]# vi /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.10.13.201 dm8rac1 10.10.13.202 dm8rac2 10.10.13.203 dm8rac3
三、 安裝達夢軟體
3.1檢查Linux(Unix)系統資訊
[root@dm8rac3 ~]# getconf LONG_BIT 64
查詢作業系統release資訊
[root@dm8rac3 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.8 Beta (Maipo)
3.2建立安裝使用者
為了減少對作業系統的影響，使用者不應該以root系統使用者來安裝和執行DM。使用者可以在安裝之前為DM建立一個專用的系統使用者。
1. 建立安裝使用者組dinstall。
[root@dm8rac3 ~]# groupadd dinstall
2. 建立安裝使用者dmdba。
[root@dm8rac3 ~]# useradd -g dinstall -m -d /home/dmdba -s /bin/bash dmdba
3. 初始化使用者密碼。
[root@dm8rac3 ~]# passwd dmdba Changing password for user dmdba. New password: Retype new password: passwd: all authentication tokens updated successfully.
3.3 Linux(Unix)下檢查作業系統限制
在Linux(Unix)系統中，因為ulimit命令的存在，會對程式使用作業系統資源進行限制。為了使DM能夠正常執行，建議使用者檢查當前安裝使用者的ulimit引數。
執行ulimit -a進行查詢。如下圖所示：
[root@dm8rac3 ~]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31152 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 31152 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
引數使用限制：
1.data seg size
data seg size (kbytes, -d)
建議使用者設定為1048576(即1GB)以上或unlimited(無限制)，此引數過小將導致資料庫啟動失敗。
2. file size
file size(blocks, -f)
建議使用者設定為unlimited(無限制)，此引數過小將導致資料庫安裝或初始化失敗。
3. open files
open files(-n)
建議使用者設定為65536以上或unlimited(無限制)。
4.virtual memory
virtual memory (kbytes, -v)
建議使用者設定為1048576(即1GB)以上或unlimited(無限制)，此引數過小將導致資料庫啟動失敗。
如果使用者需要為當前安裝使用者更改ulimit的資源限制，請修改檔案/etc/security/limits.conf。
[root@dm8rac3 ~]# vi /etc/security/limits.conf dmdba soft data unlimited dmdba hard data unlimited dmdba soft fsize unlimited dmdba hard fsize unlimited dmdba soft nofile 65536 dmdba hard nofile 65536 [root@dm8rac3 ~]# su - dmdba [dmdba@dm8rac3 ~]$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31152 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65536 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 4096 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
3.4.檢查系統記憶體與儲存空間
1.檢查記憶體
為了保證DM的正確安裝和執行，要儘量保證作業系統至少1GB的可用記憶體(RAM)。如果可用記憶體過少，可能導致DM安裝或啟動失敗。使用者可以
使用以下命令檢查操作記憶體：
#獲取記憶體總大小 [root@dm8rac3 ~]# grep MemTotal /proc/meminfo MemTotal: 8009068 kB #獲取交換分割槽大小 [root@dm8rac3 ~]# grep SwapTotal /proc/meminfo SwapTotal: 8257532 kB #獲取記憶體使用詳情 [root@dm8rac3 ~]# free -g total used free shared buff/cache available Mem: 7 0 6 0 0 6 Swap: 7 0 7
2.檢查儲存空間
1) DM完全安裝需要1GB的儲存空間，使用者需要提前規劃好安裝目錄，預留足夠的儲存空間。使用者在DM安裝前也應該為資料庫例項預留足夠的儲存空間，規劃好資料路徑和備份路徑。使用者可使用以下命令檢查儲存空間:
#查詢目錄/dm8可用空間
[root@dm8rac3 ~]# mkdir /dm8 [root@dm8rac3 ~]# chown -R dmdba:dinstall /dm8 [root@dm8rac3 ~]# chmod -R 775 /dm8 [root@dm8rac3 ~]# df -h /dm8 Filesystem Size Used Avail Use% Mounted on /dev/mapper/rhel-root 48G 5.6G 43G 12% /
2) DM安裝程式在安裝時將產生臨時檔案，臨時檔案需要1GB的儲存空間，臨時檔案目錄預設為/tmp。使用者可以使用以下命令檢查儲存空間。
如下圖所示：
[root@dm8rac3 ~]# df -h /tmp Filesystem Size Used Avail Use% Mounted on /dev/mapper/rhel-root 48G 5.6G 43G 12% /
3.5.安裝DM
建立目錄/soft/dmsoft用來儲存掛載iso檔案後來顯示軟體包中的檔案
[root@dm8rac3 ~]# cd /soft [root@dm8rac3 soft]# unzip dm8_20211021_x86_rh6_64_ent.zip Archive: dm8_20211021_x86_rh6_64_ent.zip creating: dm8_20211021_x86_rh6_64_ent/ inflating: dm8_20211021_x86_rh6_64_ent/dm8_20211021_x86_rh6_64_ent_8.1.2.84.iso extracting: dm8_20211021_x86_rh6_64_ent/dm8_20211021_x86_rh6_64_ent_8.1.2.84.iso_SHA256.txt extracting: dm8_20211021_x86_rh6_64_ent/verinfo.txt [root@dm8rac3 soft]# ls -lrt total 778320 drwxr-xr-x. 2 root root 132 Nov 12 13:43 dm8_20211021_x86_rh6_64_ent -rw-r--r--. 1 root root 796998047 Nov 29 10:25 dm8_20211021_x86_rh6_64_ent.zip [root@dm8rac3 soft]# mv dm8_20211021_x86_rh6_64_ent dm8 [root@dm8rac3 soft]# mkdir dmsoft [root@dm8rac3 soft]# mount -t iso9660 -o loop dm8/dm8_20211021_x86_rh6_64_ent_8.1.2.84.iso /soft/dmsoft mount: /dev/loop0 is write-protected, mounting read-only [root@dm8rac3 soft]# cd dmsoft [root@dm8rac3 dmsoft]# ls -lrt total 790160 -r-xr-xr-x. 1 root root 2802503 Oct 21 14:04 DM8 Install.pdf -r-xr-xr-x. 1 root root 806320703 Oct 21 14:11 DMInstall.bin
在/soft/dmsoft目錄下存在DMInstall.bin檔案， DMInstall.bin檔案就是DM的安裝程式。在執行安裝程式前，需要賦予DMInstall.bin檔案執行許可權。具體命令如下所示：
[root@dm8rac3 dmsoft]# chmod 755 DMInstall.bin chmod: changing permissions of ‘DMInstall.bin’: Read-only file system
在現實中，許多Linux(Unix)作業系統上是沒有圖形化介面的，為了使DM能夠在這些作業系統上順利安裝，DM提供了命令列的安裝方式。在終端進入到安裝程式所在資料夾，執行以下命令進行命令列安裝：
[dmdba@dm8rac3 dmsoft]$ ./DMInstall.bin -i Please select the installer's language (E/e:English C/c:Chinese) [E/e]:e Extract install files......... Welcome to DM DBMS Installer Whether to input the path of Key File? (Y/y:Yes N/n:No) [Y/y]:n Whether to Set The TimeZone? (Y/y:Yes N/n:No) [Y/y]:y TimeZone: [ 1]: GTM-12=West Date Line [ 2]: GTM-11=Samoa [ 3]: GTM-10=Hawaii [ 4]: GTM-09=Alaska [ 5]: GTM-08=Pacific(America and Canada) [ 6]: GTM-07=Arizona [ 7]: GTM-06=Central(America and Canada) [ 8]: GTM-05=East(America and Canada) [ 9]: GTM-04=Atlantic(America and Canada) [10]: GTM-03=Brasilia [11]: GTM-02=Middle Atlantic [12]: GTM-01=Azores [13]: GTM=Greenwich Mean Time [14]: GTM+01=Sarajevo [15]: GTM+02=Cairo [16]: GTM+03=Moscow [17]: GTM+04=AbuDhabi [18]: GTM+05=Islamabad [19]: GTM+06=Dakar [20]: GTM+07=BangKok,Hanoi [21]: GTM+08=China [22]: GTM+09=Seoul [23]: GTM+10=Guam [24]: GTM+11=Solomon [25]: GTM+12=Fiji [26]: GTM+13=Nukualofa [27]: GTM+14=Kiribati Please Select the TimeZone [21]:21 Installation Type: 1 Typical 2 Server 3 Client 4 Custom Please Input the number of the Installation Type [1 Typical]:4 1 Server component 2 Client component 2.1 Manager 2.2 Monitor 2.3 DTS 2.4 Console 2.5 Analyzer 2.6 DISQL 3 DM Drivers 4 Manual component 5 DBMS Service 5.1 Realtime Audit Service 5.2 Job Service 5.3 Instance Monitor Service 5.4 Assistant Plug-In Service Please Input the number of the Installation Type [1 2 3 4 5]:1 2 3 4 5 Require Space: 1242M Please Input the install path [/home/dmdba/dmdbms]:/dm8 Available Space:39G Please Confirm the install path(/dm8)? (Y/y:Yes N/n:No) [Y/y]:y Pre-Installation Summary Installation Location: /dm8 Require Space: 1242M Available Space: 39G Version Information: Expire Date: Installation Type: Custom Confirm to Install? (Y/y:Yes N/n:No):y 2021-12-10 08:52:34 [INFO] Installing DM DBMS... 2021-12-10 08:52:34 [INFO] Installing BASE Module... 2021-12-10 08:52:36 [INFO] Installing SERVER Module... 2021-12-10 08:52:39 [INFO] Installing CLIENT Module... 2021-12-10 08:52:54 [INFO] Installing DRIVERS Module... 2021-12-10 08:52:55 [INFO] Installing MANUAL Module... 2021-12-10 08:52:55 [INFO] Installing SERVICE Module... 2021-12-10 08:53:03 [INFO] Move log file to log directory. 2021-12-10 08:53:04 [INFO] Installed DM DBMS completely. Please execute the commands by root: /dm8/script/root/root_installer.sh End
以root使用者來執行上面的指令碼
[root@dm8rac3 ~]# /dm8/script/root/root_installer.sh Move /dm8/bin/dm_svc.conf to /etc Modify the files' mode of DM Server [dmdba@dm8rac3 ~]$ vi .bash_profile # .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/.local/bin:$HOME/bin export PATH export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/dm8/bin" export DM_HOME="/dm8" export PATH=$PATH:$LD_LIBRARY_PATH
四、繫結UDEV
編輯/etc/udev/rules.d/99-dm-devices.rules檔案
[root@dm8rac3 ~]# vi /etc/udev/rules.d/99-dm-devices.rules ACTION=="add", KERNEL=="sdb", RUN+="/bin/raw /dev/raw/raw1 %N" ACTION=="add", KERNEL=="sdc", RUN+="/bin/raw /dev/raw/raw2 %N" ACTION=="add", KERNEL=="sdd", RUN+="/bin/raw /dev/raw/raw3 %N" ACTION=="add", KERNEL=="sde", RUN+="/bin/raw /dev/raw/raw4 %N" ACTION=="add", KERNEL=="sdf", RUN+="/bin/raw /dev/raw/raw5 %N" ACTION=="add", KERNEL=="sdg", RUN+="/bin/raw /dev/raw/raw6 %N" ACTION=="add", KERNEL=="raw[1-6]", OWNER="dmdba", GROUP="dinstall", MODE="660"
如果不能正常顯示就重啟作業系統
[root@dm8rac3 ~]# ls -lrt /dev/raw/ total 0 crw-rw---- 1 root disk 162, 0 Dec 10 09:01 rawctl crw-rw---- 1 dmdba dinstall 162, 6 Dec 10 09:01 raw6 crw-rw---- 1 dmdba dinstall 162, 5 Dec 10 09:01 raw5 crw-rw---- 1 dmdba dinstall 162, 4 Dec 10 09:01 raw4 crw-rw---- 1 dmdba dinstall 162, 3 Dec 10 09:01 raw3 crw-rw---- 1 dmdba dinstall 162, 1 Dec 10 09:01 raw1 crw-rw---- 1 dmdba dinstall 162, 2 Dec 10 09:01 raw2
可以透過blockdev --getsize64 /dev/raw/raw1命令檢視裸裝置大小
[root@dm8rac3 ~]# blockdev --getsize64 /dev/raw/raw1 2147483648 [root@dm8rac3 ~]# blockdev --getsize64 /dev/raw/raw2 2147483648 [root@dm8rac3 ~]# blockdev --getsize64 /dev/raw/raw3 10737418240 [root@dm8rac3 ~]# blockdev --getsize64 /dev/raw/raw4 10737418240 [root@dm8rac3 ~]# blockdev --getsize64 /dev/raw/raw5 10737418240 [root@dm8rac3 ~]# blockdev --getsize64 /dev/raw/raw6 10737418240
四. 操作流程
1. 在10.10.13.201機器上使用DMASMCMD工具export出備份dmdcr_cfg_bak.ini
[dmdba@dm8rac1 ~]$ dmasmcmd DMASMCMD V8 ASM>export dcrdisk '/dev/raw/raw1' to '/dm8/data/dmdcr_cfg_bak.ini' ASMCMD export DCRDISK success. Used time: 59.153(ms).
2. 為新增節點準備日誌檔案
1) 使用DIsql登入任意一個節點執行新增日誌檔案操作：
至少兩個日誌檔案，路徑必須是ASM檔案格式，大小可以參考其他兩個活動節點。
SQL> alter database add node logfile '+DMLOG/log/rac2_log01.log' size 256,'+DMLOG/log/rac2_log02.log' size 256; executed successfully used time: 00:00:01.419. Execute id is 208.
2)使用dmctlcvt工具將dm.ctl轉換為文字檔案dmctl.txt，檢視dmctl.txt，新增節點的日誌檔案資訊已經新增進dm.ctl。
[dmdba@dm8rac1 data]$ dmctlcvt TYPE=1 SRC=+DMDATA/data/rac/dm.ctl DEST=/dm8/data/dmctl.txt DCR_INI=/dm8/data/dmdcr.ini DMCTLCVT V8 convert ctl to txt success! [dmdba@dm8rac1 data]$ ls -lrt total 28 -rw-r--r-- 1 dmdba dinstall 956 Dec 8 09:24 dmdcr_cfg.ini -rw-r--r-- 1 dmdba dinstall 143 Dec 8 09:29 dmasvrmal.ini -rw-r--r-- 1 dmdba dinstall 328 Dec 8 09:37 dmdcr.ini -rw-r--r-- 1 dmdba dinstall 864 Dec 8 10:13 dminit.ini drwxr-xr-x 2 dmdba dinstall 55 Dec 8 10:17 rac1_config drwxr-xr-x 3 dmdba dinstall 100 Dec 8 10:36 rac0_config -rw-r--r-- 1 dmdba dinstall 1647 Dec 10 09:06 dmdcr_cfg_bak.ini -rw-r--r-- 1 dmdba dinstall 8158 Dec 10 09:23 dmctl.txt [dmdba@dm8rac1 data]$ more dmctl.txt # file path fil_path=+DMLOG/log/rac2_log01.log # mirror path mirror_path= # file id fil_id=0 # whether the file is auto extend autoextend=1 # file create time fil_create_time=DATETIME '2021-12-10 9:20:50' # file modify time fil_modify_time=DATETIME '2021-12-10 9:20:50' # the max size of file fil_max_size=0 # next size of file fil_next_size=0 # file path fil_path=+DMLOG/log/rac2_log02.log # mirror path mirror_path= # file id fil_id=1 # whether the file is auto extend autoextend=1 # file create time fil_create_time=DATETIME '2021-12-10 9:20:50' # file modify time fil_modify_time=DATETIME '2021-12-10 9:20:50' # the max size of file
3)使用dmasmtool工具登入ASM檔案系統，也可以看到新增的節點日誌檔案
[dmdba@dm8rac1 ~]$ dmasmtool DCR_INI=/dm8/data/dmdcr.ini DMASMTOOL V8 ASM>ls +DMLOG/log file : rac0_log01.log file : rac0_log02.log file : rac1_log01.log file : rac1_log02.log file : rac2_log01.log file : rac2_log02.log total count 6. Used time: 6.598(ms).
3. 為新增節點準備config_path
將10.10.13.201機器/dm8/data/rac0_config目錄複製到10.10.13.203機器相同目錄下，修改名字為/dm8/data/rac2_config。
[dmdba@dm8rac1 data]$ scp -r rac0_config 10.10.13.203:`pwd` The authenticity of host '10.10.13.203 (10.10.13.203)' can't be established. ECDSA key fingerprint is SHA256:6O8c9WEeEYPbL4ncdRR1RsrjxxmfzPq9Tkq4/6uLSP4. ECDSA key fingerprint is MD5:e1:73:3e:8d:79:be:5c:82:0f:c7:58:79:45:ad:df:86. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.10.13.203' (ECDSA) to the list of known hosts. dmdba@10.10.13.203's password: dmmal.ini 100% 200 8.5KB/s 00:00 dminit20211208101727.log 100% 1144 70.0KB/s 00:00 dm.ini 100% 53KB 3.2MB/s 00:00 sqllog.ini 100% 481 19.3KB/s 00:00 [dmdba@dm8rac1 data]$ [dmdba@dm8rac3 data]$ mv rac0_config rac2_config [dmdba@dm8rac3 data]$ ls -lrt total 0 drwxr-xr-x 2 dmdba dinstall 6 Dec 10 09:54 trace drwxr-xr-x 3 dmdba dinstall 100 Dec 10 09:56 rac2_config
修改dsc2_config資料夾下的配置檔案：
1) 修改dm.ini
[dmdba@dm8rac3 rac2_config]$ vi dm.ini CONFIG_PATH = /dm8/data/rac2_config #config path INSTANCE_NAME = RAC2 #Instance name
2) 如果開啟了歸檔引數，修改dmarch.ini
4. 新建dmdcr.ini配置檔案，儲存到節點10.0.2.103的/dm8/data/目錄下面注意設定dmdcr_seqo為2，修改dm.ini路徑。
[dmdba@dm8rac3 data]$ vi dmdcr.ini DMDCR_PATH = /dev/raw/raw1 DMDCR_MAL_PATH =/dm8/data/dmasvrmal.ini DMDCR_SEQNO = 2 #ASM DMDCR_ASM_RESTART_INTERVAL = 0 DMDCR_ASM_STARTUP_CMD = /dm8/bin/dmasmsvr dcr_ini=/dm8/data/dmdcr.ini #DB DMDCR_DB_RESTART_INTERVAL = 0 DMDCR_DB_STARTUP_CMD = /dm8/bin/dmserver path=/dm8/data/rac2_config/dm.ini dcr_ini=/dm8/data/dmdcr.ini
5. 修改當前環境的MAL配置檔案
直接修改當前環境的dmasvrmal.ini檔案，新增新增節點資訊，使用DMASM的所有節點都要配置，內容完全一樣，並且將新增資訊後的dmasvrmal.ini檔案複製到節點10.10.13.203的/dm8/data目錄下。
[dmdba@dm8rac1 data]$ vi dmasvrmal.ini [MAL_INST1] MAL_INST_NAME = ASM0 MAL_HOST = 11.11.11.1 MAL_PORT = 7236 [MAL_INST2] MAL_INST_NAME = ASM1 MAL_HOST = 11.11.11.2 MAL_PORT = 7236 [MAL_INST3] MAL_INST_NAME = ASM2 MAL_HOST = 11.11.11.5 MAL_PORT = 7236 [dmdba@dm8rac2 data]$ vi dmasvrmal.ini [MAL_INST1] MAL_INST_NAME = ASM0 MAL_HOST = 11.11.11.1 MAL_PORT = 7236 [MAL_INST2] MAL_INST_NAME = ASM1 MAL_HOST = 11.11.11.2 MAL_PORT = 7236 [MAL_INST3] MAL_INST_NAME = ASM2 MAL_HOST = 11.11.11.5 MAL_PORT = 7236 [dmdba@dm8rac3 data]$ vi dmasvrmal.ini [MAL_INST1] MAL_INST_NAME = ASM0 MAL_HOST = 11.11.11.1 MAL_PORT = 7236 [MAL_INST2] MAL_INST_NAME = ASM1 MAL_HOST = 11.11.11.2 MAL_PORT = 7236 [MAL_INST3] MAL_INST_NAME = ASM2 MAL_HOST = 11.11.11.5 MAL_PORT = 7236
直接修改dmserver三個例項的dmmal.ini，新增新增節點資訊，所有節點都要配置相同內容，儲存到各自的rac_config目錄下
[dmdba@dm8rac1 rac0_config]$ vi dmmal.ini [mal_inst0] mal_inst_name = RAC0 mal_host = 11.11.11.1 mal_port = 9340 [mal_inst1] mal_inst_name = RAC1 mal_host = 11.11.11.2 mal_port = 9340 [mal_inst2] mal_inst_name = RAC2 mal_host = 11.11.11.5 mal_port = 9340 [dmdba@dm8rac2 rac1_config]$ vi dmmal.ini [mal_inst0] mal_inst_name = RAC0 mal_host = 11.11.11.1 mal_port = 9340 [mal_inst1] mal_inst_name = RAC1 mal_host = 11.11.11.2 mal_port = 9340 [mal_inst2] mal_inst_name = RAC2 mal_host = 11.11.11.5 mal_port = 9340 [dmdba@dm8rac3 rac2_config]$ vi dmmal.ini [mal_inst0] mal_inst_name = RAC0 mal_host = 11.11.11.1 mal_port = 9340 [mal_inst1] mal_inst_name = RAC1 mal_host = 11.11.11.2 mal_port = 9340 [mal_inst2] mal_inst_name = RAC2 mal_host = 11.11.11.5 mal_port = 9340
後續例項會重新讀MAL配置檔案，更新記憶體資訊。
6. 修改dmdcr_cfg_bak.ini，新增新增節點資訊，CSS/ASMSVR/DB都要配置
所有組資訊修改：
DCR_GRP_N_EP = 3
DCR_GRP_EP_ARR = {0,1,2}
每個組增加一個節點資訊，注意DCR_EP_SHM_KEY、埠號不能衝突；各組資訊要放在各自的後面，即[GRP_CSS]中CSS2放在CSS1後面，[GRP_ASM]中ASM2放在ASM1後面，RAC2放在RAC1後面。
[dmdba@dm8rac1 data]$ cat dmdcr_cfg_bak.ini
# the file is auto-created by system, self edit is invalid!
#DCR HDR
DCR_N_GRP = 3
DCR_VTD_PATH = /dev/raw/raw2
DCR_OGUID = 63635
[GRP]
DCR_GRP_TYPE = CSS
DCR_GRP_NAME = GRP_CSS
DCR_GRP_N_EP = 3
DCR_GRP_EP_ARR = {0,1,2}
DCR_GRP_N_ERR_EP = 0
DCR_GRP_ERR_EP_ARR = {}
DCR_GRP_DSKCHK_CNT = 60
[GRP]
DCR_GRP_TYPE = ASM
DCR_GRP_NAME = GRP_ASM
DCR_GRP_N_EP = 3
DCR_GRP_EP_ARR = {0,1,2}
DCR_GRP_N_ERR_EP = 0
DCR_GRP_ERR_EP_ARR = {}
DCR_GRP_DSKCHK_CNT = 60
[GRP]
DCR_GRP_TYPE = DB
DCR_GRP_NAME = GRP_RAC
DCR_GRP_N_EP = 3
DCR_GRP_EP_ARR = {0,1,2}
DCR_GRP_N_ERR_EP = 0
DCR_GRP_ERR_EP_ARR = {}
DCR_GRP_DSKCHK_CNT = 60
[GRP_CSS]
DCR_EP_NAME = CSS0
DCR_EP_HOST = 11.11.11.1
DCR_EP_PORT = 9541
[GRP_CSS]
DCR_EP_NAME = CSS1
DCR_EP_HOST = 11.11.11.2
DCR_EP_PORT = 9541
[GRP_CSS]
DCR_EP_NAME = CSS2
DCR_EP_HOST = 11.11.11.5
DCR_EP_PORT = 9541
[GRP_ASM]
DCR_EP_NAME = ASM0
DCR_EP_SHM_KEY = 93360
DCR_EP_SHM_SIZE = 10
DCR_EP_HOST = 10.10.13.201
DCR_EP_PORT = 9641
DCR_EP_ASM_LOAD_PATH = /dev/raw
[GRP_ASM]
DCR_EP_NAME = ASM1
DCR_EP_SHM_KEY = 93361
DCR_EP_SHM_SIZE = 10
DCR_EP_HOST = 10.10.13.202
DCR_EP_PORT = 9641
DCR_EP_ASM_LOAD_PATH = /dev/raw
[GRP_ASM]
DCR_EP_NAME = ASM2
DCR_EP_SHM_KEY = 93362
DCR_EP_SHM_SIZE = 10
DCR_EP_HOST = 10.10.13.203
DCR_EP_PORT = 9641
DCR_EP_ASM_LOAD_PATH = /dev/raw
[GRP_RAC]
DCR_EP_NAME = RAC0
DCR_EP_SEQNO = 0
DCR_EP_PORT = 5236
DCR_CHECK_PORT = 9741
[GRP_RAC]
DCR_EP_NAME = RAC1
DCR_EP_SEQNO = 1
DCR_EP_PORT = 5236
DCR_CHECK_PORT = 9741
[GRP_RAC]
DCR_EP_NAME = RAC2
DCR_EP_SEQNO = 2
DCR_EP_PORT = 5236
DCR_CHECK_PORT = 9741
7. 使用DMASMCMD工具將新增節點資訊寫回磁碟，新增節點作為error節點
[dmdba@dm8rac1 ~]$ dmasmcmd DMASMCMD V8 ASM>extend dcrdisk '/dev/raw/raw1' from '/dm8/data/dmdcr_cfg_bak.ini' ASMCMD extend node for dcr disk success. ASMCMD extend node for vote disk success. Used time: 00:00:02.362.
8. 在dmcssm控制檯執行擴充套件節點命令
先配置dmcssm.ini檔案
[dmdba@dm8rac1 data]$ vi dmcssm.ini CSSM_OGUID = 63635 #配置所有CSS的連線資訊， #和dmdcr_cfg.ini中CSS配置項的DCR_EP_HOST和DCR_EP_PORT保持一致 CSSM_CSS_IP = 11.11.11.1:9541 CSSM_CSS_IP = 11.11.11.2:9541 CSSM_CSS_IP = 11.11.11.5:9541 CSSM_LOG_PATH =/dm8/dmcssm/log #監視器日誌檔案存放路徑 CSSM_LOG_FILE_SIZE = 32 #每個日誌檔案最大32M CSSM_LOG_SPACE_LIMIT = 0 #不限定日誌檔案總佔用空間
啟動dmcssm監視器
[dmdba@dm8rac1 ~]$ dmcssm INI_PATH=/dm8/data/dmcssm.ini [monitor] 2021-12-10 10:46:32: CSS MONITOR V8 [monitor] 2021-12-10 10:46:32: CSS MONITOR SYSTEM IS READY. [monitor] 2021-12-10 10:46:32: Wait CSS Control Node choosed... [monitor] 2021-12-10 10:46:33: Wait CSS Control Node choosed succeed. show monitor current time:2021-12-10 10:46:57, n_group:3 =================== group[name = GRP_CSS, seq = 0, type = CSS, Control Node = 0] ======================================== [CSS0] auto check = TRUE, global info: [ASM0] auto restart = FALSE [RAC0] auto restart = FALSE [CSS1] auto check = TRUE, global info: [ASM1] auto restart = FALSE [RAC1] auto restart = FALSE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 10:46:57 CSS0 0 9541 Control Node OPEN WORKING OK TRUE 738576474 738751954 2021-12-10 10:46:57 CSS1 1 9541 Normal Node OPEN WORKING OK TRUE 738606319 738781682 =================== group[name = GRP_ASM, seq = 1, type = ASM, Control Node = 0] ======================================== n_ok_ep = 2 ok_ep_arr(index, seqno): (0, 0) (1, 1) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 10:46:57 ASM0 0 9641 Control Node OPEN WORKING OK TRUE 738588988 738764427 2021-12-10 10:46:57 ASM1 1 9641 Normal Node OPEN WORKING OK TRUE 738624010 738799326 =================== group[name = GRP_RAC, seq = 2, type = DB, Control Node = 0] ======================================== n_ok_ep = 2 ok_ep_arr(index, seqno): (0, 0) (1, 1) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 10:46:57 RAC0 0 5236 Control Node OPEN WORKING OK TRUE 2383210041 2383382787 2021-12-10 10:46:57 RAC1 1 5236 Normal Node OPEN WORKING OK TRUE 2383231629 2383404339 ================================================================================================================== extend node [monitor] 2021-12-10 10:47:13: Extend node [monitor] 2021-12-10 10:47:15: Notify current active CSS to do clear [monitor] 2021-12-10 10:47:16: Clean request of CSS(0) success [monitor] 2021-12-10 10:47:17: Clean request of CSS(1) success [monitor] 2021-12-10 10:47:17: Command EXTENT NODE execute success show monitor current time:2021-12-10 10:47:22, n_group:3 =================== group[name = GRP_CSS, seq = 0, type = CSS, Control Node = 0] ======================================== [CSS0] auto check = TRUE, global info: [ASM0] auto restart = FALSE [RAC0] auto restart = FALSE [CSS1] auto check = TRUE, global info: [ASM1] auto restart = FALSE [RAC1] auto restart = FALSE [CSS2] auto check = FALSE, global info: Connect to [CSS2] failed, please check the network or the CSSM_CSS_IP config in [/dm8/data/dmcssm.ini] . ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 10:47:22 CSS0 0 9541 Control Node OPEN WORKING OK TRUE 738576474 738751979 2021-12-10 10:47:22 CSS1 1 9541 Normal Node OPEN WORKING OK TRUE 738606319 738781707 2021-12-10 10:47:22 CSS2 2 9541 Normal Node SHUTDOWN UNKNOWN OK FALSE 0 0 =================== group[name = GRP_ASM, seq = 1, type = ASM, Control Node = 0] ======================================== n_ok_ep = 2 ok_ep_arr(index, seqno): (0, 0) (1, 1) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 10:47:22 ASM0 0 9641 Control Node OPEN WORKING OK TRUE 738588988 738764452 2021-12-10 10:47:22 ASM1 1 9641 Normal Node OPEN WORKING OK TRUE 738624010 738799351 2021-12-10 10:47:22 ASM2 2 9641 Normal Node SHUTDOWN UNKNOWN ERROR FALSE 0 0 =================== group[name = GRP_RAC, seq = 2, type = DB, Control Node = 0] ======================================== n_ok_ep = 2 ok_ep_arr(index, seqno): (0, 0) (1, 1) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 10:47:22 RAC0 0 5236 Control Node OPEN WORKING OK TRUE 2383210041 2383382812 2021-12-10 10:47:22 RAC1 1 5236 Normal Node OPEN WORKING OK TRUE 2383231629 2383404364 2021-12-10 10:47:22 RAC2 2 5236 Normal Node SHUTDOWN UNKNOWN ERROR FALSE 0 0 ==================================================================================================================
程式會通知所有例項(CSS/ASMSVR/dmserver)更新資訊，在CSS控制檯執行SHOW命令，能看到新增節點資訊，ASMSVR/dmserver是error節點，程式會通知ASMSVR/dmserver更新MAL資訊。
注意:如果由於配置檔案錯誤，動態擴充套件節點失敗，只能停掉所有例項，重新init dcr磁碟，不影響dmserver資料
9. 啟動新的DMCSS、DMASM服務程式
在10.10.13.203節點啟動dmcss、dmasmsvr程式。
手動啟動新的dmcss，dcr_ini指向新的dmdcr.ini檔案：
[/opt/dmdbms/bin]# ./dmcss DCR_INI=/home/data/dmdcr.ini
手動啟動新的dmasmsvr，dcr_ini指向新的dmdcr.ini檔案，asmsvr啟動故障重加入流程：
[/opt/dmdbms/bin]# ./dmasmsvr DCR_INI=/home/data/dmdcr.ini
如果DMCSS配置有自動拉起dmasmsvr的功能，可以等待DMCSS自動拉起dmasmsvr程式，不需要手動啟動。
我這裡將服務註冊成服務
[root@dm8rac3 system]# /dm8/script/root/dm_service_installer.sh -t dmcss -dcr_ini /dm8/data/dmdcr.ini -p rac3 Created symlink from /etc/systemd/system/multi-user.target.wants/DmCSSServicerac3.service to /usr/lib/systemd/system/DmCSSServicerac3.service. Finished to create the service (DmCSSServicerac3) [root@dm8rac3 system]# /dm8/script/root/dm_service_installer.sh -t dmasmsvr -dcr_ini /dm8/data/dmdcr.ini -p rac3 -y DmCSSServicerac3 Created symlink from /etc/systemd/system/multi-user.target.wants/DmASMSvrServicerac3.service to /usr/lib/systemd/system/DmASMSvrServicerac3.service. Finished to create the service (DmASMSvrServicerac3) [root@dm8rac3 system]# [root@dm8rac3 system]# service DmCSSServicerac3 start Redirecting to /bin/systemctl start DmCSSServicerac3.service [root@dm8rac3 system]# service DmCSSServicerac3 status Redirecting to /bin/systemctl status DmCSSServicerac3.service DmCSSServicerac3.service - DM Cluster Synchronization Services Service(DmCSSServicerac3). Loaded: loaded (/usr/lib/systemd/system/DmCSSServicerac3.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-12-10 10:59:41 CST; 19s ago Process: 4340 ExecStart=/dm8/bin/DmCSSServicerac3 start (code=exited, status=0/SUCCESS) Main PID: 4368 (dmcss) Tasks: 12 CGroup: /system.slice/DmCSSServicerac3.service └─4368 /dm8/bin/dmcss dcr_ini=/dm8/data/dmdcr.ini Dec 10 10:59:26 dm8rac3 systemd[1]: Starting DM Cluster Synchronization Services Service(DmCSSServicerac3).... Dec 10 10:59:41 dm8rac3 DmCSSServicerac3[4340]: [38B blob data] Dec 10 10:59:41 dm8rac3 systemd[1]: Started DM Cluster Synchronization Services Service(DmCSSServicerac3).. [root@dm8rac3 system]# service DmASMSvrServicerac3 start Redirecting to /bin/systemctl start DmASMSvrServicerac3.service [root@dm8rac3 system]# service DmASMSvrServicerac3 status Redirecting to /bin/systemctl status DmASMSvrServicerac3.service DmASMSvrServicerac3.service - DM Auto Storage Manager Service(DmASMSvrServicerac3). Loaded: loaded (/usr/lib/systemd/system/DmASMSvrServicerac3.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-12-10 11:00:23 CST; 7s ago Process: 4441 ExecStart=/dm8/bin/DmASMSvrServicerac3 start (code=exited, status=0/SUCCESS) Main PID: 4467 (dmasmsvr) Tasks: 18 CGroup: /system.slice/DmASMSvrServicerac3.service └─4467 /dm8/bin/dmasmsvr dcr_ini=/dm8/data/dmdcr.ini Dec 10 11:00:08 dm8rac3 systemd[1]: Starting DM Auto Storage Manager Service(DmASMSvrServicerac3).... Dec 10 11:00:23 dm8rac3 DmASMSvrServicerac3[4441]: [41B blob data] Dec 10 11:00:23 dm8rac3 systemd[1]: Started DM Auto Storage Manager Service(DmASMSvrServicerac3).. show monitor current time:2021-12-10 11:01:08, n_group:3 =================== group[name = GRP_CSS, seq = 0, type = CSS, Control Node = 0] ======================================== [CSS0] auto check = TRUE, global info: [ASM0] auto restart = FALSE [RAC0] auto restart = FALSE [CSS1] auto check = TRUE, global info: [ASM1] auto restart = FALSE [RAC1] auto restart = FALSE [CSS2] auto check = TRUE, global info: [ASM2] auto restart = FALSE [RAC2] auto restart = FALSE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 11:01:08 CSS0 0 9541 Control Node OPEN WORKING OK TRUE 738576474 738752802 2021-12-10 11:01:08 CSS1 1 9541 Normal Node OPEN WORKING OK TRUE 738606319 738782529 2021-12-10 11:01:08 CSS2 2 9541 Normal Node OPEN WORKING OK TRUE 790591989 790592089 =================== group[name = GRP_ASM, seq = 1, type = ASM, Control Node = 0] ======================================== n_ok_ep = 3 ok_ep_arr(index, seqno): (0, 0) (1, 1) (2, 2) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 11:01:08 ASM0 0 9641 Control Node OPEN WORKING OK TRUE 738588988 738765275 2021-12-10 11:01:08 ASM1 1 9641 Normal Node OPEN WORKING OK TRUE 738624010 738800174 2021-12-10 11:01:08 ASM2 2 9641 Normal Node OPEN WORKING OK TRUE 790605125 790605178 =================== group[name = GRP_RAC, seq = 2, type = DB, Control Node = 0] ======================================== n_ok_ep = 2 ok_ep_arr(index, seqno): (0, 0) (1, 1) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 11:01:08 RAC0 0 5236 Control Node OPEN WORKING OK TRUE 2383210041 2383383635 2021-12-10 11:01:08 RAC1 1 5236 Normal Node OPEN WORKING OK TRUE 2383231629 2383405186 2021-12-10 11:01:08 RAC2 2 5236 Normal Node SHUTDOWN UNKNOWN ERROR FALSE 0 0 ==================================================================================================================
10. 啟動新的資料庫伺服器
如果DMCSS配置有自動拉起dmserver的功能，可以等待DMCSS自動拉起例項，不需要手動啟動。
如果需要手動啟動，可參考下面的操作步驟：
10.10.13.203機器：
./dmserver /home/data/dsc2_config/dm.ini dcr_ini=/home/data/dmdcr.ini
我這裡註冊成服務來啟動資料庫
[root@dm8rac3 system]# /dm8/script/root/dm_service_installer.sh -t dmserver -dm_ini /dm8/data/rac2_config/dm.ini -dcr_ini /dm8/data/dmdcr.ini -p rac3 -y DmASMSvrServicerac3 Created symlink from /etc/systemd/system/multi-user.target.wants/DmServicerac3.service to /usr/lib/systemd/system/DmServicerac3.service. Finished to create the service (DmServicerac3) [root@dm8rac3 system]# service DmServicerac3 start Redirecting to /bin/systemctl start DmServicerac3.service [root@dm8rac3 system]# service DmServicerac3 status Redirecting to /bin/systemctl status DmServicerac3.service DmServicerac3.service - DM Instance Service(DmServicerac3). Loaded: loaded (/usr/lib/systemd/system/DmServicerac3.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-12-10 11:05:56 CST; 7s ago Process: 4673 ExecStart=/dm8/bin/DmServicerac3 start (code=exited, status=0/SUCCESS) Main PID: 4704 (dmserver) Tasks: 105 CGroup: /system.slice/DmServicerac3.service └─4704 /dm8/bin/dmserver path=/dm8/data/rac2_config/dm.ini dcr_ini=/dm8/data/dmdcr.ini -noconsole Dec 10 11:05:40 dm8rac3 systemd[1]: Starting DM Instance Service(DmServicerac3).... Dec 10 11:05:41 dm8rac3 DmServicerac3[4673]: Starting DmServicerac3: connnect dmasmtool successfully. Dec 10 11:05:56 dm8rac3 DmServicerac3[4673]: [11B blob data] Dec 10 11:05:56 dm8rac3 systemd[1]: Started DM Instance Service(DmServicerac3).. show monitor current time:2021-12-10 11:06:09, n_group:3 =================== group[name = GRP_CSS, seq = 0, type = CSS, Control Node = 0] ======================================== [CSS0] auto check = TRUE, global info: [ASM0] auto restart = FALSE [RAC0] auto restart = FALSE [CSS1] auto check = TRUE, global info: [ASM1] auto restart = FALSE [RAC1] auto restart = FALSE [CSS2] auto check = TRUE, global info: [ASM2] auto restart = FALSE [RAC2] auto restart = FALSE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 11:06:09 CSS0 0 9541 Control Node OPEN WORKING OK TRUE 738576474 738753101 2021-12-10 11:06:09 CSS1 1 9541 Normal Node OPEN WORKING OK TRUE 738606319 738782829 2021-12-10 11:06:09 CSS2 2 9541 Normal Node OPEN WORKING OK TRUE 790591989 790592389 =================== group[name = GRP_ASM, seq = 1, type = ASM, Control Node = 0] ======================================== n_ok_ep = 3 ok_ep_arr(index, seqno): (0, 0) (1, 1) (2, 2) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 11:06:09 ASM0 0 9641 Control Node OPEN WORKING OK TRUE 738588988 738765574 2021-12-10 11:06:09 ASM1 1 9641 Normal Node OPEN WORKING OK TRUE 738624010 738800474 2021-12-10 11:06:09 ASM2 2 9641 Normal Node OPEN WORKING OK TRUE 790605125 790605478 =================== group[name = GRP_RAC, seq = 2, type = DB, Control Node = 0] ======================================== n_ok_ep = 3 ok_ep_arr(index, seqno): (0, 0) (1, 1) (2, 2) sta = OPEN, sub_sta = STARTUP break ep = NULL recover ep = NULL crash process over flag is TRUE ep: css_time inst_name seqno port mode inst_status vtd_status is_ok active guid ts 2021-12-10 11:06:09 RAC0 0 5236 Control Node OPEN WORKING OK TRUE 2383210041 2383383934 2021-12-10 11:06:09 RAC1 1 5236 Normal Node OPEN WORKING OK TRUE 2383231629 2383405486 2021-12-10 11:06:09 RAC2 2 5236 Normal Node OPEN WORKING OK TRUE 2557760476 2557760496 ==================================================================================================================
五.注意事項
1. 擴充套件節點前由使用者保證所有dmcss/dmasmsvr/dmserver節點都是OK的，且都是活動的；
2. 每次擴充套件節點只能擴一個節點，擴充套件完成後可以再繼續擴充套件節點；
3. 擴充套件節點的過程中不能出現修改例項狀態或模式的操作；
4. 擴充套件節點的過程中，如果發生dmcss/dmasmsvr/dmserver例項故障，會導致擴充套件失敗；
5. 擴充套件過程中操作失誤（比如未修改dmmal.ini、asmsvrmal.ini，未增加日誌檔案），會導致擴充套件失敗；
6. 執行完extend node命令，使用者需要檢視log檔案，確認擴充套件操作是否成功；
7. 擴充套件失敗可能會導致叢集環境異常，需要退出所有dmcss/dmasmsvr/dmserver，重新init dcr磁碟。
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/26015009/viewspace-2871092/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- DM8搭建2節點DMDSC
- DM8 配置DMDSC主備環境(rac到單節點 )
- Azure Load Balancer : 動態擴充套件套件
- c# ExpandoObject動態擴充套件物件C#Object套件物件
- etcd管理，證書配置，擴充套件，遷移恢復，帶證書擴充套件節點套件
- activiti通過擴充套件點重寫節點行為套件
- Spring Cloud Gateway 擴充套件支援動態限流SpringCloudGateway套件
- SpringBoot擴充套件點EnvironmentPostProcessorSpring Boot套件
- DM8動態增加讀寫分離叢集節點
- kotlin 擴充套件（擴充套件函式和擴充套件屬性）Kotlin套件函式
- 巧用SpringBoot擴充套件點EnvironmentPostProcessorSpring Boot套件
- 擴充套件節能器：Lights Out for Mac套件Mac
- 不改表結構如何動態擴充套件欄位套件
- DcatAdmin 擴充套件: 自定義表單(動態表單)套件
- MoE 系列（三）｜使用 Istio 動態更新 Go 擴充套件配置Go套件
- 漫畫：Kotlin 的擴充套件細節探究Kotlin套件
- 【Kotlin】擴充套件屬性、擴充套件函式Kotlin套件函式
- SpringBoot各類擴充套件點詳解Spring Boot套件
- 雜湊表擴充套件—點陣圖套件
- 【SpringBoot】分析 SpringBoot 中的擴充套件點Spring Boot套件
- IOS setOnclick - 點選事件完美擴充套件iOS事件套件
- 聊聊Spring擴充套件點BeanPostProcessor和BeanFactoryPostProcessorSpring套件Bean
- 單體系統如何實現動態演進擴充套件套件
- 擴充套件工具套件
- Sanic 擴充套件套件
- Mybatis擴充套件MyBatis套件
- SpringMVC 擴充套件SpringMVC套件
- ORACLE 擴充套件Oracle套件
- 使用Kotlin擴充套件函式擴充套件Spring Data案例Kotlin套件函式Spring
- JMeter 擴充套件開發：擴充套件 TCP 取樣器JMeter套件TCP
- PostgreSql擴充套件Sql-動態載入共享庫(C函式)SQL套件函式
- PostgreSQL 原始碼解讀（248）- HTAB動態擴充套件圖解#2SQL原始碼套件圖解
- PostgreSQL 原始碼解讀（247）- HTAB動態擴充套件圖解#1SQL原始碼套件圖解
- gpexpand擴充gp例項和節點
- [外掛擴充套件]焦點圖外掛套件
- 自動化擴充套件挑戰：ROI套件
- shell擴充套件——免互動指令碼套件指令碼
- ?用Chrome擴充套件管理器, 管理你的擴充套件Chrome套件