启用 Db2 Data Management Console 以进行复制

如果在设置复制之前部署了 Db2® Data Management Console ，那么必须更改 OpenShift® ConfigMap 中的两个设置以指向复制 REST 服务器，以便您可以使用 DMC 来激活和配置复制。

过程

  1. 运行以下命令以查找已启用复制的数据库的实例标识:
    oc get deployment | grep qrep

    结果应该类似于以下示例。 实例标识是 -qrep之前的数字:

    c-db2wh-1635813356945179-qrep               1/1     1            1           44h
c-db2wh-1635814405003209-qrep               1/1     1            1           44h
  2. 运行以下命令以查找复制 REST 服务名称和 REST 内部端口号:
    oc get svc | grep qrep

    在以下示例中，对于实例标识为 1635814405003209的数据库， REST 服务名称为 c-db2wh-1635814405003209-qrep-rest-svc ， REST 内部端口号为 9444。

    oc get svc | grep qrep
c-db2wh-1635814405003209-qrep-mq-svc         NodePort    172.30.163.150   <none>        1414:31621/TCP,1415:32496/TCP                                                     40h
c-db2wh-1635814405003209-qrep-rest-svc       NodePort    172.30.219.125   <none>        9444:31703/TCP
  3. 通过运行以下命令以编辑方式打开 ConfigMap :
    oc edit cm instance_id
  4. 在 data.profile: 行中，将服务名称和端口号添加到 JSON。 以下示例显示了添加了步骤 2 中的值的 JSON:
    profile: '{"DB_IDENTITY_HASH":"995978196","URL":"jdbc:db2://c-db2wh-1635814405003209-db2u-engn-svc:50001/BLUDB","_PROFILE_INIT_":"true","collectionCred":{"isCollectionCred":"true","password":"jmN#481gc_LLP--3","refreshToken":"","securityMechanism":"9","user":"db2inst1"},"dataServerExternalType":"DASHDBAN","dataServerType":"DB2LUW","databaseName":"BLUDB","databaseVersion":"11.5.0","databaseVersion_VRMF":"11.5.6.0","dbUUID":"08decbef-0e6e-4338-887f-1b4167ecf117","host":"c-db2wh-1635814405003209-db2u-engn-svc","isInstPartitionable":"false","lastUpdatedTimeStamp":"1635909870271","name":"db2wh-1635814405003209","namespace":"","plan":"smp","port":"50001","qrepHost":"c-db2wh-1635814405003209-qrep-rest-svc","qrepNodePort":"31703","qrepPort":"9444","sslCertLocation":"/opt/ibm-datasrvrmgr/Config/cpd-internal-tls/ca.crt","sslConnection":"true","timeZone":"0","timeZoneDiff":"0"}'
  5. 保存 ConfigMap 文件并等待 10 分钟以使更改生效。