The following discussion assumes that the Oracle database instance is created on the command line. However, you are free to use any suitable utility to specify the required parameters. Do the following:

1. Log in to the alternative database system as the oracle user, and run the following commands:

   dbca -silent -createDatabase -gdbName EXPORT_DATABASE_NAME \
      -sid EXPORT_DATABASE_NAME -characterSet AL32UTF8 \
      -templateName Data_Warehouse.dbc -databaseType DATA_WAREHOUSING \
      -redoLogFileSize 500 -initParams recyclebin=off -initParams audit_trail=none 
   

   Where,

   • EXPORT_DATABASE_NAME specifies the literal export database instance name.

   • For performance reasons, it is recommended that the recyclebin and audit_trail features are disabled.

   • The character set instance should be specified as ALT32UTF8.

For performance reasons, it is recommended that you use compressed tablespaces. Do the following:

1. Run the following SQL command as the System Administrator on the alternative database server to enable compression on the USERS tablespace:

   alter tablespace USERS default compress;
   

2. By default, a single 32 GB datafile is created for the USERS tablespace. For most deployments, you will need to add additional table space by running the following SQL command:

   alter tablespace USERS add datafile 'user02.dbf' size 5M autoextend on;
   

   In the command shown above, the default datafile location is specified. You are free to specify an alternative location.

By default, Oracle database maintenance tasks are schedule to run at 22:00. These can have a significant impact on the overall database performance. Therefore, depending on traffic levels within the monitored environment, and the scheduled processes reading the export database tables, you may need to reschedule these maintenance tasks to a period with low traffic/load levels (for example, 03:00). For more information, see Oracle Database Administrator's Guide.

Access to the alternative database requires the creation of an authorized user. Do the following:

1. Run the following commands on the alternative database server to create the RUEI database user with the minimum required privileges:

   create user RUEI_DB_USER_BI
            identified by "password"
            default tablespace USERS
            temporary tablespace TEMP
            profile DEFAULT
            quota 50G on USERS;
   
   alter profile DEFAULT
            limit PASSWORD_LIFE_TIME unlimited;
   
   grant    create session,
            create table
            to RUEI_DB_USER_BI;

   Where,

   • RUEI_DB_USER_BI specifies the export database user name.

   • password specifies the required password variable.

After the alternative Oracle database instance has been defined, the connection data needs to be set up. This requires two files, sqlnet.ora and tnsnames.ora, in the RUEI data directory (RUEI_DATA) on the Reporter system. Do the following:

1. Ensure that the sqlnet.ora file contains the following:

   NAMES.DIRECTORY_PATH = (TNSNAMES)
   SQLNET.WALLET_OVERRIDE = TRUE
   WALLET_LOCATION = (SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=Act number : 12061130003875Name : Pavithra Mendon IFSC -
         hdfc0001206)))
   DIAG_SIGHANDLER_ENABLED = FALSE
   

   Ensure that the DIRECTORY setting points to the directory for RUEI data (RUEI_DATA) specified in the /etc/ruei.conf file.

2. Edit the tnsnames.ora files on the Reporter system. You should add the following:

   RUEI_DB_TNSNAME_BI =(DESCRIPTION=
     (ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=BI_database_server) 
        (PORT=1521)))
     (CONNECT_DATA=(SERVICE_NAME=RUEI_DB_INST_BI)))
   

   Where,

   • BI_database_server specifies the network address (hostname or IP address) of the alternative Enriched data export database server.

   • RUEI_DB_TNSNAME_BI specifies the export database connect string.

   • RUEI_DB_INST_BI specifies the export database instance name.

   Ensure that the HOST setting specifies your database. If you use a host name, ensure that it is also specified in the /etc/hosts setup. However, you can also specify an IP address.

The Reporter requires non-interactive access to the alternative Enriched data export database. In order to achieve this, the Oracle autologin wallet is used to store passwords securely. A wallet should already exist to connect to the Reporter database. Do the following:

1. Run the following command to add the new credentials to the existing wallet files ewallet.p12 and cwallet.sso:

   mkstore -wrl RUEI_DATA -createCredential RUEI_DB_TNSNAME_BI RUEI_DB_USER_BI
   

   Where,

   • RUEI_DB_TNSNAME_BI specifies the export database connect string.

   • RUEI_DB_USER_BI specifies the user of the remote database.

   You are prompted for the wallet password and the database password for RUEI_DB_USER_BI.

2. Ensure that the permissions for these files are set correctly. Both files should have the ownership of RUEI_USER and RUEI_GROUP. The ewallet.p12 file only needs to be readable by the RUEI_USER, but both files need to be readable by RUEI_GROUP.

3. If the database instance has been set up correctly, it should now be possible to access the export database without being prompted for the password. The RUEI_USER on the Reporter system can access the database instance as follows:

   sqlplus /@RUEI_DB_TNSNAME_BI
   

   If this step fails, you should carefully review the procedure described so far before proceeding.

1. Edit the /etc/ruei.conf configuration file on the Reporter from which you intend to export enriched data. Use the RUEI_DB_TNSNAME_BI setting to specify the export database connect string. For more information, see Check The RUEI Configuration File.

   Note:

   Other than the modification described above, do not make any other changes to the ruei.conf file.

2. Logout and login again as the moniforce user.

3. Restart processing on the Reporter system by running the following command:

   project -restart