Examples of redistribute event log file entries

Examples of common redistribute event log files entries and descriptions of them provide a useful reference that can be consulted when troubleshooting errors or interruptions that occur during data redistribution.

There are two event log files created each time you redistribute a database partition group. The file named database-name.database-partition-group-name.timestamp provides a brief summary of the event. For example, SAMPLE.IBMDEFAULTGROUP.2012012622083174 contains:

		Data Redistribution Utility :
		___________________________

The following options have been specified :
Database partition group name : IBMDEFAULTGROUP
Data Redistribution option : U
Redistribute database partition group : uniformly
No. of partitions to be added : 0
List of partitions to be added :
No. of partitions to be dropped : 1
List of partitions to be dropped :
2
The execution of the Data Redistribution operation on :

 Begun at  Ended at  Table (poolID;objectID)
 ________  ________  _______________________
 22.08.32            "DB2INST1"."CL_SCHED" (2;4)
           22.08.33  "DB2INST1"."CL_SCHED" (2;4)
 22.08.33            "DB2INST1"."DEPARTMENT" (2;5)
           22.08.35  "DB2INST1"."DEPARTMENT" (2;5)
 22.08.35            "DB2INST1"."EMPLOYEE" (2;6)
           22.08.36  "DB2INST1"."EMPLOYEE" (2;6)
 ...
 22.09.13            "DB2INST1"."PRODUCTSUPPLIER" (4;10)
           22.09.15  "DB2INST1"."PRODUCTSUPPLIER" (4;10)

--All tables have been successfully redistributed.--

The file named database-name.database-partition-group-name.timestamp.log provides more detailed log entries. The following examples illustrate some common log file entries. Although each field value in the redistribute log file entries is not defined, the examples illustrate the main fields and most common or most important field values.

Example 1: First event log entry dumped during a redistribute operation

2012-01-26-22.08.32.607340-300 I1850E893             LEVEL: Event
PID     : 27700                TID : 46912984049984  PROC : db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : SAMPLE
APPHDL  : 0-74                 APPID: *N0.db2inst1...
AUTHID  : DB2INST1             HOSTNAME: ...
EDUID   : 65                   EDUNAME: db2agent (SAMPLE) 0
FUNCTION: Db2, relation data serv, sqlrdrin, probe:3852
CHANGE  : DB PART MAP ID : IBMDEFAULTGROUP : FROM "1" : TO "3" : success
IMPACT  : None
DATA #1 : String, 24 bytes
HexDump Old Map Entries:
DATA #2 : Dumped object of size 65536 bytes at offset 0, 61 bytes
/home/db2inst1/sqllib/redist/27700.65.000.dump.bin
DATA #3 : String, 24 bytes
HexDump New Map Entries:
DATA #4 : Dumped object of size 65536 bytes at offset 65672, 61 bytes
/home/db2inst1/sqllib/redist/27700.65.000.dump.bin

The first event log entry dumped during a redistribute operation provides information about the distribution map files with which the utility will be working. In this case, the old distribution map for partition group IBMDEFAULTGROUP has an id of 1 and the new distribution map has an id of 3. A hexdump of each distribution map file is made to the redist directory in the instance path, and the names of the dump files are included in the entry. In this example, the file named 27700.65.000.dump.bin contains both distribution maps.

Example 2: Event log associated with the start of the redistribute operation

2012-01-26-22.08.32.625956-300 I2744E774             LEVEL: Event
PID     : 27700                TID : 46912984049984  PROC : db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : SAMPLE
APPHDL  : 0-74                 APPID: *N0.db2inst1...
AUTHID  : DB2INST1             HOSTNAME: ...
EDUID   : 65                   EDUNAME: db2agent (SAMPLE) 0
FUNCTION: Db2, relation data serv, sqlrdrInitLogfileInfo, probe:1802
START   : REDIST DB PART GROUP : IBMDEFAULTGROUP : success
IMPACT  : None
DATA #1 : String, 28 bytes
Partitioning Option: UNIFORM
DATA #2 : String, 23 bytes
Statistics: USE PROFILE
DATA #3 : String, 22 bytes
Indexing Mode: REBUILD
DATA #4 : String, 17 bytes
 PRECHECK MODE: Y
DATA #5 : String, 16 bytes
 QUIESCE MODE: Y

This entry indicates that the start of the redistribute operation has completed successfully and that redistribution of tables is about to begin. The partitioning option, statistics option, indexing mode, precheck mode, and quiesce mode to be used for the redistribution operation are also shown.

In this example, the partitioning option is UNIFORM, which indicates that data will be redistributed uniformly. Other possible values for this option include TARGETMAP, CONTINUE and ABORT.

The statistics option is USE PROFILE, which is the default statistics collection mode and means that if the table has a statistics profile, then statistics will be collected according to that profile. Otherwise, statistics will not be collected. If the value of this option is NONE, this indicates that the STATISTICS NONE option was specified, which means that no statistics are to be collected for the table, regardless of whether the table has a statistics profile defined or not.

In this example, the indexing mode is REBUILD, which is the default indexing mode and means that indexes on each table will be rebuilt during data redistribution. If the value of this option is DEFERRED, it means that the user specified the INDEXING MODE DEFERRED option, which results in indexes being marked invalid during redistribution. Such indexes must be rebuilt after data redistribution is complete.

In this example, the precheck mode is Y, which is the default precheck mode for data redistributions that are NOT ROLLFORWARD RECOVERABLE. This mode indicates that the redistribution operation begins only if the verification completes successfully.

In this example, the quiesce mode is Y, which is the default quiesce mode for data redistributions that are NOT ROLLFORWARD RECOVERABLE. This mode indicates that the redistribution operation forces all users off the database and puts it into a quiesced mode.

Example 3: Event log associated with start of redistributing a table

2012-01-26-22.08.32.843840-300 I4072E541             LEVEL: Event
PID     : 27700                TID : 46912874998080  PROC : db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : SAMPLE
APPHDL  : 0-113                APPID: *N0.DB2....
AUTHID  : DB2INST1             HOSTNAME: ...
EDUID   : 181                  EDUNAME: db2agent (SAMPLE) 0
FUNCTION: Db2, database utilities - Redistribute, sqlurRedistributeTableByID
, probe:8743
START   : REDIST TABLE : "DB2INST1"."CL_SCHED" : success
IMPACT  : None

This entry indicates that the start of redistributing table "DB2INST1"."CL_SCHED" was successful.

Example 4: Event log associated with successful completion of redistribution for a table

2012-01-26-22.08.33.659785-300 I4614E541             LEVEL: Event
PID     : 27700                TID : 46912874998080  PROC : db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : SAMPLE
APPHDL  : 0-113                APPID: *N0.DB2....
AUTHID  : DB2INST1             HOSTNAME: ...
EDUID   : 181                  EDUNAME: db2agent (SAMPLE) 0
FUNCTION: Db2, database utilities - Redistribute, sqlurRedistributeTableByID
, probe:9350
STOP    : REDIST TABLE : "DB2INST1"."CL_SCHED" : success
IMPACT  : None

This entry indicates that table "DB2INST1"."CL_SCHED" has been successfully redistributed. If an error had occurred during processing of this table, this entry would indicate failure.

Example 5: Event log associated with successful completion of redistribution of a database partition group

2012-01-26-22.09.16.746325-300 I28994E515            LEVEL: Event
PID     : 27700                TID : 46912984049984  PROC : db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   : SAMPLE
APPHDL  : 0-74                 APPID: *N0.db2inst1....
AUTHID  : DB2INST1             HOSTNAME: ...
EDUID   : 65                   EDUNAME: db2agent (SAMPLE) 0
FUNCTION: Db2, relation data serv, sqlrdrdt, probe:1308
STOP    : REDIST DB PART GROUP : IBMDEFAULTGROUP : success
IMPACT  : None

This entry indicates that redistribution of database partition group IBMDEFAULTGROUP completed successfully. If the operation had not completed successfully, this entry would indicate failure.

These example entries can be a helpful reference when you consult your log files to resolve errors that occur during data redistribution or to verify that data redistribution complete successfully.