Installation Overview

Refer to Supported Database Platforms for information about the supported platforms on which Oracle Utilities Work and Asset Management is verified to operate.

The following types of installation are available for Oracle Utilities Work and Asset Management:

• Initial Install: A database with no demo data

• Upgrade Install: A database upgrade to V2.4.0.1.1

• Demo Install: A database populated with demo data

Prerequisites

The database installation requires:

• Java Development Kit V8.0

This must be installed on the Linux, UNIX or Windows server where the install package will be staged and run.

Creating the Database

For an initial install or demo install you will create an empty database on the Linux/UNIX or Windows database server on which you operate the production instance of Oracle Utilities Work and Asset Management.

1. Create the database using the Database Configuration Assistant (DBCA). Make sure to set character set for database as AL32UTF8 and National Character Set (NLS_NCHAR_CHARACTERSET - AL16UTF16 )

2. Enable the mandatory software options.

• Oracle Spatial OR Oracle Locator

• Oracle Text

3. Run the SQL below to make sure it is successful.

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

Starting with OUAF V4.4.0.0.0, database users are assigned only the minimum set of privileges needed to be able to perform their required job functions. This privilege assignment is based on 'Principle of Least Privilege' and is implemented with a view to make the application more secure.

4. Create default tablespace CISTS_01 and required users and roles.

5. Create the required roles.

CREATE ROLE CIS_ADM NOT IDENTIFIED;

CREATE ROLE CIS_USER NOT IDENTIFIED;

CREATE ROLE CIS_READ NOT IDENTIFIED;

6. Grant privileges to roles.

GRANT CREATE TABLE TO CIS_ADM;

GRANT CREATE VIEW TO CIS_ADM;

GRANT CREATE SYNONYM TO CIS_ADM;

GRANT CREATE MATERIALIZED VIEW TO CIS_ADM;

GRANT CREATE SEQUENCE TO CIS_ADM;

GRANT CREATE INDEXTYPE TO CIS_ADM;

GRANT CREATE ROLE TO CIS_ADM;

GRANT CREATE TRIGGER TO CIS_ADM;

GRANT CREATE PROCEDURE TO CIS_ADM;

GRANT CREATE SYNONYM TO CIS_USER;

GRANT CREATE SYNONYM TO CIS_READ;

7. Create Schema Owner (CISADM).

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

ALTER USER CISADM QUOTA UNLIMITED ON CISTS_01;

8. Grant Privileges and Roles to Schema Owner (CISADM).

GRANT CREATE SESSION TO CISADM;

GRANT CREATE TABLESPACE TO CISADM;

GRANT READ on DBA_TABLESPACES TO CISADM;

GRANT ALTER TABLESPACE TO CISADM;

GRANT UNLIMITED TABLESPACE TO CISADM;

GRANT DROP TABLESPACE TO CISADM;

GRANT EXECUTE on DBMS_UTILITY TO CISADM;

GRANT SELECT_CATALOG_ROLE TO CISADM;

GRANT EXECUTE_CATALOG_ROLE TO CISADM;

GRANT CIS_ADM TO CISADM;

9. Create Read Write User (CISUSER).

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

ALTER USER CISUSER QUOTA UNLIMITED ON CISTS_01;

10. Grant Privileges and Roles to Read Write User (CISUSER).

GRANT CIS_USER to CISUSER;

GRANT CREATE SESSION TO CISUSER;

11. Create Read Only User (CISREAD).

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

ALTER USER CISREAD QUOTA UNLIMITED ON CISTS_01;

12. Grant Privileges and Roles to Read Only User (CISREAD).

GRANT CIS_READ to CISREAD;

GRANT CREATE SESSION TO CISREAD;

13. Create Operational User (CISOPR).

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

GRANT CREATE SESSION,EXP_FULL_DATABASE TO CISOPR;

14. Review the Storage.xml file under the FW45011\Install-Upgrade folder prior to an initial install or upgrade install. This file allocates all base tables and indexes to the default tablespace CISTS_01 and the required users and roles. Information in this file is used by spl-oradbi-<VERSION>.jar while installing the Oracle Utilities Work and Asset Management database objects. Refer to Updating Storage.xml for more details on updating this file.

Note: You will need to review the Storage.xml file, prior to an initial install, to update the default values to custom values (example: TableSpace Name). spl-oradbi-<VERSION>.jar can be executed by a non-schema owner in order 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 Storage.xml 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 the storage.xml file before 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, secure file options, Advanced Compression, and parallel information are used only for new objects. Therefore, for initial installs, information for each object should be reviewed. Be careful while editing this 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, verify that the Database Management System software is installed according to your site standards and the installation guide provided by the database vendor. Also verify that you have necessary licenses to use some of the advanced database features such as Advanced Compression.

Optimizing Storage Allocation

To optimize storage allocation, database administrators should do the following:

1. Create multiple tablespaces with extents sized to store different types of tables/indexes.

2. Edit the Storage.xml file before the install process, to spread tables and indexes across these tablespaces.

Be very careful when editing this file and do not change the basic format.

Tables and indexes can be created in parallel by editing the degree of parallelism. Tablespace, storage options, secure file options, Advanced Compression, and parallel information are used only for new objects. Therefore, for initial installs, information for each object should be reviewed. Make sure that tablespace names being used exist in the database.

Note: Prior to the installation of the database schema for the product, please verify that the Database Management System software is installed according to your site standards and the installation guide provided by the database vendor. Also verify that you have necessary licenses to use some of the advanced database features such as Advanced Compression.

Extended Datatypes

Some of the Oracle Utilities Application Framework application table varchar2 fields require byte size beyond 4000 bytes to store data for new application requirements. To support this requirement the Oracle Utilities Application Framework database should use the Extended Data Types - Oracle database 12c feature (EXTENDED - the 32767 byte limit introduced in Oracle Database 12c applies).

Enable the Extended Data Types by setting DB parameter, max_string_size = EXTENDED.

Follow the instructions provided in Oracle Database online documentation for including this change in your database.

Important! This change in your database environment is mandatory. If not included it will lead to errors during the V4.5.0.1.1 upgrade.