Installation Overview

Refer to Supported Database Platforms for information about the supported platforms on which Oracle Utilities Smart Grid Gateway is verified to operate.

The following types of installation are available for Oracle Utilities Smart Grid Gateway:

• Initial Install: A database with no demo data

• Upgrade Install: A database upgrade

• Demo Install: A database populated with demo data

Note: The Oracle Utilities Meter Data Management Database Component is a cumulative package comprising of data used by all the Oracle Utilities Smart Grid Gateway and Oracle Utilities Service Order Management adapters.

The database installation requires a supported version of the Java Development Kit to be installed on the Windows desktop where the install package is staged and run from. Refer to the Supported Platforms section in the Oracle Utilities Smart Grid Gateway Installation Guide for the required Java versions.

For an Initial Install or Demo Install, create an empty database on the Unix or Windows server, and then populate the database with data. For a database Upgrade Install, upgrade the current Oracle Utilities Smart Grid Gateway database.

Create the database using the Database Configuration Assistant (DBCA). Refer to the Master Note: Overview of Database Configuration Assistant (DBCA) (Doc ID 1488770.1) on My Oracle Support.

Make sure to set the character set for database as follows:

• Character set for the database (AL32UTF8)

• National Character Set ( NLS_NCHAR_CHARACTERSET - AL16UTF16 )

While prior versions of the product have included the cdxdba programs (cdxdba.plx for UNIX or CDXDBA.exe for Windows), this is no longer supported going forward, and the Database Configuration Assistant should be used instead.

Enable Mandatory Software Options

• Oracle Spatial OR Oracle Locator

• Oracle Text

Run the following SQL to ensure it is successful:

SELECT COMP_NAME,STATUS FROM DBA_REGISTRY WHERE COMP_NAME IN ('Spatial','Oracle Text');

Create default tablespace CISTS_01 and required users and roles as follows:

CREATE TABLESPACE CISTS_01 LOGGING DATAFILE '/<db_file_location>/oradata/<DB_NAME>/cists01.dbf' SIZE 1024M REUSE AUTOEXTEND ON NEXT 8192K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Create required role:

CREATE ROLE CIS_USER;

CREATE ROLE CIS_READ;

Create Users:

CREATE USER CISADM IDENTIFIED BY CISADM DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP PROFILE DEFAULT;

GRANT UNLIMITED TABLESPACE TO CISADM WITH ADMIN OPTION;

GRANT SELECT ANY TABLE TO CISADM;

GRANT CREATE DATABASE LINK TO CISADM;

GRANT CONNECT TO CISADM;

GRANT RESOURCE TO CISADM;

GRANT DBA TO CISADM WITH ADMIN OPTION;

GRANT CREATE ANY SYNONYM TO CISADM;

GRANT SELECT ANY DICTIONARY TO CISADM;

CREATE USER CISUSER PROFILE DEFAULT IDENTIFIED BY CISUSER DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT SELECT ANY TABLE TO CISUSER;

GRANT CIS_USER TO CISUSER;

GRANT CIS_READ TO CISUSER;

GRANT CONNECT TO CISUSER;

CREATE USER CISOPR PROFILE DEFAULT IDENTIFIED BY OPRPLUS DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT CONNECT,RESOURCE,EXP_FULL_DATABASE TO CISOPR;

CREATE USER CISREAD IDENTIFIED BY CISREAD DEFAULT TABLESPACE CISTS_01 TEMPORARY TABLESPACE TEMP;

GRANT SELECT ANY TABLE TO CISREAD;

GRANT CIS_READ TO CISREAD;

GRANT CONNECT TO CISREAD;

Review the Storage.xml file prior to an Initial Install or Upgrade Install. Information in this file is used by OraDBI.jar while installing and upgrading the Oracle Utilities Smart Grid Gateway database objects.

Note: Even if you have created the database without using the CDXDBA script, you will still need to review the Storage.xml file, prior to an initial install, to update the default values to custom values (for example: TableSpace Name).

OraDBI.jar can be executed by a non-schema owner to upgrade the database. The Initial Install still needs to be done by the schema owner.

If you decide to allocate some tables or indexes outside of the default tablespace, change the tablespace name from the default value to a custom value in the Storage.xml file.

For instance, if you decide to allocate table CI_ACCT in a tablespace MyTablespace, change.

The Storage.xml file is as shown:

<CI_ACCT>

<TABLESPACE>MyTablespace</TABLESPACE>

</CI_ACCT>

For optimum storage allocation, database administrators should create multiple tablespaces with extents sized to store different types of tables/indexes. They can then edit this file before each upgrade and install process, to spread tables and indexes across these tablespaces. Tables and indexes can be created in parallel by editing degree of parallelism.

Tablespace, storage options, securefile options, Advanced Compression, and parallel information are used only for new objects. Therefore, for initial installs, information for each object should be reviewed. For upgrades, only tablespace information for objects added in the current release needs to be reviewed. Be careful while editing the Storage.xml file. Make sure that tablespace names being used exist in the database. Do not change the basic format of this file.

Note: Prior to the installation of the database schema for the product, please ensure that the Database Management System software is installed according to your site standards and the installation guide provided by the database vendor.