DSNL034E DDF CANNOT BE STARTED BECAUSE OF BSDS INCONSISTENCIES, ORIGINAL LUNAME=original-luname, BSDS LUNAME=bsds-luname, ORIGINAL LOCATION=original-location, BSDS LOCATION=bsds-location

Explanation

The LUNAME or the LOCATION name stored in the bootstrap data set (BSDS) was changed after the distributed data facility (DDF) was last started, but DDF still has resynchronization responsibility with one or more partner logical units using the old LUNAME and LOCATION name. Both the original and current BSDS values of LUNAME and LOCATION name are displayed.

original-luname
The LUNAME required for resynchronization.
bsds-luname
The LUNAME currently stored in the BSDS.
original-location
The LOCATION name required for resynchronization.
bsds-location
The LOCATION name currently stored in the BSDS.

System action

DDF cannot be started until the inconsistencies are corrected.

Operator response

Inform the database administrator.

Database administrator response

Take the appropriate action, depending on whether there is a requirement to change the LUNAME or LOCATION name in the BSDS:

Name changed in error
Use the change log inventory (DSNJU003) utility to change the LUNAME, LOCATION name , or both back to the correct value. Then issue the START DDF command.
Name change required
Remove all of the resynchronization responsibility that Db2 had using the old names. You can purge this information, allow automatic resynchronization to take place, or use a combination of both.

You can purge resynchronization information by using the RESET INDOUBT command with the FORCE option. You can purge all information regardless of partner name (LOCATION (*)), or you can selectively purge by specifying a location name. DDF does not have to be started to use this command. You can use the DISPLAY THREAD command to generate a report of indoubt threads. This report indicates all resynchronization responsibility known by Db2.

If you do not purge the resynchronization information, or choose to selectively purge, and you want automatic resynchronization to occur before changing the names, you must first use the change log inventory (DSNJU003) utility to change the LUNAME, the LOCATION name, or both back to the correct value. Then issue the START DDF. At this point, automatic resynchronization begins. You can monitor the progress by periodically using the DISPLAY THREAD command for TYPE (INDOUBT) threads. Resynchronization does not complete until all needed communications paths are available and all needed partner logical units are available. If you cannot wait for availability, use the RESET INDOUBT command with the FORCE option to purge information associated with unavailable partners.