Changes to the target database

• DIAGSIZE 500
• START_STOP_TIME 5
• MAX_QUERYDEGREE 6

• LOGARCHMETH1 is set to OFF. This disables archive logging for a Db2 or Db2 Warehouse instance so that the database runs in circular logging mode. This can improve the synchronization performance, but in some cases you might have to re-enable archive logging. Consider:
  • Your target database also contains tables that are not managed by Data Gate. You can only recover these by using the backup and archive logs.

    In contrast, Data Gate tables can be recovered from Db2 for z/OS by simply reloading these.

  • Other replication tools might use the target database as a source, and replicate changes to a new target as in a replication chain. Such tools require that archive logging is enabled.
  Tip: To avoid a BACKUP PENDING state of the Db2 target database after an upgrade, adjust the target Db2 configuration in the Db2uCluster or Db2uInstance custom resource (CR) by completing these steps before the upgrade:

  1. Determine the Db2 CR name of your target database instance, either Db2ucluster or Db2uInstance, and edit it. To this end, replace ${PROJECT_CPD_INST_OPERANDS} with your project name in the following sample command. Then run the command.

     #(current): Db2uInstance
     oc get db2uinstance -n ${PROJECT_CPD_INST_OPERANDS}
     DB2UINSTANCE_ID=<db2uinstance_cr_name>
     oc edit db2uinstance ${DB2UINSTANCE_ID} -n ${PROJECT_CPD_INST_OPERANDS}

  2. The database configuration (YAML file) is now in edit mode. Database configuration parameters are added under spec.environment.databases.dbConfig. Navigate to this section and add or change the LOGARCHMETH1 value as shown in the following example:

     spec:
       environment:
         databases:
           - name: BLUDB
             dbConfig:
               LOGARCHMETH1: "OFF"

  3. Save and exit the YAML file. Then exit the container.
  4. The dbConfig changes of the Db2 CR, either Db2uCluster or Db2uInstance, will be detected and applied automatically. You can monitor pod logs to verify that the configurations are applied successfully. Run the command:

     oc logs c-${DB2UINSTANCE_ID}-db2u-0 -n ${PROJECT_CPD_INST_OPERANDS}

  Important: The Db2uCluster custom resource is deprecated and will be removed in a future release. The following example illustrates the configuration flow for the Db2uInstance CR. For further information about changing Db2 target database configurations, see Deploying Db2 using a custom resource for Db2 and Changing Db2 Warehouse configuration settings for Db2 Warehouse.
• Other changes are specific to the type of the target database that you use:

  Db2

  Db2 Warehouse

  PAGE_AGE_TRGT_MCR 30 AUTO_SAMPLING ON AUTO_CG_STATS ON AUTHN_CACHE_USERS 20 AUTHN_CACHE_DURATION 60

  MAXLOCKS 10 PCKCACHESZ 65536 LOGARCHMETH2 OFF SECTION_ACTUALS NONE AUTO_MAINT ON AUTO_TBL_MAINT ON AUTO_REORG ON AUTO_STMT_STATS ON AUTO_RUNSTATS ON EXTBL_LOCATION / AUTO_SAMPLING ON MON_DEADLOCK HIST_AND_VALUES MON_LOCKTIMEOUT HIST_AND_VALUES MON_LOCKWAIT NONE AUTO_CG_STATS ON AUTO_DEL_REC_OBJ ON TRACKMOD YES MON_LCK_MSG_LVL 3 WLM_AGENT_LOAD_TRGT 24 AUTO_STATS_VIEWS ON DFT_EXTENT_SZ 4 AUTHN_CACHE_USERS 20 AUTHN_CACHE_DURATION 60

CALL SYSINSTALLOBJECTS('ANACC','C','','')

/mnt/blumeta0/home/db2inst1/dg_config_done.XXX

Where XXX is the instance ID of the target database.