administering bss network
TRANSCRIPT
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 1/28
DN98619369 © Nokia Corporation 1 (28)
Issue 3-0 en Nokia Proprietary and Confidential
Administering BSS Network Doctor
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 2/28
Administering BSS Network Doctor
2 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.
Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.
This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.
Copyright © Nokia Corporation 2005. All rights reserved.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 3/28
DN98619369 © Nokia Corporation 3 (28)
Issue 3-0 en Nokia Proprietary and Confidential
Contents
Contents 3
List of tables 4
List of figures 5
1 About this manual 71.1 Summary of changes 71.2 What you need to know first 81.3 Where to find more 81.4 Typographic conventions 81.4.1 Text styles 81.4.2 Command line conventions 9
1.4.3 Variables 101.5 Terms and concepts 10
2 Installing BSS Network Doctor 11
3 Working with BSS Network Doctor 133.1 Creating a new database user 133.2 Organising access to the BSS Network Doctor menu 153.2.1 Access via a CDE button 153.2.2 Access via a start-up file 153.3 Running BSS Network Doctor in a remote Nokia NetAct PM database 163.4 Dropping hanging tables 173.5 Running the reports through Cron 17
3.5.1 How to manage the auto script 183.5.2 How to run the report through Cron 183.6 Defining groups by Working Set Manager 21
4 Special instructions 234.1 What to do when a report gets jammed 234.2 Report failures 234.2.1 Error: ORA-01555 Snapshot too old (Rollback segment too small) 234.2.2 Error: ORA-01630: max # extents (nnn) reached in temp segment in
tablespace <name> 244.2.3 Error: ORA-01652: unable to extend temp segment by <%s> in
tablespace <name> 24
Index 27
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 4/28
Administering BSS Network Doctor
4 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
List of tables
Table 1. Text styles in this document 9
Table 2. Command line conventions 9
Table 3. Environment variables used in this document 10
Table 4. Terms and abbreviations used in this document. 10
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 5/28
DN98619369 © Nokia Corporation 5 (28)
Issue 3-0 en Nokia Proprietary and Confidential
List of figures
Figure 1. Adding a new connection in the file tnsnames.ora 16
Figure 2. Example of running report 204 via auto scripts and Cron 20
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 6/28
Administering BSS Network Doctor
6 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 7/28
About this manual
DN98619369 © Nokia Corporation 7 (28)
Issue 3-0 en Nokia Proprietary and Confidential
1 About this manual
The purpose of this document is to give the system administrator instructions oninstalling, making the necessary settings, and on administering BSS Network Doctor. The information contained in this document relates to Nokia NetActFramework release OSS4 and to BSC release S11.5. This document should not beused with any other versions of Nokia NetAct or Nokia BSC software.
This document is intended for the network operators of Nokia NetAct. Thischapter covers the following topics:
• Summary of changes
• What you need to know first
• Where to find more
• Typographic conventions
• Concepts and terminology
1.1 Summary of changes
In OSS4 Base Release
As a result of the changes made to BSS Network Doctor software from version3.1.5 to 4.0.1, the following changes have been made to this document:
The menu option NMS Database Administration is now called NetActDatabase Administration. See section 3.4 for details.
When creating temporary tables and views, BSS Network Doctor uses theNDOBDB_1 tablespace instead of the TEMP tablespace. See section 4.2.3 fordetails.
In the previous Change Delivery (OSS CD 0163)
As a result of the changes made to BSS Network Doctor software from version3.1.4 to 3.1.5, the following changes have been made to this document:
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 8/28
Administering BSS Network Doctor
8 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
Creating a new database user and the report Database user creation (520) havebeen brought back to BSS Network Doctor with some changes to theimplementation. See section 3.1 for details.
1.2 What you need to know first
This document assumes that you are familiar with the following areas:
• The concepts of the Nokia NetAct and GSM networks in general
• The usage of the UNIX operating system and file system navigation
• The system administration tasks of the UNIX operating system. Anoverview of the responsibilities of the system administrator can be found
in the HP-UX System Administration Concepts.• A text processing utility, such as vi or dtpad. These text processors are
used for editing certain configuration files.
1.3 Where to find more
When you perform the system administrator’s tasks described in this document,you may need to refer to other documentation for further information. The listbelow contains a list of manuals that you will find useful as well as a brief description of the manual’s contents.
BSS Network Doctor documentation
• BSS Network Doctor Reports, DN98614186, for a detailed description onutilising the BSS Network Doctor reports
• BSS Network Doctor Formulas, DN98619493, for detailed descriptionsand lists of counter formulas.
1.4 Typographic conventions
The following tables present the typographic conventions which have been usedin this manual to describe different actions and restrictions.
1.4.1 Text styles
The following table presents the typefaces and fonts and their indications.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 9/28
About this manual
DN98619369 © Nokia Corporation 9 (28)
Issue 3-0 en Nokia Proprietary and Confidential
1.4.2 Command line conventions
The following conventions are used in the UNIX command line to indicatedifferent prompts for different users, and to indicate different parameters. Notethat you should not include the prompt in the command.
Table 1. Text styles in this document
Style ExplanationInitial Upper-case
Lettering
• Application names
Italiced text • Emphasis
• State, status or mode
Courier • File and directory names
• Names of database tables
• Parameters
• Usernames
• System output
• User input
UPPER-CASE
LETTERING
• Keys on the keyboard (ALT, TAB, CTRL etc.)
Bold text • User interface components
Initial Upper-case
Lettering in Italics
• Referenced documents
• Referenced sections and chapters within a document
<bracketed text> • Variable user input
Table 2. Command line conventions
Convention Indication
# Command prompt for the root user
omc>% Command prompt for the omc user
& Command prompt for any user
\ The command or example continues on the fol-
lowing line of the document
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 10/28
Administering BSS Network Doctor
10 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
1.4.3 Variables
This document assumes that the following environment variables have the valuesindicated below:
1.5 Terms and concepts
The lists below presents the abbreviations and terms used in this document.
For other terms, refer to Glossary, DN9763965.
Table 3. Environment variables used in this document
Variable Explanation
$PRODUCTCROOT This variable has the value:
/opt/nokiaoss
Table 4. Terms and abbreviations used in this document.
Term Explanation
auto script A script file for automatic running of reports.
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
IP address A 32-bit address in the TCP/IP network for
distinguishing a computer from another.
LA Location Area
Nokia NetAct A product of Nokia Networks for the operation
and maintenance of cellular networks.
SQL*Plus An interactive program for accessing the
database.
Top-level User Interface A graphical user interface (UI) in Nokia NetAct
Workstation based on windowing.
CDE Common Desktop Environment. On the screen
of a UNIX Workstation, a Hewlett-Packard
product.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 11/28
Installing BSS Network Doctor
DN98619369 © Nokia Corporation 11 (28)
Issue 3-0 en Nokia Proprietary and Confidential
Note
2 Installing BSS Network Doctor
For installing BSS Network Doctor, refer to the installation instructionsaccompanying the software. More generic information will be added to this
document later.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 12/28
Administering BSS Network Doctor
12 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 13/28
Working with BSS Network Doctor
DN98619369 © Nokia Corporation 13 (28)
Issue 3-0 en Nokia Proprietary and Confidential
3 Working with BSS Network Doctor
This chapter describes the administrator’s optional tasks related to running BSSNetwork Doctor.
This chapter covers the following topics:
• Creating a new database user
• Organising access to the BSS Network Doctor menu
• Running BSS Network Doctor in a remote Nokia NetAct PM database
• Dropping hanging tables
• Running the reports through Cron
• Defining groups by Working Set Manager
3.1 Creating a new database user
Nokia recommends you to create a separate Oracle for running BSS Network Doctor. As a database user you will have adequate but not extensive user rights.For example, the dropping of measurement tables would not be possible.
You can also follow the use of BSS Network Doctor, as the log table in reportsLog statistics (512) and Network Doctor use statistics (513) indicates thedatabase user.
The package contains the script ndp520mx.sql, which makes the creation easyand secure.
Before you create a new database user you must:
• first run BSS Network Doctor at least once as the omc user
This is needed in order that BSS Network Doctor creates the cell_doc_logtable always needed for the user log.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 14/28
Administering BSS Network Doctor
14 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
Note
• know the system password
Perform this task every time when migrating from one OSS release to another, asthe DB user or users you have created are not transferred to the new environment.
To create a new database user:
1. Run by ID the script 520 that will interactively ask you for the neededparameters.
The log file is tmp/ndp520mx.log
2. Give the system and omc passwords:
THIS SCRIPT CREATES A NEW DATABASE USER FOR NETWORK DOCTOR USE.
Give system password (not echoed):<system_password>
Give omc password (not echoed):<omc_password>
A list appears showing all existing database users.
3. Give the user a name that is not already in use:
Give a name that is not shown in the list (echoed):<username>
4. Give a password for the new user:
Give a password for the new user:<password>
5. A message appears asking you to confirm your selection:
YOU ARE ABOUT TO CREATE A NEW ORACLE USER: <username>/<password>.
6. Press ENTER to confirm the action.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 15/28
Working with BSS Network Doctor
DN98619369 © Nokia Corporation 15 (28)
Issue 3-0 en Nokia Proprietary and Confidential
Note
The new database user is created.
When you do not need the username any longer, you can remove it by issuing thecommand:
SQL> drop user <username> cascade;
3.2 Organising access to the BSS Network Doctormenu
BSS Network Doctor starts from the main menu shell script ndp001mx.sh. Toopen the menu, give the command:
& $PRODUCTROOT/content/ndobss/ndp001mx.sh
and the BSS Network Doctor main menu opens provided that you have set the$PRODUCTROOT environment variable correctly.
To have more advanced access, there are at least the following options:
• via a CDE button
• via a start-up file
3.2.1 Access via a CDE button
For frequent use, it is a good idea to start BSS Network Doctor using a CDEbutton. Use the CDE tools to create a button in your CDE Front Panel to start theapplication. See the HP-UX online help for more information.
3.2.2 Access via a start-up file
You can also organise access by creating a start-up file which contains the start-up command. The start-up file should contain the following command line:
omc>% /usr/bin/X11/xterm +ls -sb -sl 2000 -title BSS-Network-Doctor \
-geometry 90x30-80+80 -e $PRODUCTROOT/content/ndobss/ndp001mx.sh&
Just enter the command:
omc>% ./<file_name>
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 16/28
Administering BSS Network Doctor
16 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
( ./s, for example), and the main menu pops up.
You can do this without the help of Nokia NetAct system administrator and startBSS Network Doctor without the Top-level User Interface.
When you create the start-up file, it normally by default does not automaticallygive you the execution rights. Set the rights using the command:
omc>% chmod u=rwx <file_name>
3.3 Running BSS Network Doctor in a remote NokiaNetAct PM database
You can set BSS Network Doctor to fetch report data from a remote Nokia
NetAct database by defining an alias for the remote database. To do this, youmust be the owner of the Oracle administrator’s rights. Follow these instructions:
To make a logical name for a database
1. Change the default directory for TNS_ADMIN
omc> % cd $TNS_ADMIN
2. Edit the file tnsnames.ora.
omc> % $EDITOR tnsnames.ora &
3. Add the new connection xxxxxx (a short but descriptive name) in the filetnsnames.ora
xxxxxx.world =(DESCRIPTION =(ADDRESS_LIST =
(ADDRESS =(COMMUNITY = TCP.world)(PROTOCOL = TCP)(Host = yyy.zzz.xxx.www) # the IP address
(Port = 1526) # also 1521 or 1528, change if not working)
)(CONNECT_DATA =
(SID = omc)(GLOBAL_NAME = xxxxxx.world)
))
Figure 1. Adding a new connection in the file tnsnames.ora
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 17/28
Working with BSS Network Doctor
DN98619369 © Nokia Corporation 17 (28)
Issue 3-0 en Nokia Proprietary and Confidential
4. Save the file and quit the editor.
5. Define TWO_TASK to be xxxxxx always before starting up BSS Network Doctor.
omc> % setenv TWO_TASK xxxxxx
3.4 Dropping hanging tables
Many of the BSS Network Doctor reports create temporary views and tables inthe database. These views and tables are dropped (deleted) in the end of eachreport. Anyhow, if the user aborts the report (by pressing CTRL+C, for example),the report is never executed to the end and the created tables or views remainhanging in the database, unnecessarily taking up memory space.
Each time when you start BSS Network Doctor, the program automatically dropsthe possible temporary tables and views that are more than threehoursold. To seeif there exist any temporary tables and views, select NetAct DatabaseAdministration→ Show temporary tables and views created by NetworkDoctor.
In practice, temporary tables and view always exist when BSS Network Doctor isrunning, and do not require any further actions to be taken by the administrator.There is reason for concern only when a temporary table or view stays therepersistently for several days, even after you have restarted the program severaltimes. If this happens, consult your Nokia NetAct system administrator.
3.5 Running the reports through Cron
By arranging the BSS Network Doctor reports to run automatically at night orearly in the morning, you will be able to retrieve the output reports instantly whenyou come to the office. This does not only save your waiting time due to theexecution of the reports, but also reduces the load of the Nokia NetAct databaseserver in the daytime when the system is usually heavily loaded by dailyactivities.
In the BSS Network Doctor main menu there is the option Generate an auto
script by identification number. The reports produce an output file which popsup in the tdpad editor window. Of the following two files, choose the one thatserves your needs:
• nd_tmp.sh - a shell script file for repeating the run of the BSS Network Doctor report with the same input parameters
• tmp.lst - the usual output of a BSS Network Doctor report which helpsto verify that the query gives you the desired output.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 18/28
Administering BSS Network Doctor
18 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
3.5.1 How to manage the auto script
If you want the output to be saved in a different directory or under another filename, change the definitionof the variableOUTFILE in the filend_tmp.shusing
a text editor. Proceed as follows:
1. Modify the desiredreportfile name.It makesit easierfor you todistinguishthe files systematically if you include in the output file name at least theidentification number of the report and the selected area in question. Forexample, go to line:
OUTFILE=$HOME/ndp204mx.lst
and replace it, for example, by typing the line:
OUTFILE=$HOME/netqual/204_gsm900.lst
where netqual is the new directory name into which the auto script filesare saved, giving the output 204_gsm900.lst in this case.
2. Rename the auto script file by saving cd_ndtmp.sh into the directory andunder the file name you want, for example 204_gsm900.sh. Make thesaved file executable by giving the command:
omc>% chmod +x 204_gsm900.sh
3. Test the report on shell prompt by giving the command:
omc>% sh 204_gsm900.sh <username> <passwd>
where <username> is the username for the NetAct database and<passwd> is the database password for the user.
3.5.2 How to run the report through Cron
After you have created the auto script file(s), you may ask the Nokia NetActsystem administrator to schedule the report automatically through Cron, a featurefor running commands at desired moments of time in Nokia NetAct.
A good practice is to first create a shell file that contains the execution of all autoscripts and post-processing (usually naming) of the output files.
Let us assume that we want to create auto scripts of report 204 for two differentareas. The NetAct database username is omc and the password is omc. We wantto have the result files in a separate directory with a date stamp added as anextension to the file name.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 19/28
Working with BSS Network Doctor
DN98619369 © Nokia Corporation 19 (28)
Issue 3-0 en Nokia Proprietary and Confidential
To create the auto scripts
1. Create the needed directories under $HOME
omc> % mkdir NDauto
omc> % mkdir NDr
2. Generate the auto scripts of report 204 separately for each area using BSSNetwork Doctor
1. Edit the files to use the desired output file names, for example:$HOME/NDr/204_areaX.lst and $HOME/NDr/204_areaY.lst
2. Save the files under the desired name, for example:$HOME/NDr/204_areaX.sh and $HOME/NDr/204_areaY.sh
3. Collect all the jobs that should be run via Cron into one shell file named,for example, as $HOME/NDauto/NDcron.sh . File renaming can also bedone in the same file.
# Add here all the auto script runs
sh $HOME/NDauto/204_areaX.sh omc omc
sh $HOME/NDauto/204_areaY.sh omc omc
date_stamp =\Qdate +’%y%m%d’\Q # time stamp in format yymmdd
# Add here all output file renaming commands
cp $HOME/NDr/204_areaX.lst $HOME/NDr/204_areaX.lst.$date_stamp
cp $HOME/NDr/204_areaY.lst $HOME/NDr/204_areaY.lst.$date_stamp
4. Add the following command to Cron job. For instructions on this, refer toWorkstation Network Maintenance, System Administrator’s Guide:
0 1 * * * csh -c ’$HOME/NDautocron.sh’ > /dev/null
This means that the reports will be run starting daily at 1:00 a.m.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 20/28
Administering BSS Network Doctor
20 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
Note
Figure 2. Example of running report 204 via auto scripts and Cron
Do not run reports at the same time with Nokia NetAct alarms and measurementdeletion reports.
In this way you may avoid excessive load on the Nokia NetAct database server.Consult your Nokia NetAct system administrator for the implementation of Cron.It is important that Cron is managed in a well-coordinated way. Therefore theauthority to use Cron is usually limited to the superuser only. The superuser rightsare needed to allow other users to use Cron.
The users that are allowed to use Cron are defined in
/var/adm/cron/cron.allow . You may see the contents by giving thecommand
more /var/adm/cron/cron.allow
When a new version of BSS Network Doctor is introduced, it is theadministrator’s task to test all the old Cron files because changes may have beenmade into the input parameters. We recommend you to test the Cron files everytime you have loaded a new version of BSS Network Doctor and before you takeit into use.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 21/28
Working with BSS Network Doctor
DN98619369 © Nokia Corporation 21 (28)
Issue 3-0 en Nokia Proprietary and Confidential
To verify the use of automatic scheduling for a new version of BSS
Network Doctor
1. Remove from the Cron files all the auto scripts of the former BSS Network Doctor version.
2. Test the auto scripts one by one on a unix command line.
3. If the test succeeds, restore the auto scripts to Cron.
Or:
If the test fails, create a new auto script following the instructions on
section 3.5.1 ( How to Manage the Auto Script ).
Because the auto script generates the output file under the same name everytime when Cron job executes the script, it is usually handy to organise therenaming of the result file so that it receives the date as an additionalextension in the file name.
3.6 Defining groups by Working Set Manager
With the Working Set Manager application in the Top-level User Interface under
the Utils→ NMS Desktop menu, it is possible to create working sets that cancontain any managed objects. Once you have created a working set and it containsBTSs, you can use it when running the BSS Network Doctor reports by choosingWorking Set (manual, with BTSs) or Working Set (manual, with BCFs)option in BTS Area Selection.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 22/28
Administering BSS Network Doctor
22 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 23/28
Special instructions
DN98619369 © Nokia Corporation 23 (28)
Issue 3-0 en Nokia Proprietary and Confidential
4 Special instructions
This chapter gives instruction on what to do in some common error situationswhich may occur with the BSS Network Doctor reports.
4.1 What to do when a report gets jammed
When you have sent a query for a report and, instead, the SQL prompt appears onthe screen, enter the command:
SQL> exit
or exit the program by pressing CTRL+C, and restart BSS Network Doctor.
4.2 Report failures
In some situations, for example when running reports while other databaseactivities are simultaneously ongoing, it is possible that reports fail due to errorsin Oracle. This section describes some common error messages you may facewhen running BSS Network Doctor in the Oracle environment.
4.2.1 Error: ORA-01555 Snapshot too old (Rollback segment too small)
Some reports handle a large amount of data and take up more time to execute. Incase another application inserts data (new measurement results) simultaneouslyinto the same block of the table or updates data in the table ( deletion script), the
rollback segment may wrap around and cause inconsistency in the report whichis still trying to use the previous rollback segment. Thus, this error is moreprobable for the time-consuming selection operations but may in principle occurwith any report.
As an Oracle user, you will receive the following information on the error:
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 24/28
Administering BSS Network Doctor
24 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
• Cause: Rollback records needed by a recorder for consistent readareoverwritten by another user.
• Action: Use larger rollback segments.
Using larger rollback segments would slow down the wrap-around frequency.Changing the size of rollback segments is an action which the Nokia NetActsystem administrator has to do. However, the Nokia NetAct product line does notrecommend you to enlarge the rollback segments because it would lead intoineffective use of the disk and to the need of additional disk space, for example.
This error is not typical only of BSS Network Doctor reports but will mostprobably be met with other post processing tools, too.
To avoid this error:
• Try to run the reports at the end of the measurement period
For example, if the measurement period is 60 min, the last minutes of eachhour would be optimal. Check how the deletion script is scheduled andavoid running reports at the same time.
• Try to limit the amount of users of the reports
so that the overall load on Nokia NetAct would not be unnecessarily highand that the Nokia NetAct could handle the storing of new measurementsin a shorter period of time.
• Put into Cron the reports that are not needed interactively
if there are many users who need to see the reports and train people to look at the output files or to organise access via the BSS Network Doctor menuto the result files. This is part of the work which will be done by theStatistic Engineering Service.
4.2.2 Error: ORA-01630: max # extents (nnn) reached in temp segment intablespace <name>
Some reports require more memory than others. If you see the above error, ask your system administrator to check the settings.
4.2.3 Error: ORA-01652: unable to extend temp segment by <%s> intablespace <name>
This error message indicates that the creation of the temporary table fails due tolack of space in the temporary tablespace NDOBDB_1. It may well happen that onetime this succeeds and another time it does not. Try to run the report again. If theerror is persistent, it is obvious that the tablespace NDOBDB_1 needs more space.Ask the system administrator to check the situation and decide the actions thatneed to be taken.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 25/28
Special instructions
DN98619369 © Nokia Corporation 25 (28)
Issue 3-0 en Nokia Proprietary and Confidential
BSSNetwork Doctor uses NDOBDB_1 when creating temporary tables and views.At the end of a report run, when the tables and views are no longer needed, BSSNetwork Doctor deletes them. In case anything remains hanging (due tointerruption of a report), BSS Network Doctor makes another deletion when you
quit the main menu.
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 26/28
Administering BSS Network Doctor
26 (28) © Nokia Corporation DN98619369
Nokia Proprietary and Confidential Issue3-0en
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 27/28
DN98619369 ©Nokia Corporation 27 (28)
Issue 3-0 en Nokia Proprietary and Confidential
Index
A
accessing the menu
via a CDE button 15auto script 17, 18
automatic scheduling of reports 21
B
BSS Network Doctor
documentation 8
installing 7
organising access to menu 15
working with 13
CCDE button 15
creating
auto scripts 19
new database user 13
Cron 17, 18, 24
D
database user 13
defining groups by Working Set Manager 21
deletion script 23
E
environment variables
PRODUCTROOT 10
error situations 23
errors
ORA -01555 23
ORA -01630 24
ORA -01652 24
H
hanging tables 17
I
identification numbers 17, 18
M
main menu shell script 15
measurement periods 24
N
NetAct
remote database 16Nokia NetAct
database 17
load on 20
system administrator 17, 24
Nokia NetAct Framework release 7
O
Oracle
creating a username 13
errors in 23
fetching data from a remote database 16
P
passwords
omc 14, 18
system 14
R
remote database 16
removing
database username 15
report failures 23reports
identification numbers 17
running through Cron 18
temporary tables and views 17
S
script files
auto script 18
nd tmp.sh 17
ndp001mx.sh 15
ndp520mx.sql 13
special instructions 23start -up file 15
system administrator 20
T
temporary tables and views 17, 25
terms and concepts 10
Top -level User Interface 16
typographic conventions
7/26/2019 Administering BSS Network
http://slidepdf.com/reader/full/administering-bss-network 28/28
Administering BSS Network Doctor
command line conventions 9
text styles 8
variables 10
Wwhat you need to know first 8
where to find more 8
working sets 21