Run the Database Scripts

CA Risk Authentication database scripts create the database schema. Configuring DB imports the schema and the default objects into the primary database instance. This process is known as DB configuration. The Installation wizard prompts you to select the Initialize Primary DB steps with the following options: 
aatest
CA Risk Authentication database scripts create the database schema. Configuring DB imports the schema and the default objects into the primary database instance. This process is known as DB configuration. The Installation wizard prompts you to select the Initialize Primary DB steps with the following options:  
  • To automatically configure the DB instance, click Next to configure the database.
    This feature helps you configure the database easily. 
  • (Optionally) To manually configure the DB instance later, uncheck the selection.
    When you unselect this option, you must execute the DB scripts in the CA Risk Authentication database. Also, you must manually bootstrap and start the service.
Run the database scripts to create the required database tables for CA Risk Authentication and verify the database setup with a simple query.
 
Follow these steps:
 
 Verify that you are logged in as the same database user that you created in Complete Pre-Installation Tasks.
  1. Navigate to the following directory:
    ARCOT_HOME> /
    dbscripts
    /
  2. Navigate to one of the following subdirectories that are based on the database that you are using:
    • For Oracle: oracle\
    • For Microsoft SQL: mssql\ 
  3. Run the scripts in the following order, using the following example:
For Oracle on Linux:
sqlplus username/password @script-name.sql
For Microsoft SQL Server on Windows:
sqlcmd -U username -P password -I -i script-name.sql
  1. db-config-for-common.sql
     If you have installed CA Strong Authentication, do 
    not
     run db-config-for-common.sql. This script already ran when CA Strong Authentication was installed.
  2. db-config-for-riskauth.sql
  3.  
    (Optional) 
    only if you must create the 3D Secure Channel) db-config-for-3dsecure.sql 
Run the script only once.
Performance Improvement Recommendation
To improve performance, remove the existing indexes from the database as detailed in the following table:
Component
Table
Index
Index on Column
 Common 
ARUDSCONFIGAUDITLOG
ARUDSORGANIZATIONAUDITLOG
ARUDSUSERAUDITLOG
ARADMINAUDITTRAIL
IDX_ARUDSCONFIGAUDITLOG_TXTS
IDX_ARUDSORGAUDITLOG_TXTS
IDX_ARUDSUSERAUDITLOG_TXTS
IDX_ARADMINAUDITTRAIL_TS
TXTIMESTAMP
TXTIMESTAMP
TXTIMESTAMP
TIMESTAMP
Risk Authentication
ARRFSYSAUDITLOG
ARRFUPLOADAUDITLOG
ARRFINSTANCEAUDITLOG
ARRFCASEAUDITLOG
ARRFSYSAUDITLOG_3DSECURE
IDX_ARRFSYSAUDITLOG_DL
IDX_ARRFUPLOADAUDITLOG_UDT
IDX_ARRFINSTANCEAUDITLOG_OT
IDX_ARRFCASEAUDITLOG_DC
IDX_ARRFSYSAUDIT3D_DL
DATELOGGED
UPLOADDATETIME
OPERATIONTIME
DTCREATED
DATELOGGED
Verify the Database Setup
After you run the required database scripts, verify the CA Risk Authentication schema.
 
Follow these steps:
 
  1. Log in to the CA Risk Authentication database as the user who installed the database.
     If you are following the upgrade path, then log in to the database as the user who upgraded the database.
  2. Run the following query:
    SELECT SERVERNAME, VERSION FROM ARRFSERVERS;
    If your database scripts succeeded, the following output results from the preceding query:
    SERVERNAME VERSION
    ------------------------- -------
    RiskFort 9.0
    RiskFortCaseManagement 9.0
  3. Log out of the database console.