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
  • Multidomain MDM 10.4 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Configuration Guide

Configuration Guide

Back Next

Requirements for Defining Schema Objects

Requirements for Defining Schema Objects

This section describes requirements for configuring schema objects.
Make Schema Changes Only in the
Hub Console
The MDM Hub maintains schema consistency, provided that all model changes are done using the
Hub Console
 tools, and that no changes are made directly to the database. The MDM Hub provides all the tools required for maintaining the schema.
Think Before You Change the Schema
Schema changes can involve risk to data and should be approached in a managed and controlled manner. You should plan the changes to be made and analyze the impact of the changes before making them. You must also back up the database before making any changes.
You Must Have a Write Lock to Change the Schema
In order to make any changes to the schema, you must have a write lock.
Rules for Database Object Names
Database object names cannot be longer than 24 characters.
Reserved Strings for Database Object Names
The MDM Hub creates metadata objects that use prefixes and suffixes added to the names you use for base objects. In order to avoid confusion and possible data loss, database object names must not use the following strings as either standalone names or parts of column names (prefixes or suffixes). 
_BVTB
_OPL
_TMGB
BVTX_
TCMO_
TMF_
_BVTC
_ORAW
_TMIN
BVTXC_
TCRN_
TMMA_
_BVTV
_STRP
_TML0
BVTXV_
TCRO_
TMR_
BO1
_STRPT
_TMMA
CLC_
TCSN_
TPBR_
BO2
_T
_TMNX
COCS
TCSO_
TRBX_
_C
_TBKF
_TMP0
CSC_
TCVN_
TUCA_
_CL
_TBVB
_TMST
CTL
TCVO_
TUCC_
C_REPOS_
_TBVC
_TNPMA
EXP_
TCXN_
TUCF_
C_REPAR_
_TBVV
_TPMA
GG
TCXO_
TUCR_
_D
_TC0
_TPRL
HMRG
TDCC_
TUCT_
_DLT
_TC1
_TRAW
LNK
TDEL_
TUCX_
_EMI
_TDEL
_TRLG
M
TDUMP_
TUDL_
_EMO
_TEMI
_TRLT
PRL
TFK_
TUGR_
_GOV
_TEMO
_TSD
S_
TFX_
TUHM_
_HIST
_TEMP
_TSI
T_verify_
TGA_
TUID_
_HUID
_TEST
_TSNU
TBDL_
TGB_
TUK_
_HXRF
_TGA
_TSTR
TBOX_
TGB1_
TUPT_
_JOBS
_TGA1
_TUID
TBXR_
TGC_
TUTR_
_L
_TGB
_TVXR
TCBN_
TGC1_
TVXRD_
_LINK
_TGB1
_VCT
TCBO_
TGD_
TXDL_
_LMH
_TGC
_XREF
TCCN_
TGF_
TXPR_
_LMT
_TGC1
BV0_
TCCO_
TGM_
V_
_MTBM
_TMG0
BV1_
TCGN_
TGMD_
-
_MTCH
_TMG1
BV2_
TCGO_
TGV_
-
_MTFL
_TMG2
BV3_
TCHN_
TGV1_
-
_MTFU
_TMG3
BV5_
TCHO_
TLL
-
_MVLE
_TMGA
BVLNK_
TCMN_
TMA_
-
Reserved Column Names
No part of a user-defined column name can be a reserved word or reserved column name.
For example, LAST_UPDATE_DATE is a reserved column name and must not be used for user-defined columns. Also, you must not use LAST_UPDATE_DATE as part of any user-defined column name, such as S_LAST_UPDATE_DATE.
If you use a reserved column name, a warning message is displayed. For example: 
"The column physical name "XREF_LUD" is a reserved name. Reserved names cannot be used."
You cannot use the following column names in part or in whole for base object column names:
AFFECTED_LEVEL_CODE
PERIOD_REFERENCE TIME
AFFECTED_ROWID_COLUMN
PK_SRC_OBJECT
AFFECTED_ROWID_OBJECT
PKEY_SRC_OBJECT
AFFECTED_ROWID_XREF
PKEY_SRC_OBJECT1
AFFECTED_SRC_VALUE
PKEY_SRC_OBJECT2
AFFECTED_TGT_VALUE
PREFERRED_KEY_IND
AUTOLINK_IND
PROMOTE_IND
AUTOMERGE_IND
PUT_UPDATE_MERGE_IND
CASE_INSENSITIVE_INDX_IND
REPOINTED_IND
CHECKIN_ID
ROOT_IND
CONSOLIDATION_IND
ROU_IND
CREATE_DATE
ROWID
CREATOR
ROWID_GROUP
CROSS_PERIOD_ID
ROWID_JOB
CTL_ROWID_OBJECT
ROWID_KEY_CONSTRAINT
DATA_COUNT
ROWID_MATCH_RULE
DATA_ROW
ROWID_OBJECT
DELETED_BY
ROWID_OBJECT1
DELETED_DATE
ROWID_OBJECT2
DELETED_IND
ROWID_OBJECT_MATCHED
DEP_PKEY_SRC_OBJECT
ROWID_OBJECT_NUM
DEP_ROWID_SYSTEM
ROWID_PERIOD
DIRTY_IND
ROWID_SYSTEM
ERROR_DESCRIPTION
ROWID_TASK
FILE_NAME
ROWID_USER
FIRSTV
ROWID_XREF
GENERATED_XREF
ROWID_XREF1
GROUP_ID
ROWID_XREF2
GVI_NO
ROWKEY
HIST_CREATE_DATE
RULE_NO
HIST_UPDATE_DATE
SDSRCFLG
HSI_ACTION
SEQ
HUB_STATE_IND
SOURCE_KEY
INTERACTION_ID
SOURCE_NAME
INVALID_IND
SRC_LUD
LAST_ROWID_SYSTEM
SRC_ROWID
LAST_UPDATE_DATE
SRC_ROWID_OBJECT
LASTV
SRC_ROWID_XREF
LOST_VALUE
SSA_DATA
MATCH_REVERSE_IND
SSA_KEY
MERGE_DATE
STRIP_DATE
MERGE_OPERATION_ID
TGT_ROWID_OBJECT
MERGE_UPDATE_NULL_ALLOW_IND
TIMELINE_ACTION
MERGE_VIA_UNMERGE_IND
TOTAL_BO_IND
MRG_SRC_ROWID_OBJECT
TREE_UNMERGE_IND
MRG_TGT_ROWID_OBJECT
UNLINK_IND
NULL_INDICATOR_BITMAP
UNMERGE_DATE
NUM_CONTR
UNMERGE_IND
OLD_AFFECTED
UNMERGE_OPERATION_ID
ONLINE_IND
UPDATED_BY
ORIG_ROWID_OBJECT
WIN_VALUE
ORIG_ROWID_OBJECT_MATCHED
XREF_LUD
ORIG_TGT_ROWID_OBJECT
-
You cannot use the following column names in part or in whole for landing table column names:
DEP_PKEY_SRC_OBJECT
ROWID_JOB
ERROR_DESCRIPTION
SRC_ROWID
PKEY_SRC_OBJECT
VERSION_SEQ
ROWID
ONLINE_IND
You cannot use the following words as column names:
CLASS
ROWID
Reserved Words in Oracle environments
You cannot use the following words as column names in an Oracle environments:
ABORT
DIGITS
MAXLOGMEMBERS
ROLES
ACCEPT
DISABLE
MAXTRANS
ROLLBACK
ACCESS
DISMOUNT
MAXVALUE
ROW
ADD
DISPOSE
MIN
ROWID
ADMIN
DISTINCT
MINEXTENTS
ROWLABEL
AFTER
DO
MINUS
ROWNUM
ALL
DOUBLE
MINVALUE
ROWS
ALLOCATE
DROP
MLSLABEL
ROWTYPE
ALTER
DUMP
MOD
RUN
ANALYZE
EACH
MODE
SAVEPOINT
AND
ELSE
MODIFY
SCHEMA
ANY
ELSIF
MOUNT
SCN
ARCHIVE
ENABLE
NATURAL
SECTION
ARCHIVELOG
END
NEXT
SEGMENT
ARRAY
ENTRY
NEXTVAL
SELECT
ARRAYLEN
ESCAPE
NOARCHIVELOG
SEPARATE
AS
EVENTS
NOAUDIT
SEQUENCE
ASC
EXCEPT
NOCACHE
SESSION
ASSERT
EXCEPTION
NOCOMPRESS
SET
ASSIGN
EXCEPTIONS
NOCYCLE
SHARE
AT
EXCEPTION _INIT
NOMAXVALUE
SHARED
AUDIT
EXCLUSIVE
NOMINVALUE
SIZE
AUTHORIZATION
EXEC
NONE
SMALLINT
AVG
EXECUTE
NOORDER
SNAPSHOT
BACKUP
EXISTS
NORESETLOGS
SOME
BASE_TABLE
EXIT
NORMAL
SORT
BECOME
EXPLAIN
NOSORT
SPACE
BEFORE
EXTENT
NOT
SQL
BEGIN
EXTERNALLY
NOTFOUND
SQLBUF
BETWEEN
FALSE
NOWAIT
SQLCODE
BINARY_INTEGER
FETCH
NULL
SQLERRM
BLOB
FILE
NUMBER
SQLERROR
BLOCK
FLUSH
NUMBER_BASE
SQLSTATE
BODY
FOR
NUMERIC
START
BOOLEAN
FORCE
OF
STATEMENT
BY
FOREIGN
OFF
STATEMENT_ID
CACHE
FORM
OFFLINE
STATISTICS
CANCEL
FORTRAN
OLD
STDDEV
CASCADE
FOUND
ON
STOP
CASE
FREELIST
ONLINE
STORAGE
CHANGE
FREELISTS
ONLY
SUBTYPE
CHAR
FROM
OPEN
SUCCESSFUL
CHARACTER
FUNCTION
OPTIMAL
SUM
CHAR_BASE
GENERIC
OPTION
SWITCH
CHECK
GO
OR
SYNONYM
CHECKPOINT
GOTO
ORDER
SYSDATE
CLOB
GRANT
OTHERS
SYSTEM
CLOSE
GROUP
OUT
TABAUTH
CLUSTER
GROUPS
OWN
TABLE
CLUSTERS
HAVING
PACKAGE
TABLES
COBOL
IDENTIFIED
PARALLEL
TABLESPACE
COLAUTH
IF
PARTITION
TASK
COLUMN
IMMEDIATE
PCTFREE
TEMPORARY
COLUMNS
IN
PCTINCREASE
TERMINATE
COMMENT
INCLUDING
PCTUSED
THEN
COMMIT
INCREMENT
PLAN
THREAD
COMPILE
INDEX
PLI
TIME
COMPRESS
INDEXES
POSITIVE
TO
CONNECT
INDICATOR
PRAGMA
TRACING
CONSTANT
INITIAL
PRECISION
TRANSACTION
CONSTRAINT
INTRANS
PRIMARY
TRIGGER
CONSTRAINTS
INSERT
PRIOR
TRIGGERS
CONTENTS
INSTANCE
PRIVATE
TRUE
CONTINUE
INT
PRIVILEGES
TRUNCATE
CONTROLFILE
INTEGER
PROCEDURE
UID
COUNT
INTERSECT
PROFILE
UNDER
CRASH
INTO
PUBLIC
UNION
CREATE
IS
QUOTA
UNIQUE
CURRENT
KEY
RAISE
UNLIMITED
CURRVAL
LANGUAGE
RANGE
UNTIL
CURSOR
LAYER
RAW
UPDATE
CYCLE
LEVEL
READ
USE
DATABASE
LIKE
REAL
USER
DATAFILE
LIMITED
RECORD
USING
DATA_BASE
LINK
RECOVER
VALIDATE
DATE
LISTS
REFERENCES
VALUES
DBA
LOCK
REFERENCING
VARCHAR
DEBUGOFF
LOGFILE
RELEASE
VARCHAR 2
DEBUGON
LONG
REMR
VARIANCE
DEC
LOOP
RENAME
VIEW
DECIMAL
MANAGE
RESETLOGS
VIEWS
DECLARE
MANUAL
RESOURCE
WHEN
DEFAULT
MAX
RESTRICTED
WHENEVER
DEFINITION
MAXDATAFILES
RETURN
WHERE
DELAY
MAXEXTENTS
REUSE
WHILE
DELETE
MAXINSTANCES
REVERSE
WITH
DELTA
MAXLOGFILES
REVOKE
WORK
DESC
MAXLOGHISTORY
ROLE
WRITE
-
-
-
XOR
Reserved Words in IBM DB2 environments
You cannot use the following words as column names in IBM DB2 environments:
ABSOLUTE
DESTROY
LOCALTIME
SAVE
ACTION
DESTRUCTOR
LOCALTIMESTAMP
SAVEPOINT
ADA
DETERMINISTIC
LOCATOR
SCHEMA
ADD
DIAGNOSTICS
LOWER
SCOPE
ADMIN
DICTIONARY
MAP
SCROLL
AFTER
DISCONNECT
MATCH
SEARCH
AGGREGATE
DISK
MAX
SECOND
ALIAS
DISTINCT
MDMALIAS
SECTION
ALL
DISTRIBUTED
MDMNODE
SELECT
ALLOCATE
DOMAIN
MIN
SEQUENCE
ALTER
DOUBLE
MINUTE
SESSION
AND
DROP
MODIFIES
SESSION_USER
ANY
DUMMY
MONTH
SET
ARE
DUMP
NAMES
SETS
ARRAY
DYNAMIC
NATIONAL
SETUSER
AS
EACH
NATURAL
SHUTDOWN
ASC
ELSE
NCHAR
SIZE
ASSERTION
END
NCLOB
SMALLINT
AT
END-EXEC
NEXT
SOME
AUTHORIZATION
EQUALS
NO
SPACE
AVG
ERRLVL
NOCHECK
SPECIFIC
BACKUP
ESCAPE
NONCLUSTERED
SPECIFICTYPE
BEFORE
EVERY
NONE
SQL
BEGIN
EXCEPT
NOT
SQLCA
BETWEEN
EXCEPTION
NULL
SQLCODE
BINARY
EXEC
NULLIF
SQLERROR
BIT
EXECUTE
NUMERIC
SQLEXCEPTION
BIT_LENGTH
EXISTS
OBJECT
SQLSTATE
BLOB
EXIT
OCTET_LENGTH
SQLWARNING
BOOLEAN
EXTERNAL
OF
START
BOTH
EXTRACT
OFF
STATEMENT
BREADTH
FALSE
OFFSETS
STATIC
BREAK
FETCH
OLD
STATISTICS
BROWSE
FILE
ON
STRUCTURE
BULK
FILLFACTOR
ONLY
SUBSTRING
BY
FIRST
OPEN
SUM
CALL
FOR
OPENDATASOURCE
SYSTEM_USER
CASCADE
FOREIGN
OPENQUERY
TABLE
CASCADED
FORTRAN
OPENROWSET
TEMPORARY
CASE
FOUND
OPENXML
TERMINATE
CAST
FREE
OPERATION
TEXTSIZE
CATALOG
FREETEXT
OPTION
THAN
CHAR
FREETEXTABLE
OR
THEN
CHARACTER
FROM
ORDER
TIME
CHARACTER_LENGTH
FULL
ORDINALITY
TIMESTAMP
CHAR_LENGTH
FUNCTION
OUTER
TIMEZONE_HOUR
CHECK
GENERAL
OUTPUT
TIMEZONE_MINUTE
CHECKPOINT
GET
OVER
TO
CLASS
GLOBAL
OVERLAPS
TOP
CLOB
GO
PAD
TRAILING
CLOSE
GOTO
PARAMETER
TRAN
CLUSTERED
GRANT
PARAMETERS
TRANSACTION
COALESCE
GROUP
PARTIAL
TRANSLATE
COLLATE
GROUPING
PASCAL
TRANSLATION
COLLATION
HAVING
PATH
TREAT
COLUMN
HOLDLOCK
PERCENT
TRIGGER
COMMIT
HOST
PLAN
TRIM
COMPLETION
HOUR
POSITION
TRUE
COMPUTE
IDENTITY
POSTFIX
TRUNCATE
CONNECT
IDENTITYCOL
PRECISION
TSEQUEL
CONNECTION
IDENTITY_INSERT
PREFIX
UNDER
CONSTRAINT
IF
PREORDER
UNION
CONSTRAINTS
IGNORE
PREPARE
UNIQUE
CONSTRUCTOR
IMMEDIATE
PRESERVE
UNKNOWN
CONTAINS
IN
PRIMARY
UNNEST
CONTAINSTABLE
INCLUDE
PRINT
UPDATE
CONTINUE
INDEX
PRIOR
UPDATETEXT
CONVERT
INDICATOR
PRIVILEGES
UPPER
CORRESPONDING
INITIALIZE
PROC
USAGE
COUNT
INITIALLY
PROCEDURE
USE
CREATE
INNER
PUBLIC
USER
CROSS
INOUT
RAISERROR
USING
CUBE
INPUT
READ
VALUE
CURRENT
INSENSITIVE
READS
VALUES
CURRENT_DATE
INSERT
READSTEXT
VARCHAR
CURRENT_ROLE
INT
REAL
VARIABLE
CURRENT_TIME
INTEGER
RECONFIGURE
VARYING
CURRENT_TIMESTAMP
INTERSECT
RECURSIVE
VIEW
CURRENT_USER
INTERVAL
REF
WAITFOR
CURSOR
INTO
REFERENCES
WHEN
CYCLE
IS
REFERENCING
WHENEVER
DATA
ISOLATION
RELATIVE
WHERE
DATABASE
ITERATE
REPLICATION
WHILE
DATE
JOIN
RESTORE
WITH
DAY
KEY
RESTRICT
WITHOUT
DBCC
KILL
RESULT
WORK
DEALLOCATE
LANGUAGE
RETURN
WRITE
DEC
LARGE
RETURNS
WRITETEXT
DECIMAL
LAST
REVOKE
YEAR
DECLARE
LATERAL
RIGHT
ZONE
DEFAULT
LEADING
ROLE
DEFERRABLE
LEFT
ROLLBACK
DEFERRED
LESS
ROLLUP
DENY
LEVEL
ROUTINE
DEPTH
LIKE
ROW
DEREF
LIMIT
ROWCOUNT
DESC
LINENO
ROWGUIDCOL
DESCRIBE
LOAD
ROWS
DESCRIPTOR
LOCAL
RULE
Reserved Words in Microsoft SQL Server environments
You cannot use the following words as column names in Microsoft SQL Server environments:
ABSOLUTE
DESC
LEVEL
ROLLUP
ACTION
DESCRIBE
LIKE
ROUTINE
ADA
DESCRIPTOR
LIMIT
ROW
ADD
DESTROY
LINENO
ROWCOUNT
ADMIN
DESTRUCTOR
LOAD
ROWGUIDCOL
AFTER
DETERMINISTIC
LOCAL
ROWS
AGGREGATE
DIAGNOSTICS
LOCALTIME
RULE
ALIAS
DICTIONARY
LOCALTIMESTAMP
SAVE
ALL
DISCONNECT
LOCATOR
SAVEPOINT
ALLOCATE
DISK
LOWER
SCHEMA
ALTER
DISTINCT
MAP
SCOPE
AND
DISTRIBUTED
MATCH
SCROLL
ANY
DOMAIN
MAX
SEARCH
ARE
DOUBLE
MIN
SECOND
ARRAY
DROP
MINUTE
SECTION
AS
DUMMY
MODIFIES
SELECT
ASC
DUMP
MONTH
SEQUENCE
ASSERTION
DYNAMIC
NAMES
SESSION
AT
EACH
NATIONAL
SESSION_USER
AUTHORIZATION
ELSE
NATURAL
SET
AVG
END
NCHAR
SETS
BACKUP
END-EXEC
NCLOB
SETUSER
BEFORE
EQUALS
NEXT
SHUTDOWN
BEGIN
ERRLVL
NO
SIZE
BETWEEN
ESCAPE
NOCHECK
SMALLINT
BINARY
EVERY
NONCLUSTERED
SOME
BIT
EXCEPT
NONE
SPACE
BIT_LENGTH
EXCEPTION
NOT
SPECIFIC
BLOB
EXEC
NULL
SPECIFICTYPE
BOOLEAN
EXECUTE
NULLIF
SQL
BOTH
EXISTS
NUMERIC
SQLCA
BREADTH
EXIT
OBJECT
SQLCODE
BREAK
EXTERNAL
OCTET_LENGTH
SQLERROR
BROWSE
EXTRACT
OF
SQLEXCEPTION
BULK
FALSE
OFF
SQLSTATE
BY
FETCH
OFFSETS
SQLWARNING
CALL
FILE
OLD
START
CASCADE
FILLFACTOR
ON
STATEMENT
CASCADED
FIRST
ONLY
STATIC
CASE
FOR
OPEN
STATISTICS
CAST
FOREIGN
OPENDATASOURCE
STRUCTURE
CATALOG
FORTRAN
OPENQUERY
SUBSTRING
CHAR
FOUND
OPENROWSET
SUM
CHARACTER
FREE
OPENXML
SYSTEM_USER
CHARACTER_LENGTH
FREETEXT
OPERATION
TABLE
CHAR_LENGTH
FREETEXTABLE
OPTION
TEMPORARY
CHECK
FROM
OR
TERMINATE
CHECKPOINT
FULL
ORDER
TEXTSIZE
CLASS
FUNCTION
ORDINALITY
THAN
CLOB
GENERAL
OUT
THEN
CLOSE
GET
OUTER
TIME
CLUSTERED
GLOBAL
OUTPUT
TIMESTAMP
COALESCE
GO
OVER
TIMEZONE_HOUR
COLLATE
GOTO
OVERLAPS
TIMEZONE_MINUTE
COLLATION
GRANT
PAD
TO
COLUMN
GROUP
PARAMETER
TOP
COMMIT
GROUPING
PARAMETERS
TRAILING
COMPLETION
HAVING
PARTIAL
TRAN
COMPUTE
HOLDLOCK
PASCAL
TRANSACTION
CONNECT
HOST
PATH
TRANSLATE
CONNECTION
HOUR
PERCENT
TRANSLATION
CONSTRAINT
IDENTITY
PLAN
TREAT
CONSTRAINTS
IDENTITYCOL
POSITION
TRIGGER
CONSTRUCTOR
IDENTITY_INSERT
POSTFIX
TRIM
CONTAINS
IF
PRECISION
TRUE
CONTAINSTABLE
IGNORE
PREFIX
TRUNCATE
CONTINUE
IMMEDIATE
PREORDER
TSEQUEL
CONVERT
IN
PREPARE
UNDER
CORRESPONDING
INCLUDE
PRESERVE
UNION
COUNT
INDEX
PRIMARY
UNIQUE
CREATE
INDICATOR
PRINT
UNKNOWN
CROSS
INITIALIZE
PRIOR
UNNEST
CUBE
INITIALLY
PRIVILEGES
UPDATE
CURRENT
INNER
PROC
UPDATETEXT
CURRENT_DATE
INOUT
PROCEDURE
UPPER
CURRENT_ROLE
INPUT
PUBLIC
USAGE
CURRENT_TIME
INSENSITIVE
RAISERROR
USE
CURRENT_TIMESTAMP
INSERT
READ
USER
CURRENT_USER
INT
READS
USING
CURSOR
INTEGER
READTEXT
VALUE
CYCLE
INTERSECT
REAL
VALUES
DATA
INTERVAL
RECONFIGURE
VARCHAR
DATABASE
INTO
RECURSIVE
VARIABLE
DATE
IS
REF
VARYING
DAY
ISOLATION
REFERENCES
VIEW
DBCC
ITERATE
REFERENCING
WAITFOR
DEALLOCATE
JOIN
RELATIVE
WHEN
DEC
KEY
REPLICATION
WHENEVER
DECIMAL
KILL
RESTORE
WHERE
DECLARE
LANGUAGE
RESTRICT
WHILE
DEFAULT
LARGE
RESULT
WITH
DEFERRABLE
LAST
RETURN
WITHOUT
DEFERRED
LATERAL
RETURNS
WORK
DELETE
LEADING
REVOKE
WRITE
DENY
LEFT
RIGHT
WRITETEXT
DEPTH
LESS
ROLE
YEAR
DEREF
-
ROLLBACK
ZONE
Reserved Special Characters
The MDM Hub accepts all special characters, but some special characters cause issues in Informatica Data Director. For this reason, do not use the following special characters in MDM Hub attribute display names:
  • ! (exclamation point)
  • ' (single quote)
  • # (number sign)
  • & (ampersand)
  • < (less than symbol)
However, to use the
&
 and
<
 special characters in your SIF CleansePut and Put requests, you can replace them with the following valid string values:
  • Replace
    &
     with
    &amp;
  • Replace
    <
     with
    &lt;
Adding Columns for Technical Reasons
For purely technical reasons, you might want to add columns to a base object. For example, for a segment match, you must add a segment column.
To avoid confusion, Informatica recommends that you differentiate columns added to base objects for technical reasons from columns added for other business reasons. To filter out columns added for technical reasons, prefix the column names with a specific identifier, such as
CSTM_
.
0 COMMENTS
We’d like to hear from you!