When attempting to set up the Masking Configuration, TDM Portal is able to connect to the database containing our seed lists, but we are getting the error message:
Failed to save DB Seedlist Configuration
The specified schema (if any) does not exist for the connection profile <PROFILENAME>
All supported releases of TDM Portal
Looking at the connect profile being used, we found that the connection profile is not using a specified named schema.
It's recommended to specify the schema name in the Oracle connection profile, by selecting the 'Use named schema' radial button and providing the proper schema name for the connection profile. Also, when working with Oracle databases, case-sensitivity can come into play for Schema names,Table names, etc.
Changing the Connection profile, to include the specified named schema (using the proper case), and changing the table name (using proper case), in the Masking Configuration page, to GTSRC_REFERENCE_DATA resolved this issue.
NOTE: it's recommended to list out all the 'Seedlist Value Columns' defined in the seedlist table. For example, when using the GTSRC_REFERENCE_DATA table, there's a total of 30 rd_ref-vlue columns.
The 'Seedlist Value Columns' field would need to include all possible values:
rd_ref_value,rd_ref_value2,rd_ref_value3,rd_ref_value4,rd_ref_value5,rd_ref_value6,rd_ref_value7,rd_ref_value8,rd_ref_value9,rd_ref_value10,rd_ref_value11,rd_ref_value12,rd_ref_value13,rd_ref_value14,rd_ref_value15,rd_ref_value16,rd_ref_value17,rd_ref_value18,rd_ref_value19,rd_ref_value20,rd_ref_value21,rd_ref_value22,rd_ref_value23,rd_ref_value24,rd_ref_value25,rd_ref_value26,rd_ref_value27,rd_ref_value28,rd_ref_value29,rd_ref_value30