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, complete these steps before the upgrade:

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

     oc get db2ucluster -n ${PROJECT_CPD_INST_OPERANDS}
     DB2UCLUSTER_ID=<db2ucluster_cr_name>
     oc edit db2ucluster ${DB2UCLUSTER_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:
         database:
           name: BLUDB
           dbConfig:
             LOGARCHMETH1: "OFF"

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

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

     The output looks like:

     {"level":"info","result":"stdout: Waiting for up to 180 sec until a change is detected in
     the relevant configmaps... change detected\n(*) Applying DB cfg settings\nParameters that require
     updating: EXTBL_LOCATION LOCKLIST LOGARCHMETH1 LOGBUFSZ LOGFILSIZ LOGPRIMARY MAXLOCKS\nParameters
     that support online updating: LOGSECOND\nDB20000I The TERMINATE command completed
     successfully.\n(*) Applying Db2 db cfg parameters for BLUDB\nupdate db cfg for BLUDB using
     AUTO_DEL_REC_OBJ ON DFT_SCHEMAS_DCC NO EXTBL_LOCATION
     /mnt/blumeta0/db2/load;/mnt/blumeta0/home;/mnt/bludata0/scratch;/mnt/external;/mnt/blumeta0/db2/backup
     EXTBL_STRICT_IO NO LOCKLIST 500000 LOGARCHMETH1 OFF LOGBUFSZ 131070 LOGFILSIZ 250000 LOGPRIMARY 10
     LOGSECOND 20 LOG_APPL_INFO NO LOG_DDL_STMTS NO MAXLOCKS 13 NUM_DB_BACKUPS 2 REC_HIS_RETENTN 7\nDB20000I
     The UPDATE DATABASE CONFIGURATION command completed successfully.\nSQL1363W One or more of the parameters
     submitted for immediate modification \nwere not changed dynamically. For these configuration parameters,
     the database \nmust be shutdown and reactivated before the configuration parameter changes
     \nbecome effective.\n\nforce application all\nDB20000I The FORCE APPLICATION command completed
     successfully.\nDB21024I This command is asynchronous and may not be effective
     immediately.\n\n\ndeactivate db BLUDB\nDB20000I The DEACTIVATE DATABASE command completed
     successfully.\n\ndeactivate db BLUDB\nSQL1495W Deactivate database is successful, however,
     there is still a \nconnection to the database.\n\nactivate db BLUDB\nDB20000I The ACTIVATE DATABASE
     command completed successfully.\n\nDatabase was activated successfully\n hostname:
     c-db2oltp-1717040404643209-db2u-0","caller":"[13]:db2.go:346:ApplyCfg()","timestamp":"2024-05-30T16:31:39Z",
     "message":"executed apply Db2 configuration cmd for setting db"}

• 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.