”Merge into PROJECT_INFO” error in ALM?

  • Questions
  • ''Merge into PROJECT_INFO'' error in ALM?
Question ID: 106205
0
0

Hello,
We are having an issue where we are seeing the following error in our log files repeatedly:

"Failed SQL: /* ~~QC */ MERGE INTO PROJECT_INFO USING DUAL ON (PI_PUID= AND PI_KEY=) WHEN NOT MATCHED THEN INSERT (PI_PUID,PI_KEY,PI_VALUE) VALUES (,,) WHEN MATCHED THEN UPDATE SET PI_VALUE=
[Mercury][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist"

We have just started noticing it, but are not seeing any other residual effects from this error (such as lost data or performance deecrease). Do you have any insight into this issue?

HomerJ

Marked as spam
Posted by (Questions: 314, Answers: 12)
Asked on July 23, 2015 12:11 pm
5 views
Answers (1)
1
Private answer

Hello HomerJ,

The error you are experiencing is a known issue in ALM11.00 in patch 17 and 18 within the SA logs.

This is a known issue that has been reported to HP and further information (if you have a valid HPO Passport ID here:

https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1J72393

As per HP:
''After upgrading to ALM 11.0 Patch 17 and now in patch 18 SA logs are capturing a new and unseeing error message pointing to PROJECT_INFO table under qcsiteadmin_db which is not valid for ALM 11.
The error is only captured when there are more than 15-20 concurrent users connected to the application.
This has been reported when using JBOSS as well as when using WebSphere as the application server.

This is a known issue on ALM 11 and already reported to R&D but is deferred meaning that the issue has been reviewed and determined as a valid request, however it is unable to be addressed at this time.

This is a known issue and the error will not break functionality if the customer does not use Gossip (AKA: HP ALM Synchronizer).

If customer uses Gossip, this table should be manually created in Site Admin db. The DDL for MS SQL Server db is as below:

CREATE TABLE [td].[PROJECT_INFO](
[PI_PUID] [varchar](36) NOT NULL,
[PI_KEY] [varchar](255) NOT NULL,
[PI_VALUE] [varchar](255) NULL,
CONSTRAINT [PI_PK] PRIMARY KEY ([PI_PUID] ASC,[PI_KEY] ASC))

The query for Oracle DB is the following:

create table QCSITEADMIN_DB11.PROJECT_INFO
(PI_PUID varchar(36) not null,
PI_KEY varchar(255) not null,
PI_VALUE varchar(255) null,
constraint PI_PK primary key (PI_PUID,PI_KEY)
);

If customer do not use Gossip (HP Synchronizer), they could just ignore the error. If they insist on resolving the error, creating the table above manually is the workaround for this issue.

Note: Please keep in mind that is always important to create backups of all the data before changing anything on the ALM system. Also any kind of change instituted from the DB is not supported from HP, since it is only a workaround.''

I hope this helps clarify your issue.

Thanks,
Dan

Marked as spam
Posted by (Questions: 0, Answers: 709)
Answered on July 23, 2015 12:21 pm
Thanks for the complete and concise answer and explanation. It is exactly what we are seeing. We have decided to just let the error reside until we upgrade to a newer version since it doesn't affect performance and we don't use Synchronizer at this time. Thanks
( at July 23, 2015 12:22 pm)