Search & Repair

Search & Repair

The Search & Repair UI allows users to perform the following:

  • Search for Data Veracity records (erroneous UDRs or batch files)

  • Change the state

  • Mark Data Veracity records for deletion

  • Force delete Data Veracity records

  • Repair Data Veracity records

Data Veracity - Search

Searching for UDR Input Type

To perform a search for UDR Input Type in Data Veracity, follow the steps below:

Unsupported Data Type for Search

  • Searching or filtering of UDRs with list and map data types are currently not supported by Data Veracity.

  • Searching by filter with Bit Set Field data type is not supported by Data Veracity as well.

  1. To search for UDR Input Type, you must first select a Data Veracity profile. Click the Filter button to open the Search dialog. 


    Data Veracity Search dialog

  2. Click Browse to select the Data Veracity profile.

  3. Select UDR for Input type.

  4. When you have selected UDR for Input type, you can configure the following:

    1. UDR types - Select the specific UDR from a list. You can only choose ONE UDR type to access.
       


      Data Veracity UDR types combo box

    2. Display Fields - Select specific fields (which includes meta data, user defined MIMs and UDR fields) that you would like to display in the query results.


      Display Fields selection dialog box

    3. Search Query - Add the filter rules that you want in the query builder by clicking on Add. If more than one rule is defined, you would be able to choose between AND or OR by clicking on either of the buttons. You could also add a new group of rules by clicking on the Add Group button to define a nested set of rules for the query. When you run a query, rows in the table that matches the expression will be displayed in the Query Results
      For more information, see the Search Query section below.

  5. Click OK to execute the query and the results will be displayed.


    Example Query Result for UDR Input type

Query Results Sort Order

Sorting of search results is done from the Data Veracity Database via SQL query statement and so the sorting behavior will depend on the behavior of the Data Veracity Database(for example, sorting of alphabetical characters in Oracle and SAP HANA is case sensitive, whereas in PostgreSQL it is case insensitive).

Data Veracity State column values is represented as numbers in the Data Veracity Database. State column will be sorted by the order of the numbers assigned to the states where:

  1. NEW

  2. UPDATED

  3. PRE_DELETE

  4. REPROCESSED

  5. DELETE_APPROVED

Searching for Batch Input Type

To perform a search for Batch Input Type in Data Veracity, follow the steps below:

  1. To search for Batch, you must first select a Data Veracity profile. Click the Filter button to open the Search dialog. 


    Data Veracity Search dialog

  2. Click Browse to select the Data Veracity profile.

  3. Select Batch for Input type.

  4. When you have selected Batch for Input type, you can configure the following:

    1. Display Fields - Select specific fields (which includes meta data and user defined MIMs) that you would like to display in the query results.


      Display Fields selection dialog box

    2. Search Query - In the Search Query panel, add the Filter rules that you want in the query builder by clicking on Add. If more than one rule is defined, you would be able to choose between AND or OR by clicking on either of the buttons. You could also add a new group of rules by clicking on the Add Group button to define a nested set of rules for the query. For more information, see the Search Query section below.

  5. Click OK to execute the query and the results will be displayed.


    Example Query Result for Batch Input type

Query Results Sort Order

Sorting of search results is done from the Data Veracity Database via SQL query statement and so the sorting behavior will depend on the behavior of the Data Veracity Database(for example, sorting of alphabetical characters in Oracle and SAP HANA is case sensitive, whereas in PostgreSQL it is case insensitive).

Searching with Saved Filters