When dropping a table using Db2Admin, it should be possible to ensure that any related LOB tablespaces will be dropped as well. This could be done via a new parameter.
An explicitly defined LOB tablespaces does not get dropped by Db2 when the base tables is dropped. Neither does Db2Admin drop it when using parameter KEEPTARGET=’Y’. We always use this parameter for security reasons.
This gives us two challenges:
We opened PMR 61544,040,678 against Db2 for this problem, and PMR 61771,040,678 against Db2Admin.
|Priority Justification||Today we have to have extra administrative routines to check for orphaned LOB tablespaces.|
|Client Name||JN Data A/S|