|
Problem IT41264
|
Status: Closed |
IN A DPF, MULTI-NODE ENVIRONMENT, A BACKUP TO PIPE WON'T TERMINATE (CTRL+C OR FORCE APP) UNTIL BOTH ENDS OF THE PIPE ARE IN USE
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In a DPF, multi-node environment, a backup to pipe can't be
terminated (ctrl+c or force app) if db2med (EDU responsible for
writing the backup image) hasn't opened the pipe for the write
yet (which requires another process opening it for read).
For example, with a partitioned database named DPFDB, set up
with 3 partitions (0-2), a backup started like this:
mkdir /home/dbinst/db_backups
mkfifo /home/dbinst/db_backups/backup_pipe_mpp_{0..2}
db2 "backup database dpfdb on all dbpartitionnums online to
'/home/dbinst/db_backups/backup_pipe_mpp_ $N' parallelism 1"
cannot be terminated or interrupted (ctrl+c or force app). The
backup won't be terminated until both ends of the pipe are open
and the db2med can start writing to it, which occurs when the
restore is started.
This only affects multi-node environments. Non-DPF or
single-node DPF environments are not affected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Those that perform backups via pipe in a multi-node DPF *
* environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.8.0 or later. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Those that perform backups via pipe in a multi-node DPF *
* environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.5.8.0 or later. *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.06.2022
27.07.2022
08.09.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
