1

Exact Match Flag

C_REPOS_TABLE.EXACT_MATCH_ OBJ_IND = 0

Fuzzy Match Base Object

N/A

2

Exact Match Flag

C_REPOS_TABLE.EXACT_MATCH_ OBJ_IND = 1

Exact Match Base Object

N/A

3

Exclude From Match flag

Exclude from Match flag not enabled

N/A

4

Exclude From Match flag

Count of BaseObject Records.exclude_from_match = 1

Exclude from Match flag enabled for the BaseObject. %,d records(flagged as 1) to be excluded for tokenization

Review the records with exclude_from_match =1 status to confirm.

5

Exclude From Match flag

Count of BaseObject Records.exclude_from_match = 1

Exclude from Match flag enabled for the Base Object. No record(flagged as 1) to be excluded for tokenization

N/A

6

Dirty Indicator

Count of BaseObject Records which are the records in <BO_NAME>_DRTY table

%,d records(flagged with dirty indicator as 1) to be tokenized

Execute "Tokenization" job to tokenize records.

7

Dirty Indicator

Count of BaseObject Records which are the records not in <BO_NAME>_DRTY table

No records (flagged as dirty indicator as 1) available to be tokenized

N/A

8

Tokens in <BO>_STRP table

Count of <BO>_STRP records

%s table is empty. No tokens available

Execute "Tokenization" job to tokenize records.

9

Tokens in <BO>_STRP table

Count of <BO>_STRP records

%,d tokens available in %s table

You might re-execute tokenization job if additional tokens must be created.

10

Hub State Indicator

C_REPOS_TABLE.match_pending_ind = 1 and BaseObject Records.hub_state_ind not in (0,1) and dirty indicator as 1

Match Pending records flag is enabled on the Base Object. %,d soft deleted records(hub state indicator as -1) not be tokenized

To tokenize such records, either update match pending indicator flag or hub state indicator flag.

11

Hub State Indicator

C_REPOS_TABLE.match_pending_ind = 1 and "No" Base Object Records.hub_state_ind not in (0,1) and dirty indicator as 1

Match Pending records flag is enabled on the Base Object. No soft deleted records(hub state indicator as -1) will be tokenized

N/A

12

Hub State Indicator

C_REPOS_TABLE.match_pending_ind = 0 and BaseObject Records.hub_state_ind in (0,1) and dirty indicator as 1

Match Pending records flag is disabled on the Base Object. %,d pending/soft deleted records (hub state indicator as 0 or -1) not to be tokenized

To tokenize such records, either update match pending indicator flag or hub state indicator flag.

13

Hub State Indicator

C_REPOS_TABLE.match_pending_ind = 0 and "No" BaseObject Records.hub_state_ind in (0,1) and dirty indicator as 1

Match Pending records flag is disabled on the Base Object. No pending/soft deleted records (hub state indicator as 0 or -1) will be tokenized

N/A

14

Consolidation Indicator

Count of BaseObject Records.Consolidation Ind = 9 and Dirty Ind = 1

%,d records(flagged with consolidation indicator as 9) are marked on-hold and will not be tokenized

To tokenize such records, update the consolidation indicator.

15

Consolidation Indicator

Count of BaseObject Records.Consolidation Ind = 9 and Dirty Ind = 1

No records (flagged with consolidation indicator as 9) are marked on-hold

N/A

16

NLS Length Semantics

NLS_LENGTH_SEMANTICS = CHAR and C_REPOS_DB_RELEASE.column_length_in_bytes_ind = 0

NLS_LENGTH_SEMANTICS is CHAR and COLUMN_LENGTH_IN_BYTES is 0

N/A

17

NLS Length Semantics

NLS_LENGTH_SEMANTICS = CHAR and C_REPOS_DB_RELEASE.column_length_in_bytes_ind <> 0

NLS_LENGTH_SEMANTICS is CHAR, but COLUMN_LENGTH_IN_BYTES is not marked as 0 (zero)

Set COLUMN_LENGTH_IN_BYTES to 0 if NLS_LENGTH_SEMANTICS is CHAR

18

NLS Length Semantics

NLS_LENGTH_SEMANTICS = BYTE and C_REPOS_DB_RELEASE.column_length_in_bytes_ind = 1

NLS_LENGTH_SEMANTICS is BYTE and COLUMN_LENGTH_IN_BYTES is 1

N/A

19

NLS Length Semantics

NLS_LENGTH_SEMANTICS = BYTE and C_REPOS_DB_RELEASE.column_length_in_bytes_ind <> 1

NLS_LENGTH_SEMANTICS is BYTE but COLUMN_LENGTH_IN_BYTES is not marked as 1

Set COLUMN_LENGTH_IN_BYTES to 1 if NLS_LENGTH_SEMANTICS is BYTE

20

NLS Length Semantics

NLS_LENGTH_SEMANTICS not in (BYTE, CHAR)

NLS_LENGTH_SEMANTICS is neither BYTE not CHAR

Set NLS_LENGTH_SEMANTICS to either CHAR or BYTE

21

NLS Character Set

NLS_CHARECTERSET in UTF-8, UTF-16

NLS_CHARACTERSET is %s

N/A

22

NLS Character Set

NLS_CHARECTERSET not in UTF-8, UTF-16

NLS_CHARACTERSET is neither UTF-8 nor UTF-16

Set NLS_CHARACTERSET to either UTF-8 or UTF-16)

23

SIP_POP Column

SIP_POP column not included

N/A

24

SIP_POP Column

SIP_POP column included

SIP_POP column value in BaseObject must match a valid population file name from C_REPOS_SSA_POPULATION table.

25

Fuzzy Match Key

No fuzzy match key column is defined in the base object

Define a fuzzy match key column to participate in the tokenization.

26

Fuzzy Match Key

Physical columns not configured for fuzzy match key

Configure one or more physical columns for the fuzzy match key.

27

Records with NULL Fuzzy Key Columns

Fuzzy match key column(s) : %s [%s] No NULL values on any of the fuzzy match key columns

%s - comma separated key columns
%s - fuzzy match key table

N/A

28

Records with NULL Fuzzy Key Columns

Fuzzy match key column(s) : %s [%s] %,d records have NULL values on fuzzy match key columns

%s - comma separated key columns
%s - fuzzy match key table

NULL values on fuzzy match key columns will generate NULL tokens. Try to keep NOT NULL values on such columns.

29

Check Missing Children

No match path defined

Match paths not defined

N/A

30

Check Missing Children

No match path defined with check missing children as No

No match paths defined with Check Missing Children flag as No

N/A

31

Check Missing Children

Match path defined with check missing children as No

Match paths (%s) defined in base object have Check Missing Children flag as No

If this flag is No, parent records will not be tokenized when any child/grandchild record is missing. And it can affect the search results as well. Set it based on the business requirements .

32

Java Version

Java_Version

Java Version: %s

N/A