Error when adding comments to defects – Failed to setValue for key in table 'BUG' in project
Question ID: 107258
0
0

When adding comments to defects the following error occurs. The issue occurs for multiple users and client machines, and it is currently being experienced in multiple projects within different domains. We are currently using ALM 11.52 Patch 3 with Oracle, which was just upgraded to v11.2.0.4.

**Error Message Displayed in ALM:**

Failed to setValue for key 2659 in table ‘BUG' in project
'com.hp.alm.platform.connection. TreadSafeCachedSessionContect@6d996783’

![alt text][1]

**Error Message Displayed from the QC log:**

Message

Failed to setValue for key 2616 in table ‘BUG’ in project ‘com.hp.alm.platform.connection.authentication.ThreadSafeCachedSessionContext@5817882a’; [Mercury][Oracle JDBC Driver][Oracle]ORA-00604: error occurred at recursive SQL level 1 ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to ‘SYNCRN’ ORA-06550: line 1, column 7: PL/SQL: Statement ignored Failed SQL: /* ~~QC */ UPDATE BUG SET BG_DEV_COMMENTS=/*P*/’### Clob! Begins with: html
body
div align="left" font face="Aria ###’, BG_BUG_VER_STAMP=BG_BUG_VER_STAMP+1, BG_VTS=/*P*/’2016-11-07 13:28:29′ where BG_BUG_ID=/*P*/2616;

Stack Trace

java.sql.SQLException: [Mercury][Oracle JDBC Driver][Oracle]ORA-00604: error occurred at recursive SQL level 1 ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to ‘SYNCRN’ ORA-06550: line 1, column 7: PL/SQL: Statement ignored Failed SQL: /* ~~QC */ UPDATE BUG SET BG_DEV_COMMENTS=/*P*/’### Clob! Begins with: html
body
div align="left" font face="Aria ###’, BG_BUG_VER_STAMP=BG_BUG_VER_STAMP+1, BG_VTS=/*P*/’2016-11-07 13:28:29′ where BG_BUG_ID=/*P*/2616

[1]: /storage/temp/509-capture.png

Marked as spam
Posted by (Questions: 239, Answers: 31)
Asked on November 9, 2016 9:50 pm
268 views
Answers (1)
0
Private answer

In the error message displayed in the QC log, I see the Oracle error ''PLS-00306: wrong number or types of arguments in call to 'SYNCRN' ORA-06550'' which happens to be a known problem with Oracle that has been analyzed in unpublished Bug 17501296 - Commit callback procedure ctxsys.syncrn is not in sync with 11.2.0.4.

In order to resolve this issue, your DBA will either need to apply Patch 17501296, or recreate the ctxsys.syncrn procedure as described in Oracle technote Doc ID 1586704.1. Your DBA will need to contact Oracle Support to request Patch 17501296, as well as the Oracle technote Doc ID 1586704.1, which covers recreating the ctxsys.syncrn procedure.

After your DBA has applied the patch or recreated the procedure, test to see if the issue still exists when adding comments to your defects.

Marked as spam
Posted by (Questions: 2, Answers: 300)
Answered on November 9, 2016 9:51 pm
0
We deployed the patch to the Quality Center database server last night and we no longer experience the issue. Thanks!
( at November 9, 2016 9:51 pm)
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

X
Scroll to Top