How-To GuideEnabling SAP NetWeaver BW to Use IBM DB2 for Linux, UNIX,and Windows as Near-Line Storage (NLS)

Target Audience

ConsultantsAdministratorsOthers

PublicDocument version 1.2 – 04/19/2010

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p,System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5,POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, SystemStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks orregistered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. andother countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML, and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP Business ByDesign, and other SAP products andservices mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product andservice names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informationalpurposes only. National product specifications may vary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may not bemodified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at:http://service.sap.com/instguidesnw <Your SAPNetWeaver Release> Operations Database-SpecificGuides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

Terms for Included OpenSource SoftwareThis SAP software contains also the third party open source softwareproducts listed below. Please note that for these third party productsthe following special terms and conditions shall apply.1. This software was developed using ANTLR.2. gSOAPPart of the software embedded in this product is gSOAP software.Portions created by gSOAP are Copyright (C) 2001-2004 Robert A.van Engelen, Genivia inc. All Rights Reserved.THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDEDBY GENIVIA INC AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORYOF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.3. SAP License Agreement for STLport SAP License Agreement forSTLPort between SAP Aktiengesellschaft Systems, Applications,Products in Data Processing Neurottstrasse 16 69190 Walldorf,Germany (hereinafter: SAP) and you (hereinafter: Customer)a) Subject Matter of the AgreementA) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++ library (STLport) and itsdocumentation without fee.B) By downloading, using, or copying STLport or any portion thereofCustomer agrees to abide by the intellectual property laws, and to allof the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport(whether original or modified) without any royalties or restrictions.D) Customer shall maintain the follo777wing copyright andpermissions notices on STLport sources and its documentationunchanged:Copyright 2001 SAP AGE) The Customer may distribute original or modified STLport sources,provided that:o The conditions indicated in the above permissions notice are met;o The following copyright notices are retained when present, andconditions provided in accompanying permission notices are met:Coypright 1994 Hewlett-PackardCompanyCopyright 1996,97 Silicon GraphicsComputer Systems Inc.Copyright 1997 Moscow Center forSPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AGPermission to use, copy, modify, distribute and sell this software andits documentation for any purposes is hereby granted without fee,provided that the above copyright notice appear in all copies and thatboth that copyright notice and this permission notice appear insupporting documentation. Hewlett-Packard Company makes norepresentations about the suitability of this software for any purpose.It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software andits documentation for any purpose is hereby granted without fee,provided that the above copyright notice appear in all copies and thatboth that copyright notice and this permission notice appear insupporting documentation. Silicon Graphics makes no representationsabout the suitability of this software for any purpose. It is provided “asis” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software andits documentation for any purposes is hereby granted without fee,provided that the above copyright notice appear in all copies and thatboth that copyright notice and this permission notice appear insupporting documentation. Moscow Center for SPARC makes norepresentations about the suitability of this software for any purpose. Itis provided “as is” without express or implied warranty.

Boris Fomitchev makes no representations about the suitability of thissoftware for any purpose. This material is provided "as is", withabsolutely no warranty expressed or implied.Any use is at your own risk. Permission to use or copy this softwarefor any purpose is hereby granted without fee, provided the abovenotices are retained on all copies.Permission to modify the code and to distribute modified code isgranted, provided the above notices are retained, and a notice that thecode was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software andits documentation for any purposes is hereby granted without fee,provided that the above copyright notice appear in all copies and thatboth that copyright notice and this permission notice appear insupporting documentation. SAP makes no representations about thesuitability of this software for any purpose. It is provided with alimited warranty and liability as set forth in the License Agreementdistributed with this copy.SAP offers this liability and warranty obligations only towards itscustomers and only referring to its modifications.b) Support and Maintenance SAP does not provide softwaremaintenance for the STLport. Software maintenance of the STLporttherefore shall be not included.All other services shall be charged according to the rates for servicesquoted in the SAP List of Prices and Conditions and shall be subject toa separate contract.c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and freeof charge, SAP cannot guarantee that the STLport is error-free,without material defects or suitable for a specific application underthird-party rights. Technical data, sales brochures, advertising text andquality descriptions produced by SAP do not indicate any assurance ofparticular attributes.

d) Limited LiabilityA) Irrespective of the legal reasons, SAP shall only be liable fordamage, including unauthorized operation, if this (i) can becompensated under the Product Liability Act or (ii) if caused due togross negligence or intent by SAP or (iii) if based on the failure of aguaranteed attribute.B) If SAP is liable for gross negligence or intent caused by employeeswho are neither agents or managerial employees of SAP, the totalliability for such damage and a maximum limit on the scope of anysuch damage shall depend on the extent to which its occurrence oughtto have anticipated by SAP when concluding the contract, due to thecircumstances known to it at that point in time representing a typicaltransfer of the software.C) In the case of Art. 4.2 above, SAP shall not be liable for indirectdamage, consequential damage caused by a defect or lost profit.D) SAP and the Customer agree that the typical foreseeable extent ofdamage shall under no circumstances exceed EUR 5,000.E) The Customer shall take adequate measures for the protection ofdata and programs, in particular by making backup copies at theminimum intervals recommended by SAP. SAP shall not be liable forthe loss of data and its recovery, notwithstanding the other limitationsof the present Art. 4 if this loss could have been avoided by observingthis obligation.F) The exclusion or the limitation of claims in accordance with thepresent Art. 4 includes claims against employees or agents of SAP.4. Adobe Document Services Adobe, the Adobe logo, Acrobat,PostScript, and Reader are either registered trademarks or trademarksof Adobe Systems Incorporated in the United States and / or othercountries. For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer, see SAPNote 854621.

Typographic Conventions

Type Style Description

Example Text Words or characters quoted fromthe screen. These include fieldnames, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table names,and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directory namesand their paths, messages,names of variables andparameters, source text, andnames of installation, upgradeand database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For moreinformation, see Help on Help GeneralInformation Classes and Information Classesfor Business Information Warehouse on thefirst page of any version of SAP Library.

6 February 2010

Contents

1 Introduction ........................................................................................ 72 Installation of the NLS Database ...................................................... 9

2.1 Installing DB2 as NLS Database .......................................................... 92.2 Setting Up the Connection to the NLS Database .............................. 11

3 Database Layout of NLS Objects.................................................... 133.1 Database Layout of an NLS InfoCube ............................................... 143.2 Database Layout of an NLS DataStore Object .................................. 17

4 NLS Operations ................................................................................ 204.1 Creating a Data Archiving Process for an InfoProvider ................... 204.2 Archiving Data to the NLS Database ................................................. 214.3 Reloading Archived Data .................................................................... 264.4 Using InfoProviders with NLS in a MultiProvider Environment ...... 28

5 Administration of the NLS Database Using the DBA Cockpit ..... 325.1 Monitoring NLS Objects ..................................................................... 335.2 Deleting Invalid Data from the NLS Database ................................... 35

6 Business Warehouse Query Processing with NLS ...................... 376.1 Enabling Business Warehouse Queries to Read NLS Data ............. 376.2 Using the Improved Query Lookup Functionality ............................ 38

7 Backup and Recovery of the NLS Database ................................. 407.1 Configuring the NLS Database for Archive Logging ........................ 407.2 Backing Up the NLS Database ........................................................... 407.3 Recovering the NLS Database ........................................................... 41

8 Using DB2 as NLS Database with a BW System Running on aDifferent Database Platform ................................................................ 44

February 2010 7

1 IntroductionPurposeThis document describes how you enable an SAP NetWeaver Business Warehouse (BW)system to use IBM DB2 for Linux, UNIX, and Windows as a near-line storage (NLS)database.Near-line storage is a new category of data persistency that is similar to archiving. Using anNLS database enables you to transfer historical read-only data of your InfoProviders (forexample, InfoCubes and DataStore objects) to an additional NLS database. The databaseserver and the storage devices of the NLS solution can be located on the same server as theSAP NetWeaver BW system or on a dedicated server. However, you can still access theseparated data in the NLS database transparently from an SAP NetWeaver BW system.The following figure shows a basic setup of the NLS solution with DB2 for Linux, UNIX, andWindows as NLS database:

You can access NLS data online via the OLAP processor and the additional NLS interfacethat consists of the following parts:

General NLS interface, which is database independent DB2-specific interface that establishes a database connection to the NLS database

server and accesses the NLS data

8 February 2010

Implementation ConsiderationThe NLS solution described in this document is available as of the following SAP NetWeaverreleases and DB2 releases:

DB2 9.7 for Linux, UNIX, and Windows (for the installation of the NLS database)

To use the IBM DB2 compression feature in the NLS database, you must havepurchased the correct license.

Enhancement Package 1 of SAP NetWeaver 7.0 Support Package 6 or higher with atleast DB2 V9.1 or higher

Only Unicode SAP NetWeaver BW systems are supported

About This DocumentThis document contains the following sections:

Installation of the NLS Database [page 9]Database Layout of NLS Objects [page 13]NLS Operations [page 20]Administration of the NLS Database Using the DBA Cockpit [page 32]Business Warehouse Query Processing [page 37]Backup and Recovery of the NLS Database [page 40]Using DB2 as NLS Database with a BW System Running on a Different DatabasePlatform [page 44]

For more information about the SAP NetWeaver BW NLS solution on DB2 forLinux, UNIX, and Windows, see SAP Note 1405664.

Naming ConventionsThe following naming conventions apply in this document:

Near-line storage is referred to as NLSIBM DB2 for Linux, UNIX, and Windows is referred to as DB2 9.7, DB2 V9.5 or DB2 –depending on the context used.SAP NetWeaver Business Warehouse system is referred to as SAP NetWeaver BW orBW system.

February 2010 9

2 Installation of the NLS Database

2.1 Installing DB2 as NLS DatabaseThe installation process of the NLS database has been completely integrated in the SAPinstallation tool (SAPinst) and is similar to the installation of other SAP products. Theinstallation is fast and simple because only the database is created and no content is loadedat the time of installation.

PrerequisitesThe minimal SAPinst level supporting the NLS database installation is the 7.2-based SAPinstversion.

If you are using an SAP NetWeaver system lower than release 7.2, you candownload the 7.2-based version of SAPinst from SAP Service Marketplace athttp://service.sap.com/swdc. For more information, see SAP Note 929929.

ProcedureTo install the NLS database, run SAPinst as described in section Installing a Near-LineStorage Database for an SAP NetWeaver BW in the installation documentation InstallationGuide – SAP NetWeaver 7.0 including Enhancement Package 2 on <OS>: IBM DB2 forLinux, UNIX, and Windows that is available on SAP Service Marketplace at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 Installation Installation –SAP NetWeaver SystemsSAPinst performs the following steps:

Installs the DB2 software on the appropriate server Creates the operating system users and groups Creates a DB2 instance Creates and activates the DB2 database for NLS

The following table lists the most important parameters that you must specify during thedialog phase of the NLS database installation.

Since you require the values of these parameters to configure the connection toyour NLS database from your BW system, we recommend that you note themdown.

Parameter Description

Database ID (DBSID) Three-letter database identifier of the NLSdatabase

Password of databaseadministrator

Default user for the database administrator user isdb2<dbsid> where <dbsid> is the three-letterdatabase identifier of your NLS database

10 February 2010

Database communication port Required for TCP/IP communication between theNLS database server and the remote DB2 clients

You can leave this field empty.If you do not enter any value in thisfield, SAPinst automatically choosesthe port number for you.

Instance memory size Amount of memory (RAM) used by the DB2instance running the NLS database.Since the installation tool assumes that there mightbe other applications running on the same host (forexample, another database or an SAP applicationserver), SAPinst automatically proposes thememory size, which is approximately one third ofthe overall system memory.However, this is only a proposal. You can optionallyadapt this value to improve the performance of yourNLS database.

If you are installing the NLS databaseon a dedicated host, you might want toincrease the instance memory toapproximately 90% of the overallsystem memory to achieve optimalperformance.

You do not have to note the value ofthis parameter to configure theconnection to the NLS database.

After the installation has completed, you can set up the connection to the NLS database inyour BW system using the DBA Cockpit as described in the following section.

February 2010 11

2.2 Setting Up the Connection to the NLSDatabase

The following procedure only applies if your BW system is running on DB2 forLinux, UNIX, and Windows. If your BW system is running on a differentdatabase platform, follow the instructions in Using DB2 as NLS Database with aBW System Running on a Different Database Platform [page 44].

To set up a connection to the DB2 NLS database, you can use the NLS-specific extension ofthe DBA Cockpit. To set up this connection, you require the following information that isspecified during the installation of the NLS database:

Remote database name Remote database host name Remote communication port

Procedure...

1. In your BW system, call transaction DBACOCKPIT and choose BW AdministrationNLS Configuration in the navigation frame of the DBA Cockpit.The screen BW Administration – NLS Configuration appears.

2. From the application toolbar, choose the Add pushbutton.The dialog box DB Connections: Add Connection Entry appears.

3. Enter the appropriate values in the required fields as described in the following table:

Field Description

ConnectionName

Name of the NLS connection

DatabaseSystem

Name of the remote database platform

ConnectionMaximum

Number of simultaneous database connections

We recommend that you leave this field empty.

ConnectionOptimum

Optimal number of simultaneous database connections

We recommend that you leave this field empty.

12 February 2010

PermanentConnection

Sets up a permanent connection to the remote database

We recommend that you do not select thischeckbox.

User Name Name of the connection userThis user must already exist on the remote NLS host. Thedefault user generated by the installation process isdb2<dbsid>.

Password Password of the connection user

Database Name Name of the remote NLS database

Service Name(Port)

Communication port for the remote NLS database server

Database Host Host name of the remote NLS database server

Schema Name Name of the DB2 schema for the creation and access ofdatabase objects

If you do not enter a schema name, the nameof the connection user is used as the schemaname.

4. Add the new NLS connection to your system.

If you want to change any of the specified values, you have to change themusing the DB Connections option in the DBA Cockpit.

5. To test the newly added connection to the NLS database, choose the Test Connectionpushbutton in the application toolbar.

February 2010 13

3 Database Layout of NLS ObjectsThis section provides information about the layout of the NLS objects that are created in theremote NLS database for the different types of supported InfoProviders as well as the namingconventions used for NLS tables.After you have successfully established and configured a connection to the installed DB2NLS database, you create a data archiving process for an InfoProvider. The following typesof InfoProviders are supported for NLS:

Standard InfoCubes Real-time InfoCubes Standard DataStore objects Write-optimized DataStore objects DataStore object for direct update MultiProviders (only if each single InfoProvider of the MultiProvider is one of the

previous types)For more information, see Using InfoProviders with NLS in a MultiProviderEnvironment [page 28].

During the creation of the data archiving process, you configure the InfoProvider to use thenewly created NLS connection. As soon as the data archiving process is activated, a set oftables is created in the NLS database. If an NLS archiving request is later executed, selecteddata is transferred from the BW database to the NLS tables.The number of NLS tables and their structure mainly depends on the type of InfoProvider forwhich you created the data archiving process. Even though there are different types ofInfoProviders, the NLS solution with DB2 mainly uses two data models depending on whetherthe InfoProvider is like an InfoCube or like a DataStore object.The NLS table names consist of the following elements in the sequence given here:

Namespace of the original InfoProvider DB2 NLS-specific prefix (OA) Technical name of the original InfoProvider For InfoCubes only: A dimension identifier

This identifier is added in combination with the character “-“.

For the fact table of an InfoCube or the active data table of a DataStore object inthe NLS database, the table name is not amended with the combination of thecharacter “-“ and the identifier of the type of table.The fact table of an InfoCube and the active data table of a DataStore object arethe only NLS tables that are also created as transparent tables in the ABAPDictionary.

ExampleThe table name of the NLS fact table for the InfoCube ZBENCH is /BIC/OAZBENCH, where/BIC/ is the namespace, OA the NLS-specific prefix and ZBENCH the technical name of theInfoCube.

14 February 2010

The table lists the values that you can use as the identifier for the dimension tables of NLSobjects:

Value Description

R Archiving request data

P Package dimension data (in case of an InfoCube)

T Time dimension data (in case of an InfoCube)

U Unit dimension data (in case of an InfoCube)

1 First user-defined dimension data (in case of anInfoCube)

2 Second user-defined dimension data (in case of anInfoCube)

… …

C 12th user-defined dimension data (in case of anInfoCube)

D 13th user-defined dimension data (in case of anInfoCube)

As a result, the table name of the NLS package dimension table for the InfoCube ZBENCH is/BIC/OAZBENCH-P.

3.1 Database Layout of an NLS InfoCubeAn InfoCube is created in an SAP NetWeaver BW database with an extended star schema.This data model is implemented in SAP NetWeaver BW with the following tables:

Two fact tables (E and F fact table).When data is inserted into an InfoCube, data is at first stored in the F fact table. Youcan use BW compression to optionally compress records from the F fact table with thesame key value in one record only. During BW compression, data is transferred fromthe F fact table to the E fact table, which has only unique keys. In addition to the keyfigures, the E and F fact tables also store the DIMID columns that serve as foreignkeys to the InfoCube dimension tables.

Up to 16 dimension tablesThese tables contain descriptive information key figures for the fact table in a technicalformat.

A certain number of master data tables containing the characteristics of the InfoCube

The dimension tables also act as a link between the fact tables and the masterdata tables.

In contrast to the extended star schema of an InfoCube in a BW system, an InfoCube iscreated in the NLS database with a simplified star schema.

February 2010 15

This data model is implemented in the NLS database with the following tables: One table to store the archiving request information

Throughout this document, this table is called archiving request table. Every executionof a data archiving process to move data to the NLS database creates an archivingrequest.

One fact tableThis fact table stores the key figures of the original InfoCube, references to dimensiontables, a reference to the NLS archiving request table, and other archiving information.

A set of dimension tablesThese tables store the characteristics of the original InfoCube. The number ofdimension tables for the NLS object equals the number of dimension tables for theoriginal InfoCube in the BW database.

The following figure shows the simplified star schema for an InfoCube in the NLS database:

DB2-Specific Features in an NLS InfoCubeTo optimize query performance, the multidimensional clustering (MDC) feature of IBM DB2for Linux, UNIX, and Windows is used in the NLS fact table. The columns used in the MDCdefinition are (in order of their usage) as follows:

Column containing the archiving request identifier Columns of the original InfoCube for which MDC has also been defined

To ensure space savings when a large amount of data is transferred to the NLS database,DB2 row compression (introduced with DB2 V9.1) is automatically enabled for each NLStable. As of DB2 9.7, index compression is also automatically enabled for each created NLStable.Each dimension table in the NLS database has a unique identifier for the differentcombinations of characteristic values. To simplify its handling, this identifier is represented asan identity column in the dimension table.The fact table and dimension tables (including the archiving request table) from the NLSdatabase are stored in dedicated tablespaces. The NLS tablespace names consist of theSAP system ID (<SAPSID>) that is appended as a prefix to the BW tablespace name and thetablespace name that is inherited from the original InfoProvider in the BW database. Theextent size of these tablespaces is also inherited from the original InfoProvider.

16 February 2010

The following table lists the tablespace names in the NLS database for the InfoCube ZBENCHof SAP system NL1:

InfoCubeTable

BWTablespace

NLS Table Name NLSTablespace

Description

/BIC/FZBENCH NL1#FACTD

NL1#FACTI

/BIC/OAZBENCH NL1#NL1#FACTD

NL1#NL1#FACTIFact data andindextablespaces

/BIC/DZBENCHT NL1#DIMD

NL1#DIMI

/BIC/OAZBENCH-T NL1#NL1#DIMD

NL1#NL1#DIMIDimension dataand indextablespaces

N/A N/A /BIC/OAZBENCH-R NL1#NL1#DIMD

NL1#NL1#DIMIArchivingrequest data andindextablespaces

If they do not yet exist, the NLS tablespaces are automatically created when a data archivingprocess is created in the BW system.During the tablespace creation for the dimension tables (including the archiving requesttable), the tablespace is assigned to the database partition group NGRP_NLSDIM_<SAPSID>.If the tablespace of the fact table is created, the tablespace is assigned to the databasepartition group NGRP_NLSDATA_<SAPSID>. Both database partition groups are automaticallycreated as soon as a new NLS connection is added to the BW system using the DBACockpit.With the DB2 database partitioning feature (DPF), you can improve query performance. Youcan add database partitions to the NLS database, for example, by having a partitioned NLSdatabase with n+1 database partitions starting with partition number 0.

We recommend that you store the NLS dimension tables on database partition0 and that you distribute the NLS fact tables over the database partitions 1, ...,n.

Example of NLS Tables for an InfoCubeThe following table lists the NLS tables and their relationship with InfoCube ZBENCH.

InfoCube Table Name NLS Table Name Description/BIC/FZBENCH/BIC/EZBENCH

/BIC/OAZBENCH Fact table

/BIC/DZBENCHP /BIC/OAZBENCH-P Package dimension table

/BIC/DZBENCHT /BIC/OAZBENCH-T Time dimension table

/BIC/DZBENCHU /BIC/OAZBENCH-U Unit dimension table

February 2010 17

/BIC/DZBENCH1 /BIC/OAZBENCH-1 First user-defined dimensiontable

… … …

/BIC/DZBENCHD /BIC/OAZBENCH-D 13th user-defined dimensiontable

N/A /BIC/OAZBENCH-R Archiving request table

3.2 Database Layout of an NLS DataStoreObjectHow a DataStore object (DSO) is represented in the BW database depends on the type ofDataStore object. If it is a standard DataStore object, it is represented by the following tables:

Activation queue tableThis table acts like a staging table of the DataStore object. When data is inserted into aDataStore object, it is at first inserted into this table. During DataStore object activationprocess, records from DSO activation queue table are transferred into the DSO activedata table and changes are logged in the DSO change log table.

Active data tableThis table contains the consolidated data of the DataStore object and is also used forreporting.

Change log tableThis table stores - similar to a log file - the changes in the active data table after theactivation queue table has been processed.

A write-optimized DataStore object is only represented by the active data table. Data that isto be transferred to the NLS database is only read from this active data table, which simplifiesthe representation in the NLS database.The following tables are created in the NLS database when a data archiving process for aDataStore object is created:

NLS archiving request tableThis table stores the archiving request information. Every execution of a data archivingprocess to move data to the NLS database creates an archiving request.

NLS active data tableThis table stores the business-related information of the original DataStore object (thatis, key columns and non key columns). In addition, the reference to the correspondingarchiving request record and other archiving information are stored in this table.

18 February 2010

The following figure shows the layout of a DataStore object in the NLS database:

DB2-Specific Features in an NLS DataStore ObjectTo optimize query performance, the multidimensional clustering (MDC) feature of IBM DB2for Linux, UNIX, and Windows is used in the NLS fact table. The columns used in the MDCdefinition are as follows:

Column containing the archiving request identifier Columns of the original DataStore Object for which MDC has also been defined.

To ensure space savings when large amounts of data are transferred to the NLS database,DB2 row compression, which was introduced with DB2 V9.1, is automatically enabled foreach NLS table. As of DB2 9.7, index compression is also automatically enabled for eachcreated NLS table.The tablespace name that is used when the active data table is created in the NLS databaseconsists of the tablespace name inherited from the original InfoProvider in the BW databaseand the SAP system ID (<SAPSID>) that is appended as a prefix to the tablespace name.The extent size of this tablespace is also inherited from the BW database. The archivingrequest table uses <SAPSID>_NLSGENERALD for its data and <SAPSID>_NLSGENERALI forits indexes.The following table shows the tablespace names in the NLS database for the DataStoreobject ZDSOBEN of SAP system NL1:

InfoCube Table Tablespace NLS Table Name NLSTablespace

Description

/BIC/AZDSOBEN00 NL1#ODSD

NL1#ODSI

/BIC/OAZDSOBEN NL1#NL1#ODSD

NL1#NL1#ODSIActive dataand indextablespaces

N/A N/A /BIC/OAZDSOBEN-R NL1_GENERALD

NL1_GENERALIArchivingrequestdata andindextablespace

If they do not already exist, the NLS tablespaces are automatically created when a dataarchiving process is created in the BW system.When the tablespace of the active data table is created, the tablespace is assigned to thedatabase partition group NGRP_NLSDATA_<SAPSID>. The database partition group isautomatically created as soon as a new NLS connection is added to the BW system using theDBA Cockpit.

February 2010 19

With the DB2 database partitioning feature (DPF), you can improve query performance. Youcan add database partitions to the NLS database, for example by having a partitioned NLSdatabase with n+1 database partitions starting with partition number 0.

We recommend that you store the archiving request table on database partition0 and that you distribute the NLS active data table over the database partitions1, ..., n.

Example of NLS Tables for a DataStore ObjectThe following table lists the DataStore object tables in the NLS database for a standardDataStore object named ZDSOBEN:

Table Name of DataStoreObject

NLS Table Name Description

/BIC/AZDSOBEN00(Active data table)/BIC/AZDSOBEN40 (Activationqueue table)/BI0/B0…(Change data table)

/BIC/OAZDSOBEN Active data table

N/A /BIC/OAZDSOBEN-R Archiving request table

If the DataStore object ZDSOBEN is a write-optimized DataStore object, then it has only onetable:

DataStore Object Table Name NLS Table Name Description

/BIC/AZDSOBEN00 /BIC/OAZDSOBEN Active data table

N/A /BIC/OAZDSOBEN-R Archiving request table

20 February 2010

4 NLS OperationsThis section provides information about how you enable InfoProviders to use the NLSdatabase by creating a data archiving process (DAP). In addition, you learn how to performbasic operations on the NLS database (that is, archiving data to and reloading data from theNLS database).

4.1 Creating a Data Archiving Process for anInfoProviderBefore you can archive data to the NLS database, you have to enable the InfoProvider (forexample, the InfoCube or DataStore object) to use DB2 as NLS database.

Procedure1. In your BW system, call transaction RSA1, choose the required InfoProvider and

choose Create Data Archiving Process from the context menu.The screen Change Data Archiving Process appears.

2. On the tab page General Settings, perform the following steps:In the field Long Description, enter the long text for the DAP description.In the field Short Description, enter the short text for the DAP description.If you have not installed the ADK software, deselect the checkbox ADK-BasedArchiving. ADK is used for traditional BW data archiving.In the field Nearline Connection, enter the name of the connection to the NLSdatabase. If this connection has not yet been set up, perform the stepsdescribed in Setting Up the Connection to the Near-Line Storage Database[page 11].

If you are creating a DAP for a write-optimized DataStore object, you can onlychoose Request-Based Archiving in the group box Selection Profile (instead ofTime Slice Archiving).That is, during NLS archiving of the write-optimized DataStore object, you mustchoose such time restrictions that only complete BW requests are archived.

February 2010 21

3. If you want to further customize the DAP, you can optionally perform the followingsteps on the Selection Profile tab page:

In the field Characteristic for Time Slices, choose the required level of timegranularity from the dropdown list.For example, if you select 0CALMONTH, you can archive data only as completemonths.In the group box Additional Partitioning Characteristics, define the requiredadditional characteristics. That is, if you define values here, you can setadditional restrictions during the data archiving process (for example,0CALDAY < 01.01.2000 AND 0SALESORG = EUROPE).

4. Save and activate the DAP.The dialog box Log Display appears displaying the detailed status information aboutthe created DAP for your InfoProvider.

ResultAfter you have successfully activated the DAP, the appropriate NLS tables and, if required,the tablespaces are created in the NLS tablespace. You can now archive data from thisInfoProvider to the NLS database as described in the next section.

4.2 Archiving Data to the NLS DatabaseYou use the following procedure to archive data to the NLS database by creating an archivingrequest for your InfoProvider.

Enhancement Package 1 for SAP NetWeaver BW 7.0 SP6:You can only archive data from InfoCubes if the BW requests containing thisdata have been completely compressed into the E fact table (that is,condensed).

Procedure1. In your BW system, call transaction RSA1, select the required InfoProvider and choose

Manage from the context menu.The screen InfoProvider Administration appears.

22 February 2010

2. Choose the tab page Archiving.If you access this screen for the first time, there are no archiving requests available.

3. To create a new archiving request, choose the pushbutton Archiving Request.The dialog box Create and Execute Archiving Request appears.

On the tab page Primary Time Restriction, you can choose between the following waysto specify the time interval:

Specifying relative time restrictionIn the group box Relative, you can specify if you want to archive records olderthan a certain time period – counting from today.Specifying absolute time restrictionIn the group box Absolute, you can specify if you want to archive records thatbelong to an exactly specified time frame.

You can also combine both methods. In this case, only the records that meetboth restrictions are archived.

4. If you had, for example, selected additional partitioning characteristics on the tab pageSelection Profile when the DAP was created, you can define the restrictions for thesecharacteristics on the Further Restrictions tab page of the dialog box Create andExecute Archiving Request:

February 2010 23

To define restrictions as in the example shown here, specify values in the CalendarDay, Version, and Value type fields.

5. In the field Continue Processing Until Target Status, select the target status for theprocessing of the archiving request, which can be as follows:

10 Request Generated30 Data Area of the Request is Locked Against Changes40 Write Phase Completed Successfully50 Verification Phase Ended Successfully70 Deletion Phase Confirmed and Request Completed

Once the archiving request processing has been initiated, it has status 10 RequestGenerated and the archiving request is continuously processed until the status set byyou has been reached.

By default, the status 70 Deletion Phase Confirmed and Request Completed ispreselected. The archiving request is only completed and available for reportingafter it has reached status 70. Therefore, if you set one of the previous statusvalues (for example, 40 or 50), you have to complete the processing of thearchiving request at a later point in time until status 70 is reached.

6. To execute the archiving request, you can either choose the pushbutton CreateRequest and Execute in Background (F9) or Create Request and Execute in Dialog(F8).

You can also simulate a data archiving process by choosing either thepushbutton Simulate Request Processing in the Background (Shift+F9) orSimulate Request Processing in Dialog (Shift+F8).Simulation mode means that no data is transferred to the NLS database and nodata is deleted from the BW database. However, all required parts of theprocess are executed. You can check the amount of records to be archived, andwhether any errors occur during the simulation.

If data was successfully archived (that is, transferred to the NLS database) and deletedfrom the BW database, status 70 has been reached. The InfoProvider Administrationscreen appears. All status indicators for your archiving request are displayed in green:

24 February 2010

If you were executing the archiving request in dialog mode, at the end of the dataarchiving process a new screen appears displaying the status of the archiving requestas well as log information as shown in the following figure:

If the archiving request was running as a background job, you can view the loginformation for completed archiving processes (that is, processes that are not currentlyrunning regardless of the final status) by choosing the Display Logs pushbutton on theArchiving tab page of the InfoProvider Management screen.

You can also automate the data archiving steps by defining BW process chains.For more information, see Scheduling Data Archiving Processes Using ProcessChains, for example, in the SAP NetWeaver 7.0 EhP1 Library at:http://help.sap.com/saphelp_NW70EHP1/helpdata/en/43/f0ed9f81917063e10000000a1553f6/frameset.htm

February 2010 25

Special Considerations for Write-Optimized DataStore ObjectsFor write-optimized DataStore objects, there is a minor difference in the display options onthe Requests tab page. Since write-optimized DataStore objects only support the request-based NLS archiving, the green check mark in the column Request is Archived is set for allBW requests that have been transferred to the NLS database as shown in the followingfigure:

Recommendation for Parallel NLS ArchivingTo improve the performance of the data load process, you can also start several archivingrequests in parallel for the same InfoProvider. Before you do so, you should consider thefollowing recommendations:

Define multiple data archiving requests each with a different time restriction so thatthey do not overlap. Otherwise, an error can occur and the archiving process isterminated.

The following is an example of how to define the time interval for parallel NLSarchiving:You want to archive historical data between 2001 and 2003 from yourInfoProvider to the NLS database.If you want to archive the data in three parallel archiving requests, you defineabsolute time restrictions by splitting the data into complete years, for example,Year 2001, Year 2002, Year 2003.If you want to archive the data in six parallel archiving requests, you define timerestrictions by splitting the data into six months: January 2001-June 2001,July 2001-December 2001, and so on.

You must only execute all your parallel archiving requests to target status of maximum50 Verification Phase Ended Successfully. The highest status 70 Deletion PhaseConfirmed and Request Completed can only be reached after the deletion phase.However, the deletion phase cannot be executed in parallel because of BWInfoProvider locking.

After all your parallel archiving requests have successfully reached status 50Verification Phase Ended Successfully, you should create and schedule a processchain that executes sequentially every request until the final status 70 has reached.You can also manually continue every request sequentially until status 70 DeletionPhase Confirmed and Request Completed is reached by using transaction RSA1.

26 February 2010

4.3 Reloading Archived DataOnce data has been successfully archived, you can no longer modify the data in the NLSdatabase. That is, you can neither delete nor modify the archived data (for example, youcannot add records to the archived time frame).If you want to delete the archived data from your InfoProvider or if you want to modify thedata of this InfoProvider, you must reload the data from the NLS database back into the BWsystem where data becomes changeable.

Procedure1. In your BW system, call transaction RSA1, select the required InfoProvider and choose

Manage from the context menu.The InfoProvider Administration screen appears.

2. To reload data, choose the Archiving tab page and double-click the required archivingrequest.The Process Request dialog box appears.

3. Choose the Reload radio button and execute the request either by choosing thepushbutton Execute Required Option in Background (F9) or the Execute RequiredOption in Dialog (F8).The Archiving tab page appears again and the new request transfers data from theNLS database back in to the BW system.

4. To display the latest request on the Archiving tab page, choose the Refreshpushbutton.The time restriction for the reloading request is the same as the time restriction for thecorresponding archiving request. The values displayed in the Records and Size/KBytecolumns are the same for both types of archiving requests (archiving or reloading).However, the value for the reloading request has a negative sign indicating that datawas transferred from the NLS database back to the BW system.

February 2010 27

Even after the request was reloaded into the BW system and after data wasmarked as invalid in the NLS database, the data records belonging to thatrequest still exist in the NLS database. Invalidated data records are notavailable for query reporting.To delete these data records from the NLS database, you can use the DBACockpit as described in Deleting Invalid Data from the NLS Database [page 35].

Checking for Reloaded RequestsTo check if data has been successfully reloaded into the BW system, go to the Requests tabpage on the InfoProvider Administration screen and choose the Refresh pushbutton.In the event of a successful reload, the request (without InfoPackage) appears on the list asshown in the following figure:

This new BW request contains all data from the NLS archiving request that was reloaded.You can now perform all usual operations on this request, such as, reporting, aggregaterollup, compression into the E fact table (in case of an InfoCube), deletion, and so on.

Modifying Reloaded DataAfter data was reloaded into the BW system, you can modify data by loading new data intoyour BW InfoProvider with the same time characteristics as the reloaded data. After you havemodified the data, you can then archive it again. Since you cannot directly maintain data inthe NLS database, reloading data into the BW system is the only option to change data thatwas once archived to the NLS database.

If you want to archive such a reloaded request again, you must first compressthe selected BW request into the E fact table (using the Collapse tab page onthe InfoProvider Administration screen).Afterwards, you can archive the data to the NLS database.

28 February 2010

Reloading Data for Write-Optimized DataStore ObjectsFor write-optimized DataStore objects, there is a small difference in the reloading algorithmfor the archived data:After the data was reloaded, no new requests appear on the Requests tab page. The greencheck mark in the column Request is Archived is removed from the BW requests that werepreviously archived to the NLS database, as shown in the following figure:

4.4 Using InfoProviders with NLS in aMultiProvider EnvironmentTo enable NLS support in MultiProviders of Enhancement Package 1 of SAP NetWeaver7.0 SP 6 and higher NLS, you have to extend the MultiProviders with VirtualProviders usingone of the following options:

One VirtualProvider for all InfoProviders with an NLS data archiving process (DAP) in asingle MultiProviderThis approach requires minimal modeling effort. However, note that using thisapproach can have an impact on the performance of MultiProvider queries that readdata from NLS database.

As many VirtualProviders as there are InfoProviders with an NLS data archivingprocess (DAP)This approach requires a higher modeling effort, although it provides fasterperformance due to the parallel data access.

To reach an optimal balance between performance and modeling effort, you cancombine the modeling methods described in the following.For example, if you have one MultiProvider with 10 InfoProviders that each havean NLS DAP, you can create two VirtualProviders and configure each of them toaccess 5 InfoProviders with NLS.

February 2010 29

Using One VirtualProvider for All InfoProviders with an NLS DAPBelonging to a Single MultiProviderThe VirtualProvider shown in the following figure only allows sequential access to all NLSobjects of all single InfoProviders that belong to the MultiProvider:

Procedure1. In your BW system, call transaction RSA1, select the appropriate InfoArea, and choose

Create VirtualProvider from the context menu.The dialog box Edit InfoCube appears.

2. Specify a name for the VirtualProvider to be created as well as the name of theMultiProvider that you want to use as copy source. Choose the Based on DataTransfer Process for Direct Access radio button and do not specify any other values.To continue, choose the Add pushbutton.The screen Data Warehousing Workbench: Modeling appears.

3. Save and activate the newly created VirtualProvider.4. On the screen Data Warehousing Workbench: Modeling, choose Create Data Transfer

Process from the context menu of the newly created VirtualProvider.The dialog box Creation of Data Transfer Process appears.

5. Specify DTP for Direct Access for your data transfer process (DTP) and specify theInfoProvider with NLS as data source for the DTP.The screen Change Data Transfer Process appears.

6. Choose the radio button Archive (Full Extraction Only) and save your changes.

30 February 2010

7. Repeat step 4 to 6 for each InfoProvider with NLS in your original MultiProvider. Thatis, you create several new DTPs on the same VirtualProvider.

8. On the screen Data Warehousing Workbench: Modeling, choose Activate DirectAccess from the context menu of the VirtualProvider. On the dialog box Activate DirectAccess, select all DTPs shown in the list and confirm your selection to activate thedirect access by choosing the Save Assignments (Ctrl.+S) pushbutton.

9. To enable the MultiProvider to read the NLS data, extend the MultiProvider by addingthe VirtualProvider as a new data source.

Using as Many VirtualProviders as There Are InfoProviders with an NLSDAPThe following figure shows how a setup looks like if you use as many VirtualProviders asthere are InfoProviders with an NLS DAP:

In this approach, one VirtualProvider is created for each single InfoProvider.

Procedure1. In your BW system, call transaction RSA1, select the appropriate InfoArea and choose

Create VirtualProvider from the context menu.The dialog box Edit InfoCube appears.

2. Specify a name for the VirtualProvider to be created as well as the name of theMultiProvider that you want to use as copy source. Choose the radio button Based onData Transfer Process for Direct Access and do not specify any other values. Tocontinue, choose the Add pushbutton.The screen Data Warehousing Workbench: Modeling appears.

3. Save and activate the newly created VirtualProvider.4. On the screen Data Warehousing Workbench: Modeling, choose Create Data Transfer

Process from the context menu of the newly created VirtualProvider.The dialog box Creation of Data Transfer Process appears.

5. Specify DTP for Direct Access for your DTP and specify the InfoProvider with NLS asdata source for the DTP.The screen Change Data Transfer Process appears.

February 2010 31

6. Choose the radio button Archive (Full Extraction Only) and save your changes.7. Repeat steps 1 to 6 to create for each InfoProvider (with an NLS DAP) one

VirtualProvider with one DTP.8. To enable the MultiProvider to read the NLS data, change the MultiProvider by adding

the VirtualProviders as new data sources.

32 February 2010

5 Administration of the NLS DatabaseUsing the DBA CockpitThe following sections describe how you can administer the DB2 NLS database remotelyfrom your BW system using the DBA Cockpit.To be able to do so, you first have to add the NLS database as a remote system to yoursystem landscape as described in Database Administration Using the DBA Cockpit: IBM DB2for Linux, UNIX, and Windows at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 Operations Database-Specific GuidesAfter you have successfully established a connection to the NLS database, you can startadministering it using, for example, the following general monitoring functions of the DBACockpit:

Space TablespacesLets you retrieve a list of the tablespaces created in the remote NLS database. Byselecting a tablespace and using the Contents pushbutton on the Space: TablespaceConfiguration screen, you can retrieve a list of tables that were created in a particulartablespace.Performance TablespacesLets you retrieve performance indicators about the I/O operationsPerformance Buffer PoolsLets you evaluate the efficiency of the available buffer poolsBackup and Recovery: OverviewLets you retrieve information about the existing backups of your NLS database

For more information about all available monitoring functions in the DBACockpit, see the separate document Database Administration Using the DBACockpit: IBM DB2 for Linux, UNIX, and Windows at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 OperationsDatabase-Specific Guides

In addition to the generic monitoring functions, the DBA Cockpit of your BW system offers thefollowing NLS-specific extensions:

BW Administration NLS ConfigurationThis screen provides an overview of existing connections to NLS databases. On thisscreen, you can also maintain the connection to an NLS database.For more information, see Setting Up the Connection to the NLS Database [page 11].BW Administration NLS OverviewOn this screen, you can monitor the space consumed by the InfoProviders in the BWdatabase and by NLS objects in the NLS database.In addition, you can use this function to enable BW queries to automatically access theNLS database.Jobs DBA Planning Calendar NLS Cleanup jobYou can use this NLS-specific job to remove invalid data from your NLS database.

February 2010 33

5.1 Monitoring NLS ObjectsYou can monitor, for example, the space consumption of an InfoProvider in the BW databasein comparison to the remote NLS database using the NLS-specific function NLS Overview inthe DBA Cockpit.In addition, you can also update the configuration of your BW queries so that theyautomatically read data from the NLS database. After the creation of a data archiving process(DAP), the corresponding queries receive a new property with the description Read Near-Line Storage as well. A query with this new property reads data from the normal BWdatabase as well as from the NLS database. If this new property is not set, the content of theNLS database is not accessed and not used to build the query results.

Enhancement Package 1 for SAP NetWeaver BW 7.0 SP6:By default, newly created queries ignore the data residing in the NLS database.If you also want NLS data to be read, you must change the property of a singlequery of an InfoProvider using transaction RSRT. For more information, seeExecuting Business Warehouse Queries [page 37].To change the property for all queries of an InfoProvider, you can use theEnable Queries pushbutton on the NLS Overview screen of the DBA Cockpit asdescribed in this section.

Procedure1. In your SAP system, call transaction DBACOCKPIT and choose BW Administration

NLS Overview in the navigation frame of the DBA Cockpit.2. To set a filter on the InfoProviders to be monitored, enter the required values in the

following input fields:

Field Description

InfoProvider Name Name of the InfoProvider in the BW database

InfoProvider Size Size of the InfoProvider in the BW databaseProvide a value that is lower or equal to theestimated size of the InfoProvider.

NLS Connection Name of the InfoProvider in the remote NLSdatabase

NLS Size Size of the InfoProvider in the remote NLSdatabaseProvide a value that is lower or equal to theestimated size of the NLS object.

Note that the size information displayed on the NLS Overview screen is anestimated value. The estimated value is calculated and stored in internal tablesof the DBA Cockpit when the REORGCHK for all Tables job is run for the BWand the NLS database tables using the DBA Planning Calendar of the DBACockpit. If you do not run this job, the displayed value is -1. Every InfoProvideror NLS object that has a size of -1 is also displayed in the table.

3. Choose the Apply pushbutton.The following information is displayed:

Name and size of the InfoProvider in the BW database,Name and size of the InfoProvider in the NLS database,Name of the database connection

34 February 2010

A flag to indicate if there are BW queries that are pending to be enabled to readdata from the NLS database

4. If you want to enable all BW queries of an InfoProvider to also read data from the NLSdatabase, select the InfoProvider from the list and choose the Enable Queriespushbutton.As a result, the checkbox in the Query Enabled column is selected.

5. To display more detailed information for an InfoProvider, double-click the InfoProvider.The NLS Details screen appears.

The left-hand table contains information (that is, schema name, table name, and size inKB) for the database tables of an InfoProvider in the BW database. The right-handtable contains the same information for the database tables of the same InfoProvider inthe NLS database.

Analyzing Single Tables of the BW and the NLS DatabaseBy double-clicking a cell in the left table on the NLS Details screen, you are redirected to theSpace: Tables and Indexes Details screen. On this screen, you can access detailedinformation for the selected table in the BW database, for example, about the structure of theselected table, its indexes, the tablespaces used, and so on.

February 2010 35

If you want to analyze a single NLS table, you cannot navigate to the Space:Single Table Analysis screen by double-clicking a table cell in the right table ofthe NLS Details screen.Instead, proceed as follows:1. Select the NLS database system from the Currently Selected System drop- down list in the system landscape toolbar of the DBA Cockpit.2. In the navigation frame of the DBA Cockpit, choose Space Single Table Analysis.3. On the Space: Tables and Indexes Details screen, provide the schema and the table name of the NLS table in the appropriate fields.

For more information about the information provided on the Space: Single Table Analysisscreen, see Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, andWindows at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 Operations Database-Specific Guides

5.2 Deleting Invalid Data from the NLSDatabaseWhen data is reloaded from the NLS database into the BW system, it continues to exist in theNLS database. It is marked, however, as invalid. To remove this invalid data in the NLSdatabase, you can use the NLS Cleanup job in the DBA Planning Calendar of the DBACockpit.

Procedure1. In your local BW system, call transaction DBACOCKPIT and choose Jobs DBA

Planning Calendar in the navigation frame of the DBA Cockpit.2. In the Action Pad of the DBA Planning Calendar, choose NLS Cleanup and drag and

drop it in the calendar frame.The Schedule a New Action dialog box appears.

3. On the Action Parameters tab page, specify the NLS connection and the name of theInfoProvider for which you want to delete invalid data in the NLS database.

If you want to run the NLS Cleanup job for multiple InfoProviders with similarnames, you can use the wild card character “*”.

36 February 2010

4. To run the job, you first have to specify when you want it to run:At a certain day and time by entering the respective date and time in thePlanned Start input fieldsImmediately by choosing the Execute Immediately pushbuttonPeriodically by specifying the appropriate parameters on the Recurrence tabpage

February 2010 37

6 Business Warehouse Query Processingwith NLSThe following section describes how you can execute queries on an InfoProvider for whichdata has been transferred to the NLS database.You also learn how you can use the enhanced query lookup function that improves theperformance of the query processing for certain types of queries.

6.1 Enabling Business Warehouse Queries toRead NLS DataBW reporting tools can transparently access data in the NLS database the same way as theyaccess regular data in the BW database. That is, you cannot see a difference if data for theBW query is being read from the BW database or the NLS database.To be able to read data from the NLS database, you have to enable the BW queries to alsoread NLS data. The method to enable BW queries to read NLS data for SAP systems basedon Enhancement Package 1 for SAP NetWeaver 7.0 SP6 are as follows:

You can enable a single BW query for NLS using transaction RSRT as describedbelow.

You can enable all BW queries of a single InfoProvider for NLS using the DBA Cockpitas described in Monitoring NLS Objects [page 33].

After you have enabled BW queries to read NLS data, the BW OLAP processor connects toboth the NLS database and the BW database, and reads data that corresponds to the queryrestrictions. The NLS data is also read if queries are executed using external tools, forexample, the Business Explorer (BEx).

Enabling BW Queries to Read NLS Data Using Transaction RSRT1. In your BW system, call transaction RSRT.

The Query Monitor screen appears.2. In the Query field, enter the name of the BW query and choose the Properties

pushbutton.The Query Properties Move into Query Designer dialog box appears.

3. Select the checkbox Read Near-Line Storage As Well.

Once the checkbox Read Near-Line Storage As Well is selected, the BW querypermanently keeps this status until you actively disable it again.

4. To confirm your selection, choose Enter.

38 February 2010

6.2 Using the Improved Query LookupFunctionalityWith Enhancement Package 1 of SAP NetWeaver 7.0 SP6, the standard NLS interface hasbeen extended to provide enhanced lookup functionality. The enhanced lookup functionalitynow uses a dedicated temporary table to store the records for lookup. Using a dedicatedtemporary table improves the performance of some queries that retrieve data from the NLSdatabase in combination with time-dependent filtering criteria.The NLS interface implementation based on DB2 for Linux, UNIX, and Windows has beenextended accordingly to take advantage of the new lookup functionality.To activate the use of the lookup functionality in your BW system, you must set theRSADMIN parameter RSDAI_LOOKUP to 3 as described in SAP Note 1167489. This SAPNote also contains detailed information about all available values for this parameter as wellas the behavior of the NLS solution for each of the values.

Example of How Queries Benefit from the Improved LookupFunctionalityThe NLS table /BIC/OAEMPLOYEE has time-dependent attributes for an employee. Thetable consists of the following columns:

Table Column Description

EMPLID Employee ID

DATETO Ending date

DATEFROM Starting date

Salary Salary of employee

The columns DATETO and DATEFROM define a validity interval.An NLS-enabled BW query retrieves data records from the NLS table /BIC/OAEMPLOYEEand builds its result set using a list with a combination of employee IDs (MY_EMPLID) and keydates (MY_DATE) as filtering criteria.The following table is an example of such a list:

MY_EMPLID MY_DATE

0000004711 20071231

0000004712 20071231

0000004712 20080131

0000004713 20071231

February 2010 39

For this example, the normal SELECT SQL statement to query the NLS table/BIC/OAEMPLOYEE is as follows:SELECT "EMPLID", “DATETO”, “DATEFROM”, “SALARY”

FROM "/BIC/OAEMPLOYEE"

WHERE ( "EMPLID" = '00004711' AND "DATETO" >= '20071231' AND

"DATEFROM" <= '20071231' OR

"EMPLID" = '00004712' AND "DATETO" >= '20070131' AND

"DATEFROM" <= '20070131' OR

"EMPLID" = '00004712' AND

"DATETO" >= '20080131' AND "DATEFROM" <= '20080131' OR

"EMPLID" = '00004713' AND

"DATETO" >= '20071231' AND "DATEFROM" <= '20071231' )

The NLS table contains the following rows:

EMPLID DATETO DATEFROM DEPTID SALARY

00004711 99991231 20070101 1233 200000

00004712 20080229 20070101 1234 300000

00004712 99991231 20080301 1233 350000

00004713 20071231 20070101 1234 400000

Using the SQL statement above, the result set is as follows:

EMPLID DATETO DATEFROM SALARY

00004712 99991231 20080229 300000

00004713 20070101 20071231 400000

However, if there is a large number of query restrictions, the restrictions are automaticallystored in a temporary table (for example, TEMP0001). You then use a correlated subquery toquery the NLS table. Otherwise, the built SQL statement might be too long.The following example shows a SELECT statement using the correlated subquery:SELECT "EMPLID", ”DATETO”, ”DATEFROM”, ”SALARY” FROM "/BIC/OAEMPLOYEE" U

WHERE EXISTS ( SELECT * FROM "TEMP0001" T

WHERE T."MY_EMPLID" = U."EMPLID" AND T.”MY_DATE” <= U.”DATETO”

AND T.”MY_DATE” >= U.”DATEFROM” )

40 February 2010

7 Backup and Recovery of the NLSDatabaseThe following sections provide basic information about backup and recovery of an NLSdatabase that you have to consider when using DB2 as NLS database:

Configuring the NLS Database for Archive Logging [page 40]Backing Up the NLS Database [page 40]Recovering the NLS Database [page 41]

7.1 Configuring the NLS Database for ArchiveLoggingBefore you can take a backup from an NLS database, you have to configure it for archivelogging. Archive logging enables you to take online backups as well as to recover the NLSdatabase to a certain point in time in case of a system failure.To enable the NLS database for archive logging, you have to set the database configurationparameter LOGARCHMETH1. For more information, see Enabling the Database for RollforwardRecovery in the document Database Administration Guide – SAP on IBM DB2 for Linux,UNIX, and Windows at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 Operations Database-Specific Guides

Make sure that you have configured your NLS database for archive loggingbefore you start using the NLS database.

7.2 Backing Up the NLS DatabaseAs for any other database in your system landscape, you have to define an appropriatebackup and recovery strategy for the NLS database. This NLS-specific strategy depends on,for example, available hardware, backup devices, and so on. Since new data is lessfrequently added to the NLS database than to a BW database, you do not have to takebackups from the NLS database as often as from a BW database.The execution of BW queries does not change the data in the NLS database because the BWqueries only read data. The only operations that change data in the NLS database arecreating, modifying, or deleting a data archiving process, archiving data to NLS database,and reloading data back into the BW system.For the NLS database, the same backup methods are supported as for the BW databasebecause the NLS database is a regular DB2 database. That is, you can perform an offline oronline backup, you can start a backup directly from the DB2 command prompt, or you canschedule a backup job using the DBA Planning Calendar in the DBA Cockpit.For more information about how to schedule a backup job in the DBA Planning Calendar, seeDatabase Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 Operations Database-

Specific Guides

February 2010 41

For more information about database backups, see the Database Administration Guide –SAP on IBM DB2 for Linux, UNIX, and Windows at:http://service.sap.com/instguidesnw SAP NetWeaver 7.0 Operations Database-Specific Guides

7.3 Recovering the NLS DatabaseYou have to recover the NLS database in one of the following situations:

The BW database fails while data is being transferred to the NLS database. You have to restore and roll forward the BW database to a specific point in time. Due to a hardware failure in your system landscape, you have to recover the NLS

database.To fully recover the NLS database, you have to perform the following steps from thecommand line:

1. You restore the NLS database using a suitable backup image.2. You roll forward the NLS database using the available log files to the end of logs or to a

specific point in time.However, note that the successful execution of the required commands does not guaranteethat the information in the NLS database is logically consistent with the BW databasebecause these are two different databases.

For example, the BW database is in a consistent state and contains the datafrom today. The NLS database is also in consistent state but contains data fromyesterday.This means that the data that was archived to the NLS databasetoday might be missing.

The NLS solution based on DB2 for Linux, UNIX, and Windows is able to identify whether theNLS database is logically consistent with the BW database by comparing timestamps. If thisis not the case, no connection to the NLS database is allowed until the inconsistencies havebeen resolved.In addition, you can perform a consistency check in your BW system using function moduleFM_RSDA_DB6_SYNC_CHECKER as described in the following.

Checking the Database Consistency Using Function ModuleFM_RSDA_DB6_SYNC_CHECKERThe NLS solution includes function module FM_RSDA_DB6_SYNC_CHECKER that allows youto check the current logical state of both the BW and the NLS database. Each time youexecute this function module, it returns the current status of both databases and suggests, ifrequired, the steps to perform to reach a consistent status.

We strongly recommend that you use this program for consistency checks notonly occasionally but especially after either the NLS or the BW database hascrashed.

42 February 2010

Procedure1. In your BW system, call transaction SE37.

The screen Function Builder: Initial Screen appears.2. In the Function Module input field, enter FM_RSDA_DB6_SYNC_CHECKER and choose

the Test/Execute (F8) pushbutton.The screen Test Function Module: Initial Screen appears.

3. Enter the name of the NLS connection in the input field beside theI_NLS_CONNECTION import parameter and choose the Execute pushbutton.

The report displays one of the following messages:Status normal: BW and Near-Line Storage databases are completely in sync.

The timestamps of the last operation on the NLS database are identical in boththe BW database (export parameter E_BW_TIMESTAMPL) and the NLSdatabase (export parameter E_NLS_TIMESTAMPL).Warning: Some Archiving Requests are not in sync.

February 2010 43

Some data archiving requests were running when one of the databasescrashed. As a result, these requests are now in an inconsistent state. The NLSdatabase is not available but it can be repaired. For more information about thesolution to this problem, see SAP Note 1405664.You can display the InfoProvider names containing the inconsistent requests bydouble-clicking the output table E_NLS_CUBES_DETAILS.

Error: BW and NLS databases are not in sync. The Near-Line Storage databasemust be restored and rolled forward to the timestamp <consistent_time>.

The NLS database is in a different logical state than the BW database andcontains different data. One possible cause for this problem can be a databasecrash (either the BW database or the NLS database) with the resulting rollbackof some transactions. Therefore, the NLS database is not available until it hasagain been synchronized with the BW database.You can solve this problem by restoring your NLS database to the point in timethat is displayed in the output of function moduleFM_RSDA_DB6_SYNC_CHECKER (see export parameter E_BW_TIMESTAMPL).

44 February 2010

8 Using DB2 as NLS Database with a BWSystem Running on a Different DatabasePlatformThis section provides information that you have to consider if you are planning to use the IBMDB2 NLS solution with a BW system that is running on a different database platform.If your BW system is running on different database platform, you can still archive data fromyour InfoProviders to the DB2 NLS database, reload data into the BW system, and queryNLS data without any dependencies. However, there are differences in the basicconfiguration and operations that you have to consider. These differences are as follows:

Configuring the NLS connection for non IBM DB2 for LUW databases Using the NLS objects viewer for non IBM DB2 for LUW databases

Configuring the NLS Connection for Non-IBM DB2 for LUW DatabasesAfter you have installed DB2 as NLS database using SAPinst [page 9], you have to manuallyconfigure the connection to the NLS database because the DB2 NLS-specific extensions inthe DBA Cockpit are only available if your BW system is running on DB2.To configure the DB2 NLS database as remote database in your DBA Cockpit, follow theinstruction in SAP Note 1405664.After you have configured the database connection and the NLS connection, you can startcreating DAPs for your InfoProviders and transferring data into the DB2 NLS database.

Using the NLS Objects Viewer for Non-IBM DatabasesThe DB2 NLS solution includes function module FM_RSDA_DB6_OBJECTS_VIEWER. You canuse this function module to display the list of the BW tables for a given InfoProvider, and thecorresponding list of NLS tables. This is especially useful because your BW system isrunning on a different database platform than DB2, which means that DB2 NLS-specificextensions in the DBA Cockpit are not available.To display BW and NLS tables for a given InfoProvider, proceed as follows:

1. In your BW system, call transaction SE37.The screen Function Builder: Initial Screen appears.

2. Enter FM_RSDA_DB6_OBJECTS_VIEWER in the Function Module input field andchoose the Test/Execute (F8) pushbutton.The screen Test Function Module: Initial Screen appears.

February 2010 45

3. Enter the following parameters and choose the Execute pushbutton.I_INFOPROVIDER_NAME:Enter the name of the InfoProvider using NLS.

You can also specify the wildcard ‘*’ as the part of the name, or just enter thewildcard ‘*’ to display all NLS tables for all InfoProviders.I_NLS_CONNECTION:Enter the name of the NLS connection.

To display a list with the InfoProviders matching the selection criteria specified in step3, double-click the result table E_NLS_OBJECTS on the output screen:

If you double-click an entry in the NLS_TABLES_DETAILS column, the functionmodule displays another table with detailed overview information including the tablenames of both the BW InfoProvider and the appropriate NLS object.The table size information (for example, in columns INFOPROVIDER_SIZE andNLS_SIZE) is displayed after you have installed the latest version of the functionmodule FM_RSDA_DB6_OBJECTS_VIEWER. For more information about functionmodule FM_RSDA_DB6_OBJECTS_VIEWER, see SAP Note 1405664.