Tag Archives: HP ALM

Initialization of the ALM Octane Server

If you are not getting past the initialization of the ALM Octane Server and getting database connection issues like

error: url=’jdbc:mercury:sqlserver://′, dbType=MSSQL, userName=’sa’]. Error: Connections could not be acquired from the underlying database!

The root cause for this is the SQL services.The SQL Agent and Browser are not running, causing the connection issue between the DB and the Octane server.


Copy test with requirement coverage

User wants to have all the test cases with the linked requirement from 3 different projects to one new project.

• Go to Management module (old projects)
• Go Libraries
• Create a new Library
o Select all the requirements
o Select ‘Test covering selected requirements’
• Create a baseline
o Check the logs

• Import a library
• Check the logs
This copies the test and its requirement coverage as your user has requested.

The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.LISTS’ and the index

Migrated our HP ALM to new windows server and sql server. Was able to migrate HP ALM to version 12.55 however projects fail to upgrade.

Getting the below error message after upgrading a project,

Exception occurred. Message: [Mercury][SQLServer JDBC Driver][SQLServer]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.LISTS’ and the index name ‘LS_LOGICAL_NAME_IDX’. The duplicate key value is (hp.qc.plan-status.imported).

In this case the issue is because there is a duplicate key in [dbo].[LISTS] table.

You may need to run the following query in order to identify which is the duplicated one : select * from [dbo].[LISTS] where ls_logical_name=’hp.qc.plan-status.imported’

In this case it seems that the value for the LS_NAME had been modified, the default value is "Imported" and in your case is "Feedback Provided".

So the application notices the original value does not exist so it insets it (as seen in the last upgrade attempt, after running it another one was created) and consequently this causes the index duplicate error.

For fixing this issue it is necessary to update the LS_NAME to the original value, then run the upgrade process and later you can update the records again and have the customized as desired. This will not affect the data that is already in the entities .

After that you may need to follow the next steps in order to resolve the issue:

To update the records a simple query like this can be used:
Update [td].[LISTS] set LS_NAME ‘Imported’ WHERE LS_ID = ‘355’

“Too many open files” error in ALM wrapper log

When ALM is deployed on Linux and the error “Too many open files” exists in the wrapper logs, this is an indicator the “open file” limit on the Unix file system has been exceeded.

This can cause issues where attachments can’t be opened, tests executed, inability to open scripts or save scripts.

By default the “open file” limit on Linux is set to 1024; the number of concurrently open files.

To determine the “open file” value type the following in the Unix shell…

utlimit -a

Many results will be returned. Examine the value of the “open files” parameter.

To correct do the following…

1) Using vi or similar method, open the file /etc/security/limits.conf

2) Add the following lines to the file…

root soft  nofile <value>
root hard  nofile <value>

For example…

root soft  nofile 2048
root hard  nofile 2048

The value should be increased until the “Too many open files” error goes away. Start by doubling the current value.

3) Save the file
4) Restart Linux

Suggest checking to make sure the changes were implemented by issuing: ulimit -a
Then check the “open files” limit to make the changes took place.

Cannot add HTTPS Performance Center URL in Application Lifecycle Management LAB Management

ALM and PCS were configured to work with HTTPS, when adding the HTTPS PCS URL, the lab management shows an error message that it could not connect to the PCS through HTTPS .

ALM and PCS certificates are installed in the correct keystone, and both URLS work.

Please review with the customer Information Technology (IT) team if there are any IT policy that automatically disable TLS 1.0 after a Server reboot.

If there is a policy on disabling  the TLS 1.0 in the PCS machine, it can result in the PC machine rejecting the ALM communication.

Once TLS 1.0 was enabled, PCS servers with HTTPS URL can be added to the ALM LAB management.

How to switch between “HTML” and “Run Results Viewer” format in UFT 12.5X

In UFT 12.5X Run Results are created, by default, in HTML. Although this is preferred as it offers a multi-platform, browser independent format for Run Results, it be desirable to switch to the legacy format where the Run Results Viewer format is used.

To change the desired format, do the following steps:
1)      Open UFT 12.5X
2)      Click Tools>Options
3)      Select the General item at the top of the window
4)      In the body, under “Report Format” select the desired format “HTML” or “Run Results Viewer Report
Mind that selecting the Run Results Viewer Report option will require a Windows OS with the Run Results Viewer installed in order to view the report.
Also know the HTML format option consumes less disk space; the results files are approximately 50% smaller than Run Results Viewer format.

Note: When running tests from ALM, you can view the HTML report only if you are using one of the following ALM versions:
– ALM 11.52 Patch 5 or higher,
– ALM 12.21 and higher.

Project statuses in ALM/QC

Project status is determined by PR_IS_ACTIVE field in PROJECTS table, in QC SITEADMIN schema.

Project statuses:


When you are doing operations ( like copy or import project operation), Some times browser seems to be hanged, to confirm whether operation going on or not, check the project status(PR_IS_ACTIVE) in PROJECTS table.
Wait until the operation on the project is completed(i.e change in the status)