DSNL447I CANNOT DELETE ENTRY value BECAUSE THERE IS AN INDOUBT THREAD TO BE RESOLVED FIRST

Explanation

A -RESET INDOUBT command was issued with LUNAME(value), IPADDR(value), LOCATION(value), or LUWID(value). The value is an LU name, an IP address, a location, or a LUWID (or its token), that identifies a logical unit of work for which Db2 has participant indoubt resolution responsibility, coordinator indoubt resolution responsibility, or both.

System action

Resynchronization responsibility information was not purged. System processing continues normally.

User response

Use the information in this section to determine the correct action to take. Then issue the proper command to perform that action.

The two most probable causes for the problem are that the -RESET INDOUBT command was issued with the wrong parameters, or that an incorrect 'value' was specified. Use the -DISPLAY THREAD(*) TYPE(INDOUBT) LOCATION(*) command to display the indoubt information known to Db2.
  1. If the intent was to purge participant or coordinator indoubt resolution responsibility, then examine the -DISPLAY THREAD output (DSNV401) to determine the location name, or names, for which this responsibility is to be purged. Then use the -RESET INDOUBT LUNAME(luname) command with the FORCE option or the -RESET INDOUBT IPADDR(ip-address) command with the FORCE option to purge this responsibility.
    To determine the luname or IP address and resync port for an upstream coordinator that can be used with the FORCE option, look at the coordinator information after the DSNV406I message in the -DISPLAY THREAD output. There are two tokens associated with the coordinator information that are delimited by a dash (-) for SNA connections, and by a double period (..) for TCP/IP connections.
    • The first token is the partner location name or "<luname>" for an SNA connection, or the IP address for the TCP/IP connection.
    • The second token is the partner LU name for an SNA connection, or the resync port number for a TCP/IP connection.
    To determine the luname or IP address and resync port for downstream participants that can be used with the FORCE option, look at the location names after the V444 message and in the V450 message in the DISPLAY THREAD output (DSNV401). There are two or three tokens associated with the participant location.
    • The first token is the partner location name.
    • The second token is the partner LU name for an SNA connection, or the IP address for a TCP/IP connection. The second token is delimited from the first token by a dash (-).
    • The third token is the partner resync port number. The third token appears only if the second token is an IP address, and is delimited from the second token by a double period (..).

    Remember that the FORCE option causes Db2 to purge all knowledge of indoubt resolution responsibility involving the LUNAME or IPADDR values specified in the command.

    Use caution when using the FORCE parameter to purge participant indoubt information when no errors are precluding automatic resolution. Normally, after the use of the RECOVER INDOUBT command, automatic resolution with the coordinator determines if heuristic damage occurred. This detection is lost if RESET INDOUBT is used before automatic resolution with the coordinator can be achieved.

    Use caution when using the FORCE parameter to purge coordinator indoubt information when no errors are precluding automatic resolution. Once the information is purged, any participant that is indoubt is forced to use a heuristic decision process to resolve the indoubt logical unit of work.

  2. Examine the -DISPLAY THREAD output. If the value specified in the command (and displayed in the DSNL447I message) is incorrect, determine the correct value and reissue the command using the correct value.