Description

During a VB analysis, the following error occurs :

Error SQL Error: ERROR: could not create unique index "idx_in_keysanad3".

SQL Error: DETAIL: Table contains duplicated values..

SQL Error: CONTEXT: SQL statement "create unique index IDX_IN_KEYSANAD3 on IN_KEYSANAD(KEYNAMANA, KEYCLASS, ORDNUM, IDIDENTPARENT, IDDISPPARENT)".
SQL Error: PL/pgSQL function "keysana_tb_update" line 24 at SQL statement (Severity 1, Msg No 1).
Error: error saving analysis objects

It seems that the creation of the index idx_in_keysanad3 fails in the function keysana_tb_update, because of duplicated data in table IN_KEYSANAD.

Observed in CAST AIP
Release
Yes/No
8.3.x(error)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)
7.3.x(tick)
7.2.x(tick)
7.0.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(error)
CSS2(tick)
CSS1(tick)
Step by Step Scenario
  1. Package the source code
  2. Run the analysis,
  3. Analysis stops with errors in the log.
Action Plan

This issue occurs because of object sharing and occurs when there are shared objects among the analysis units.

Example: For the job 'Global Test Client', the file src\Global Test Client\Test Plug-In\FrmCredit.frm is used in the following two VB projects :

  • src\Global Test Client\TestPlug-In\MSSmartPayments.vbp and
  • src\Global Test Client\TestPlug-In\TestPro.vbp

So we have to put the above two projects in separate job, which can be done by below:

  1. In CAST-MS set the audience to Expert
  2. Open the Analysis Units of the projects that shares objects with other projects if you cannot identify them do the below for all the analysis units.
  3. Go to the ‘Execute’ tab and put a different annotation string (for instance the name of the AU) in each of them in order to analyze them separately.
  4. Launch the analysis again.
Impact on Analysis Results and Dashboard

 

Notes/comments

Ticket # 1842

Related Pages