Accessing the config.ini File

1. Log in to the server as the user with the required permissions.

2. Navigate to the directory where you have downloaded the installation package.
   For example, /opt/protegrity/databaseprotector/teradata/data/

3. To view the contents within the directory, run the following command:

   /opt/protegrity/databaseprotector/teradata/data #  ls -ltr
   

4. Press ENTER.
   The list of available configurable files appears.

   total 4
   -rw-r----- 1 tdatuser tdtrusted 1058 Oct 14 01:27 config.ini
   

5. To open the config.ini file, run the following command:

   /opt/protegrity/databaseprotector/teradata/data # vim config.ini
   

6. Press ENTER.
   The vim utility starts and the contents of the config.ini file appears.

   ###############################################################################
   # Log Provider Config
   ###############################################################################
   [log]
   
   # In case that connection to fluent-bit is lost, set how audits/logs are handled
   # 
   # drop  : (default) Protector throws logs away if connection to the fluentbit is lost
   # error : Protector returns error without protecting/unprotecting 
   #         data if connection to the fluentbit is lost
   mode = drop
   
   # Host/IP to fluent-bit where audits/logs will be forwarded from the protector
   #
   # Default localhost
   host = localhost
   
   ###############################################################################
   # Protector Config
   ###############################################################################
   [protector]
   
   # cadence is used to decide whether deployment is dynamic or immutable.
   #
   # '0' is used for immutable deployment.
   # Non-negative values other than '0' is used as policy sync interval for dynamic deployment.
   # default cadence value is '60'.
   cadence = 60
   

   For more information about parameters in the config.ini file, refer to Parameters in the config.ini file.

7. To close the config.ini file, run the following command:

   # :q
   

   Important: To reflect any changes made to the config.ini file, you must restart the Teradata Database.

8. To restart the Teradata Database, run the following command:

   # tpareset -f <reason for restart>
   

9. Press ENTER.
   A prompt to continue with restarting the database appears.

   You are about to restart the database
     on the system
        'localhost'
   Do you wish to continue (default: n) [y,n]
   

10. To continue with restarting the database, type y.
    The Teradata Database restarts successfully.