Creating Oracle databases and setting up the database server

This topic describes how to set up and configure Oracle database for a TrueSight Network Automation - Data Warehouse installation. For information about the databases supported for use with Network Automation - Data Warehouse, see System-requirements.

While setting up the database described in these instructions, record the database parameter values. You are prompted for the these values during the Network Automation - Data Warehouse installation.

To create the Oracle user

1. On the database server, create a user (for example, BCAN_DWH) for the data warehouse.
   

   Important

   Use the following guidelines for the user name and password:

   • If you are creating user with any other name, do not use any special characters in the name.
   • Database password cannot contain more than 16 characters.
   • Database password cannot contain any special characters, such as the following:
     
     • Exclamation mark (!)
     • Ampersand symbol (&)
     • Dollar symbol ($)
2. Ensure that the database user meets the following requirements:
   • Database user must be able to log on to the database by using the same SID.
   • Database user must have complete control of the databases. Grant the following permissions to the user:
     • connect
     • create function
     • create materialized view
     • create procedure
     • create session
     • create sequence
     • create table
     • create trigger
     • create view
     • drop
     • truncate
     • unlimited tablespace
3. Log on by using the user credentials (avoid changing the password after the product installation).

To set up the database for Oracle RAC environments

If you are using Oracle Real Application Clusters (RAC), after meeting the requirements for using Oracle RAC (see System-requirements), configure the tnsnames.ora file to access the Oracle RAC database server as follows:

1. Navigate to the <Oracle_Client_installation_directory>\client_1\network\admin directory.

2. Locate the tnsnames.ora file and open it for editing.
   The file contents looks similar to the following:

   <TNS_NAME> =
   (DESCRIPTION =
   (ADDRESS_LIST =
   (ADDRESS = (PROTOCOL = TCP)(HOST = <HOST_NAME>)(PORT = 1521))
   )
   (CONNECT_DATA =
   (SERVICE_NAME = <SERVICE_NAME>)
   )
   )
   
3. Edit the following variables in the file:
   • Replace <TNS_NAME> with the service name of your Oracle RAC database instance.
   • Replace <HOST_NAME> with the Oracle RAC database server host name.
   • Replace <SERVICE_NAME> with service name of the Oracle RAC database instance.
4. Save and close the file.

To set up the database for Oracle database 12c environments

In Oracle database 12c, the default value of the SQLNET.ALLOWED_LOGON_VERSION parameter has been updated to 11. Therefore, the database clients using pre-11g JDBC thin drivers cannot authenticate to 12c database servers. In order to work with the existing JDBC thin drivers, you need to modify the sqlnet.ora file, as follows:

1. On the database server, locate the sqlnet.ora file, as follows:
   1. (Oracle 12c) ORACLE_HOME\network\admin
   2. (Oracle 12c RAC) ORACLE_HOME\network\admin and GRID_HOME\network\admin
2. Open the sqlnet.ora file with a text editor.
   Create this file if it does not exist. You can use the sample file located in the ORACLE_HOME\network\admin\sample directory (GRID_HOME\network\admin\sample in case of RAC) to create this file.
3. If the following parameters exist in the file, update them. If they do not exist, add them as follows:
   • SQLNET.ALLOWED_LOGON_VERSION=8
   • SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
   • SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
4. Restart all the database services.

To verify the database server setup

Before starting the installation, verify that the server has enough space and that it meets the following requirements:

• The database server must be accessible from the reporting and application servers in your deployment.
• The Listener and TNS files must be configured correctly to access the database from the application server through JDBC drivers.
• Ensure that there are no port conflicts.