The Reporter Database Schema 2 - The Static Tables

Body

This is the second post in a series of three which give an overview of the Reporter Database Schema and its tables, columns, triggers and procedures.

The first one was https://ibm.biz/BdjgV8 which looked at the three dynamic tables - REPORTER_STATUS, REPORTER_JOURNAL and REPORTER_DETAILS.

This post focuses on the static tables.

 

The Static Data Tables: Members, Classes, Conversions, Groups, Names, Types

There are 5 static data tables, which hold non-event data that has been transferred across from the ObjectServer into the reporting RDBMS. They are

REPORTER_MEMBERS

REPORTER_NAMES

REPORTER_CLASSES

REPORTER_GROUPS

REPORTER_CONVERSIONS

These tables hold information from the ObjectServer about user names, group names, classes, types and conversions.

When you

a) add or remove users,

b) change the permissions of existing users

c) add conversions, classes or severities to the ObjectServer,

that information is recorded there. The static tables in the database are populated infrequently and not dynamically like the Reporter status, journal and details tables.

As a result you must transfer their contents either automatically when the gateway starts via the startup.cmd file or manually using  nco_sql.

If the gateway is running on Unix, you can also create a cron job which connects to the gateway via nco_sql at regular intervals to transfer any changes which may

have been made while the gateway is operational.

The following tables list the fields in each of the Netcool/Reporter static tables. Fields that are marked with an asterisk (*) are primary key fields.

 

REPORTER_NAMES maps to master.names in the ObjectServer

Field Name	Field Type	Field Size	Mandatory	Description
Name *	varchar2	64	Yes	Name of the user.
OwnerUID	number	16	Yes	UserID
OwnerGID	number	16	Yes	Maps to OwnerGID field in REPORTER_GROUPS table.
Password	varchar2	64	No	Password for the user
Type	number	4	Yes	Type of user

 

REPORTER_GROUPS maps to master.groups in the ObjectServer

Field Name	Field Type	Field Size	Mandatory	Description
Name *	varchar2	64	Yes	Name of the group
OwnerGID	number	16	Yes	Identifier for group

REPORTER_MEMBERS maps to master.members in the ObjectServer

Field Name	Field Type	Field Size	Mandatory	Description
OwnerUID *	number	16	Yes	Maps to OwnerUID field in REP_AUDIT_OWNERUID table.
OwnerGID *	number	16	Yes	Maps to OwnerGID field in REPORTER_GROUPS table.

 

REPORTER_CLASSES maps to alerts.objclass in the ObjectServer

Field Name	Field Type	Field Size	Mandatory	Description
Class *	number	16	Yes	Unique key field for the table; Class's numeric value.
Name	varchar2	64	Yes	Name of class.
Icon	varchar2	64	No	Path and file name of default icon for tools.
Menu	varchar2	64	No	Name of tools menu (in objmenus table) for the menu associated with this class for tools to be able to display the appropriate menu.

 

REPORTER_CONVERSIONS maps to alerts.conversions in the ObjectServer

Field Name	Field Type	Field Size	Mandatory	Description
ConversionKey *	varchar2	255	Yes	Unique key for the table. Internal sequencing string (comprised of Colname and Value).
Column_Name	varchar2	255	Yes	Name of column this conversion is appropriate for.
Value	number	16	Yes	Numeric value for conversion.
Conversion	varchar2	255	Yes	String value for conversion.

 

 

Other Static, Non-Event Related Tables

 

REP_SEVERITY_TYPES stores the severity names associated with the six severity numbers (0-5), while REP_TIME_PERIODS

provides the number of days elapsed since the start of the report.

 

REP_SEVERITY_TYPES

Field Name	Field Type	Field Size	Mandatory	Description
Severity *	number	16	Yes	Severity number.
Name	varchar2	64	Yes	Severity name, for example “Minor”.

 

REP_TIME_PERIODS

Field Name	Field Type	Field Size	Mandatory	Description
Elapsed_Period *	number	16	Yes	Days elapsed values from 1 to 365.
Period_Name	varchar2	64	Yes	Elapsed period text in the format n days.

 

 

Related links:

Configure the JDBC Gateway for nco_sql access on Linux

Update static Reporter tables regularly - Unix only

 

The next post in this series looks at:

REP_AUDIT_SEVERITY

REP_AUDIT_ACKNOWLEDGE

REP_AUDIT_OWNERUID

REP_AUDIT_OWNERGID

Triggers

Stored Procedures

 

Other blogs in this series:

Historical Database Gateways - An Overview https://ibm.biz/BdjeyS
Reporter Database Schema 1 – The Dynamic Tables https://ibm.biz/BdjgV8
Reporter Database Schema 3 – The Audit Tables https://ibm.biz/BdjAHH

 

Subscribe and follow us for all the latest information directly on your social feeds:

 

 

  

Check out all our other posts and updates:
Academy Blogs:	https://goo.gl/eZjStB
Academy Videos:	https://goo.gl/kJeFZE
Academy Google+:	https://goo.gl/HnTs0w
Academy Twitter :	https://goo.gl/DiJbvD