Run 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:
aa9
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:
Run DBcripts Automatically
- 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.
Run Additional DB Script (MSSQL only)
When you run the DB scripts automatically by selecting the Initiate Primary DB option, run the following script (MSSQL only) before starting the Risk Authentication service.
DROP PROCEDURE GETNEXTSEQID;GOCREATE PROCEDURE GETNEXTSEQID@pServer_ID ARADMIN_TXID_SERVER_ID_TYPE,@pInstance_ID ARADMIN_TXID_INSTANCE_ID_TYPE,@pIP_Address ARADMIN_TXID_IP_ADDRESS_TYPE,@pBlock_Size INT,@pReturn_Seq_ID ARADMIN_TXID_USED_SEQ_NUM_TYPE OUTPUTAS DECLARE @lnewseq INT;DECLARE @errorvar INT SET @errorvar = -1 ;SET NOCOUNT ON;SELECT @errorvar = USEDSEQNUM FROM ARADMINTXIDWHERE SERVERID = @pServer_ID AND INSTANCEID = @pInstance_ID;IF @errorvar = -1BEGINSET @pReturn_Seq_ID = 0INSERT INTO ARADMINTXID(SERVERID, INSTANCEID, IPADDRESS, USEDSEQNUM)VALUES (@pServer_ID, @pInstance_ID, @pIP_Address, @pBlock_Size);RETURNENDELSEBEGINSET @pReturn_Seq_ID = @errorvar;SET @lnewseq = @pReturn_Seq_ID + @pBlock_Size;UPDATE ARADMINTXID SET USEDSEQNUM = @lnewseq, IPADDRESS = @pIP_AddressWHERE SERVERID = @pServer_ID AND INSTANCEID = @pInstance_ID;ENDRETURN
Run DB Scripts Manually
Run the required database scripts manually to create the database tables.
Follow these steps:
Verify that you are logged in as the same database user that you created in
Configure Database Server
.- Navigate to the <install_location>/dbscripts/ directory, go to one of the following subdirectories that are based on the database that you are using:
- For Oracle: oracle\
- For Microsoft SQL: mssql\
- Run the scripts in the following order, using the following example as a guide:
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
- db-config-for-common.sqlIf you have installed CA Strong Authentication, donotrun db-config-for-common.sql. It already ran when CA Strong Authentication was installed.
- db-config-for-riskauth.sql
- (Optional -only if you must create the 3D Secure Channel) db-config-for-3dsecure.sql
Only run the script once.
Performance Improvement Recommendation
For both manual and automatic DB initialization, remove the existing indexes from the database as detailed in the following table to improve performance:
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 that the CA Risk Authentication schema are working correctly.
Follow these steps:
- 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.
- 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.0RiskFortCaseManagement 9.0
- Log out from the database console.