CONCURRENT MERGE PROCESS blocks Harvest DB
Article ID: 4214
Updated On:
Products
Issue/Introduction
There is one user attempting to merge a package. His Eclipse (or Workbench) workspace freezes and he decides to kill Eclipse (or Workbench). This leaves the database with a locked session, thereby blocking any other update/insert/delete transaction accessing the same table(s) blocked by the locked session.
Environment
Harvest Software Change Manager all versions
Cause
The Package was locked. It was determined that this locking transaction was created by a user manually closing their Eclipse (or Workbench) Workspace session during a long-running Harvest process.
Resolution
The Database administrator should check to see if there is a query in Oracle or SQL Server that is blocking the Harvest DB. The workaround is to kill the query. After this all users are ok to resume, EXCEPT the user that attempted to merge that can not continue working.
Next, check the package status , if status is locked unlock it using the Harvest command line utility hpkgunlk.exe. The syntax of the unlock package is provided below:
hpkgunlk -b <Broker Name > -usr <user name > -pw < password> -en <project name> "<package name>"
Be sure to check the "hpkgunlk.log" file after the command to confirm that it was successful.
If package is not blocked, check the Oracle or SQL Server "blocking event" and report it to Broadcom support.
Additional Information
For more information about the "hpkgunlk" command you can refer to the documentation: hpkgunlk Command-Unlock Package. This command can be executed from the broker machine or any client machine that contains the Administrator Tool.
Feedback
