purescale install

字数 33968阅读 3155评论 1赞 0

(以前是写给自己看) 2 virtualboxes (以前练oracle用的，装的oracle linux 6）s1: 192.168.1.31s2: 192.168.1.32-- make sure pre-check pass[root@s1 stage]# ./db2prereqcheck-- install on both s1 and s2[root@s1 stage]# ./db2_install -- create cluster domain[root@s1 ~]# db2cluster -cfs -create -domain expdomain -host s1The shared file system cluster has been successfully created.[root@s1 ~]# db2cluster -cfs -add -host s2Host 's2' has been successfully added to the shared file system cluster.-- add license[root@s1 ~]# mmchlicense server --accept -N s1,s2The following nodes will be designated as possessing GPFS server licenses:        s1        s2mmchlicense: Command successfully completedmmchlicense: Propagating the cluster configuration data to all  affected nodes.  This is an asynchronous process.[root@s1 ~]# db2cluster -cfs -add -licenseThe license for the shared file system cluster has been successfully added.-- create nsd[root@s1 ~]# mmcrnsd -F ~/nsd.txt mmcrnsd: Processing disk sdbmmcrnsd: Propagating the cluster configuration data to all  affected nodes.  This is an asynchronous process.[root@s1 ~]# mmlsnsd File system   Disk name    NSD servers                                    --------------------------------------------------------------------------- (free disk)   expnsd       (directly attached)      -- create FS[root@s1 ~]# mmstartup -aWed Dec 17 20:46:18 GMT 2014: mmstartup: Starting GPFS ...s1:  The GPFS subsystem is already active.[root@s1 ~]# mmgetstate -a Node number  Node name        GPFS state ------------------------------------------       1      s1               active       2      s2               active[root@s1 ~]# mmcrfs -T /expnsd expnsd expnsdThe following disks of expnsd will be formatted on node s1:    expnsd: size 6291456 KBFormatting file system ...Disks up to size 103 GB can be added to storage pool system.Creating Inode FileCreating Allocation MapsCreating Log FilesClearing Inode Allocation MapClearing Block Allocation MapFormatting Allocation Map for storage pool systemCompleted creation of file system /dev/expnsd.mmcrfs: Propagating the cluster configuration data to all  affected nodes.  This is an asynchronous process.[root@s1 ~]# mmmount all -aWed Dec 17 20:55:39 GMT 2014: mmmount: Mounting file systems ...[root@s1 ~]# dfFilesystem           1K-blocks      Used Available Use% Mounted on/dev/mapper/vg_ai0-lv_root                      44969032  25317712  17366984  60% /tmpfs                   380372        88    380284   1% /dev/shm/dev/sda1               495844    100408    369836  22% /boot/dev/expnsd            6291456    172800   6118656   3% /expnsd[root@s2 ~]# dfFilesystem           1K-blocks      Used Available Use% Mounted on/dev/mapper/vg_ai0-lv_root                      44969032  25358984  17325712  60% /tmpfs                   380372        88    380284   1% /dev/shm/dev/sda1               495844    100408    369836  22% /boot/dev/expnsd            6291456   1221376   5070080  20% /expnsd## another way to do[root@s1 ~]# fdisk -l | grep devDisk /dev/sda: 51.5 GB, 51539607552 bytes/dev/sda1   *           1          64      512000   83  Linux/dev/sda2              64        6267    49818624   8e  Linux LVMDisk /dev/sdb: 11.8 GB, 11811160064 bytesDisk /dev/mapper/vg_ai0-lv_root: 46.8 GB, 46783266816 bytesDisk /dev/mapper/vg_ai0-lv_swap: 4227 MB, 4227858432 bytes[root@s1 ~]# db2cluster_prepare -instance_shared_dev /dev/sdbDBI1446I  The db2cluster_prepare command is running.DB2 installation is being initialized. Total number of tasks to be performed: 1 Total estimated time for all tasks to be performed: 60 second(s) Task #1 startDescription: Creating IBM General Parallel File System (GPFS) Cluster and Filesystem Estimated time 60 second(s) Task #1 end The execution completed successfully.For more information see the DB2 installation log at"/tmp/db2cluster_prepare.log".DBI1070I  Program db2cluster_prepare completed successfully.[root@s1 ~]# db2cluster -cfs -add -host s2Host 's2' has been successfully added to the shared file system cluster.[root@s1 ~]# db2cluster -cfs -add -licenseThe license for the shared file system cluster has been successfully added.[root@s1 ~]# mmstartup -aFri Dec 19 20:35:53 GMT 2014: mmstartup: Starting GPFS ...s1:  The GPFS subsystem is already active.[root@s1 ~]# mmgetstate -a Node number  Node name        GPFS state ------------------------------------------       1      s1               active       2      s2               active[root@s1 ~]# mmmount all -aFri Dec 19 20:36:26 GMT 2014: mmmount: Mounting file systems ...d[root@s1 ~]# df -hFilesystem            Size  Used Avail Use% Mounted on/dev/mapper/vg_ai0-lv_root                       43G   24G   18G  58% /tmpfs                1004M   88K 1004M   1% /dev/shm/dev/sda1             485M   99M  362M  22% /boot/dev/db2fs1            11G  613M   11G   6% /db2sd_20141219203116[root@s1 ~]# ssh s2 df -hFilesystem            Size  Used Avail Use% Mounted on/dev/mapper/vg_ai0-lv_root                       43G   24G   18G  58% /tmpfs                1004M   88K 1004M   1% /dev/shm/dev/sda1             485M   99M  362M  22% /boot/dev/db2fs1            11G  613M   11G   6% /db2sd_20141219203116### Continued[root@s0 server_t]# db2cluster -cfs -create -domain mygpfsdomain -host s0The shared file system cluster has been successfully created.[root@s0 server_t]# mmstartupSat Mar 21 12:40:27 GMT 2015: mmstartup: Starting GPFS ...[root@s0 server_t]# db2cluster -cfs -create -filesystem gpfs_db2data -disk /dev/sdb -mount /gpfs_db2dataFile system 'gpfs_db2data' has been successfully created.[root@s0 server_t]# mmgetstate Node number  Node name        GPFS state ------------------------------------------       1      s0               active[root@s0 server_t]# df -hFilesystem            Size  Used Avail Use% Mounted on/dev/mapper/vg_ai0-lv_root                       43G   22G   19G  54% /tmpfs                1004M   88K 1004M   1% /dev/shm/dev/sda1             485M   99M  362M  22% /boot/dev/gpfs_db2data      12G  612M   12G   5% /gpfs_db2dataPart II -- set up second PS (s2 and s3) [root@s2 ~]# db2cluster -cfs -create -domain stbydomain -host s2The shared file system cluster has been successfully created.[root@s2 ~]# db2cluster -cfs -add -host S3Host 'S3' has been successfully added to the shared file system cluster.[root@s2 ~]# mmchlicense server --accept -N s2,S3The following nodes will be designated as possessing GPFS server licenses:        s2        s3mmchlicense: Command successfully completedmmchlicense: Propagating the cluster configuration data to all  affected nodes.  This is an asynchronous process.[root@s2 ~]# db2cluster -cfs -start -allAll specified hosts have been started successfully.[root@s2 ~]# mmgetstate -a Node number  Node name        GPFS state ------------------------------------------       1      s2               active       2      s3               active[root@s2 ~]# db2cluster -cfs -create -filesystem gpfs_db2data -disk /dev/sdb -mount /gpfs_db2dataFile system 'gpfs_db2data' has been successfully created.[root@s2 ~]# df -hFilesystem            Size  Used Avail Use% Mounted on/dev/mapper/vg_ai0-lv_root                       43G  8.8G   32G  22% /tmpfs                1004M   88K 1004M   1% /dev/shm/dev/sda1             485M   99M  362M  22% /boot/dev/gpfs_db2data      11G  613M   11G   6% /gpfs_db2data[root@s2 ~]# ssh s3 df -hFilesystem            Size  Used Avail Use% Mounted on/dev/mapper/vg_ai0-lv_root                       43G   12G   30G  29% /tmpfs                1004M   88K 1004M   1% /dev/shm/dev/sda1             485M   99M  362M  22% /boot/dev/gpfs_db2data      11G  613M   11G   6% /gpfs_db2data[root@s2 ~]# db2icrt -cf s2 -cfnet s2 -m s3 -mnet s3 -instance_shared_dir /gpfs_db2data -tbdev 192.168.1.1 -u i1 i1DBI1446I  The db2icrt command is running.DB2 installation is being initialized. Total number of tasks to be performed: 11 Total estimated time for all tasks to be performed: 1104 second(s) Task #1 startDescription: Installing DB2 files on remote hosts Estimated time 600 second(s) Task #1 end Task #2 startDescription: Installing or updating DB2 HA scripts for IBM Tivoli System Automation for Multiplatforms (Tivoli SA MP) Estimated time 40 second(s) Task #2 end Task #3 startDescription: Installing or updating DB2 Cluster Scripts for IBM General Parallel File System (GPFS) Estimated time 40 second(s) Task #3 end Task #4 startDescription: Registering licenses on remote hosts Estimated time 40 second(s) Task #4 end Task #5 startDescription: Compiling GPL Estimated time 30 second(s) Task #5 end Task #6 startDescription: Setting default global profile registry variables Estimated time 1 second(s) Task #6 end Task #7 startDescription: Register NTP Estimated time 40 second(s) Task #7 end Task #8 startDescription: Initializing instance list Estimated time 5 second(s) Task #8 end Task #9 startDescription: Initiating the remote host list Estimated time 5 second(s) Task #9 end Task #10 startDescription: Configuring DB2 instances Estimated time 300 second(s) Task #10 end Task #11 startDescription: Updating global profile registry Estimated time 3 second(s) Task #11 end The execution completed successfully.For more information see the DB2 installation log at "/tmp/db2icrt.log.10888".DBI1070I  Program db2icrt completed successfully.[i1@s3 ~]$ db2start03/28/2015 01:19:13     0   0   SQL1063N  DB2START processing was successful.SQL1063N  DB2START processing was successful.[i1@s3 ~]$ db2 connect to sample   Database Connection Information Database server        = DB2/LINUXX8664 10.5.5 SQL authorization ID   = I1 Local database alias   = SAMPLE[i1@s3 ~]$ db2 list tables | headTable/View                      Schema          Type  Creation time             ------------------------------- --------------- ----- --------------------------ACT                             I1              T     2015-03-28-01.41.05.289833ADEFUSR                         I1              S     2015-03-28-01.41.11.032454CL_SCHED                        I1              T     2015-03-28-01.41.00.837140DEPARTMENT                      I1              T     2015-03-28-01.41.01.787346DEPT                            I1              A     2015-03-28-01.41.02.644292EMP                             I1              A     2015-03-28-01.41.03.095928EMPACT                          I1              A     2015-03-28-01.41.05.282848[i1@s3 ~]$ db2instance -listID        TYPE             STATE                HOME_HOST               CURRENT_HOST            ALERT   PARTITION_NUMBER        LOGICAL_PORT       NETNAME--        ----             -----                ---------               ------------            -----   ----------------        ------------       -------0       MEMBER           STARTED                       s3                         s3               NO                  0                   0            s3128     CF               PRIMARY                       s2                         s2               NO                  -                   0            s2HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT--------                   -----                ----------------        -----      s2                  ACTIVE                              NO           NO      s3                  ACTIVE                              NO           NO[i1@s3 ~]$ Part III HADRReference:==========<a href="http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0061088.html" rel="nofollow" target="_blank">http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0061088.html</a>Given Env:==========    Database name: sample    Instance owner on all hosts: i1    TCP port that is used for HADR primary-standby communication: 54321    TCP port that is used for SQL client/server communication: 50000    Hosts for cluster caching facilities and members on the primary: s0, and s1    Hosts for cluster caching facilities and members on the standby: s2, and s3Configure HADR:==============    The DBA takes a backup of the intended primary database sample:    db2 BACKUP DB sample TO /tmp    The DBA restores the backup onto the intended standby cluster:    db2 RESTORE DB sample FROM /tmp    On the primary, the DBA sets the cluster-level HADR parameters    db2 "UPDATE DB CFG FOR sample USING         HADR_TARGET_LIST  {s3:54321}         HADR_REMOTE_HOST  {s3:54321}         HADR_REMOTE_INST  i1         HADR_SYNCMODE     async"        For member 0:        db2 "UPDATE DB CFG FOR sample MEMBER 0 USING             HADR_LOCAL_HOST   s1             HADR_LOCAL_SVC    54321"[root@s1 ~]# su - i1[i1@s1 ~]$ db2 update db cfg for sample using logindexbuild onDB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.[i1@s1 ~]$ db2 update db cfg for sample using indexrec restartDB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.[i1@s1 ~]$ db2 backup db sample to /tmpBackup successful. The timestamp for this backup image is : 20150328033939[i1@s1 ~]$[i1@s1 ~]$     db2 "UPDATE DB CFG FOR sample USING>          HADR_TARGET_LIST  {s3:54321}>          HADR_REMOTE_HOST  {s3:54321}>          HADR_REMOTE_INST  i1>          HADR_SYNCMODE     async"DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.[i1@s1 ~]$[i1@s1 ~]$         db2 "UPDATE DB CFG FOR sample MEMBER 0 USING>              HADR_LOCAL_HOST   s1>              HADR_LOCAL_SVC    54321"DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.[i1@s1 ~]$ ls /tmp | grep SAMSAMPLE.0.i1.DBPART000.20150328033939.001[i1@s1 ~]$ scp /tmp/SAMPLE.0.i1.DBPART000.20150328033939.001 s3:/tmpSAMPLE.0.i1.DBPART000.20150328033939.001    The DBA restores the backup onto the intended standby cluster:    db2 RESTORE DB sample FROM /tmp    On the standby, the DBA sets the cluster-level HADR parameters that    db2 "UPDATE DB CFG FOR sample USING         HADR_TARGET_LIST  {s1:54321}         HADR_REMOTE_HOST  {s1:54321}         HADR_REMOTE_INST  i1         HADR_SYNCMODE     async"        For member 0:        db2 "UPDATE DB CFG FOR sample MEMBER 0 USING HADR_LOCAL_HOST   s3 HADR_LOCAL_SVC    54321"[i1@s3 ~]$ db2 RESTORE DB sample FROM /tmpDB20000I  The RESTORE DATABASE command completed successfully.[root@s3 ~]# su - i1[i1@s3 ~]$     db2 "UPDATE DB CFG FOR sample USING>          HADR_TARGET_LIST  {s1:54321}>          HADR_REMOTE_HOST  {s1:54321}>          HADR_REMOTE_INST  i1>          HADR_SYNCMODE     async"DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.[i1@s3 ~]$ db2 "UPDATE DB CFG FOR sample MEMBER 0 USING HADR_LOCAL_HOST   s3 HADR_LOCAL_SVC    54321"DB20000I  The UPDATE DATABASE CONFIGURATION command completed successfully.Starting HADRAs with other HADR environments, the standby database must be started first.Because the member that the START HADR command is issued from is designatedthe preferred replay member, the DBA issues the following commands:    From member 0 on the standby:    db2 START HADR ON DB sample AS STANDBY    From member 0 on the primary:    db2 START HADR ON DB sample AS PRIMARY[i1@s3 ~]$ db2 START HADR ON DB sample AS STANDBYDB20000I  The START HADR ON DATABASE command completed successfully.[i1@s1 ~]$ db2 START HADR ON DB sample AS primaryDB20000I  The START HADR ON DATABASE command completed successfully.[i1@s1 ~]$ db2 connect to sample   Database Connection Information Database server        = DB2/LINUXX8664 10.5.5 SQL authorization ID   = I1 Local database alias   = SAMPLE[i1@s1 ~]$ db2 "select LOG_STREAM_ID, PRIMARY_MEMBER, STANDBY_MEMBER,HADR_STATE from table (mon_get_hadr(-2))"LOG_STREAM_ID PRIMARY_MEMBER STANDBY_MEMBER HADR_STATE             ------------- -------------- -------------- -----------------------            0              0              0 PEER                     1 record(s) selected.Role swicth===========At site B, the DBA issues the TAKEOVER HADR command on member 0:TAKEOVER HADR ON DB hadr_db============================[i1@s3 ~]$ db2 takeover hadr on db sampleDB20000I  The TAKEOVER HADR ON DATABASE command completed successfully.[i1@s3 ~]$ db2 connect to sample   Database Connection Information Database server        = DB2/LINUXX8664 10.5.5 SQL authorization ID   = I1 Local database alias   = SAMPLE[i1@s3 ~]$ db2 "select LOG_STREAM_ID, PRIMARY_MEMBER, STANDBY_MEMBER,HADR_STATE from table (mon_get_hadr(-2))"LOG_STREAM_ID PRIMARY_MEMBER STANDBY_MEMBER HADR_STATE             ------------- -------------- -------------- -----------------------            0              0              0 PEER                     1 record(s) selected.Failover========[i1@s1 ~]$ db2pd -d sample -hadr | head -17Database Member 0 -- Database SAMPLE -- Standby -- Up 0 days 00:06:18 -- Date2015-03-28-12.51.19.819014                            HADR_ROLE = STANDBY                          REPLAY_TYPE = PHYSICAL                        HADR_SYNCMODE = ASYNC                           STANDBY_ID = 0                        LOG_STREAM_ID = 0                           HADR_STATE = REMOTE_CATCHUP_PENDING                           HADR_FLAGS =                   PRIMARY_MEMBER_HOST = s3                     PRIMARY_INSTANCE = i1                       PRIMARY_MEMBER = 0                  STANDBY_MEMBER_HOST = s1                     STANDBY_INSTANCE = i1                       STANDBY_MEMBER = 0                  HADR_CONNECT_STATUS = DISCONNECTED[i1@s1 ~]$ db2 TAKEOVER HADR ON DB sample BY FORCEDB20000I  The TAKEOVER HADR ON DATABASE command completed successfully.[i1@s1 ~]$ db2pd -d sample -hadr | head -17Database Member 0 -- Database SAMPLE -- Active -- Up 0 days 00:06:33 -- Date2015-03-28-12.51.34.921518                            HADR_ROLE = PRIMARY                          REPLAY_TYPE = PHYSICAL                        HADR_SYNCMODE = ASYNC                           STANDBY_ID = 1                        LOG_STREAM_ID = 0                           HADR_STATE = DISCONNECTED                           HADR_FLAGS =                   PRIMARY_MEMBER_HOST = s1                     PRIMARY_INSTANCE = i1                       PRIMARY_MEMBER = 0                  STANDBY_MEMBER_HOST = s3                     STANDBY_INSTANCE = i1                       STANDBY_MEMBER = 0                  HADR_CONNECT_STATUS = DISCONNECTED[i1@s1 ~]$ db2 connect to sample   Database Connection Information Database server        = DB2/LINUXX8664 10.5.5 SQL authorization ID   = I1 Local database alias   = SAMPLE

数据库 ps HADR

著作权归作者所有

如果觉得我的文章对您有用，请点赞。您的支持将鼓励我继续创作！

添加新评论1 条评论

atpeace331数据库管理员银行
2015-07-17 10:18

大哥，DB2 purescale 好玩吗？

Ctrl+Enter 发表

匿名评论

purescale install

添加新评论1 条评论

作者其他文章

相关文章

相关问题

相关资料