Empty Connectors list while importing metadata in Infosphere Information Server v8.7 Identifying dangling or unbalanced references in IBM InfoSphere Xmeta repository

Problem(Abstract)

Empty Connectors list while importing metadata in Infosphere Information Server v8.7

Identifying dangling or unbalanced references in IBM InfoSphere Xmeta repository

Agent Connection Error : Failed to create connection.

Cause

There is a dangling reference on xmeta that needs to be replaced with the object's RID found in the logs

Diagnosing the problem

In SystemOut.log , there is a record like "An inconsistent graph was read from the repository. Encountered reference to non-existent object from an instance of "ASCLModel.Connector"

XmetaDiagnosticReport.xml log file obtained after running ISALite Xmeta Diagnostic Test displays the following record :

<log4j:eventlogger="com.ascential.xmeta.diagnostic.probes.database.danglingreferences.DanglingReferencesProbe" timestamp="1352894335920" level="ERROR" thread="org.apache.commons.launcher.ChildMain">
<log4j:message><![CDATA[A dangling reference was found!
Dangling Reference Information:

Rid of object with dangling reference: b1c497ce.54ec142d.modjlca5q.81eudlr.0s3ge1.v9tmqfpsrmhn6bttqg690
Package nsUri of object with dangling reference:
http:///4.0/ASCLModel.ecore
EClass of object with dangling reference:
Connector
Name of reference that is dangling: uses_DataConnection
Rid of object that was not found: b1c497ce.8e4c0a48.214jlt6au.ral4u5f.cqh6d8.jhbiudgk0tus0h0nkn4vq
Package nsUri of object that was not found: http:///4.0/ASCLModel.ecore

EClass of object that was not found: DataConnection]]>
</log4j:message>
</log4j:event>


Resolving the problem

Run ISALite Xmeta Diagnostic Test to locate the dangling reference on xmeta located in DB2

To fix the dangling reference by replacing with the object's RID found on the error on xmeta

  • back up your xmeta
  • run the following query on xmeta
CONNECT TO XMETA;

UPDATE
XMETA.ASCLModel_xmetagen_Connectorb1c497ce
SET
uses_DataConnection_xmeta = CLOB(REPLACE(uses_DataConnection_xmeta,CONCAT(CONCAT(CHR(1),' b1c497ce.8e4c0a48.214jlt6au.ral4u5f.cqh6d8.jhbiudgk0tus0h0nkn4vq'),CHR(1)),CHR(1)))
WHERE
xmeta_repos_object_id_xmeta=' b1c497ce.54ec142d.modjlca5q.81eudlr.0s3ge1.v9tmqfpsrmhn6bttqg690';


XMETA : Xmeta DB Name

Popular posts from this blog

Shrink you container size up to 95%.

alma linux: dnf Module yaml error: Unexpected key in data