CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Errors on Documentation - V2

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ABAP - duplicate key value violates unique constraint

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page outlines the error which is faced when running an ABAP analysis :

The error only occurs on the 2nd analysis. The first analysis will succeed and will properly create the objects, but any subsequent analyses will fail.

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	✅ x < 2
8.1.x	✅ x < 2
8.0.x	✅ x < 5
7.3.x	✅ x < 11

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ABAP - duplicate key value violates unique constraint pk-objdsc

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page outlines the error which is faced when running an ABAP analysis :

SQL Error: ERROR: duplicate key value violates unique constraint "pk_objdsc".
SQL Error: DETAIL: Key (idobj, inftyp, infsubtyp, blkno, ordnum)=(28420, 37000, 103, 59214, 0) already exists

The error only occurs on the 2nd analysis. The first analysis will succeed and will properly create the objects, but any subsequent analyses will fail.
You can have ABAP data in two formats – one an older format and another which is a newer format. We normally have seen one or the other in the code.
This is due to a bug in the ABAP analyzer when a classpool contains at same times following files:
#XEIT#CLNRO===================CL.abap
and
#XEIT#CLNRO===================CCDEF.abap
or: #XEIT#CLNRO===================CCIMP.abap
or: #XEIT#CLNRO===================CCMAC.abap

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Cannot insert duplicate key row in object dboObjPro with unique index ObjPro_ProObj

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page talks about the analysis throwing below error while running the analysis:

Error - Cannot insert duplicate key row in object ‘dbo.ObjPro’ with unique index ‘ObjPro_ProObj

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	?

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	✅
CSS2	✅
CSS1	?

Step by Step Scenario

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - C - Invalid byte sequence for encoding UTF8 0xed 0xb1 0xb8

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

On analysis of a C/C++ job,SQL errors are found-Invalid byte sequence for encoding “UTF8”: 0xed 0xb1 0xb8

Starting External Link processing

Ending External Link processing
SQL Error: ERROR: invalid byte sequence for encoding “UTF8”: 0xed 0xb1 0xb8.
SQL Error: CONTEXT: COPY in_char_properties, line 4284 (Severity 1, Msg No 1).
Database BCP operation dbbcp_done failed on table test_local.IN_CHAR_PROPERTIES(session_id,object_id,property_type_id,property_offset,char_block,property_char)
New Job status
Execution date=2015/02/04 09:38
Execution duration=0 days, 00 hours, 38 mins, 51 secs
Execution result=error
0 fatal error(s); 20370 error(s); 6678 warning(s); 27228 information message(s).

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - could not create unique index idx_cat

Mon, 01 Jan 0001 00:00:00 +0000

Description

During an analysis, the following error seen in the synchronization log :

SQL Error: ERROR: could not create unique index “idx_cat”.

SQL Error: DETAIL: Key (idcat)=(139512) is duplicated. (Severity 1, Msg No 1).

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	✅
CSS2	✅
CSS1	✅

Step by Step Scenario

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - C - relation all synonyms does not exist

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution to the following C Analysis error:

Starting External Link processing:

Error INTERNAL ; Job execution SQL Error: ERROR: relation “all_synonyms” does not exist.
Error INTERNAL ; Job execution SQL Error: LINE 1: … FOR select table_owner, table_name, db_link from all_synony….
Error INTERNAL ; Job execution SQL Error: ^ (Severity 1, Msg No 1).
Error INTERNAL ; Job execution SQL Error: ERROR: current transaction is aborted, commands ignored until end of transaction block (Severity 1, Msg No 1).

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - duplicate key value violates unique constraint idx1 coobject

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page will help you to solve the issue related to analysis failiure during the Saving step at the Comparing objects on server with the following SQL Error message:

Comparing objects on server…
SQL Error: ERROR: duplicate key value violates unique constraint “idx1_coobject”.
SQL Error: DETAIL: Key (object_id)=(63261) already exists..
SQL Error: CONTEXT: SQL statement “insert into AMT_OBJECT (OBJECT_ID, NAME_ID, SHORT_NAME_ID, OBJECT_TYPE_ID, INTERNAL_ID, STATUS).
SQL Error: select OBJECT_ID, NAME_ID, SHORT_NAME_ID, OBJECT_TYPE_ID, .
SQL Error: coalesce(o.IdKey, nextval(‘IDKEY_GENERATOR’) ),.
SQL Error: case when o.IdKey is null then ‘I’.
SQL Error: else ‘U’.
SQL Error: end.
SQL Error: from IN_OBJECTS left join Objects o.
SQL Error: on o.IdShortNam = IN_OBJECTS.SHORT_NAME_ID .
SQL Error: and o.IdNam = IN_OBJECTS.NAME_ID .
SQL Error: and o.ObjTyp = IN_OBJECTS.OBJECT_TYPE_ID.
SQL Error: where SESSION_ID = I_IDSESSION”.
SQL Error: PL/pgSQL function amt_p_fill_obj(integer) line 20 at SQL statement.
SQL Error: SQL statement “select AMT_P_FILL_OBJ (I_IDSESSION)”.
SQL Error: PL/pgSQL function amt_p_split_fill(integer) line 12 at SQL statement.
SQL Error: SQL statement “select AMT_P_SPLIT_FILL (I_IDSESSION)”.
SQL Error: PL/pgSQL function amt_p_split_in(integer) line 15 at SQL statement.
SQL Error: SQL statement “select AMT_P_SPLIT_IN (I_IDSESSION)”.
SQL Error: PL/pgSQL function cache_processid(integer,integer) line 14 at SQL statement (Severity 1, Msg No 1).
Procedure call failed: ?test_app_test_local.CACHE_PROCESSID,I_IDSESSION,I_IDUSRPRO

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - duplicate key value violates unique constraint idx2_objects

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

The following error occurs during analysis which are made on Kb that have been wrongly exported and restored with CSS tools (CSSdump & CSSrestore) ;

SQL Error: ERROR: duplicate key value violates unique constraint “idx2_objects”.
SQL Error: CONTEXT: SQL statement “insert into Objects (IdKey, IdNam, IdShortNam, ObjTyp) select INTERNAL_ID, NAME_ID, SHORT_NAME_ID, OBJECT_TYPE_ID from AMT_OBJECT obj where obj.STATUS = ‘I’”.
SQL Error: PL/pgSQL function “amt_f_maj_kb_prj” line 76 at SQL statement.
SQL Error: SQL statement “select AMT_F_MAJ_KB_PRJ ( $1 )”.
SQL Error: PL/pgSQL function “amt_f_maj_kb” line 15 at SQL statement.
SQL Error: SQL statement “select AMT_F_MAJ_KB ( $1 )”.

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - duplicate key value violates unique constraint pk_accidacc

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page will help you to solve the issue related to analysis failure during the Saving step on the server with the following SQL Error message:

2019-07-24 08:43:23.401149 MODULMSG ; Job execution Comparing objects on server . . .
2019-07-24 08:43:33.885615 MODULMSG ; Job execution Comparison completed.
2019-07-24 08:43:33.885615 MODULMSG ; Job execution Merging objects on server . . .
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: ERROR: duplicate key value violates unique constraint “pk_accidacc”.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: DETAIL: Key (idacc)=(218593998) already exists..
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: CONTEXT: SQL statement “insert into Acc (IdAcc, IdClr, IdCle, AccTypLo, AccTypHi, AccTypLo2, AccTypHi2, AccKnd, IdPro, Prop).
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: select distinct IdAcc, INTERNAL_SOURCE_ID, INTERNAL_TARGET_ID, AccTypLo, AccTypHi, 0, 0, 0, IDPRO, PROP .
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: from TMP_WK_RESACC t.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: where t.STATUS = ‘I’.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: and t.LINK_KIND=‘N’”.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: PL/pgSQL function amt_f_maj_lnkmain(integer) line 90 at SQL statement.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: SQL statement “select AMT_F_MAJ_LNKMAIN (I_IDSESSION)”.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: PL/pgSQL function amt_f_maj_objmain(integer) line 111 at SQL statement.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: SQL statement “select AMT_F_MAJ_OBJMAIN (I_IDSESSION)”.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.316284 Error MODULMSG ; Job execution SQL Error: PL/pgSQL function amt_f_maj_kb_obj(integer) line 24 at SQL statement.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.331906 Error MODULMSG ; Job execution SQL Error: SQL statement “select AMT_F_MAJ_KB_OBJ (I_IDSESSION)”.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.331906 Error MODULMSG ; Job execution SQL Error: PL/pgSQL function amt_f_maj_kb(integer) line 24 at SQL statement.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.331906 Error MODULMSG ; Job execution SQL Error: SQL statement “select AMT_F_MAJ_KB (I_IDSESSION)”.
0 gcommon\gcconnectionopen.h 23
2019-07-24 08:46:27.331906 Error MODULMSG ; Job execution SQL Error: PL/pgSQL function cache_flushdata(integer) line 40 at SQL statement (Severity 1, Msg No 1).
0 gcommon\gcconnectionopen.h 19
2019-07-24 08:46:27.425664 Error MODULMSG ; Job execution Procedure call failed: ?cml_004.CACHE_FLUSHDATA,I_IDSESSION 0 amt\dbsaver.cpp 705

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ERROR could not write block XXXXXXXX of temporary file

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page gives the information for the troubleshooting of the SQL Error in analysis log file:

ERROR: could not write block XXXXXXXX of temporary file: No space left on device.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	✅
CSS2	✅

Action Plan

This error usually occurs when there is actually no disk space left on the database Server (CSS / ORACLE / MS SQL SERVER). For instance if you are using CSS then the machine on which the CSS is installed is falling out of disk space.

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ERROR D_Acc Object to delete not found Link

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page will guide you to deal with the error Error INTERNAL : Job execution SQL Error: ERROR: D_Acc : Object to delete not found. Link

Observed in CAST AIP

Release	Yes/No
8.3.x	❓
8.2.x	❓
8.1.x	❓
8.0.x	❓
7.3.x	❓
7.2.x	✅
7.0.x	❓

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	❓
Microsoft SQL Server	❓
CSS3	❓
CSS2	✅
CSS1	❓

Step by Step Scenario

Discover the source
Run the analysis
Create another version and run the analysis on the new version.

Action Plan

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - J2EE - duplicate key value violates unique constraint pk objdsc

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page outlines the error “duplicate key value violates unique constraint pk objdsc” which is faced when running a J2EE analysis.

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	✅ x < 2
8.1.x	✅ x < 2
8.0.x	✅ x < 4
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	❌
CSS2	✅

Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Mainframe - could not extend file XXXX No space left on device

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page provides information about the Mainframe analysis error:

SQL Error: ERROR: could not extend file “base/12002/t12_530455”: No space left on device.
SQL Error: HINT: Check free disk space..
SQL Error: CONTEXT: SQL statement “create local temporary table TMP_DELOBJPAR as.
SQL Error:    select wobj.INTERNAL_OBJECT_ID as INTERNAL_OBJECT_ID, aop.SOURCE_ID as SOURCE_ID.
SQL Error:    from AMT_OBJPRO aop join TMP_WK_OBJECTSTATUS wobj.
SQL Error:                          on aop.SOURCE_ID = wobj.INTERNAL_OBJECT_ID.
SQL Error:     and aop.PROP = 0 .
SQL Error:     and wobj.STATUS in (‘I’, ‘U’) .
SQL Error:     union.
SQL Error:     select wobj.INTERNAL_OBJECT_ID as INTERNAL_OBJECT_ID, aop.SOURCE_ID as SOURCE_ID.
SQL Error:       from AMT_OBJPRO aop join TMP_WK_OBJECTSTATUS wobj.
SQL Error:                             on aop.SOURCE_ID = wobj.INTERNAL_OBJECT_ID.
SQL Error:       and aop.PROP = 1 .
SQL Error:       and wobj.STATUS = ‘I’”.
SQL Error: PL/pgSQL function amt_f_maj_param(integer) line 15 at SQL statement.
SQL Error: SQL statement “select AMT_F_MAJ_PARAM (I_IDSESSION)”.
SQL Error: PL/pgSQL function amt_f_maj_objmain(integer) line 106 at SQL statement.
SQL Error: SQL statement “select AMT_F_MAJ_OBJMAIN (I_IDSESSION)”.
SQL Error: PL/pgSQL function amt_f_maj_kb_obj(integer) line 24 at SQL statement.
SQL Error: SQL statement “select AMT_F_MAJ_KB_OBJ (I_IDSESSION)”.
SQL Error: PL/pgSQL function amt_f_maj_kb(integer) line 22 at SQL statement.
SQL Error: SQL statement “select AMT_F_MAJ_KB (I_IDSESSION)”.
SQL Error: PL/pgSQL function cache_flushdata(integer) line 35 at SQL statement (Severity 1, Msg No 1).
Procedure call failed: ?fr_test_app_local.CACHE_FLUSHDATA,I_IDSESSION

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - null value in column source_id violates not-null constraint

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page outlines the error which is faced when running HTML/JS analysis :

 2019-05-14 17:57:33.990268	Error	MODULMSG ; Job execution	SQL Error: ERROR: null value in column "source_id" violates not-null constraint.
 2019-05-14 17:57:33.990268	Error	MODULMSG ; Job execution	SQL Error: DETAIL: Failing row contains (null, 6167556, 0, I)..
 2019-05-14 17:57:33.990268	Error	MODULMSG ; Job execution	SQL Error: CONTEXT: SQL statement "insert into AMT_OBJPRO (SOURCE_ID, TARGET_ID, PROP, STATUS).
 2019-05-14 17:57:33.990268	Error	MODULMSG ; Job execution	SQL Error: select il.INTERNAL_SOURCE_ID, .
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: il.INTERNAL_TARGET_ID, .
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: min(ip.PROPERTY_INT), .
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: 'I'.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: from AMT_PRJLINK il .
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: join AMT_PRJREL ip.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: on il.LINK_ID = ip.OBJECT_ID.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: where il.LINK_TYPE_ID = L_LINKTYPE.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: group by il.INTERNAL_SOURCE_ID, il.INTERNAL_TARGET_ID".
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: PL/pgSQL function amt_p_fill_prj(integer) line 63 at SQL statement.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: SQL statement "select AMT_P_FILL_PRJ (I_IDSESSION)".
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: PL/pgSQL function amt_p_split_fill(integer) line 60 at SQL statement.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: SQL statement "select AMT_P_SPLIT_FILL (I_IDSESSION)".
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: PL/pgSQL function amt_p_split_in(integer) line 17 at SQL statement.
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: SQL statement "select AMT_P_SPLIT_IN (I_IDSESSION)".
 2019-05-14 17:57:33.991265	Error	MODULMSG ; Job execution	SQL Error: PL/pgSQL function cache_processid(integer,integer) line 28 at SQL statement (Severity 1, Msg No 1).
 2019-05-14 17:57:34.230285	Error	MODULMSG ; Job execution	Procedure call failed: ?us93520_1_local.CACHE_PROCESSID,I_IDSESSION,I_IDUSRPRO

Observed in CAST AIP

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error ORA-00600 internal error code arguments kdifind kcbget_24

Mon, 01 Jan 0001 00:00:00 +0000

Applicable in CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	✅

Description

Following error encountered while running J2EE analysis on Oracle 11.0.2

Comparing objects on server . . .
SQL Error: ORA-00600: internal error code, arguments: [kdifind:kcbget_24], [4207104], [1], [0], [1], [], [], [], [], [], [], [].
SQL Error: ORA-06512: at “LOCAL.AMT_P_FILL_LNKTRSF”, line 65. SQL Error: ORA-06512: at “LOCAL.AMT_P_SPLIT_FILL”, line 31.
SQL Error: ORA-06512: at “LOCAL.AMT_P_SPLIT_IN”, line 18. SQL Error: ORA-06512: at “LOCAL.CACHE_PROCESSID”, line 57.
SQL Error: ORA-06512: at line 1 (Severity 1, Msg No 600).
Procedure call failed: ?LOCAL.CACHE_PROCESSID,I_IDSESSION,I_IDUSRPRO
Internal exception occurred during running listener CPersistingAction::ProcessPersistentInstance : Analysis saving could not be finalized

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ORA-01427 single-row subquery returns more than one row during Saving step

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

This page helps investigating any oracle error during saving step for a given AMT analyzer.

Example of errors for Oracle

Comparing objects on server . . .
SQL Error: ORA-01427: single-row subquery returns more than one row
SQL Error: ORA-06512: a “KB.AMT_P_FILL_OBJ”, ligne 44.
SQL Error: ORA-06512: a “KB.AMT_P_SPLIT_FILL”, ligne 40.
SQL Error: ORA-06512: a “KB.AMT_P_SPLIT_IN”, ligne 18.
SQL Error: ORA-06512: a “KB.CACHE_PROCESSID”, ligne 57.
SQL Error: ORA-06512: a ligne 1 (Severity 1, Msg No 1427).
Procedure call failed: ?KB.CACHE_PROCESSID,I_IDSESSION,I_IDUSRPRO

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ORA-01654 unable to extend index by 128 in tablespace

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

This page deals with the following error

SQL Error: ORA-01654:unable to extend index CAST_KB.FUSACC_IDFUS by 128 in tablespace.

SQL Error:ORA-06512: at “CAST_KB.INT_I_F_ACC”. Line 181

SQL Error: ORA-06512 : at “CAST_KB.I_TB_ACC”,line 17

“Error with saving manager”

Applicable in CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	✅

Action Plan

The error ‘unable to extend index’ is produced in the case where there is no more free space in the tablespace that contains the knowledge base:
Therefore, you need to allocate free space to the concerned tablespace and re-run the analysis.

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - ORA-17410 - No more data to read from socket

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Snapshot generation failed with error during the execute linker step with following error:

ORA-17410: No more data to read from socket

This issue has been observed in CAST version 7.0.9

Applicable in CAST Version

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	✅

Action Plan

This problem may occur on the router side because there is a time-out that closes the socket.

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Oracle Forms - null value in column objtyp violates not-null constraint

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution for the following error encountered while running Forms Analysis :

Error :

SQL Error: ERROR: null value in column “objtyp” violates not-null constraint
SQL Error: DETAIL: Failing row contains (10762688, XXX_AC_FORMS_281924 used by XXX_AC_FORMS_281924
SQL Error: CONTEXT: SQL statement “insert into Keys(IdKey, KeyNam, KeyLib, KeyTyp, KeySubTyp, KeyClass, KeyProp, ObjTyp, IdUsrDevPro, KeyDevDat, SqlOwner)
SQL Error: values (IO_IdKey, I_KeyNam, I_KeyLib, I_KeyTyp, I_KeySubTyp, I_KeyClass, I_KeyProp, I_ObjTyp, ‘???’, L_KeyDevDat, I_Owner)
SQL Error: PL/pgSQL function i_keys(integer,character varying,character varying,character,integer,integer,integer,integer,character varying)
SQL Error: SQL statement “select I_Keys (IO_IDPRO, I_PRONAM, cast(null as varchar), ‘XXXXXX’, -1,0,0 , I_OBJTYPPRO, NULL)”
SQL Error: PL/pgSQL function int_subpro_create(integer,character varying,integer,integer,integer,integer)
SQL Error: SQL statement “select INT_SUBPRO_CREATE(L_IDPRO_SUBSET, L_PRONAM_SUBSET, L_OBJTYP_SUBSET, I_IDJOB, L_IDPROMAIN, 8)”
SQL Error: PL/pgSQL function int_dbepro_create(integer)
SQL Error: SQL statement “select INT_DBEPRO_CREATE(I_IDJOB)”

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - PeopleSoft - duplicate key value violates unique constraint psoft_objects_pk

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page describes the solution when you get the following error during the analysis using peoplesoft package 5.0.0,

INF: 2015-02-10 19:48:22: [SQL] select psoft5_v_local.PSOFT_CONTENT_ENRICHMENT() INF: 2015-02-10 19:48:23: [SQL] select psoft5_v_local.PSOFT_DISCRIMINATION_DATA() ERR: 2015-02-10 19:48:45: Error while executing Batch: select psoft5_v_local.PSOFT_DISCRIMINATION_DATA() Query failed because: ERROR: duplicate key value violates unique constraint “psoft_objects_pk” Detail: Key (object_id)=(593532) already exists. Where: SQL statement “insert into psoft_objects (object_id,object_type,object_name,object_fullname,object_lastupd,object_checksum,parent_id) select t1.idkey,t1.objtyp,t1.keynam,t4.fullname ,coalesce((select upd.infval from psoft_wk_lastupd upd where upd.idobj = t1.idkey),’’) ,coalesce((select upd.infval from psoft_wk_checksum upd where upd.idobj = t1.idkey),0) ,(select T2.idparent from keypar T2 where T2.idkey = t1.idkey) from keys t1 join objpro t2 on (t2.idobj = t1.idkey) join objfulnam t4 on (t4.idobj = t1.idkey) where t1.objtyp in (1600673,1600999) and t2.idpro = L_IDSUBSET” PL/pgSQL function psoft_discrimination_data() line 136 at SQL statement Batch entry 0 select psoft5_v_local.PSOFT_DISCRIMINATION_DATA() was aborted. Call getNextException to see the cause.

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Peoplesoft - Error while executing Batch select PSOFT DISCRIMINATION

Mon, 01 Jan 0001 00:00:00 +0000

Description

While running the analysis, the tool after analysis Peoplesoft Discrimination with Vanilla tool fail with the error - Error while executing Batch : select PSOFT_DISCRIMINATION(0)

Figure 1

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	❌
CSS2	✅

Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Peoplesoft - O6550 SQL Error PLS - 00201 identifier xyz PSOFT UAMETRICS UPDATE must be declared

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page gives a solution to below error which occurs during PeopleSoft analysis while running the job PeopleSoft Analysis Content Update

Starting SQL TOOL
SQL Error: ORA-O6550 :LINE 4, COL 11
SQL Error:PLS-00201:identifier ‘xyz.PSOFT_UAMETRICS_UPDATE’ must be declared.
SQL Error:ORA-06550;LINE 4, COL 2
SQL Error:PL/SQL :Statment ignored (severity 1,Msg No. 6550)
Failed to launch SQL Queries.

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x	❌
7.2.x	❌
7.0.x	✅

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - PeopleSoft - PSOFT DISCRIMINATION DATA null value in column parent id

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page is a troubleshooting guide for the problem where PeopleSoft Analysis fails while running the content Enrichment job with the below error :

select 01_local.PSOFT_CONTENT_ENRICHMENT()
INF: 2015-09-09 23:09:03: [SQL] select 01_local.PSOFT_DISCRIMINATION_DATA()
ERR: 2015-09-09 23:09:20: Error while executing Batch: select 01_local.PSOFT_DISCRIMINATION_DATA()
Query failed because:
ERROR: null value in column "parent_id" violates not-null constraint
 Detail: Failing row contains (28300, 1600500, null, Subscription, TIME_DEVICE_TASK_VALS_FULLSYNC.TimeDeviceTaskValsFullsync.Subscr..., PPLSOFT, 399302383).
 Where: SQL statement "insert into psoft_objects (object_id,object_type,object_name,object_fullname,object_lastupd,object_checksum,parent_id)
 select t1.idkey,t1.objtyp,t1.keynam,t4.fullname
 ,coalesce((select upd.infval from psoft_wk_lastupd upd where upd.idobj = t1.idkey),'')
 ,coalesce((select upd.infval from psoft_wk_checksum upd where upd.idobj = t1.idkey),0)
 ,case when T1.objtyp < 1600100 then 0 else (select T2.idparent from keypar T2 where T2.idkey = t1.idkey) end
 from keys t1
 join objpro t2 on (t2.idobj = t1.idkey)
 join objfulnam t4 on (t4.idobj = t1.idkey)
 where t2.idpro = L_IDPRO"
PL/pgSQL function psoft_discrimination_data() line 126 at SQL statement
Batch entry 0 select 01_local.PSOFT_DISCRIMINATION_DATA() was aborted. Call getNextException to see the cause.

Note - If this error has occurred while running the vanilla Analysis then it is expected to get the same error while running the analysis of project as well since the project as is an extension of the Vanilla (it includes all Vanilla objects). This page is applicable for Vanilla as well as Project analysis.

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - PL SQL - SQL Error ORA - 00001 unique constraint KB Name

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Following error encountered while running analysis:

SQL Error: ORA-00001: unique constraint (.COL_IDOBJCOLNAM) violated.
SQL Error: ORA-06512: at “.TR_I_COL”, line 64.
Error in Cwmm_import_table( lpszObjectName=‘TQ_CALC2’, Operation=CWMMOP_ALL, lpszOwner=NULL, lpszSchemaName=‘CTR’, &o_nRootCwmmId, szImportMessage ): Incorrect parameters / Internal error

This error had been encountered in CAST version 7.0.4 & 7.0.6

Applicable in CAST Version

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x	❌
7.2.x	❌
7.0.x	✅

Action Plan

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Errors - duplicate key value violates unique constraint pk accidacc

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page provides assistance with resolving the error: duplicate key value violates unique constraint “pk_accidacc” when running an analysis.

The analysis may look like this in the analysis log.

ERROR:  duplicate key value violates unique constraint "pk_accidacc".
DETAIL:  Key (idacc)=(9586593) already exists..
CONTEXT:  SQL statement "insert into Acc (IdAcc, IdClr, IdCle, AccTypLo, AccTypHi, AccTypLo2, AccTypHi2, AccKnd, IdPro, Prop).
  select distinct IdAcc, INTERNAL_SOURCE_ID, INTERNAL_TARGET_ID, AccTypLo, AccTypHi, 0, 0, 0, IDPRO, PROP  .
    from TMP_WK_RESACC t.
  where t.STATUS = 'I'.
    and t.LINK_KIND='N'".
PL/pgSQL function amt_f_maj_lnkmain(integer) line 90 at SQL statement.
SQL statement "select AMT_F_MAJ_LNKMAIN (I_IDSESSION)".
PL/pgSQL function amt_f_maj_objmain(integer) line 111 at SQL statement.
SQL statement "select AMT_F_MAJ_OBJMAIN (I_IDSESSION)".
PL/pgSQL function amt_f_maj_kb_obj(integer) line 24 at SQL statement.
SQL statement "select AMT_F_MAJ_KB_OBJ (I_IDSESSION)".
PL/pgSQL function amt_f_maj_kb(integer) line 24 at SQL statement.
SQL statement "select AMT_F_MAJ_KB (I_IDSESSION)".
PL/pgSQL function cache_flushdata(integer) line 40 at SQL statement (Severity 1, Msg No 1).

Observed in CAST Version

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Errors - ORA-04045 errors during recompilation revalidation

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution for the fatal error Sql Error ORA 04045 encountered during J2EE application analysis shown in the below analysis log :

Merging objects on server . . .

Merge completed.
SQL Error: ORA-04045: errores durante la recompilación/revalidación de .CLEANUPEXTERNALPROJECTS.
SQL Error: ORA-04027: autointerbloqueo durante la validación automática del objeto .PROJECT_DELETE.
SQL Error: ORA-06508: PL/SQL: no se ha encontrado la unidad de programa llamada : “.CLEANUPEXTERNALPROJECTS”.
SQL Error: ORA-06512: en “.INT_FINAL_JOBANA”, línea 100.
SQL Error: ORA-06512: en línea 1.
SQL Error: ORA-06512: en “.FINAL_JOBANA”, línea 70.

CMS Snapshot analysis - Run Analyzer - Fatal Error - SQL Error - syntax error at or near and transaction aborted

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

This error is common to some of the Analyzers (as reported till now for J2ee and Mainframe) where the analysis log contains SQL ERROR.
Error found on the log :

SQL Error: ERROR: syntax error at or near “.”
SQL Error: LINE 1: … select convert(smalldatetime,crdate) from master..sysdataba….
SQL Error: ^ (Severity 1, Msg No 1).
SQL Error: ERROR: current transaction is aborted, commands ignored until end of transaction block (Severity 1, Msg No 1).
Invalid value 1200 for T-SQL version!
Invalid value 1200 for T-SQL version: function call ignored!_histsqlresword(): Error - T-SQL version #759448096 given to this function is unhandled!

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Value too long for type character varying

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page will help you to find a solution, if your analysis is failing with the below mentioned error and can be seen in the analysis log file.

SQL Error: ERROR: value too long for type character varying(30).
SQL Error: CONTEXT: PL/pgSQL function i_opetrack(integer,character varying) line 13 at SQL statement.
SQL Error: SQL statement “select I_OpeTrack (1 /*CWMM_UPDATE_STATISTICS*/, ‘UpdateStats : AppW stat updated’)”.
SQL Error: PL/pgSQL function updateappwarehousestats() line 47 at SQL statement (Severity 1, Msg No 1).

CMS Snapshot Analysis - Run Analyzer - Fatal Error - SQL Error - Violation of PRIMARY KEY constraint XXX Cannot insert duplicate key in object XXX

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Following Error/warning encountered while analyzing the .Net or UA Analysis

SQL Error: Violation of PRIMARY KEY constraint ‘PK_KeyPar’. Cannot insert duplicate key in object ‘dbo.KeyPar’.
SQL Error: The CREATE UNIQUE INDEX has been interrupted because a duplicate key was found for object ‘dbo. AccLinkSymb_00000005E93E #’ and index ‘IDX_TmpAccLinkS’ . Duplicate key value:
SQL Error: The statement has been terminated.

SQL Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint ‘PK_ACCIDACC’. Cannot insert duplicate key in object ‘dbo.Acc’. The duplicate key value is (729782). (Severity 1, Msg No 2627).