How Can Maintaining STORMMAN_LOOKUP Database Records Be Simplified? (Doc ID 2123111.1)

Last updated on APRIL 01, 2016

Applies to:

Oracle Utilities Network Management System - Version 1.10.0.6 and later
Oracle Network Management for Utilities - DMS - Version 1.10.0.6 and later
Information in this document applies to any platform.

Goal

Are all 225 entries per ncg region needed?

In the STORMMAN_LOOKUP database table, there are many fields (shift, outage level, ncg, weekday/weekend, etc).  Do you need a row for each combination of these or can you only populate what you will be using so you do not have 225 rows per region for all the combinations.

Example if 'storm type' is not used, do you need 4-5 different entries then, can't you have 1 row for that 1 combination and all storm types would then be the same as the 1.
You are trying to reduce the number of sql statements you have to deal with when modifying ert travel times on the stormman_lookup table.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms