Database related - IBM Tivoli Netcool Performance Manager Wireless Component Document Revision

Database OS partitions sizing

The following is an example layout of tablespaces and disk partitions for a large system.

v /oradata01- holds the system tablespaces, temporary tablespace, and smaller application tablespaces. Their sizes are relatively static.

v /oradata02- holds the Undo tablespace. You must keep the tablespaces separate from the other tablespaces, especially Traffic tablespaces, to avoid contention.

v /oradata03And /oradata04 - hold all Traffic tablespaces. Can be sized only by getting information of the Technology Pack tables, customer data, and volume of data per day. This must be obtained from the Dimensioning procedure.

v /oradump- holds Archive logs when the database is in archive log mode. It contains customer data and depends on the backup policy that is implemented by the customer.

Note: If required, you can spread the traffic tablespaces across oradata01 to oradata04 partitions to avoid congestion of data.

Table 8. Layout of tablespaces and disk partitions

Disk Partition Tablespaces Tablespace Size (GB) Disk size (GB)

/oradata01 SYSTEM 66

SYSAUX 66

WM_CLIENT 20

WM_FLEXPM 20

WM_SA 20

WM_QUEUES 20

ENTERPRISE 20

TEMP 80

Total disk size 400

/oradata02 UNDO 100

Total disk size 300 /oradata03 TRAFFIC_SMALL <data dependent>

TRAFFIC_MEDIUM <data dependent>

TRAFFIC_LARGE <data dependent>

Total disk size xxx /oradata04 TRAFFIC_JUMBO <data dependent>

TRAFFIC_JUMBOPLUS<data dependent>

Total disk size xxx

/oralogs1 redo log group1,

member a

3 (range 1-3GB)

redo log group2, member a

3 (range 1-3GB)

Table 8. Layout of tablespaces and disk partitions (continued)

Disk Partition Tablespaces Tablespace Size (GB) Disk size (GB) redo log group3,

Total disk size 70

/oralogs2 redo log group1,

member b

Total disk size 70

/oradump Archive logs and

backups

Total disk size xxx

The configuration and sizing of the database tablespaces are updated and delivered to a customer in a customer database template:

vtdb_<customer_name>.dbt.

See “Updating customer database template” on page 34, for information about creating and updating a customer's database template with the correct sizings and locations.

Database extents sizing

Tivoli Netcool Performance Manager systems are deployed with a database, which contains five default tablespaces for holding traffic data. These tablespaces are as follows:

The default traffic tablespaces are configured with different extent sizes so that data can be stored in the correct tablespace for the associated data growth rate. The aim is to ensure that data is stored in the database for efficient data access and data storage. Tables must be stored in tablespaces with appropriate extent sizes.

The default extent sizes that are included with a Tivoli Netcool Performance Manager system are listed in the following section. You must update the default

extent sizes to the values obtained from the customer-specific sizing tool. One approach is to size the extents so that a maximum of 10 extents are created per day. The extent size will be 1/10 of the table growth rate per day:

TRAFFIC_JUMBOPLUS 1024 KBs (1 MB)

TRAFFIC_JUMBO 512 KBs (0.5 MB)

TRAFFIC_LARGE 256 KBs (0.25 MB)

TRAFFIC_MEDIUM 256 KBs (0.25 MB)

TRAFFIC_SMALL 128 KBs (0.125 MB)

For example, with the default extent sizes mentioned earlier, if a table is stored in TRAFFIC_JUMBOPLUS, each table, table partition, or both are allocated 1 MB. When a new partition is created, it is created with an initial size of 1 MB. Also, when data is loaded into the table and the table grows, it grows in chunks of 1 MB extents.

It is important to correctly size the extent sizes before you deploy a Tivoli Netcool Performance Manager system. Oversizing a tablespace extent results in wasted disk space. Undersizing a tablespace extent results in the system continually having to create extents and so can be inefficient. One method for estimating the extent size is to use the Technology Pack Dimensioning tool.

The Technology Pack Dimensioning tool can be used to calculate the estimated daily tablespace size per table. This list of tables can then be split into five groups of tables and used to determine the boundaries for each tablespace and the optimal extent size.

After the five extent sizes are calculated, they can be used to update the

uniAllocSizeparameter that is associated with the TablespaceAttributes section, for each tablespace in a customer's vtdb.dbt database template. The following is an example of the TablespaceAttributes for the TRAFFIC_SMALL tablespace. Note the <uniAllocSize unit="KB"> line. You must update this value to the correct extent size:

Chapter 7. Database related information 33

Additionally, for each Technology Pack that is to be loaded on a Tivoli Netcool Performance Manager system, each table must be assigned to an appropriate tablespace. A table must be assigned to a tablespace, where no more than 10 extents are created per day.

A method for determining default extent sizes and for deciding which tablespace must be used for a table is described in the Dimensioning procedure.

When new extent sizes are determined, they might be changed on the system by editing the customer database template vtdb.dbt file. You must edit the template at the time of installation before the database is created. See “Updating customer database template.”

Setting the database block size

Tivoli Netcool Performance Manager uses one block size for the database, 16 KB.

This size is set while you create the database and cannot be changed for the lifetime of the database.

Multiple block sizes must not be used. Multiple blocks sizes are used by Oracle for extracting, transforming, and loading data from a transactional system to a data warehouse. Multiple block sizes must not be used within the Tivoli Netcool Performance Manager application.

Updating customer database template

A customer database template vtdb_<customer_name>.dbt is used to create a customer Oracle database with the appropriate memory settings, tablespace sizes, and data file locations. The Oracle Database Configuration Assistant

($ORACLE_HOME/bin/dbca) is used to create and update the customer database template.

About this task

Each customer requires a customer-specific vtdb database template that contains all database sizing information, which is determined during the sizing exercise.

Typical values are memory settings, tablespace sizes, data files sizes, and extent sizes.

The following are the steps that are required for modifying the current database template.

Procedure

1. Copy the current vtdb.dbt file to a system with Oracle 11 installed. Copy the file to the following location as user Oracle:

/appl/oracle/product/11.2.0/db_1/assistants/dbca/templates/vtdb.dbt 2. Export your DISPLAY:

$ export DISPLAY=<IP ADDRESS>:0.0

3. Run the following command to start the Oracle Database Configuration Assistant (DBCA) as user Oracle:

$ dbca

4. Select the MANAGE TEMPLATE check box, and then click NEXT.

5. Select the FROM AN EXISTING TEMPLATE check box, and then click NEXT.

6. Select the current VTDB template check box, and then click NEXT.

7. Enter vtdb_<customer_name>_prod as the template name, and then click NEXT.

8. Select the USE DATABASE FILE LOCATIONS FROM TEMPLATE check box, and then click NEXT.

9. Leave the defaults, and click NEXT.

10. Leave the defaults, and click NEXT.

11. Specify the SGA and PGA sizes. The default values are PGA=2 GB and SGA=2 GB. These values vary depending on the size of the system and the outcome of the sizing exercise. Click NEXT. See section “Manually setting memory parameters” for sizing PGA and SGA.

12. Go through each of the tablespaces and resize them to the size from the output of the sizing exercise. Ensure the extent sizes, locations, and total tablespace sizes are correct. The maximum data file size must be 20 GB. You can add multiple data files to a tablespace to increase its size to the target size, in multiples of 20 GB. The extent sizes, file locations, and tablespace sizes must be determined during the sizing exercise.

Note: By default Autoextend is set to ON, you must consider this when you size and create tablespaces.

13. If required, change the storage parameters of each data file that is associated with each tablespace and set the autoextend values for each data file.

a. Select STORAGE > DATAFILES.

b. Click the data file that you want to modify.

c. Select the STORAGE tab of the data file in the right side of the screen.

d. Set the size of the data file and setting AUTOEXTEND on, and setting the maximum size of the data file.

14. Click NEXT.

15. Click FINISH.

A new database template file is created:

/appl/oracle/product/11.2.0/db_1/assistants/dbca/templates/

vtdb_<customer_name>_prod.dbt

This file must be added to the client project to the configuration package in:

/appl/virtuo/admin/oracle/conf/vtdb_<customer_name>_prod.dbt

This file name must be added to the install template for the client so that it is picked up automatically by the installation.

Manually setting memory parameters

You set the PGA and SGA memory in the database template, vtdb_<customer_name>.dbt.

Memory parameters must be set correctly for performance reasons. These parameters must be obtained from the sizing exercise.

As a guideline, the PGA can be allocated 30% of the total memory available to the database. The SGA can be allocated 70% of the total memory available to the database. For a system with a separate database, 8 GB of the total memory available must be reserved for the OS before the PGA and SGA settings are determined. If the application is also on this system, reserve an extra 7 GB for the application and the calculated memory that is required for the Loaders.

Chapter 7. Database related information 35

To update the PGA setting in the customer database template, update the following line:

To update the SGA settings in the customer's database template, update the following lines:

v Automatic Shared Memory Management (ASMM) is set to ON in the vtdb.dbt.

You must set it to OFF in all Tivoli Netcool Performance Manager production systems. Set ASMM to off by setting SGA_TARGET=0:

v For SGA, as a guideline 3 GB can be allocated for SHARED_POOL_SIZE and the remaining space can be allocated to DB_CACHE_SIZE (minus large_pool_size and java_pool_sizeof 100 M each).

Specify the following settings to the size that is determined by the sizing exercise:

Manually setting tablespace

Tablespace sizes are set in the database template, vtdb_<customer_name>.dbt. The maximum size of a data file must not exceed 20 GB. It helps in easier file

management and backing up. If the size of a tablespace is greater than 20 GB, you must create multiple data files of 20 GB each, and associate these data files with the tablespace.

About this task

To set the tablespace, you update the vtdb_<customer_name>.dbt in two steps. The first step is to add the additional data files, and the second step is to add the data files to the tablespace. You might set the tablespace for most traffic tablespaces.

Procedure

1. Add more <DatafileAttributes> sections for the extra data files, for example temp02.dbf, temp03.dbf, temp04.dbf:

2. Add the new data files to the appropriate tablespace, in

<TablespaceAttributes>:

Chapter 7. Database related information 37

Notices

This information was developed for products and services that are offered in the USA.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation

North Castle Drive, MD-NC119 Armonk, NY 10504-1785

United States of America

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd.

19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those

websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

Department number/Building number Site mailing address_

City, State; Zip Code_

USA (or appropriate country)

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

Portions of this code are derived from IBM Corp. Sample Programs.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any

information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as

determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

Notices 41

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE

PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT

In document IBM Tivoli Netcool Performance Manager Wireless Component Document Revision R2E1. Deployment Guide (Page 39-54)