Dropping RiskMinder Schema

Note: If for some reason, you want to retain the database schema, then do not proceed with the instructions in this section.

Important! You may be using both CA RiskMinder and CA AuthMinder. If you plan to uninstall only RiskMinder, then:

If you had first installed RiskMinder and then installed AuthMinder, first drop the AuthMinder schema and then drop the RiskMinder schema.
If you had first installed AuthMinder and then installed RiskMinder, drop only the RiskMinder schema. You need not drop the AuthMinder schema.

Note that if you plan to uninstall both products, then you can drop the schemas in any order.

Refer to the section, "Uninstalling RiskMinder Server" to proceed with the uninstallation.

To uninstall the RiskMinder database:

Navigate to the following directory:
```
<install_location>/arcot/dbscripts/
```

Based on the database that you are using, navigate to:

For Oracle Database:

<install_location>/arcot/dbscripts/oracle/

For Microsoft SQL:

<install_location>/arcot/dbscripts/mssql/

For MySQL:

<install_location>/arcot/dbscripts/mysql/

Run the scripts in the following order to drop all database tables of RiskMinder and related components:
1. Run drop-riskfort-3.1.sql.
2. If applicable, run drop-arcot-common-2.0.sql.
3. If you have not installed or upgraded to CA AuthMinder release 7.1, run drop-riskfort-3dsecure-3.1.sql.
  Note: The drop-arcot-common-2.0.sql script is used to remove the schema for Arcot common components. This schema is used by both AuthMinder and RiskMinder. If you have already (successfully) installed AuthMinder, you must not drop this schema because AuthMinder can continue to use it.
If you have no further use for the database user account that you had created for the RiskMinder schema, delete that user account.