04_OS86074EN41GLN0_Admin Tasks for Reporting

8/18/2019 04_OS86074EN41GLN0_Admin Tasks for Reporting

http://slidepdf.com/reader/full/04os86074en41gln0admin-tasks-for-reporting 1/28

1 © Nokia Siemens Networks OS86074EN41GLN0

Administrative Tasks for

ReportingOSS4.1, Reporter3.2

SCNNOCREP




Legal notice

Intellectual Property Rights All copyrights and intellectual property rights for Nokiatraining documentation, product documentation and slidepresentation material, all of which are forthwith known as

Nokia training material, are the exclusive property of Nokia.Nokia owns the rights to copying, modification, translation,adaptation or derivatives including any improvements ordevelopments.

Nokia has the sole right to copy, distribute, amend, modify,develop, license, sublicense, sell, transfer and assign theNokia training material. Individuals can use the Nokiatraining material for their own personal self-development

only, those same individuals cannot subsequently pass onthat same Intellectual Property to others without the prior




Trainer Guide in Note Page




Module Objectives

At the end of this module the trainee will be able to:

Check, if a measurement is active and produces countervalues using MML and KPI Browser.

Check, if a measurement is active and produces countervalues by using SQL.

Explain the structure of the OSS database structure for SCNPerformance Measurements.

Outline the relationship between raw measurements tables

and views and the corresponding naming conventions.Demonstrate basic SQL commands to check the PM

database tables and the object tables in the OSSdatabase.




Administrative Tasks for Reporting

Checking the PM database with MML and KPI Browser

Structure of PM database for SCN measurementsChecking the PM Database with SQL




Check a specific MSC measurementwith MML




Check MSC measurementswith MML








Database Tables and Views

table view

Summary tables for reporter

RAW Tables

Views

Raw views for report

Summary views for reporter

Benefits•longer storeperiod•Speed upprocess

Profile

•Time and

element

•Daily atmidnight

•Weekly at

Monday

morning




Database views

User views are created on top of each measurement table. You shouldalways use suitable views to access the database instead of accessingthe tables directly.

The view names and table names have different prefixes. Table nameshave the prefix P _ whereas view names have the prefix PS _ or PV _.

Measurement tables, marked with _PV_ are used by the GeneralReporter process, cosprcmx.pl, for writing raw and aggregatedmeasurement data to the NetAct Database

Measurement views, marked with _PS_ are used by the reportingapplications, such as Report Builder, for reading raw and aggregatedmeasurement data from the NetAct Database




Naming of database tablesMSC, HLR and VLR database tables

The names of Reporter database objects (for example, tables, views,primary keys etc) are built according to the following namingconvention:

• <subsystem_abbreviation>_<db.object>_<Reporter.meas.type>_<object level>_<tgr>

All Reporter Nokia 2G/3G Mobile Circuit Switched Core M12 (MSC)database object names start with RNS (=subsystemabbreviation). The values in brackets are placeholders and stand

for:• database object <db.object>, i.e. P_, PV_ or PS_

• <tgr> stands for time granularity: DAY, WEEK, DAYBH,WEEKBH

Example for raw measurements table:

• RNS_P_MEAS_CGR_O2

The following raw view is related to this table:• RNS_PV_CGR_CGRDIR1_RAW




Naming of database tablesVLR, HLR and MGW database tables

VLR and HLR measurements are handled from MSC.

• Example for VLR raw data table M78: RNS_P_MEAS_ VLR MSC_O2• Corresponding name of raw view: RNS_PV_ VLR MSC_MSC_RAW

• Example for HLR raw data table M79: RNS_P_MEAS_HLR SS_O2

• Corresponding name of raw view: RNS_PV_HLRSS_HLR _RAW

All Reporter MGW database object names start with NOKMWW.

According to this, a raw table of measurement type ‘ int f tc ’ , object level‘phyt tp2’ and time level ‘ raw’ leads to a table name:

• NOKMWW _P_INTFTC_PHYTTP2_RAW

where INTFTC stands for interface specific TC measurement andPHYTTP2 for physical interface 2




Checking PM database with SQL

tom:/m/home/omc (104) omc% sqlplus

SQL*Plus: Release 8.1.7.0.0 - Production on Mon Feb 1420:01:19 2005

(c) Copyright 2000 Oracle Corporation. All rights reserved.

Enter user-name: rdr Enter password:

Connected to:Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bitProductionJServer Release 8.1.7.4.0 - 64bit Production

SQL>

tom:/m/home/omc (104) omc% sqlplus

SQL*Plus: Release 8.1.7.0.0 - Production on Mon Feb 1420:01:19 2005

(c) Copyright 2000 Oracle Corporation. All rights reserved.

Enter user-name: rdr Enter password:

Connected to:Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bitProductionJServer Release 8.1.7.4.0 - 64bit Production

SQL>

• Open an Xtermwindow and start an

SQL session with:

“sqlplus”

• Enter username and

password, e.g. rdr/rdr

• Open an Xtermwindow and start an

SQL session with:

“sqlplus”

• Enter username and

password, e.g. rdr/rdr




Trainer Guide in Note Page




MSC Managed Object Classes and Ids

BSCM

NWLA

BTSM

NEMU

SGSM

NEMU

MSC

PCM

HLR

PCM

LA

SRR NEMU

15

107

110

114

145

15

146

469

485

108

485

MGW

757

485581




CN Managed Object Classes and IDs

SQL> select oc_id,oc_abbreviation fromutp_object_class order by oc_abbreviation;

OC_ID OC_ABBREVIATION

---------- --------------------1157 A2NE

1158 A2ST

2 ACLO

140 ACP

730 ADAP1 ADCE

: :

1162 MSA

107 MSC

121 MSFU

: :

463 SGSN

: :

SQL> select oc_id,oc_abbreviation fromutp_object_class order by oc_abbreviation;

OC_ID OC_ABBREVIATION

---------- --------------------

1157 A2NE

1158 A2ST

2 ACLO

140 ACP

730 ADAP1 ADCE

: :

1162 MSA

107 MSC

121 MSFU: :

463 SGSN

: :

• To check the relationshipbetween Object Class ID andObject Class with SQL, selectoc_id and oc_abbreviationfrom the utp_object_classtable.




Checking the database with SQL

• Using the Object Class ID (e.g. 107 for MSC), you can outputfurther details from the object table.

• Example: Output the names and IDs of all MSCs in theobjects table.

SQL> select name, int_id from objects where object_class=107

NAME INT_ID------------------ ----------MARI1 23761

MILLA 23958MARGE 23595: :

SQL> select name, int_id from objects where object_class=107;

NAME INT_ID------------------ ----------MARI1 23761MILLA 23958MARGE 23595

: :




Checking PM database with SQLSwitching Core M11

SQL> select table_name from all_tables wheretable_name like 'P_MSC_%';

TABLE_NAME------------------------------P_MSC_AC_COUNTP_MSC_AC_VLRP_MSC_ANNP_MSC_AVAIL

P_MSC_CCGRP_DESTP_MSC_CC_CALLSP_MSC_CC_DESTP_MSC_CEP_MSC_CELLP_MSC_CELL_CELL

P_MSC_CG ....

SQL> select table_name from all_tables wheretable_name like 'P_MSC_%';

TABLE_NAME------------------------------P_MSC_AC_COUNTP_MSC_AC_VLRP_MSC_ANNP_MSC_AVAILP_MSC_CCGRP_DESTP_MSC_CC_CALLSP_MSC_CC_DESTP_MSC_CEP_MSC_CELLP_MSC_CELL_CELLP_MSC_CG

.

.

.

.

• The Circuits Switched Coreraw measurement tables inbinary format (up to M11)

start with P_MSC.• To get a listing of all

measurement tables, whichstart with this string, youcan enter the command,shown in the picture on theleft.





SQL> desc P_MSC_CGName Null? Type----------------------------------------- -------- ----------------------------

MEASUREMENT_TIME NOT NULL VARCHAR2(16)MEASUREMENT_DURATION NUMBERINT_ID NOT NULL NUMBERCIRCUIT_GROUP_NBR NOT NULL NUMBERCIRCUIT_GROUP_NAME NOT NULL VARCHAR2(12)CIRCUIT_GROUP_DIRECTION NUMBER

SUM_FLAG NUMBERTIME_CONGESTION_OUT_CIRC NUMBERCALL_CONGESTION_OUT_CIRC NUMBERTOTAL_NBR_CIRCUITS NUMBERAVR_NBR_CARRYING_INC_CIRC NUMBERAVR_NBR_CARRYING_OUT_CIRC NUMBER

NBR_CALLS_INC_CIRC NUMBERNBR_CALLS_OUT_CIRC NUMBERSUCC_CALLS_INC_CIRC NUMBER

::

SQL> desc P_MSC_CGName Null? Type----------------------------------------- -------- ----------------------------MEASUREMENT_TIME NOT NULL VARCHAR2(16)

MEASUREMENT_DURATION NUMBERINT_ID NOT NULL NUMBERCIRCUIT_GROUP_NBR NOT NULL NUMBERCIRCUIT_GROUP_NAME NOT NULL VARCHAR2(12)CIRCUIT_GROUP_DIRECTION NUMBERSUM_FLAG NUMBER

TIME_CONGESTION_OUT_CIRC NUMBERCALL_CONGESTION_OUT_CIRC NUMBERTOTAL_NBR_CIRCUITS NUMBERAVR_NBR_CARRYING_INC_CIRC NUMBERAVR_NBR_CARRYING_OUT_CIRC NUMBERNBR_CALLS_INC_CIRC NUMBER

NBR_CALLS_OUT_CIRC NUMBERSUCC_CALLS_INC_CIRC NUMBER

::

Enter:

Desc

<Name_of_Database>

to see the description ofthe correspondingdatabase table

Enter:

Desc

<Name_of_Database>








SQL> desc RNS_P_MEAS_ULOAD_O2

Name Null? Type

----------------------------------------- --------------- ------------GLOBAL_ID NOT NULL NUMBER

MEO_ID NOT NULL NUMBER

MEASUREMENTTYPE_ID NOT NULL NUMBER

STARTTIME NOT NULL DATEDURATION NUMBER

GEN_ID1 NOT NULL VARCHAR2(255)


:

GCN1 NUMBER

GCN2 NUMBER

GCN3 NUMBER

: :

SQL> desc RNS_P_MEAS_ULOAD_O2

Name Null? Type

----------------------------------------- --------------- ------------GLOBAL_ID NOT NULL NUMBER

MEO_ID NOT NULL NUMBER

MEASUREMENTTYPE_ID NOT NULL NUMBER

STARTTIME NOT NULL DATE

DURATION NUMBER



:

GCN1 NUMBERGCN2 NUMBER

GCN3 NUMBER

: :

Enter:

Desc

<Name_of_Database>

to see the description ofthe corresponding

database table

Enter:

Desc

<Name_of_Database>


Generic number Generic number





In NED, you can find the correspondence between a translation for thCounter names (GNC) and Counter names in View.

In NED, you can find the correspondence between a translation for thCounter names (GNC) and Counter names in View.





SQL> select view_name from all_views whereview_name like ‘RNS_PV%';

VIEW_NAME------------------------------RNS_PV_ACHDEST_DEST4_RAWRNS_PV_ACHHLR_HLR_RAWRNS_PV_ACHSPC_SPC3_RAWRNS_PV_ACVDEST_DEST2_RAW

RNS_PV_ACVMSC_MSC_RAWRNS_PV_ACHSPC_SPC2_RAWRNS_PV_ANN_ANN1_RAWRNS_PV_AVAHLR_SPC5_RAWRNS_PV_AVAMSC_SPC4_RAWRNS_PV_AVANHLR_SLSN5_RAW

RNS_PV_AVANMSC_SLSN4_RAW

::

SQL> select view_name from all_views whereview_name like ‘RNS_PV%';

VIEW_NAME------------------------------RNS_PV_ACHDEST_DEST4_RAWRNS_PV_ACHHLR_HLR_RAWRNS_PV_ACHSPC_SPC3_RAWRNS_PV_ACVDEST_DEST2_RAWRNS_PV_ACVMSC_MSC_RAW

RNS_PV_ACHSPC_SPC2_RAWRNS_PV_ANN_ANN1_RAWRNS_PV_AVAHLR_SPC5_RAWRNS_PV_AVAMSC_SPC4_RAWRNS_PV_AVANHLR_SLSN5_RAWRNS_PV_AVANMSC_SLSN4_RAW

::

• The Mobile Switching Coreviews start with RNS_PV.

• To get a listing of all views,

which start with this string,you can enter thecommand, shown in thepicture on the left.




Checking the database with SQL

You can also copy andpaste Report Descriptionsfrom the Reporting tools toan SQL window e.g. toinvestigate or modify them.

selecttrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD') as "Day0",

'load (MSC Computer Unit Load)' as fact, avg(P_MSC_COMPUTER_LOAD.load) as resultfromP_MSC_COMPUTER_LOAD,nssrc1_computer_unit,objects msc_objectswhereP_MSC_COMPUTER_LOAD.name = nssrc1_computer_unit.nam

e andmsc_objects.object_class = 107 andP_MSC_COMPUTER_LOAD.int_id = msc_objects.int_idand( P_MSC_COMPUTER_LOAD.period_start_time >= (to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS')-(2*7)) and P_MSC_COMPUTER_LOAD.period_start_time < to_dat

e('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD')

selecttrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD') as "Day0",'load (MSC Computer Unit Load)' as fact, avg(P_MSC_COMPUT

ER_LOAD.load) as resultfromP_MSC_COMPUTER_LOAD,nssrc1_computer_unit,objects msc_objectswhereP_MSC_COMPUTER_LOAD.name = nssrc1_computer_unit.nam

e andmsc_objects.object_class = 107 andP_MSC_COMPUTER_LOAD.int_id = msc_objects.int_idand

( P_MSC_COMPUTER_LOAD.period_start_time >= (to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS')-(2*7)) and P_MSC_COMPUTER_LOAD.period_start_time < to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD')





selecttrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD') as "Day0",'load (MSC Computer Unit Load)' as fact, avg(P_MSC_COMPUTER_LOAD.load)

as result fromP_MSC_COMPUTER_LOAD,nssrc1_computer_unit,objects msc_objects

whereP_MSC_COMPUTER_LOAD.name = nssrc1_computer_unit.name andmsc_objects.object_class = 107

andP_MSC_COMPUTER_LOAD.int_id = msc_objects.int_idand( P_MSC_COMPUTER_LOAD.period_start_time >= (to_date('2006.06.19 23:5

9:59', 'YYYY.MM.DD HH24:MI:SS')-(2*7)) and P_MSC_COMPUTER_LOAD.period_start_time < to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD')

selecttrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD') as "Day0",'load (MSC Computer Unit Load)' as fact, avg(P_MSC_COMPUTER_LOAD.load)as result fromP_MSC_COMPUTER_LOAD,nssrc1_computer_unit,objects msc_objects

whereP_MSC_COMPUTER_LOAD.name = nssrc1_computer_unit.name and

msc_objects.object_class = 107andP_MSC_COMPUTER_LOAD.int_id = msc_objects.int_idand( P_MSC_COMPUTER_LOAD.period_start_time >= (to_date('2006.06.19 23:5

9:59', 'YYYY.MM.DD HH24:MI:SS')-(2*7)) and P_MSC_COMPUTER_LOAD.period_start_time < to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD')






as result fromP_MSC_COMPUTER_LOAD,nssrc1_computer_unit,objects msc_objects

where

P_MSC_COMPUTER_LOAD.name = nssrc1_computer_unit.name andmsc_objects.object_class = 107andP_MSC_COMPUTER_LOAD.int_id = msc_objects.int_idand( P_MSC_COMPUTER_LOAD.period_start_time >= (to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS')(2*7)) and P_MSC_COMPUTER_LOAD.period_start_time < to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD')


as result fromP_MSC_COMPUTER_LOAD,nssrc1_computer_unit,objects msc_objectswhereP_MSC_COMPUTER_LOAD.name = nssrc1_computer_unit.name andmsc_objects.object_class = 107andP_MSC_COMPUTER_LOAD.int_id = msc_objects.int_idand( P_MSC_COMPUTER_LOAD.period_start_time >= (to_date('2006.06.19 23:59

:59', 'YYYY.MM.DD HH24:MI:SS')(2*7)) and P_MSC_COMPUTER_LOAD.period_start_time < to_date('2006.06.19 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(P_MSC_COMPUTER_LOAD.period_start_time, 'DD')

C o u

n t e r

i s a v e

r a g e d

C o

u n t e

r i s a v

e r a g e

d

T a b l e

n a m e

T a b l e

n a m

e

C o u n t e

r n a m

e

C o u n t e

r n a m

e

T i m

e p e

r i o d =

d

d - 2 w e e k s

T i m

e p e

r i o d =

d d - 2

w e e k s

O b j e c

t c l a s

s ( M

S C )

O b j e c

t c l a s s (

M S C

)




Version History

Version Date Author Commentsv1.0 19.06.2006 Bettina Baacke First version

v2.0 28.08.2006 Bettina Baacke Updae to OSS4.1

v3.0 07.12.2006 Bettina Baacke Correctiosns and Improvements

Documents

04_OS86074EN41GLN0_Admin Tasks for Reporting