Removing the Data Quality Stored Procedures from the Database

Note: Stop the embedded process by using the instructions at Controlling the SAS Embedded Process before following these steps. Stopping the SAS Embedded Process ensures that none of the accelerator files are locked when dq_uninstall.sh attempts to remove them.
The accelerator provides the dq_uninstall.sh shell script for removing the data quality stored procedures from the Teradata database. The dq_uninstall.sh script is located in the /opt/SAS/SASTKInDatabaseServer/9.4/TeradataonLinux/install/pgm directory of the Teradata database server.
The dq_uninstall.sh script requires modification before it can be run. The Teradata administrator must edit the shell script to specify the site-specific Teradata server name and DBC user logon credentials for the DBC_PASS=, DBC_SRVR=, and DBC_USER= variables.
Here is the syntax for executing dq_uninstall.sh:
./dq_uninstall.sh <-l log-path>

log-path

specifies an alternative name and location for the dq_uninstall.sh log. When this parameter is omitted, the script creates a file named dq_uninstall.log in the current directory.

Running dq_uninstall.sh disables the SAS Data Quality Accelerator for Teradata functionality and removes the data quality stored procedures from the database. The dq_uninstall.sh script does not remove the QKB or the SAS Embedded Process from the Teradata nodes. Follow whatever procedure is appropriate at your site for removing the QKB. See Upgrading from or Reinstalling a Previous Version for information about how to uninstall the SAS Embedded Process from the Teradata database. The dq_grant.sh script also does not remove permissions that were granted by dq_grant.sh. You need to remove the permissions in accordance with the procedures used at your site.