Inix企业复制指南.doc

Informix企业复制指南三月 18, 2020目录1.概述12.实施12.1.安装数据库12.2.修改操作系统相关配置12.3.建立对方机器的信任关系12.4.配置Informix数据库组22.5.测试连接对方机器数据库22.6.定义参与企业复制的数据库服务器22.7.定义企业复制32.8.测试企业复制33.注意事项31. 概述通过企业复制（Enterprise Replication）可以达到两台机器上的Informix互为备份，即“双机热备”。以下是两台机器上Informix数据库的配置机器Sco1机器Sco2IP地址172.18.60.5172.18.60.6Informix服务名wlserv1wlserv2数据库zwsrvzwsrv2. 实施2.1. 安装数据库参见：服务器应用程序安装2.2. 修改操作系统相关配置修改两台机器上的/etc/hosts修改后文件中包含以下两条内容来指示两台机器172.18.60.5Sco1Sco1.zwsrv172.18.60.6Sco2Sco2.zwsrv修改/etc/services增加对方informix数据库服务的端口号sqlport7689/tcp如果对方机器数据库服务端口和本机的相同，则无需修改（一般安装两台机器时都使用了7689端口来作为数据库服务端口号）检查两台机器的时间是否一致：l 检查两台机器的所在时区是否一致，可查看系统环境变量 TZ .若不相同，以root登录，用tz 命令修改，然后重新启动机器；cst-8l 检查两台机器时间是否一致，若时间不一致，用root登录，用asktime命令修改，尽量保证两台机器时间相差不要太远。2.3. 建立对方机器的信任关系修改两台机器上的/etc/hosts.equiv，建立来自对方机器用户informix的来访操作l 机器Sco1增加Sco2 informixl 机器Sco2增加Sco1 informix2.4. 配置Informix数据库组修改$INFORMIXDIR/etc/sqlhosts修改后其内容为（两台机器的必须一样，尤其时group组的i值）：g_5group-i=105wlserv1ontlitcpSco1sqlexecg=g_5g_6group-i=106wlserv2ontlitcpSco2sqlexecg=g_6其中：i代表数据库服务器组的编码，可随意定义，但是必须保持唯一性2.5. 测试连接对方机器数据库以informix用户登录，分别重启Sco1和Sco2上的informix数据库。然后，执行“dbaccess”命令，当弹出informix菜单界面，选择“Connect”菜单项，然后检查是否存在对方服务器的数据库。如果存在，请选择，这时界面上会显示输入用户名及口令，连续按回车；此时，如果能够连接并能打开数据库，说明本机可以访问对方的数据库了，退出“dbaccess”。2.6. 定义参与企业复制的数据库服务器用informix用户登录服务器Sco1（所有有关复制的定义工作，只在其中一台服务器上操作即可，所以此处在Sco2上操作也可以）。Sco1 cdr define server -init g_5Sco1 cdr define server -connect g_6 -init -sync g_5 g_6这样就定义了参与企业复制的两个数据库服务器，可以如下查看信息：Sco1 cdr list serverSERVER ID STATE STATUS CONNECTION CHANGED-g_5 105 Activeg_6 106 Active Connected Nov 3 18:09:40 2008显示两个服务器都是处于激活状态，操作顺利。此时两台机器的Informix数据库中的自动建立了数据库syscdr此数据库包含了双机企业复制时的参数和log日志发送队列，如果有一台机器被关机，在线机器数据库就会把log日志暂存在syscdr库中的发送队列中，等待对方机器在线，然后把log日志发送到对方机器，完成企业复制。2.7. 定义企业复制定义要进行复制的数据库表的复制内容Sco1 cdr define repl -C ignore repl_zwsrv_006 zwsrv g_5:informix.TUNUSED select * from TUNUSED zwsrv g_6:informix.TUNUSED select * from TUNUSED(格式为”dbnamedb_group:user.table”)Sco1 cdr start repl -connect g_6 repl_zwsrv_006 (定义企业复制名为repl_zwsrv_006)2.8. 测试企业复制在Sco2机器上进入dbaccess，选择zwsrv数据库，修改tunused表update tunused set c_org_code=00000;随后在Sco1机器上进入dbaccess，选择zwsrv数据库，查看tunused相应的内容select * from tunused;会发现c_org_code已经被修改为00000了，测试通过！已经实现两个数据库服务器之间的数据异步双向复制。3. 注意事项l 一旦将某一数据表定义为复制状态，则不能对它做以下操作；DROP TABLERENAME TABLEALTER FRAGMENTl 一旦将某一数据表定义为复制状态，log接收队列大小可以被修改，但需要重新启动数据库服务才能起效；l 一旦将某一数据表定义为复制状态,，log发送队列大小则不可以被改变。Example of a Replication ScriptThe following text file is the result of saving a replication script:Scripting View Archive* Definition of Servers *ObjectType: ServerName: g_sharky_73ServerType: ROOT_SERVERSync/ParentServer: -ATSDirectory: /tmpRISDirectory: /tmpSendQueueDBSpace: -ReceiveQueueDBSpace: -IdleTimeOut(mins): 0ObjectType: ServerName: g_cathl_73ServerType: ROOT_SERVERSync/ParentServer: -ATSDirectory: /tmpRISDirectory: /tmpSendQueueDBSpace: -ReceiveQueueDBSpace: -IdleTimeOut(mins): 0ObjectType: ServerName: g_od_us_tli73ServerType: NONROOT_SERVERSync/ParentServer: g_judith_73ATSDirectory: /tmpRISDirectory: /tmpSendQueueDBSpace: -ReceiveQueueDBSpace: -IdleTimeOut(mins): 0ObjectType: ServerName: g_judith_73ServerType: ROOT_SERVERSync/ParentServer: -ATSDirectory: /tmpRISDirectory: /tmpSendQueueDBSpace: -ReceiveQueueDBSpace: -IdleTimeOut(mins): 0* Definition of Groups (Replicates & Participants) *ObjectType: GroupName: A_groupFrequencyType: FREQ_TIME_CHARHour: 7Minute: 36Day: 76Month: 0Sequential: TRUEObjectType: ReplicateName: r_stateConflictResolutionScope: TRANSACTIONConflictResolutionType: IGNOREStoredProcedureName: -FrequencyType: FREQ_IMMED_CHARHour: 0Minute: 0Day: 0Month: 0ATSSpooling: FALSERISSpooling: FALSECanonicalMessageFormat: FALSEFireTriggers: FALSEGroupName: A_groupObjectType: ParticipantName: g_cathl_73DataBase: odin7Owner: informixTable: statePrimary/Target: PrimarySelectStatement: Select * from informix.stateReplicateName: r_stateObjectType: ParticipantName: g_judith_73DataBase: smoke7Owner: informixTable: statePrimary/Target: PrimarySelectStatement: Select * from informix.stateReplicateName: r_stateObjectType: ReplicateName: r_call_typeConflictResolutionScope: TRANSACTIONConflictResolutionType: IGNOREStoredProcedureName: -FrequencyType: FREQ_IMMED_CHARHour: 0Minute: 0Day: 0Month: 0ATSSpooling: FALSERISSpooling: FALSECanonicalMessageFormat: FALSEFireTriggers: FALSEGroupName: A_groupObjectType: ParticipantName: g_cathl_73DataBase: odin7Owner: informixTable: call_typePrimary/Target: PrimarySelectStatement: Select * from informix.call_typeReplicateName: r_call_typeObjectType: ParticipantName: g_judith_73DataBase: smoke7Owner: informixTable: call_typePrimary/Target: PrimarySelectStatement: Select * from informix.call_typeReplicateName: r_call_type* Definition of Replicates (Participants) *ObjectType: ReplicateName: r_ordersConflictResolutionScope: TRANSACTIONConflictResolutionType: TIMESTAMPStoredProcedureName: -FrequencyType: FREQ_TIME_CHARHour: 0Minute: 25Day: 76Month: 0ATSSpooling: TRUERISSpooling: TRUECanonicalMessageFormat: FALSEFireTriggers: FALSEGroupName: -ObjectType: ParticipantName: g_sharky_73DataBase: shark7Owner: informixTable: ordersPrimary/Target: PrimarySelectStatement: Select * from informix.ordersReplicateName: r_ordersObjectType: ParticipantName: g_judith_73DataBase: smoke7Owner: informixTable: ordersPrimary/Target: PrimarySelectStatement: Select * from informix.ordersReplicateName: r_ordersObjectType: ReplicateName: r_custConflictResolutionScope: ROWBYROWConflictResolutionType: IGNOREStoredProcedureName: -FrequencyType: FREQ_IMMED_CHARHour: 0Minute: 0Day: 0Month: 0ATSSpooling: T