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

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 2^nd 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

When *===CL.abap file is present, the other following files are not parsed, but the bookmark file is created, and results in inconsistency between tables..

1. Run ABAP analysis
2. Analysis fails with the mentioned error- duplicate key value violates unique constraint pk-objdsc

1. Rename file <CAST_AIP_FOLDER>\configuration\Languages\abap\ASTABAPMetaModel.xml in ASTABAPMetaModel.xml.old
2. Replace it with the one attached ASTABAPMetaModel.xml
3. Open ServMan, and on each schema of your triplet, right-click : "Load MetaModel ->From disk"
4. Open Cast-MS and relaunch analysis

Analysis will fail with mentioned error.

Ticket #10233