Tablespace creation post installation of CA Strong Authentication

Products

• CA Strong Authentication
• CA Advanced Authentication
• CA Risk Authentication

Issue/Introduction

If you have setup CA Strong Authentication without having ARREPORTS table space the report fetching will show errors. This article helps you to configure the table space post CA Strong Authentication installation.

Environment

Release : 9.1

Cause

During installation CA Strong Authentication, tables space for reports wasn't configured

Resolution

If you missed creating the ARREPORTS tablespace during the installation, please follow the below process of creating ARREPORTS tablespace. It is used to run the reports.

Running Strong Authentication on Oracle requires two tablespaces:

• The first tablespace is used for configuration data, audit logs, and user information. This tablespace can be the default user tablespace.
• The second tablespace is used to run reports. For high performance, it is recommended that you use a separate tablespace.

If the database user running the script has sufficient permissions to create a tablespace, the database configuration script (db-config-for-common-9.1.02.sql) automatically creates the reports tablespace. 

If the user does not have the required permissions, a DBA can manually create the reports tablespace.

Follow these steps in order to create a tablespace:

1. Log in to the Oracle database server as SYS or SYSTEM.
2. Ensure the character set is AL32UTF8.
3. Create a user (the recommended name is arcotuser) in the new database arcotdb.
4. Create the ARREPORTS tablespace to let the user generate reports in Advanced Authentication. Also create a default tablespace for the user for general transactions.
5. Set the quota of user to at least 5 to 10 GB for a development or test deployment, which is primarily used for audit logs. For production this can be set to unlimited.
6. Grant the following privileges to the user:
   • CREATE SESSION
   • CREATE TABLE
   • CREATE SEQUENCE
   • CREATE PROCEDURE

If you have previously added privileges to the user that the user does not require, you can use the following queries to identify and remove them:

• SQL > select *from dba_sys_privs where grantee=’<dbusername>’;
• SQL > revoke <privilege name> from <dbusername>;

Replace <dbusername> with the database user name (arcotuser in these procedures). Replace <privilege name> with the name of the privilege to remove.