Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • MDM Registry Edition 10.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Defining a System
  4. Flattening IDTs
  5. Link Tables
  6. Loading a System
  7. Persistent-ID (Dynamic Clustering)
  8. Cluster Governance
  9. Static Clustering
  10. Simple Search
  11. Search Performance
  12. Miscellaneous Issues
  13. Limitations
  14. Error Messages

Design Guide

Design Guide

Back Next

Persistent-ID Report Format

Persistent-ID Report Format

Persistent-ID report has a fixed format with the length defined for each element. Ensure that third-party Persistent-ID reports follow the same format.
Use the
Tools
Load PID Report
 menu in the MDM Registry Edition Console Client to load all Persistent-ID reports.
A Persistent-ID report includes the following sections:
  • Persistent-ID Report header
  • Persistent-ID Report
  • End of metadata marker
  • Actual data
Persistent-ID Report Header
The Persistent-ID report header contains the following information:
  • Database. Name of the database. Internal.
  • ViewName. Name of the view. Internal.
Persistent-ID Report
The Persistent-ID report contains the following information:
  • RECID.
     Record ID of the corresponding Identity Table row.
  • CLUSTERING-ID.
     Cluster ID defined by
    Persistent-ID-Prefix
    .
  • SCORE-COUNT.
     Internal. Reserved for future use.
  • SCORE-ACCEPTED.
     Internal. Reserved for future use.
  • CLUSTER.
     Number of the cluster.
  • MAX-SCORE.
     The score achieved by the record when it joins the cluster.
  • IDT Fields.
     Identity Table field layout as defined and in the same order of IDT.
  • The report layout information follows the report details.
The report layout informations contains the following information:
  • Title.
     Header for field metadata that contains the information about the
    Field
     metadata that follows.
  • Field.
     Information for each field that includes the offset, length, and format.
End of metadata marker
End of metadata marker includes a marker that indicates the end of metadata immediately followed by header for field metadata. End of metadata also contains the information about the
Field
 metadata that follows.
Actual Data
Actual data section contains the actual clustering results arranged in the format specified in the metadata.

Report Sample

The following sample report explains the structure of a Persistent-ID report. 
 Section: User-Source-Tables
 create table 
						Idemo ,1
 Sourced_from odb:1:uid/pwd@svc
 		#SSA_SRC_UID#.IDS_01_IDEMO.RECID RECID,
 		#SSA_SRC_UID#.IDS_01_IDEMO.ids_SourceId SourceId,
 		#SSA_SRC_UID#.IDS_01_IDEMO.ids_Name Name ,
 		#SSA_SRC_UID#.IDS_01_IDEMO.ids_Addr Address ,
 select_by IDS_CL_ID IS NULL OR IDS_CL_ID =	
''
;
*

Section: Views 
view-definition
*==============
NAME=post-view
FIELD=RECID , N, 10
FIELD=CLUSTERING-ID , C,2
FIELD=CLUSTER-SRC , N,10
FIELD=SCORE-COUNT, R, 6
FIELD=SCORE-ACCEPTED, R, 4
FIELD=ATTRIBUTES, N, 3
FIELD=Cluster, N, 10
FIELD=Max-Score, N, 3
FIELD=SourceId, F, 10
FIELD=Name , C, 50
FIELD=Address , C, 75
FIELD=CL_ID, C,2
*
*
The following table describes the fields in the Persistent-ID report with the offset and length for each element:
Offset
Length
Description
0
1034
Reserved for database file name ( Persistent-ID Report Header )
1035
1034
ViewName (Persistent-ID Report Header )
2069
1034
Persistent-ID Report Header
3103
1034
Persistent-ID Report Field definition - Field (
RECID
 )
4137
1034
Persistent-ID Report Field definition - Field (
CLUSTERING-ID
 )
5171
1034
Persistent-ID Report Field definition - Field (
CLUSTER-SRC
 )
6205
1034
Persistent-ID Report Field definition - Field (
SCORE-COUNT
)
7239
1034
Persistent-ID Report Field definition - Field (
SCORE-ACCEPTED
)
8273
1034
Persistent-ID Report Field definition - Field (
ATTRIBUTES
)
9307
1034
Persistent-ID Report Field definition - Field (
Cluster
)
10341
1034
Persistent-ID Report Field definition - Field (
Max-Score
)
11375
1034
Persistent-ID Report Field definition - Field (
SourceId
)
12409
1034
Persistent-ID Report Field definition - Field (
Name
)
13443
1034
Persistent-ID Report Field definition - Field (
Address
)
14477
1034
Persistent-ID Report Field definition - Field (
CL_ID
15511
1034
End of Meta Data marker
16545
VARIABLE
(Size of View Layout)
IDT Record 1
16545 +
VARIABLE
VARIABLE
 (Size of View Layout)
IDT Record 2
A sample Persistent-ID report is as follows: 
DataBase: sdb:file:C:\InformaticaMDMRE910\ids\dpnin6g.pr\ids
ViewName: post-view
Title:     #     FieldName     Off   Len   Fmt
Field:     00000 RECID         00000 00010 N
Field:     00001 CLUSTERING-ID 00010 00002 C
Field:     00002 CLUSTER-SRC   00012 00010 N
...
Field:     00022 CL_ID         00398 00002 C
EndOfMeta: #     FieldName     Off   Len   Fmt

0000000001M20000000000...
0000000005  0000000000...                           
0000000002M20000000000...
...
In the sample report, 0000000001M20000000000 indicates
RECID
 as 0000000001,
CLUSTERING-ID
 as M2, and
CLUSTER-SRC
 as 0000000000.
0 COMMENTS
We’d like to hear from you!