Flashes (Alerts)
Abstract
When you use the automated method to delete unnamed snapshots, you must apply interim fix JR58096 to the following releases: IBM Business Process Manager (BPM) V8.5,0.2, V8.5.5.0, V8.5.6.0 cumulative fix (CF) 2, and all the CFs on V8.5.7.
You can use the the BPMDeleteSnapshot and BPMSnapshotCleanup commands on IBM BPM V8.5.6 and V8.5.7. If you use IBM BPM V7.5.1.2, V8.0.1.2, V8.0.1.3 , V8.5,0.0, V8.5.0.1, or V8.5.5.0, you must apply all the interim fixes listed in this document before you can use these commands.
Content
Using the automated method to delete unnamed snapshots
To get the interim fix for the automated method, see JR58096: ARCHIVED SNAPSHOT IS CORRUPTED WHEN THE DELETE UNNAME SNAPSHOT AUTOMATION RUNS.
Using the BPMDeleteSnapshot and BPMSnapshotCleanup commands
The following information pertains to the BPMDeleteSnapshot and BPMSnapshotCleanup commands.
The snapshot deletion commands do not delete all of the related artifacts, which potentially leads to issues when you subsequently install or import snapshots. The fixes address the completeness of the deletion and repair previous deletions as needed.
Important:
- Before you apply these interim fixes, you see a Delete button after you click the Archived filter in Process Center. Do not click the Delete button or your databases might become corrupted.
- Before you apply these interim fixes, if you run the BPMSnapshotCleanup command on Process Center do not change the default value of the ignoreDependency optional parameter.
- After the interim fixes are applied, ensure that you back up your database before you run these commands.
The tables within the tabs show the date or projected date when the interim fix will be available for the latest fix packs. These tables will be updated as interim fixes become available.
Disclaimer: The availability dates that are projected in the following table are subject to change.
Tab navigation
| APAR | 7.5.1.2 |
| JR48877 Symptom A participant group (called “team” in V8.5) is not visible in the Process Admin Console of Process Server under Role Bindings when a snapshot is installed after you use the BPMDeleteSnapshot command. Prevention Interim fix JR48877 Repairs Interim fix JR49635 | Express: 7.5.1.2-WS-BPM-IFJR48877 Standard: 7.5.1.2-WS-BPM-IFJR48877 Advanced: 7.5.1.2-WS-BPM-IFJR48877 |
| JR49374 Symptom You receive the following error after you run the BPMSnapshotCleanup or BPMDeleteSnapshot command: CWLLG1414E - An exception occurred while getting user attributes Prevention Interim fix JR49374 Repairs Interim fix JR49374 or modify each user attribute definition in your process application and save it | Express: 7.5.1.2-WS-BPM-IFJR49374 Standard: 7.5.1.2-WS-BPM-IFJR49374 Advanced: 7.5.1.2-WS-BPM-IFJR49374 |
| JR49606 Symptom A participant group (called “team” in V8.5) is not visible in the Process Admin Console of IBM Process Center under Role Bindings when a snapshot is installed after you use the BPMSnapshotCleanup command. Prevention Interim fix JR49606 Repairs Interim fix JR49928 | Express: 7.5.1.2-WS-BPM-IFJR49606 Standard: 7.5.1.2-WS-BPM-IFJR49606 Advanced: 7.5.1.2-WS-BPM-IFJR49606 |
| JR49635 This repair-only interim fix applies to the issue that is addressed in JR48877. JR49635 looks for and repairs issues when importing a snapshot. Although JR48877 repairs most of the issues, you still need interim fix JR49635 if there are more than 1000 participant groups (called “teams” in V8.5). JR49635 repairs the damage done by the issue that is fixed by JR48877 in the event that you encounter the issue before you apply JR48877. | Express: 7.5.1.2-WS-BPM-IFJR49635 Standard: 7.5.1.2-WS-BPM-IFJR49635 Advanced: 7.5.1.2-WS-BPM-IFJR49635 |
| JR49848 Symptom After you run the BPMSnapshotCleanup command, you can no longer save artifacts that have advanced content in Process Designer in a process application or toolkit from IBM Integration Designer Prevention Interim fix JR49848 Repairs Interim fix JR49848 or edit the LSW_SCA_CONNECTOR table of the BPMDB database and put the outOfSync value into the LAST_SYNCHRONIZED column for the Advanced Integration Service that is affected | Express: Not applicable Standard: Not applicable Advanced: 7.5.1.2-WS-BPM-IFJR49848 |
| JR49928 This repair-only interim fix applies to the issue that is addressed in JR49606. JR49928 looks for and repairs issues when the server starts. You do not require interim fix JR49928 if the interim fixes JR48877 and JR49606 are applied before snapshots are deleted. | Express: 7.5.1.2-WS-BPM-IFJR49928 Standard: 7.5.1.2-WS-BPM-IFJR49928 Advanced: 7.5.1.2-WS-BPM-IFJR49928 |
| JR50444 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see the DATAINTEGRITYVIOLATIONEXCEPTION. This fix checks whether there are exposed items before deleting the groups, preventing you from deleting those groups. | Express: 7.5.1.2-WS-BPM-IFJR50444 Standard: 7.5.1.2-WS-BPM-IFJR50444 Advanced: 7.5.1.2-WS-BPM-IFJR50444 |
| JR50460 An exception occurs while history information for a process app or toolkit is being loaded when that history information contains references to deleted snapshots. | Express: 7.5.1.2-WS-BPM-IFJR50460 Standard: 7.5.1.2-WS-BPM-IFJR50460 Advanced: 7.5.1.2-WS-BPM-IFJR50460 |
| JR50667 Deleting a snapshot destroys most smart folders. Smart folders are used for the entire project's track or branch. It is not expected that the smart folders will be deleted when snapshots are deleted. | Express: 7.5.1.2-WS-BPM-IFJR50667 Standard: 7.5.1.2-WS-BPM-IFJR50667 Advanced: 7.5.1.2-WS-BPM-IFJR50667 |
| JR50671 When snapshots are deleted, the corresponding LSW installation table entries are not deleted. | Express: 7.5.1.2-WS-BPM-IFJR50671 Standard: 7.5.1.2-WS-BPM-IFJR50671 Advanced: 7.5.1.2-WS-BPM-IFJR50671 |
| JR50718 The BPMDeleteSnapshot command proceeds even though there are running instances of stand-alone human services. | Express: 7.5.1.2-WS-BPM-IFJR50718 Standard: 7.5.1.2-WS-BPM-IFJR50718 Advanced: 7.5.1.2-WS-BPM-IFJR50718 |
| JR50720 The BPMDeleteSnapshot command proceeds even though there business process definition (BPD) instances in another snapshot that point to tasks from the snapshot that is being deleted. | Express: 7.5.1.2-WS-BPM-IFJR50720 Standard: 7.5.1.2-WS-BPM-IFJR50720 Advanced: 7.5.1.2-WS-BPM-IFJR50720 |
| JR50721 The BPMSnapshotCleanup command proceeds even though there are running instances of stand-alone human services. | Express: 7.5.1.2-WS-BPM-IFJR50721 Standard: 7.5.1.2-WS-BPM-IFJR50721 Advanced: 7.5.1.2-WS-BPM-IFJR50721 |
| JR50742 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see a DATAINTEGRITYVIOLATION exception. | Express: 7.5.1.2-WS-BPM-IFJR50742 Standard: 7.5.1.2-WS-BPM-IFJR50742 Advanced: 7.5.1.2-WS-BPM-IFJR50742 |
| JR52327 When you run the BPMSnapshotCleanup command with -ignoreDependency = true, toolkits that have other toolkits and process apps depending on them can be deleted without warning, leading to other problems. | Express: 7.5.1.2-WS-BPM-IFJR52327 Standard: 7.5.1.2-WS-BPM-IFJR52327 Advanced: 7.5.1.2-WS-BPM-IFJR52327 |
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
To use the BPMDeleteSnapshot and BPMSnapshotCleanup commands, upgrade to IBM BPM V8.0.1 Fix Pack 3.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
To use the BPMDeleteSnapshot and BPMSnapshotCleanup commands, upgrade to IBM BPM V8.0.1 Fix Pack 3.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
All the following individual interim fixes for the BPMDeleteSnapshot and BPMSnapshotCleanup commands are available for IBM Business Process Manager V8.0.1.2. You must download and install all these interim fixes and their dependencies before you can use these commands on IBM Business Process Manager V8.0.1.2. However, instead of installing these fixes individually, consider installing them as a cumulative fix instead for convenience.
Important: The IBM BPM V8.0.1.2 cumulative fix contains all the interim fixes in the table except JR52327. Links to information about interim fix JR52327 and the fix itself are in the following table.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
Important: The IBM BPM V8.0.1.2 cumulative fix contains all the interim fixes in the table except JR52327. Links to information about interim fix JR52327 and the fix itself are in the following table.
| APAR | 8.0.1.2 |
| JR48877 Symptom A participant group (called “team” in V8.5) is not visible in the Process Admin Console of Process Server under Role Bindings when a snapshot is installed after you use the BPMDeleteSnapshot command. Prevention Interim fix JR48877 Repairs Interim fix JR49635 | Express: 8.0.1.2-WS-BPM-IFJR48877 Standard: 8.0.1.2-WS-BPM-IFJR48877 Advanced: 8.0.1.2-WS-BPM-IFJR48877 |
| JR49267 Symptom A NullPointerException error occurs when you delete the last snapshot from Process Server. Prevention Interim fix JR49267 or do not try to delete the last snapshots. Repairs Interim fix JR49267 | Express: 8.0.1.2-WS-BPM-IFJR49267 Standard: 8.0.1.2-WS-BPM-IFJR49267 Advanced: 8.0.1.2-WS-BPM-IFJR49267 |
| JR49374 Symptom You receive the following error after you run the BPMSnapshotCleanup or BPMDeleteSnapshot command: CWLLG1414E - An exception occurred while getting user attributes Prevention Interim fix JR49374 Repairs Interim fix JR49374 or modify each user attribute definition in your process application and save it | Express: 8.0.1.2-WS-BPM-IFJR49374 Standard: 8.0.1.2-WS-BPM-IFJR49374 Advanced: 8.0.1.2-WS-BPM-IFJR49374 |
| JR49606 Symptom A participant group (called “team” in V8.5) is not visible in the Process Admin Console of IBM Process Center under Role Bindings when a snapshot is installed after you use the BPMSnapshotCleanup command. Prevention Interim fix JR49606 Repairs Interim fix JR49928 | Express: 8.0.1.2-WS-BPM-IFJR49606 Standard: 8.0.1.2-WS-BPM-IFJR49606 Advanced: 8.0.1.2-WS-BPM-IFJR49606 |
| JR49635 This repair-only interim fix applies to the issue that is addressed in JR48877. JR49635 looks for and repairs issues when importing a snapshot. Although JR48877 repairs most of the issues, you still need interim fix JR49635 if there are more than 1000 participant groups (called “teams” in V8.5). JR49635 repairs the damage done by the issue that is fixed by JR48877 in the event that you encounter the issue before you apply JR48877. | Express: 8.0.1.2-WS-BPM-IFJR49635 Standard: 8.0.1.2-WS-BPM-IFJR49635 Advanced: 8.0.1.2-WS-BPM-IFJR49635 |
| JR49848 Symptom After you run the BPMSnapshotCleanup command, you can no longer save artifacts that have advanced content in Process Designer in a process application or toolkit from Integration Designer Prevention Interim fix JR49848 Repairs Interim fix JR49848 or edit the LSW_SCA_CONNECTOR table of the BPMDB database and put the outOfSync value into the LAST_SYNCHRONIZED column for the Advanced Integration service that is affected | Express: Not applicable Standard: Not applicable Advanced: 8.0.1.2-WS-BPM-IFJR49848 |
| JR49928 This repair-only interim fix applies to the issue that is addressed in JR49606. JR49928 looks for and repairs issues when the server starts. You do not require interim fix JR49928 if the interim fixes JR48877 and JR49606 are applied before snapshots are deleted. | Express: 8.0.1.2-WS-BPM-IFJR49928 Standard: 8.0.1.2-WS-BPM-IFJR49928 Advanced: 8.0.1.2-WS-BPM-IFJR49928 |
| JR50003 In a clustered IBM Business Process Manager (BPM) environment, caches are reset multiple times in all cluster members when process applications that have many groups are deployed. As a result, IBM BPM performance is significantly affected. | Express: 8.0.1.2-WS-BPM-IFJR50003. Standard: 8.0.1.2-WS-BPM-IFJR50003 Advanced: 8.0.1.2-WS-BPM-IFJR50003 |
| JR50667 Deleting a snapshot destroys most smart folders. Smart folders are used for the entire project's track or branch. It is not expected that the smart folders will be deleted when snapshots are deleted. | Express: 8.0.1.2-WS-BPM-IFJR50667. Standard: 8.0.1.2-WS-BPM-IFJR50667 Advanced: 8.0.1.2-WS-BPM-IFJR50667 |
| JR50671 Removing snapshots does not and must cascade delete with snapshot because this could cause problems if a snapshot is deleted and then added back. | Included in JR50667 |
| JR50718 The BPMDeleteSnapshot command proceeds even though there are running instances of stand-alone human services. | Express: 8.0.1.2-WS-BPM-IFJR50718. Standard: 8.0.1.2-WS-BPM-IFJR50718 Advanced: 8.0.1.2-WS-BPM-IFJR50718 |
| JR50720 The BPMDeleteSnapshot command proceeds even though there business process definition (BPD) instances in another snapshot that point to tasks from the snapshot that is being deleted. | Express: 8.0.1.2-WS-BPM-IFJR50720. Standard: 8.0.1.2-WS-BPM-IFJR50720 Advanced: 8.0.1.2-WS-BPM-IFJR50720 |
| JR50721 The BPMSnapshotCleanup command proceeds even though there are running instances of stand-alone human services. | Express: 8.0.1.2-WS-BPM-IFJR50721. Standard: 8.0.1.2-WS-BPM-IFJR50721 Advanced: 8.0.1.2-WS-BPM-IFJR50721 |
| JR50742 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see a DATAINTEGRITYVIOLATION exception. | Express: 8.0.1.2-WS-BPM-IFJR50742. Standard: 8.0.1.2-WS-BPM-IFJR50742 Advanced: 8.0.1.2-WS-BPM-IFJR50742 |
| JR52327 When you run the BPMSnapshotCleanup command with -ignoreDependency = true, toolkits that have other toolkits and process apps depending on them can be deleted without warning, leading to other problems. | Express: 8.0.1.2-WS-BPM-IFJR52327. Standard: 8.0.1.2-WS-BPM-IFJR52327 Advanced: 8.0.1.2-WS-BPM-IFJR52327 |
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
| APAR | 8.0.1.3 |
| JR52327 When you run the BPMSnapshotCleanup command with -ignoreDependency = true, toolkits that have other toolkits and process apps depending on them can be deleted without warning, leading to other problems. | Express: 8.0.1.3-WS-BPM-IFJR52327. Standard: 8.0.1.3-WS-BPM-IFJR52327 Advanced: 8.0.1.3-WS-BPM-IFJR52327 |
| JR54063 When you try to clean up snapshots on IBM Process Center or delete a snapshot on IBM Process Server, the operation fails and you receive a database exception about the violation of the BPM_SHARED_OBJECT_FK constraint. | Express: 8.0.1.3-WS-BPM-IFJR54063 Standard: 8.0.1.3-WS-BPM-IFJR54063 Advanced: 8.0.1.3-WS-BPM-IFJR54063 |
| JR56448 You receive an error when running the bpmsnapshotcleanup command because of a constraint violation in the lsw_usr_grp_xref table" | Express: 8.0.1.3-WS-BPM-IFJR56448 Standard: 8.0.1.3-WS-BPM-IFJR56448 Advanced: 8.0.1.3-WS-BPM-IFJR56448 |
All the following individual interim fixes for the BPMDeleteSnapshot and BPMSnapshotCleanup commands are available for IBM Business Process Manager V8.5.0.0. You must download and install all these interim fixes and their dependencies before you can use these commands on IBM Business Process Manager V8.5.0.0.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
| APAR | 8.5.0.0 |
| JR46969 A NullPointerException error occurs when you delete snapshots that have scheduled undercover agents (UCAs) from IBM Process Server. Prevention Interim fix JR46969 Repairs Interim fix JR47249 | Express: 8.5.0.0-WS-BPM-IFJR46969 Standard: 8.5.0.0-WS-BPM-IFJR46969 Advanced: 8.5.0.0-WS-BPM-IFJR46969 |
| JR47249 This repair-only interim fix cleans up the UCAs that are orphaned by the issue that is addressed in JR46969. | Express: 8.5.0.0-WS-BPM-IFJR47249 Standard: 8.5.0.0-WS-BPM-IFJR47249 Advanced: 8.5.0.0-WS-BPM-IFJR47249 |
| JR48877 Symptom A participant group (called “team” in V8.5) is not visible in the Process Admin Console of Process Server under Role Bindings when a snapshot is installed after you use the BPMDeleteSnapshot command. Prevention Interim fix JR48877 Repairs Interim fix JR49635 | Express: 8.5.0.0-WS-BPM-IF-JR48877 Standard: 8.5.0.0-WS-BPM-IF-JR48877 Advanced: 8.5.0.0-WS-BPM-IF-JR48877 |
| JR49267 Symptom A NullPointerException error occurs when you delete the last snapshot from Process Server. Prevention Interim fix JR49267 or do not try to delete the last snapshots. Repairs Interim fix JR49267 | Express: 8.5.0.0-WS-BPM-IFJR49267 Standard: 8.5.0.0-WS-BPM-IFJR49267 Advanced: 8.5.0.0-WS-BPM-IFJR49267 |
| JR49374 Symptom You receive the following error after you run the BPMSnapshotCleanup or BPMDeleteSnapshot command: CWLLG1414E - An exception occurred while getting user attributes Prevention Interim fix JR49374 Repairs Interim fix JR49374 or modify each user attribute definition in your process application and save it | Express: 8.5.0.0-WS-BPM-IFJR49374 Standard: 8.5.0.0-WS-BPM-IFJR49374 Advanced: 8.5.0.0-WS-BPM-IFJR49374 |
| JR49606 Symptom A participant group (called “team” in V8.5) is not visible in the Process Admin Console of IBM Process Center under Role Bindings when a snapshot is installed after you use the BPMSnapshotCleanup command. Prevention Interim fix JR49606 Repairs Interim fix JR49928 | Express: 8.5.0.0-WS-BPM-IF-JR49606 Standard: 8.5.0.0-WS-BPM-IF-JR49606 Advanced: 8.5.0.0-WS-BPM-IFJR49606 |
| JR49635 This repair-only interim fix applies to the issue that is addressed in JR48877. JR49635 looks for and repairs issues when importing a snapshot. Although JR48877 repairs most of the issues, you still need interim fix JR49635 if there are more than 1000 participant groups (called “teams” in V8.5). JR49635 repairs the damage done by the issue that is fixed by JR48877 in the event that you encounter the issue before you apply JR48877. | Express: 8.5.0.0-WS-BPM-IF-JR49635 Standard: 8.5.0.0-WS-BPM-IF-JR49635 Advanced: 8.5.0.0-WS-BPM-IFJR49635 |
| JR49848 Symptom After you run the BPMSnapshotCleanup command, you can no longer save artifacts that have advanced content in Process Designer in a process application or toolkit from IBM Integration Designer Prevention Interim fix JR49848 Repairs Interim fix JR49848 or edit the LSW_SCA_CONNECTOR table of the BPMDB database and put the outOfSync value into the LAST_SYNCHRONIZED column for the Advanced Integration Service that is affected | Express: Not applicable Standard: Not applicable Advanced: 8.5.0.0-WS-BPM-IFJR49848 |
| JR49928 This repair-only interim fix applies to the issue that is addressed in JR49606. JR49928 looks for and repairs issues when the server starts. You do not require interim fix JR49928 if the interim fixes JR48877 and JR49606 are applied before snapshots are deleted. | Express: 8.5.0.0-WS-BPM-IF-JR49928 Standard: 8.5.0.0-WS-BPM-IF-JR49928 Advanced: 8.5.0.0-WS-BPM-IFJR49928 |
| JR50444 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see the DATAINTEGRITYVIOLATIONEXCEPTION. This fix checks whether there are exposed items before deleting the groups, preventing you from deleting those groups. | Express: 8.5.0.0-WS-BPM-IFJR50444 Standard: 8.5.0.0-WS-BPM-IFJR50444 Advanced: 8.5.0.0-WS-BPM-IFJR50444 |
| JR50667 Deleting a snapshot destroys most smart folders. Smart folders are used for the entire project's track or branch. It is not expected that the smart folders will be deleted when snapshots are deleted. | Express: 8.5.0.0-WS-BPM-IFJR50667 Standard: 8.5.0.0-WS-BPM-IFJR50667 Advanced: 8.5.0.0-WS-BPM-IFJR50667 |
| JR50671 Removing snapshots does not and must cascade delete with snapshot because this could cause problems if a snapshot is deleted and then added back. | Included in JR50667 |
| JR50718 The BPMDeleteSnapshot command proceeds even though there are running instances of stand-alone human services. | Express: 8.5.0.0-WS-BPM-IFJR50718 Standard: 8.5.0.0-WS-BPM-IFJR50718 Advanced: 8.5.0.0-WS-BPM-IFJR50718 |
| JR50720 The BPMDeleteSnapshot command proceeds even though there business process definition (BPD) instances in another snapshot that point to tasks from the snapshot that is being deleted. | Express: 8.5.0.0-WS-BPM-IFJR50720 Standard: 8.5.0.0-WS-BPM-IFJR50720 Advanced: 8.5.0.0-WS-BPM-IFJR50720 |
| JR50721 The BPMSnapshotCleanup command proceeds even though there are running instances of stand-alone human services. | Express: 8.5.0.0-WS-BPM-IFJR50721 Standard: 8.5.0.0-WS-BPM-IFJR50721 Advanced: 8.5.0.0-WS-BPM-IFJR50721 |
| JR50722 The automatic unnamed snapshot cleanup feature for IBM Process Center can cause some database rows to incorrectly be removed for named snapshots that were initially created in the time frame of the cleaned-up unnamed snapshots. | Express: 8.5.0.0-WS-BPM-IFJR50722 Standard: 8.5.0.0-WS-BPM-IFJR50722 Advanced: 8.5.0.0-WS-BPM-IFJR50722 |
| JR50742 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see a DATAINTEGRITYVIOLATION exception. | Express: 8.5.0.0-WS-BPM-IFJR50742 Standard: 8.5.0.0-WS-BPM-IFJR50742 Advanced: 8.5.0.0-WS-BPM-IFJR50742 |
| JR52313 When you call the BPMUpdateSystemApp admin task to renew a system application, the command hangs. Therefore, the task does not return and seems to hang in a database call. | Express: 8.5.0.0-WS-BPM-IFJR52313 Standard: 8.5.0.0-WS-BPM-IFJR52313 Advanced: 8.5.0.0-WS-BPM-IFJR52313 |
| JR52327 When you run the BPMSnapshotCleanup command with -ignoreDependency = true, toolkits that have other toolkits and process apps depending on them can be deleted without warning, leading to other problems. | Express: 8.5.0.0-WS-BPM-IFJR52327 Standard: 8.5.0.0-WS-BPM-IFJR52327 Advanced: 8.5.0.0-WS-BPM-IFJR52327 |
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
Interim fix JR52436 now supersedes the following DeleteSnapshot-related interim fixes :
JR48877, JR49267, JR49374, JR49606, JR49635, JR49928, JR50444, JR50667, JR50671,
JR50718, JR50720, JR50721, JR50742, JR52313
In addition, JR52436 also supersedes these additional interim fixes:
JR47596, JR47706, JR48172, JR48446, JR48507, JR48508, JR48550, JR48787, JR49168, JR49359, JR49408, JR49503, JR49505, JR49509, JR49514, JR49638, JR49730, JR50003, JR50117, JR50137, JR50193, JR50233, JR50263, JR50335, JR50794, JR50807, JR50899, JR51268, JR51282, JR51292, JR51699, JR51707, JR51776, JR51777, JR51817, JR51895, JR51910, JR52079, PI18805
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
JR48877, JR49267, JR49374, JR49606, JR49635, JR49928, JR50444, JR50667, JR50671,
JR50718, JR50720, JR50721, JR50742, JR52313
In addition, JR52436 also supersedes these additional interim fixes:
JR47596, JR47706, JR48172, JR48446, JR48507, JR48508, JR48550, JR48787, JR49168, JR49359, JR49408, JR49503, JR49505, JR49509, JR49514, JR49638, JR49730, JR50003, JR50117, JR50137, JR50193, JR50233, JR50263, JR50335, JR50794, JR50807, JR50899, JR51268, JR51282, JR51292, JR51699, JR51707, JR51776, JR51777, JR51817, JR51895, JR51910, JR52079, PI18805
| APAR | 8.5.0.1 |
| JR52436 This cumulative fix supersedes the following interim fixes: JR48877 JR49267 JR49374 JR49606 JR49635 JR49928 JR50444 JR50667 JR50671 JR50718 JR50720 JR50721 JR50742 JR52313 | Express: 8.5.0.1-WS-BPM-IFJR52436 Standard: 8.5.0.1-WS-BPM-IFJR52436 Advanced: 8.5.0.1-WS-BPM-IFJR52436 |
| JR49848 Symptom After you run the BPMSnapshotCleanup command, you can no longer save artifacts that have advanced content in Process Designer in a process application or toolkit from IBM Integration Designer Prevention Interim fix JR49848 Repairs Interim fix JR49848 or edit the LSW_SCA_CONNECTOR table of the BPMDB database and put the outOfSync value into the LAST_SYNCHRONIZED column for the Advanced Integration service that is affected | Express: Not applicable Standard: Not applicable Advanced: 8.5.0.1-WS-BPM-IFJR49848 |
| JR50722 The automatic unnamed snapshot cleanup feature for IBM Process Center can cause some database rows to incorrectly be removed for named snapshots that were initially created in the time frame of the cleaned-up unnamed snapshots. | Express: 8.5.0.1-WS-BPM-IFJR50722 Standard: 8.5.0.1-WS-BPM-IFJR50722 Advanced: 8.5.0.1-WS-BPM-IFJR50722 |
| JR52327 When you run the BPMSnapshotCleanup command with -ignoreDependency = true, toolkits that have other toolkits and process apps depending on them can be deleted without warning, leading to other problems. | Express: 8.5.0.1-WS-BPM-IFJR52327 Standard: 8.5.0.1-WS-BPM-IFJR52327 Advanced: 8.5.0.1-WS-BPM-IFJR52327 |
| JR54063 When you try to clean up snapshots on IBM Process Center or delete a snapshot on IBM Process Server, the operation fails and you receive a database exception about the violation of the BPM_SHARED_OBJECT_FK constraint. | Express: 8.5.0.1-WS-BPM-IFJR54063 Standard: 8.5.0.1-WS-BPM-IFJR54063 Advanced: 8.5.0.1-WS-BPM-IFJR54063 |
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
All the following individual interim fixes for the BPMDeleteSnapshot and BPMSnapshotCleanup commands are available for IBM Business Process Manager V8.5.5. You must download and install all these interim fixes and their dependencies before you can use these commands on IBM Business Process Manager V8.5.5.0. However, instead of installing these fixes individually, consider installing them as a cumulative fix instead, either on Standard or Advanced, for convenience.
Important: The cumulative fix does not include JR52313. Links to information about this interim fix and the fix itself are in the following table.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
Important: The cumulative fix does not include JR52313. Links to information about this interim fix and the fix itself are in the following table.
| APAR | 8.5.5.0 |
| JR50444 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see the DATAINTEGRITYVIOLATIONEXCEPTION. This fix checks whether there are exposed items before deleting the groups, preventing you from deleting those groups. | Express: 8.5.5.0-WS-BPM-IFJR50444 Standard: 8.5.5.0-WS-BPM-IFJR50444 Advanced: 8.5.5.0-WS-BPM-IFJR50444 |
| JR50667 Deleting a snapshot destroys most smart folders. Smart folders are used for the entire project's track or branch. It is not expected that the smart folders will be deleted when snapshots are deleted. | Express: 8.5.5.0-WS-BPM-IFJR50667 Standard: 8.5.5.0-WS-BPM-IFJR50667 Advanced: 8.5.5.0-WS-BPM-IFJR50667 |
| JR50671 Removing snapshots does not and must cascade delete with snapshot because this could cause problems if a snapshot is deleted and then added back. | Express: 8.5.5.0-WS-BPM-IFJR50671 Standard: 8.5.5.0-WS-BPM-IFJR50671 Advanced: 8.5.5.0-WS-BPM-IFJR50671 |
| JR50718 The BPMDeleteSnapshot command proceeds even though there are running instances of stand-alone human services. | Express: 8.5.5.0-WS-BPM-IFJR50718 Standard: 8.5.5.0-WS-BPM-IFJR50718 Advanced: 8.5.5.0-WS-BPM-IFJR50718 |
| JR50720 The BPMDeleteSnapshot command proceeds even though there business process definition (BPD) instances in another snapshot that point to tasks from the snapshot that is being deleted. | Express: 8.5.5.0-WS-BPM-IFJR50720 Standard: 8.5.5.0-WS-BPM-IFJR50720 Advanced: 8.5.5.0-WS-BPM-IFJR50720 |
| JR50721 The BPMSnapshotCleanup command proceeds even though there are running instances of stand-alone human services. | Express: 8.5.5.0-WS-BPM-IFJR50721 Standard: 8.5.5.0-WS-BPM-IFJR50721 Advanced: 8.5.5.0-WS-BPM-IFJR50721 |
| JR50722 The automatic unnamed snapshot cleanup feature for IBM Process Center can cause some database rows to incorrectly be removed for named snapshots that were initially created in the time frame of the cleaned-up unnamed snapshots. | Express: 8.5.5.0-WS-BPM-IFJR50722 Standard: 8.5.5.0-WS-BPM-IFJR50722 Advanced: 8.5.5.0-WS-BPM-IFJR50722 |
| JR50742 When the server starts or when you use the BPMInstallOfflinePackage administrative command, you might see a DATAINTEGRITYVIOLATION exception. | Express: 8.5.5.0-WS-BPM-IFJR50742 Standard: 8.5.5.0-WS-BPM-IFJR50742 Advanced: 8.5.5.0-WS-BPM-IFJR50742 |
| JR52313 When you call the BPMUpdateSystemApp admin task to renew a system application, the command hangs. Therefore, the task does not return and seems to hang in a database call. | Express: 8.5.5.0-WS-BPM-IFJR52313 Standard: 8.5.5.0-WS-BPM-IFJR52313 Advanced: 8.5.5.0-WS-BPM-IFJR52313 |
| JR52327 When you run the BPMSnapshotCleanup command with -ignoreDependency = true, toolkits that have other toolkits and process apps depending on them can be deleted without warning, leading to other problems. | Express: 8.5.5.0-WS-BPM-IFJR52327 Standard: 8.5.5.0-WS-BPM-IFJR52327 Advanced: 8.5.5.0-WS-BPM-IFJR52327 |
| JR54063 When you try to clean up snapshots on IBM Process Center or delete a snapshot on IBM Process Server, the operation fails and you receive a database exception about the violation of the BPM_SHARED_OBJECT_FK constraint. | Express: 8.5.5.0-WS-BPM-IFJR54063 Standard: 8.5.5.0-WS-BPM-IFJR54063 Advanced: 8.5.5.0-WS-BPM-IFJR54063 |
| JR56448 You receive an error when running the bpmsnapshotcleanup command because of a constraint violation in the lsw_usr_grp_xref table" | Express: 8.5.5.0-WS-BPM-IFJR56448 Standard: 8.5.5.0-WS-BPM-IFJR56448 Advanced: 8.5.5.0-WS-BPM-IFJR56448 |
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
There are currently no additional interim fixes for IBM BPM V8.5.6.0.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
There are currently no additional interim fixes for IBM BPM V8.5.7.0.
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
For more information about these commands, see the following topics:
BPMDeleteSnapshot command
BPMSnapshotCleanup command
Deleting snapshots on process servers
[{"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Process Center","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.5.7;8.5.6;8.5.5;8.5.0.1;8.5;8.0.1.3;8.0.1.2;8.0.1.1;8.0.1;8.0;7.5.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Process Center","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.7;8.5.6;8.5.5;8.5.0.1;8.5;8.0.1.3;8.0.1.2;8.0.1.1;8.0.1;8.0;7.5.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSFTBX","label":"IBM Business Process Manager Express"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Process Center","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.5.7;8.5.6;8.5.5;8.5.0.1;8.5;8.0.1.3;8.0.1.2;8.0.1.1;8.0.1;8.0;7.5.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Product Synonym
BPM
Was this topic helpful?
Document Information
Modified date:
25 September 2022
UID
swg21669992