live cache administration sap

SAP AG 1999

BC555 liveCache Administration

R/3 Release 4.6C 50040750 R/3 Release 4.6C 50040750

liveCache AdministrationliveCache Administration

��R/3 ��Release 4.6 C ��Material Number 5004 0750

SAP AG 2002

Copyright 2002 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted inany form or for any purpose without the express permission ofSAP AG. The information contained herein may be changedwithout prior notice.

All rights reserved.

Copyright

Trademarks:

��Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

��Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

��IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

��ORACLE® is a registered trademark of ORACLE Corporation.

��INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

��UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

��HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

��JAVA® is a registered trademark of Sun Microsystems, Inc.

��JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

��SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

© SAP AG BC555 1-1

SAP AG 1999

6$3�%DVLV�$GPLQLVWUDWLRQ�7UDLQLQJ��([SHUW�&RPSHWHQFH

��

&RUH�&RPSHWHQFH

�! #"�$�%3 days

Advanced R/3 System Administration

&'�( �"�$2 days

R/3-Technical Implementation and Operation Management

Technical Core Competence

�) +*�,�, 5 days

�) #"�-�%3 days

Software Logistics

�! #"/.�%3 days

Workload Analysis

�) )%�"�%3 days

Database AdministrationDB2 UDB

�) )%�"�$5 days

Database AdministrationDB2/390

0�1�2�2 3547681�98:�; 9=<(>�? @BADC54E; 4F 9818G/H 3I:7<73BJK2 17:�L8M5N7C89E:=? 1�2O�P�JRQ7S76=382 N F 9E1=G/H 3I:T<E3UAK171�V

�) )%�$�%3 days

DatabaseAdministration Oracle

DatabaseAdministration Informix

�) )%/.�.5 days

DatabaseAdministration SAP DB

�) )%/.�%2 days

�) )%�-�$3 days

Database AdministrationMS SQL Server

WYX 3IMEZ797; M=C8H[0�1�2 3/0�1�\]6835N 3E98MI3�^�3E2 4E; 1T984

AD0�@E_[`ba#; 9=:T1=G�4Uc X ?Ed�2 CIM=H 3AD0�@E_[eba#; 9=:T1=G�4Uc X ?EOEP�J(f�AAD0�@E_hgia#; 9=:T1=G�4Uc Xkj O!OTlnmUO�382 o83E2AD0�@E_[prq a�; 97:817G�4sc X ?7t�c�u vKw8?7f�AKeAD0�@=xI`yt�cDu vR?8d�2 C=M8H 3AD0�@=x8_zt�cDu vR?7u 98{ 1�2�\]; SAD0�@=xIeyt�cDu vR?8O�P�J(fDAAD0�@=pI`yu A j P�O�g=`I`AD0�@=|I`yu A j ? @I|=`W}W AD0�@=~I`ba!1T2YVI6EH C=MI3n� �� D�T�I��

�) )"�%�$��=�3 days

TCC Workplace

�) )%�%�%2 days

LiveCache Administration

�) )%�-�%3 days

Database AdministrationDB2/400j�� @=`=_�e/:7CI�I4

Workplace

© SAP AG BC555 2-1

SAP AG 1999��

6$3µV�.QRZOHGJH�7UDQVIHU�0RGHO

�� "! #%$'&�#(*)+� $*,%-/.10

2'#%-434�'5 -764!8 #4)1.�5 9�5 -/67.�5 �*�/0

�� :� � � ��

; <>=%#�) .?�@� ��A! #%$�&�#BC��*DFEG#4)�5 #70

�� >� HI� ��J�� SAP AG 1999 fi lename (author) / 2

D atabase Administrat ionSA P DB

K L M N M2 days

O P Q R O P S T R U R V W R X Y T R Q U O P S T R U R V W R

K L Z [ M3 days

Advanced R /3 System Administratio n

\Techni cal C or e Competence Versi ons

BC310 Windows NT / Oracl eBC314 Wi ndow s NT MS SQL Serv erBC317 (W indow s N T / U N IX) / D B2BC360 UNI X / OracleBC362 UNI X / SAP DB

] K L Z [2 days

R /3-Techni cal I mp lementation and Operation M anagem ent

Technical C ore Com petence

K L ^ _ _ \5 days

L ` a a b c d ` e f g e h i j Z K k c g cl e ` m n b f h b o a ` f p q r

K L M [ M3 days

D atabase Administrat ionORAC LE

K L Z s M3 days

Soft ware L ogistics

K L M s [3 days

D atabase Administrat ionM S SQL S erver

t u v w x y z y u { | z } z y ~ � x ~ z � } � � x z } z } � � � �

K L M Z M3 days

D atabase Administrat ionD B2 UD B

SAP AG KTM mySAP.com for Techn. Imp l., IT Cons. , Sys. Integration UH / 7

� � � � � � � � � � � � � � � � � � � � �� (SD) 2 days

� � � � � � � � � � � � � � � � � � � � �� ¡ � � � ¢ � � � ¡ � � � � �� (SD) 2 days

� � � � � � � � � � � � � � � � � � � � �� £ � � � � � � � � � � � � � � � � �� ¤ (SD) 2 days

� � � � � � � � � � � � � � � � � � � � �� ¥ � � ¡ � � ¦ � � � � � � � � �� §( SD) 2 day s

� � � � � � � � � � � � � � � � � � � � �� ¨ � � � � � � � � � � � � � �� © ( SD) 1 day

� � � � � � � � � � � � � � � � � � � � �� ¡ � � � ¢ � � � � � � � �� ª ( SD) 1 day

� � � � � � � � � � � � � � � � � � � � �� « ( SD) 1 day

� � � � � � � � � � � � � � � � � � � � �� £ � � ¬ � � � � � � � � �� ¡ � � � � � � � � ¡ � � � � � � ( PP) 2 day s

� � � � � � � � � � � � � � � � � � � � �� ® � � � � ¯ � � � � ° ¥ � � � ¬� � ¥ � �( SD/PP) 2 day s

� � � � � � � � � � � � � � � � � � � � �� ¦ ± � ± � � � � ¡� � � � � � � � � � � � � � � ��

( PP) 2 day s

� � � � � � � � � � � � � � � � � � � � �� ¯ � � � � ° � � � � ° � � � � � ² ( C O) 2 days

� � � � � � � � � � � � � � � � � � � � �� ¥ � � � � � � � � � � � �� ¡ � � � � � � � � ¡ � � � � ¥ � ¤ (PP/ CO) 2 days

� � � � � � � � � � � � � � � � � � � � �¢ � � � � � � � � � ¡� � � � � � � � ¦ � � � � � � � � �� ¥ � ª ( SD) 2 days

³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¶ ¹ ¾ ¿ À ¶ µ ¿ Á Â µ µ Ã º Ä Å Æ º ¶ » Å » Ç È ¹ ¶ ¿ ¿Â µ µ Ã º Ä Å Æ º ¶ »

É £ Ê � � � � � � �� ¡ Ë � � ¯ � �� ¬ � � �

� � � � � � � � � � � � � � � � � � � � �� ¥ � � � � � � � � � � � �� Ì � � � � � � � � ¥ � �

( SD/PP) 2 days

³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¶ ¹ ¾ ¿ À ¶ µ ¿

2�#%-434�'5 -764!�2C)Í6�5 ��5 � &Î6�� $ÏÐ�>)�D�0'3%�*=/0�� >� Ñ�Ò�Ó��:� Ô �� Õ��Ö ×�Ô ��

�� '� HI�� Ô ��ØI�Ù�Ö ��Ò

E>ÚÛ(ÝÜF�G5 �%&*Þ45 ß%# 8 3/#�- D �� >� à ��Ô á�â�Ô × ��ã7��J

E>ÚÛ(ä;�6�):! å/Ïæ6/.+-43çE*#4)Íß'5 -/# �� >� Ñ��Ö è é�êë��

E>ÚÛ(ä;�6�):! å/Ïæ6/.+-43�Úì! #�)Í. �� >� Ñ�ê@í

E>ÚÛ( 8 �G�%04,'! .�5 ��&ÎEG#�) ß>5 -7#I0 �� >� ã7�� Ó�è � Ô �á�Õ��Ö × Ô ��

2'#/6 îAE'ÚÛ(ÎE�,'=�=%�G)1. �� >� �� >Õ�í�Ù�� Ó��Ö �

© SAP AG BC555 3-1

SAP AG 1999

&RXUVH�3UHUHTXLVLWHV��7DUJHW�*URXS��'XUDWLRQ

l &RXUVH�3UHUHTXLVLWHV� %&��RU�VLPLODU�6$3�V\VWHP�DGPLQLVWUDWLRQ�FRXUVH�

DOWHUQDWLYHO\�'DWDEDVH�$GPLQLVWUDWLRQ�FRXUVH�OLNH�%&��%&��«

l 5HOHDVH�GHSHQGHQF\�� $32�5HOHDVH��$�DQG�OLYH&DFKH�UHOHDVH��

l 7DUJHW�*URXS� 3URMHFW�WHDP�PHPEHUV�UHVSRQVLEOH�IRU�WKH�LQVWDOODWLRQ�DQG

PDLQWHQDQFH�RI�D�OLYH&DFKHl 'XUDWLRQ��GD\V

© SAP AG BC555 3-2

SAP AG 1999

7KLV�FRXUVH�ZLOO�HQDEOH�\RX�WR�l 'HILQH�$32�V\VWHP�UHTXLUHPHQWVl ,GHQWLI\�WKH�VSHFLILF�OLYH&DFKH

FRQILJXUDWLRQ�LQ�WKH�6$3�HQYLURQPHQWl 3HUIRUP�OLYH&DFKH�PRQLWRULQJ�DQG

PDLQWHQDQFHl /LVW�DQG�SHUIRUP�ZRUN�ZLWK�'%0*8,�DQG

6$3�DGPLQLVWUDWLRQ�WRROVl 8QGHUVWDQG�EDFNXS�DQG�UHFRYHU\

FRQFHSWV�RI�OLYH&DFKH�LQ�WKH�$32V\VWHP

&RXUVH�*RDO

© SAP AG BC555 3-3

SAP AG 1999

&RXUVH�2YHUYLHZ

&RQFOXVLRQ

&RXUVH�&RQWHQWV

Unit 4 OLYH&DFKH�0RQLWRULQJUnit 5 OLYH&DFKH�%DFNXS�DQG5HVWRUH�7HFKQLTXHVUnit 6 OLYH&DFKH�%DFNXS�DQG5HVWRUH�IRU�$32

Unit 1 OLYH&DFKH�&RQFHSWVUnit 2 OLYH&DFKH�$UFKLWHFWXUHDQG�5HTXLUHPHQWVUnit 3 OLYH&DFKH$GPLQLVWUDWLRQ

© SAP AG BC555 4-1

SAP AG 1999

��OLYH&DFKH�&RQFHSWV�

��OLYH&DFKH�%DFNXS�DQG5HVWRUH�IRU�$32

��OLYH&DFKH�$UFKLWHFWXUHDQG�5HTXLUHPHQWV

��OLYH&DFKH�$GPLQLVWUDWLRQ

��OLYH&DFKH�0RQLWRULQJ

��OLYH&DFKH�%DFNXS�DQG5HVWRUH�7HFKQLTXHV

OLYH&DFKH�&RQFHSWV

© SAP AG BC555 4-2

SAP AG 1999

l 'HVFULEH�WKH�SXUSRVH�RI�OLYH&DFKHl 'HVFULEH�WKH�DUFKLWHFWXUH�RI�6$3�V\VWHPV

XVLQJ�OLYH&DFKH�WHFKQRORJ\l 'HVFULEH�KRZ�OLYH&DFKH�LQWHUIDFHV�ZLWK

6$3�EDVLV�WHFKQRORJ\l ([SODLQ�ZKLFK�GDWD�DUH�VWRUHG�LQ�OLYH&DFKH

DQG�KRZ�WKH\�JHW�WKHUH

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW�\RX�ZLOO�EH�DEOH�WR�

OLYH&DFKH�&RQFHSWV

© SAP AG BC555 4-3

SAP AG 1999

5��5��3,

6$3%:

/HJDF\2/73

1RQ�6$32/73

1RQ�6$32/73

4XHXHG�5)&��T5)&��6\QFKURQRXV�5)&��V5)&��%$3,Model Generator, mapping, connectivity

$322SWLPL]HUVOLYH&DFKHOLYH&DFKH

3URGXFWLRQ3ODQQLQJ�'HWDLOHG�

6FKHGXOLQJ

'HPDQG3ODQQLQJ�XVHV�%:�

9HQGRU0DQDJHG,QYHQWRU\

6XSSO\1HWZRUN3ODQQLQJ

$YDLODEOH7R

3URPLVH

� � �

6XSSO\�&KDLQ�&RFNSLW

'DWDEDVH�ZLWK�%:�WHFKQLTXHV

DYDLODEOH

$SSOLFDWLRQ�DQG�%DVLV�&RPSRQHQWV�RI�6$3�$32

&DSDEOH7R�

0DWFK

n liveCache is a component of the SAP New Dimension Product APO (Advanced Planner andOptimizer).

n As of Release 4.5A, the SAP system can connect to multiple databases. The APO system utilizes thisfunctionality and connects to two database systems:

é the liveCache system which uses object-oriented and memory-based computing

é the APO relational database management system (RDBMS), which contains persistent data and iscomparable to the RDBMS of a standard SAP system. It provides Business InformationWarehouse (BW) functionality that is mainly used by the application module Demand Planning.

n APO modules SNP, CTM and PP/DS use additional standalone programs called optimizers whichalso communicate with the liveCache. These programs provide sophisticated optimizationalgorithms.

n SAP R/3 uses the APO-CIF interface to handle data transfer to APO. APO-CIF is part of R/3 PlugIn, a collection of interfaces to the different components of the mySAP.com system landscape. TheAPO system and APO-CIF communicate through qRFC (asynchronous RFC call with secure transfer(tRFC) and guaranteed sequence as defined in the OUT-queue) and sRFC (synchronous RFC, usedby ATP) calls with SAP systems. This allows for a seamless integration of APO functions into thecustomer’s SAP system landscape.

n APO can also communicate with legacy systems that may include Online Transaction Processing(OLTP) systems and non-OLTP systems (for example, batch processing systems).

© SAP AG BC555 4-4

SAP AG 1999

OLYHOLYH&DFKH�7HFKQRORJ\&DFKH�7HFKQRORJ\

$%$3$%$3

5'%065'%06

!��PV&��

��µV

$SSOLFDWLRQ�6HUYHU

'DWDEDVH�6HUYHU

OLYH&DFKH�6HUYHU

l OLYH&DFKH�LV�DQ�REMHFW�RULHQWHG�GDWDEDVH�PDQDJHPHQW�V\VWHPGHYHORSHG�E\�6$3�WKDW�UHVLGHV�LQ�D�YHU\�ODUJH�PHPRU\�

l 2SWLPL]HG�&��SURJUDPV�UXQ�RQ�WKH�OLYH&DFKH�VHUYHU�DQG�KDYHDFFHVV�WR�OLYH&DFKH�GDWD�

l 7KH�PDLQ�REMHFWLYH�LV�WR�RSWLPL]H�SHUIRUPDQFH�� OLYH&DFKH�UHVLGHV�LQ�PDLQ�PHPRU\�DQG�WKHUHIRUH�DYRLGV�GLVN�,�2� 2EMHFW�RULHQWDWLRQ�HQDEOHV�HIILFLHQW�SURJUDPPLQJ�WHFKQLTXHV� OLYH&DFKH&DFKH�SURFHVVHV�SURYLGHV�VFDODELOLW\

OLYH&DFKHOLYH&DFKH

n In a standard SAP system, typical database request times are above 1 ms. For data intensiveapplications, a new technology is required in order to achieve better response times. liveCache hasbeen developed to reduce typical database request times to below 10 µs. Key factors in achievingthese response times are:

é Accesses to liveCache data usually do not involve any disk I/O

é The processes accessing the data are optimized C++ routines that run in the process context of theliveCache on the liveCache server

é Object orientation enables the use of efficient and versatile programming techniques

n APO is the first product to use liveCache technology.

n In principle, multiple liveCache instances can be used in parallel to increase performance for variousapplications. APO does not yet use this possibility. Currently two logical connections to liveCacheare used by APO. Both connections point to the same physical liveCache.

é Logical connection LCA is used by all APO application modules but GATP.

é Logical connection LDA is used by GATP only.

© SAP AG BC555 4-5

SAP AG 1999

$FFHVVLQJ�OLYH&DFKH

64/�GDWD2EMHFW�GDWD

7\SH�OLEUDU\

5HJLVWU\

)UDPHZRUN�IRU�PHWKRG�HPEHGGLQJ

64/64/�EDVLV�% �WUHHV�

&RPPDQG�DQDO\]HU

206�EDVLV�SDJH�FKDLQV�

20664/FODVV

'DWD�&DFKH

&20�REMHFWV��'//�

64/�/RJ

OLYH&DFKH

OLYH&DFKH

'DWDE

DVH�L

QWHUID

FH�RI

�6$3�N

HUQHO

�1DWL

YH�64

/�2S

WLPL]H

UV�61

3��&7

0�DQ

G�33�'

6�1

DWLYH

�64/�

n ABAP Programs and the APO optimizers use native SQL for communicating through the standardSAP database interface to liveCache. liveCache has an SQL interface that is used to communicatewith the SAP instances. With native SQL, ABAP programs call stored procedures in the liveCachethat point to Component Object Model (COM) routines written in C++. An SQL class providesaccess from the COM routine to the SQL data.

n In an SQL trace of an APO application, the statements for calls to COM routines contain the stringDBPROC SAPR3."SAPAPO_.

n The COM routines are part of a dynamic link library that runs in the process context of the liveCacheinstance. In the Windows NT implementation of liveCache, COM routines and their interface areregistered in the NT Registry. For the Unix implementation, a registry file is provided by liveCache.A persistent C++ class provides the COM routines with access to the corresponding ObjectManagement System (OMS) data that is stored in the liveCache.

n All liveCache data are stored in the caches as well as, if necessary, on disk in 8 Kbyte blocks calledpages.

n liveCache stores the OMS objects in page chains, the pages in the chain linked by pointers. SQLtable data are stored in the form of B* trees. SQL and OMS data reside together in the data cache ofthe liveCache. Each page in liveCache is marked as an SQL page or an OMS page.

© SAP AG BC555 4-6

SAP AG 1999

OLYH&DFKH�3URJUDPPLQJ�&RQFHSWV

l 7UDQVDFWLRQ�&RQFHSW� /RFNLQJ� 5ROOEDFN� &RPPLW� 5HDG�FRQVLVWHQF\

l OLYH&DFKH�VXSSRUWV�WKH�IROORZLQJ�REMHFW�RULHQWHG�FRQFHSWV� (QFDSVXODWLRQ� 8QLTXH�REMHFW�LGHQWLW\� 0HWKRGV�VXFK�DV�LQVWDQFH�DQG�FODVV�OHYHO

l 7KH�IROORZLQJ�FRQFHSWV�DUH�LPSOHPHQWHG�LQ�WKH�&��DSSOLFDWLRQ�OD\HU�

� $EVWUDFW�FODVVHV� ,QKHULWDQFH� 3RO\PRUSKLVP� $JJUHJDWLRQ

OLYH&DFKHOLYH&DFKH

n The transaction concept common to relational database systems is also available for liveCacheobjects. liveCache supports read-consistency, that is, the data returned by liveCache represent thestate of the data at the time, when the transaction that issued the read operation was started, even ifsome of these data have changed during retrieval by liveCache.

n The liveCache concept incorporates both SQL data access and object orientation. The COM routineshave direct access to the objects stored in the liveCache and can manipulate them. This manipulationincludes creation and deletion of objects in the liveCache .

n On the liveCache level, the following object-oriented features are implemented:

é Encapsulation: keeping together data structures and the methods which act on them

é Unique object identity: each object has its own set of variables belonging to its class

é Methods: procedures or routines associated with one or more classes

n The following object-oriented features can be implemented on the C++ routine level:

é Abstract classes: parent classes from which sub-classes may be derived (cannot be instantiated)

é Inheritance: derived subclasses inherit instance variables and methods of the superclass

é Polymorphism: variables may refer at run-time to objects of different classes

é Aggregation: a technique for building a new object from one or more existing objects

© SAP AG BC555 4-7

SAP AG 1999

$32�'DWD�LQ�OLYH&DFKH

OLYH&DFKH�6HUYHU$32

$32�'DWDEDVH$32�'DWDEDVH

$SSOLFDWLRQ

$SS

$SS �6

HUYHU

�6HUYH

U)URQWHQG)URQWHQG

OLYH&DFKHGHYVSDFHV

0DVWHU�GDWD7UDQVDFWLRQ

GDWD

OLYH&DFKHOLYH&DFKH

'DWD�PXVW�EHFRQVLVWHQW�

n Some APO data only exist in the APO DB, others only in liveCache, some data are stored in APOdatabase and liveCache. Data in APO DB and liveCache have to be in a consistent state. It is notacceptable, if redundant data are only present in liveCache and not in APO DB or vice versa.

é The APO DB contains master data like resources, materials, PPMs (Production Process Models),setup matrices, location definitions, transportation lanes, planning books and customizing data.

é The APO DB also contains some transaction data including texts

é As of APO release 3.0A, liveCache contains time series of current planning data from DemandPlanning.

é liveCache stores master data in compressed form (information like material texts is not required byCOM routines). Transaction data (e. g. sales order, confirmed shipments, purchase ordersincluding items and schedule lines and stock) is stored only in liveCache to improve performance.For planned and production orders, this is almost all data which is generated during BOMexplosion and routing (PPM and PPU, Production Planning Unit).

é SQL tables /SAPAPO/ORDKEY and /SAPAPO/ORDMAP are stored in liveCache as well.

© SAP AG BC555 4-8

SAP AG 1999


$32�'DWDEDVH$32�'DWDEDVH

$SSOLFDWLRQ

$SS

$SS �6

HUYHU

�6HUYH

U)URQWHQG)URQWHQG

OLYH&DFKHGHYVSDFHV

0DVWHU�GDWD7UDQVDFWLRQDO

GDWD �� 'HOHWH�GHUHIHUHQFHGGDWD�LQ�$32�'%

/RDGLQJ�'DWD�LQWR�OLYH&DFKH

OLYH&DFKHOLYH&DFKH

�� 5HORDG�PDVWHU�DQGWUDQVDFWLRQ�GDWD�IURP�$32'%�WR�OLYH&DFKH

�� ,QLWLDOL]HOLYH&DFKH

�� 5HORDG'3�GDWD

n liveCache can be re-initialized. As a result, all data in liveCache are deleted. This is, e.g., required ifa new version of COM routines with a modified interface to the objects in liveCache is installed.After such an initialization, report /SAPAPO/DELETE_LC_ANCHORS synchronizes APO databaseand liveCache.

é SQL tables /SAPAPO/ORDKEY and /SAPAPO/ORDMAP are re-created in liveCache

é Data in the APO database is deleted, which refers to orders stored in the liveCache

é All required data must be transferred from APO database into liveCache. These include resources(biggest part of data, can be loaded in parallel), setup matrices and product-location combinations.

é You can use the Copy Management of Demand Planning to copy one or more key figures fromplanning areas in liveCache into a pre-defined backup info cube. If you have backed up DemandPlanning data into such a backup infocube, reload these data into liveCache.

© SAP AG BC555 4-9

SAP AG 1999

OLYH&DFKH�$GPLQLVWUDWLRQ��'%0*8,�DQG�/&��

n liveCache, like the standard SAP RDBMS, can be administered from within the SAP system. Youcan use the administration tools DBMGUI, dbmcli and the SAP transaction LC10 to monitor,configure and administer liveCache. As the basic functionalities of an SAP system are still availablewithout liveCache, LC10 allows for additional actions like starting and stopping the liveCache.

n DBMGUI is a graphical user interface to the liveCache management client interface dbmcli. BothDBMGUI and dbmcli can be used for all liveCache administration tasks including backup andrestore.

n From the initial screen of transaction LC10, you can access the:

é “liveCache administration” menu (for liveCache administration)

é “liveCache configuration” menu (for liveCache administration)

é “liveCache console” menu (for liveCache monitoring using calls to x_cons)

é “liveCache monitor” (for statistics about calls to database procedures)

é “liveCache performance” menu (for monitoring the performance of the liveCache)

© SAP AG BC555 4-10

SAP AG 1999

OLYH&DFKH�&RQFHSWV��8QLW�6XPPDU\

<RX�DUH�QRZ�DEOH�WR�l 'HVFULEH�KRZ�OLYH&DFKH�FRQFHSWV�DUH�XVHG�WR

DFKLHYH�IDVW�UHVSRQVH�WLPHV�LQ�DSSOLFDWLRQV�ZLWK�DKLJK�GDWD�YROXPH

l ([SODLQ�WKH�REMHFW�RULHQWDWLRQ�RI�OLYH&DFKHl 'HVFULEH�KRZ�OLYH&DFKH�LQWHUIDFHV�ZLWK�WKH�6$3

V\VWHPl 1DPH�WKH�OLYH&DFKH�DGPLQLVWUDWLRQ�WRROV

© SAP AG BC555 4-11

SAP AG 1999

8QL[�6HUYHU__________

L01: l01adm

L15: l15adm

.

.

17�7HUPLQDO�6HUYHU________

LCAOMO

APO System202�(3.0A)

Check, ifbc555-NN exists.If not: Copy UserTraining/bc555to bc555-NN

7UDLQLQJ�JURXSVNN01

02

DBMGUI

L02: l02admRegister

telnet:user

l02admpasswordl02adm

R/3 System'(9�(4.6C)

Check, ifbc555-NN exists.If not: Copy usertraining/bc555to bc555-NN

..

15

StartDBMGUI

usingTS Client

LC10:user

bc555-NNattaches

LNN

([HUFLVHV��6HUYHU�/DQGVFDSH

n Each group NN logs on to unix server ___________ with telnet and lNNadm/lNNadm as userpassword/combination. On this server,

é a liveCache LNN is available for the group NN, lNNadm is the <SID<adm> liveCacheadministration user.

é 1 R/3 system DEV is available, administered by devadm user. Attach your liveCache totransaction LC10 and make user and password for user lNNadm known to R/3 adminstratordevadm.

n Each group calls DBMGUI application. The NT application DBMGUI actually runs on the terminalserver _________ and is called with the help of a terminal server client. Register your liveCacheLNN in DBMGUI. Depending on the terminal server setup, you will have to repeat this registrationafter each startup of DBMGUI, as log on to terminal server happens with a temporary user.

n See section Preliminaries in the exercises for further details on the server landscape and availableusers for operating system and SAP systems.

© SAP AG BC555 4-12

([HUFLVHV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�Due to the particular requirements of this course, its actual implementation may vary betweenindividual training centres. Before commencing the following exercises, please ensure yourinstructor has explained in detail the network and hardware topology in place for yourparticular training environment.

You will be assigned a number that uniquely identifies the resources that are assigned to youduring this course – network login id, APO system login id, logical OLYHCache.

The default configuration is the following:

On a Unix server (instructor will let you know the name at the beginning of the course), theSAP system DEV (Rel 4.6C) is available. In addition, 15 OLYHCaches with SID ranging betweenL01 and L15 are available for the groups.

On a Windows NT terminal server, program DBMGUI is available for administration of theOLYHCaches installed on the Unix server. In addition, APO system OMO (APO release 3.0A) isavailable for APO specific topics.

Each two course attendees that share a training PC, form a group. Each group is assigned anumber ranging from 01 to 20 in the following wayGroup 01 is the rightmost group in the first row (as seen from the instructor). Example ofgroup number assignment in other rows: If group 04 is the leftmost group in row 1, then therightmost group in row 2 is assigned number 05.

$V�VHHQ�IURP�WKH�WUDLQHU $V�VHHQ�E\�FRXUVH�DWWHQGHHV07 08 09 10 11 12 Trainer

01 02 03 04 05 06 01 02 03 04 05 06

Trainer 07 08 09 10 11 12

Logon to Unix server: Group NN can log on to Unix server using telnet as lNNadm withpassword lNNadm (Example for group 01: user l01adm, password l01adm). On this server aliveCache LNN is available and will be administered by group NN (Example: group 01 willadminister OLYHCache L01)

Logon to Windows Terminal server: Simply click the DBMGUI server icon and DBMGUI willbe started in a separate window. Group NN has to register OLYHCache LNN for administrationpurposes.

SAP Systems DEV and OMO: You can log on info with user training, password bc555. Afterloging on, copy user training to user BC555-<NN> (Example BC555-01 for group 01) with thehelp of transaction SU01. If user BC555-NN is already defined, change the password to bc555-NN. Group NN has to register OLYHCache LNN for administration with transaction LC10

© SAP AG BC555 4-13

�([HUFLVHV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�To perform the following exercises, you will need to logon to the SAP systems OMO andDEV. To do this, please follow the instructions given to you by your course instructor.

1R� ([HUFLVH� 6KRZ�EDVLF�$32��OLYH&DFKH�UHODWLRQVKLS�1.1 What OLYHCache(s) are defined to APO system OMO?

1.2 Which logical OLYHCache is used by the majority of APO application components?

1.3 Which logical OLYHCache is used by ATP (Available To Promise)?

1.4 On what server is logical OLYHCache “ LCA“ of the APO system OMO running?

� OLYH&DFKH�DGPLQLVWUDWLRQ��PRQLWRULQJ�WRROV��8VH�6$3�V\VWHP�'(9�2.1 Via which tool(s) can you administer and monitor a OLYHCache?

2.2 Start transaction LC10

2.3 Register your OLYHCache <LNN> for usage with LC10. Is LC10 is already fullyfunctional for your OLYHCache? If not: see exercises for chapter 4.

2.4 Start DBMGui

� 7KH�IROORZLQJ�TXHVWLRQV�DUH�LQWHQGHG�WR�VKRZ�\RX�KRZ�WR�H[WUDFW�VRPH�EDVLFLQIRUPDWLRQ�DERXW�WKH�OLYH&DFKH�)RU�WKH�PRPHQW��SUHIHUDEO\�XVH�$32�V\VWHP�202��&DOO�WUDQVDFWLRQ�/&��IRUORJLFDO�OLYH&DFKH�³/&$³�

3.1 How can you tell if a particular OLYHCache is active and ready to use?

3.2 What is the version and build level of the OLYHCache kernel.

3.3 Can a physical OLYHCache be identical to the DBMS used by APO?

3.4 Can a physical OLYHCache be identical to the DBMS used by APO, when the DBMS isSAP DB?

3.5 Does a physical OLYHCache have to run on the same server as the APO DBMS?

© SAP AG BC555 4-14

�6ROXWLRQV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�To perform the following exercises, you will need to logon to the SAP systems OMO andDEV. To do this, please follow the instructions given to you by your course instructor.

1R� 6ROXWLRQ�1.1 Table DBCON contains the relationship between logical and physical name of all

OLYHCaches accessible from an SAP system. Use either of the following methods todisplay the contents of this table.Method #1:Run transaction SE16 from the command line (“ /NSE16” ) oruse menu path “ Menu Å SAP menu” , then select from the resulting menu tree"Tools Å ABAP/4 Workbench Å Overview Å Data Browser” .thenInput “ DBCON” as the table name and press the ENTER key.Method #2:Menu path of “ Menu Å SAP menu” , then select from the resulting menu tree "ToolsÅ CCMS Å DB administration Å Database connection maintenance” .

1.2 LCA

1.3 LDA

1.4 Start transaction LC10. Specify a logical OLYHCache of “ LCA” and select any of thepushbuttons. The server name can be found in field “ OLYHCache server” at the topLHS (Left hand Side) of the resulting screen.

�2.1 Within SAP System:

Via transaction LC10

Outside SAP System:Method #1:Via the SAP DB Database Manager Gui (DBMGui)

Method #2:Via the SAP DB Database Client Interface (DBMCLI).

2.2 Method 1:Input “ /NLC10” in the command line and press the ENTER key.

Method 2:Menu path of “ Menu Å SAP menu” , then select from the resulting menu tree "ToolsÅ APO Administration Å OLYHCache / COM Routines Å Monitor” .

2.3 Call LC10. In the field Logical connection, enter the value of your group for <LNN>.Push the Edit button and enter the required info 3K\VLFDO�OLYH&DFKH�1DPH andOLYH&DFKH�VHUYHU�QDPH.

2.4 On your desktop, double click the Icon called GEPJXL�,&$�

© SAP AG BC555 4-15

�3.1 Select any pushbutton except “ OLYHCache monitor” .

The traffic light attached to field “ OLYHCache status” should be GREEN.

3.2 Select any of the following pushbuttons: “ OLYHCache administration” , “ OLYHCache console” or “ OLYHCache performance” .

The relevant information can be found attached to field “ OLYHCache version” .

3.3 No.It must run in its own object oriented DBMS. This must be OLYHCache.

3.4 No.It must run in its own object oriented DBMS. /LYHCache installation is different to astandard DBMS installation

3.5 NoIn fact, for mid-range to large APO systems, SAP recommends that the OLYHCacheruns on its own server.

© SAP AG BC555 5-1

SAP AG 1999







OLYH&DFKH�$UFKLWHFWXUH�DQG�5HTXLUHPHQWV

© SAP AG BC555 5-2

SAP AG 1999

l $32�EDVLV�DUFKLWHFWXUHl OLYH&DFKH�SURFHVVHV�DQG�WDVNVl OLYH&DFKH�PHPRU\�UHJLRQVl OLYH&DFKH�GLVN�DUFKLWHFWXUHl ,PSRUWDQW�OLYH&DFKH�SDUDPHWHUVl +DUGZDUH�UHTXLUHPHQWV�RI�DQ�$32�V\VWHP

$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW�\RX�ZLOO�EH�DEOH�WR�GHVFULEH�

OLYH&DFKH�$UFKLWHFWXUH�DQG�5HTXLUHPHQWV

© SAP AG BC555 5-3

SAP AG 1999

3UHVHQWDWLRQ�OHYHO

$SSOLFDWLRQ�OHYHO

'DWDEDVH�OHYHO

6$3�*8, 6$3�*8,

:3 :3 :3 :3

'LVSDWFKHU'LVSDWFKHU

:3

%DVLV�$UFKLWHFWXUH�RI�6$3�$32

�� ! #"� $� % $&�% ��'

$322SWLPL]HUV

OLYH&DFKHOLYH&DFKH

n The 3-tier client/server architecture of a standard SAP system consists of presentation, application,and database levels. On the SUHVHQWDWLRQ�OHYHO, SAP users communicate with the SAP system usingthe SAP GUI. Events like the user choosing ENTER or Save, trigger the execution of a dialog step.On the DSSOLFDWLRQ�OHYHO, the SAP dispatcher process receives the user’s request for the processingof a dialog step and dispatches it for processing to an available SAP work process (WP).

n The SAP WP retrieves the current transactional information from the user session and processes theABAP instructions corresponding to the dialog step. The work process sends ABAP SQL databaseinstructions to the appropriate database and receives the answer from that database.

n When the work process has finished the processing of the dialog step, it sends its data directly to theuser's SAP GUI. The WP issues a database COMMIT just before sending the screen output.

n In the standard SAP system, the SAP system appears to the databases as a group of processes of asingle user, called SAPR3. Work processes connect to the relational database at SAP instance startupand disconnect at SAP instance shutdown.

n As of SAP Release 4.5A, a work process can open not only the standard SAP database connection,but can also dynamically open additional database connections. The connection is closed when it isno longer required. Work processes use such an additional database connection to communicate withliveCache.

n APO optimizers communicate via RFC with the SAP instance. Some, but not all, optimizers directlycommunicate with liveCache by establishing a liveCache session.

© SAP AG BC555 5-4

SAP AG 1999

��6$3�LQVWDQFHV��

OLYH&DFKH�WKUHDGV

OLYH&DFKHPHPRU\�DUHDV

:3:3'LVSDWFKHU'LVSDWFKHU'LVSDWFKHU'LVSDWFKHU:3:3 :3:3

&RRUGLQDWRU&RRUGLQDWRU 5HTXHVWRU5HTXHVWRU

:3:3

��8VHU��WDVNV��8VHU��WDVNV

7KH�6$3�6\VWHP�DQG�OLYH&DFKH�&RPPXQLFDWLRQ

'DWD�&DFKH

64/�5ROOEDFN�&DFKH&RQYHUWHU�&DFKH

64/�/RJ�,�2�4XHXH

(*) ��,+.-�/102) 3 ��45+.3637��989:;0<)63 ��

n A liveCache consists of main memory areas, a group of database threads and various files.

n SQL and object data are buffered in the data cache to avoid physical read and write operations on thehard disks. Changes to objects are logged into transaction specific rollback and history files in datacache. ‘Before’ images of OMS data are required for rollback and consistent reads.

n The converter cache caches information regarding the disk location of liveCache data.

n Changes to SQL objects are logged in the rollback cache. The resulting log data is copied to the logI/O queue and then written to the archive log. This data is required in case of a rollback of SQL data,since it contains ‘before’ images of changed SQL data. APO tables /SAPAPO/ORDKEY and/SAPAPO/ORDMAP are stored as SQL tables in liveCache.

n The database threads perform all database activities. Some threads are separated into smaller unitscalled tasks. Each of the tasks performs specialized functions. The thread hosting tasks is called userkernel thread (UKT). The UKT can coordinate its own tasks more efficiently than the operatingsystem.

n Tasks called user tasks are used to establish and maintain liveCache sessions. As soon as liveCachefunctionality is required, an SAP work process logs on to liveCache and is assigned to a user task ina UKT.

© SAP AG BC555 5-5

SAP AG 1999

8VHU�

.HUQHO�

7KUHD

G�8.7

��8V

HU�.H

UQHO�

7KUHD

G�8.7

��

8VHU��Q�8VHU��Q�8VHU��8VHU��8VHU��8VHU��

8VHU8VHU

8VHU8VHU

8VHU8VHU

GDWDZULWHUGDWDZULWHU

8VHU8VHU8VHU8VHU

8VHU8VHU8VHU8VHU

6HUYHU6HUYHU6HUYHU6HUYHU

8VHU8VHU

8VHU8VHU

'HY�,!�VODYH�WKUHDGV'HY�,!�VODYH�WKUHDGV

'HY��7KUHDG'HY��7KUHDG��Master forMaster for��I/O on DEVSPACEI/O on DEVSPACE

&RRUGLQDWRU&RRUGLQDWRUInitialization / UKP coordinationInitialization / UKP coordination

&RQVROH&RQVROHDiagnosisDiagnosis

5HTXHVWRU5HTXHVWRUConnect processingConnect processing

&ORFN&ORFNTime monitoringTime monitoring

$V'HYL�WKUHDGV$V'HYL�WKUHDGV�$V\QF�!�WKUHDG��$V\QF�!�WKUHDG�I/O onI/O onDEVSPACEDEVSPACE

8VHU�

.HUQHO�

7KUHD

G�8.7

��8V

HU�.H

UQHO�

7KUHD

G�8.7

��8VHU��Q�8VHU��Q�8VHU��8VHU��8VHU��8VHU��

8VHU8VHU

8VHU8VHU

8VHU8VHU

GDWDZULWHUGDWDZULWHU

8VHU8VHU8VHU8VHU

8VHU8VHU8VHU8VHU


8VHU8VHU

8VHU8VHU

8VHU�

.HUQ

HO�7K

UHDG�8

.7��

8VHU�

.HUQ

HO�7K

UHDG�8

.7��

8VHU��Q�8VHU��Q�8VHU��8VHU��8VHU��8VHU��

6HUYHU��Q�6HUYHU��Q�

6HUYHU��6HUYHU��

8WLOLW\8WLOLW\

7LPHU7LPHU

&RQY6FDQQHU&RQY6FDQQHU7UDFH:ULWHU7UDFH:ULWHU

$ORJ:ULWHU$ORJ:ULWHU'DWD:ULWHU'DWD:ULWHU��Q��Q�

6HQGHU6HQGHU5HFHLYHU5HFHLYHU

*DUEDJH&ROOHFWRU*DUEDJH&ROOHFWRU

6HUYHU��6HUYHU��

OLYH&DFKH�7KUHDGV�DQG�WKHLU�7DVNV

n Coordinator controls initialization of the liveCache. During runtime, the Coordinator coordinates theuser kernel threads (UKTs) and their tasks.

n The Requestor receives a connect request and establishes connection to a user task within a UKT.

n The Console thread receives messages from the liveCache kernel and writes them to log files at theoperating system level. On Windows NT, the console thread provides information for the x_consdiagnosis tool.

n The Clock thread measures the time consumed by liveCache components.

n The Device threads, Dev1, Dev2, and so on, perform I/O operations on the data and log disks. Dev0coordinates the Dev threads. The liveCache starts a configurable number of dev processes for eachdevspace.

n One or more user kernel threads (UKTs) can be configured (with parameter MAXCPU) to establishand maintain user sessions.

n The AsDev processes are created temporarily during a backup to perform backup-related I/Ooperations. Their number depends on the number of data devspaces and backup devices. They arecoordinated by an additional thread called Async0.

© SAP AG BC555 5-6

SAP AG 1999

8.7�7DVNV8.7�7DVNV([HFXWHV�FRPPDQGV�IURP�DSSOLFDWLRQV�DQG([HFXWHV�FRPPDQGV�IURP�DSSOLFDWLRQV�DQGLQWHUDFWLYH�FRPSRQHQWVLQWHUDFWLYH�FRPSRQHQWV

3HUIRUPV�,�2�GXULQJ�EDFNXSV3HUIRUPV�,�2�GXULQJ�EDFNXSV

:ULWHV�WKH�ORJV�WR�WKH�ORJ:ULWHV�WKH�ORJV�WR�WKH�ORJ�GHYVSDFHV�GHYVSDFHV

:ULWHV�GLUW\�SDJHV�IURP�WKH�GDWD�FDFKH�WR�GLVN:ULWHV�GLUW\�SDJHV�IURP�WKH�GDWD�FDFKH�WR�GLVN6FDQV�IRU�IUHH�FRQYHUWHU�SDJHV6FDQV�IRU�IUHH�FRQYHUWHU�SDJHV:ULWHV�WKH�NHUQHO�WUDFH�WR�WKH�NHUQHO�WUDFH�ILOH:ULWHV�WKH�NHUQHO�WUDFH�WR�WKH�NHUQHO�WUDFH�ILOH+DQGOHV+DQGOHV��OLYHOLYH&DFKH&DFKH�DGPLQLVWUDWLRQ�DGPLQLVWUDWLRQ0RQLWRUV�/2&.�DQG�5(48(670RQLWRUV�/2&.�DQG�5(48(67�7,0(287V�7,0(287V5HPRYHV�5HPRYHV�KLVWRU\�ILOHVKLVWRU\�ILOHV�RI�RI�RXWGDWHG�RXWGDWHG�REMHFW�REMHFW��GDWDGDWD

8VHU8VHU8VHU8VHU

8VHU8VHU8VHU8VHU


8WLOLW\8WLOLW\7LPHU7LPHU

'DWD:ULWHU'DWD:ULWHU��Q��Q�

7UDFH:ULWHU7UDFH:ULWHU

2/RJ:ULWHU2/RJ:ULWHU��$/RJ:ULWHU$/RJ:ULWHU��

&RQY6FDQQHU&RQY6FDQQHU

8.7�7DVN�'HVFULSWLRQ

*DUEDJH&ROOHFWRU*DUEDJH&ROOHFWRU��Q��Q�*DUEDJH&ROOHFWRU*DUEDJH&ROOHFWRU��

n Each UKT makes various tasks available, including:

é user tasks, that is, tasks that users connect to in order to work with the liveCache

é tasks with specific internal functions

n The total number of of tasks is determined at start-up time and they are then distributed dynamicallyover the configured UKTs according to defined rules. Task distribution is controlled by supportparameters like, e.g., _TASKCLUSTER_02.

n UKT tasks allow for a more effective synchronization of actions involving several components of theliveCache, and minimize expensive process-switching.

© SAP AG BC555 5-7

SAP AG 1999

OLYH&DFKH�5RRW�'LUHFWRU\

ELQ��ELQ��6KHOOVFULSWV�IRU�6KHOOVFULSWV�IRU�OLYHOLYH&DFKH�V\VWHP�SURJUDPV&DFKH�V\VWHP�SURJUDPVSJP�SJP� OLYHOLYH&DFKH�V\VWHP�SURJUDPV��WRROV&DFKH�V\VWHP�SURJUDPV��WRROVHQY��HQY��0HVVDJH�DQG�KHOS�ILOHV0HVVDJH�DQG�KHOS�ILOHVPLVF��PLVF��0LVF�ILOHV0LVF�ILOHVHWFHWF��OLVW�RI�LQVWDOOHG�ILOHVOLVW�RI�LQVWDOOHG�ILOHVOLE��OLE��/LEUDULHV�IRU�SUHFRPSLOHU��FDOO�LQWHUIDFHV/LEUDULHV�IRU�SUHFRPSLOHU��FDOO�LQWHUIDFHVLQFO��LQFO��,QFOXGH�ILOHV�IRU�SUHFRPSLOHU,QFOXGH�ILOHV�IRU�SUHFRPSLOHUGHPRGHPR��'HPRQVWUDWLRQ�SURJUDPV'HPRQVWUDWLRQ�SURJUDPVZUN��ZUN��'HIDXOW�GLUHFWRU\�IRU�581',5(&725<�DQG�%$&.83',5(&725<�'HIDXOW�GLUHFWRU\�IRU�581',5(&725<�DQG�%$&.83',5(&725<�FRQWDLQV�FRQILJXUDWLRQ�GLUHFWRU\�³FRQILJ´�DQG�'LDJQRVLV�GLUHFWRU\��'%1$0(!FRQWDLQV�FRQILJXUDWLRQ�GLUHFWRU\�³FRQILJ´�DQG�'LDJQRVLV�GLUHFWRU\��'%1$0(!VDSVDS��6$3�VSHFLILF��6$3�VSHFLILF�OLYHOLYH&DFKH�XWLOLWLHV&DFKH�XWLOLWLHV

VDSGE

�

=�>�?&�� @" ��A� % � & � �B��% ? � ��C�� ?ED �B =

F$GIH J@K L<MN<G@H J@K L2M�O PRQ6Q

N<GIH S6Q L<T<P N<G@H J@U@VXW

�6,'!�YHUV!ELQSJP ZUNY9Z5[ �]\

FRQILJ<SID>

n The path to the DBROOT directory is assigned to the environment variable DBROOT which isdefined for the operating system user "<liveCache SID>adm".

n In its standard subdirectories, the DBROOT directory contains all the operating system filesnecessary to operate the liveCache. You should not change the names of these subdirectories.

n In a predominant directory (Default /sapdb), predominant instance information and programs arestored like the downward compatible network server program.

n Three important liveCache kernel diagnostics files exist in the run directory /sapdb/wrk/<SID>".Kernel parameter RUNDIRECTORYspecifies the path to the current liveCache rundirectory:

é Diagnosis file “knldiag” is recreated after each liveCache restart, and the previous version iscopied to “knldiag.old”

é Trace file “knltrace” contains the liveCache developer trace that can be switched on for low leveldiagnosis

é Dump file “knldump” is written if the liveCache crashes unexpectedly

é Backup related information can be found in the RUNDIRECTORY as well.

n Parameters adapted using the the liveCache administration tools, are stored in a parameter file withthe name <SID>. This file can be found under: /sapdb/config. Previous versions are available underthe name <SID>.<version#>

© SAP AG BC555 5-8

SAP AG 1999

OLYH&DFKH�'LVN�5HJLRQV

&RQYHUWHU

6<67(0

',6.'��',6.'��

',6.'��

^`_9��acb`3 � dè�fhgi��/��j�k3 +`lman+ò��ho��ap+

ZXq!Zsr ûtv�*^�w Z5x`y{z ^ |k}�~��b�l�]��i��o��o��mb��8�� }� y{r�y �*^`wEe ��b�l� y{r�y �*^`w5f ��b�l� y{r�y �*^`w5} ��b�l��g��!^`wEe��j4]�`) o�e�� b�l

&RQYHUWHU�&DFKH&RQYHUWHU�&DFKH&RQYHUWHU�&DFKH

y -,89�`) �9��+ml

Converter Page Header: Version #data page# devno offset type filler4711 1 240 f 04712 3 219 t 1

Converter Page Header: Version #data page# devno offset type filler4711 3 140 p 04712 2 191 t 1

'DWD�&DFKH'DWD�&DFKH'DWD�&DFKH

n The entire liveCache disk area is divided into 8 Kbytes blocks called pages. Disk areas used byliveCache are called devspaces and include:

é a system devspace

é up to 1024 data devspaces

é up to 32 log devspaces for the archive log

n The pages located in the data devspaces are called data pages. They are distributed by the liveCacheonto existing data devspaces using a 64 Kbyte striping mechanism to ensure balanced I/O. Datapages are cached in the data cache in main memory.

n liveCache administers the disk storage location of the logical pages in the converter. The logicalpages are consecutively numbered data pages that are available to store data. Each logical page canexist in two versions on disk. Different versions are stored in different converter pages. For eachversion of a logical page, a converter entry describes the location on a data devspace. Since aconverter entry is 35 bits long, 2000 converter entries make up one converter page. Converterversion numbers are incremented by a checkpoint.

n The size of the system devspace is approximately 0.1% of the size of the liveCache. When youextend the liveCache, converter entries are created and the system devspace grows.

n Converter pages are cached in the converter cache. The optimal size of the converter cache is 0.05%of the sum of sizes of the liveCache data devspaces.

© SAP AG BC555 5-9

SAP AG 1999

&DFKHV�DQG�.HUQHO�3DUDPHWHUV

8.7�7KUHDGV�DQG�7DVN�&RQILJXUDWLRQ8.7�7KUHDGV�DQG�7DVN�&RQILJXUDWLRQ0$;&380$;&380$;86(57$6.60$;86(57$6.6B7$6.&/867(5B��B7$6.&/867(5B��

&DFKHV�DQG�0HPRU\�6L]HV&DFKHV�DQG�0HPRU\�6L]HV'$7$B&$&+(�'$7$B&$&+(�&$7B&$&+(B6833/<�&$7B&$&+(B6833/<�&219(57(5B&$&+(�&219(57(5B&$&+(�206B+($3/,0,7206B+($3/,0,7

8SSHU�OLPLWV8SSHU�OLPLWV��0$;'$7$'(963$&(6��0$;'$7$'(963$&(6�

�� 0$;'$7$3$*(60$;'$7$3$*(6

$1$/<6,6$1$/<6,6 ��581',5(&725<�581',5(&725<�

6<67(0'DWD��

'DWD�1��

8.7�8.7� 8.7Q8.7Q 5HTXHVWRU5HTXHVWRU &RRUGLQDWRU&RRUGLQDWRU&ORFN&ORFN 'HY�'HY� 'HY��'HY�� 'HYQ'HYQ &RQVROH&RQVROH

'DWD�&DFKH'DWD�&DFKH'DWD�&DFKH&RQYHUWHU�&DFKH&RQYHUWHU�&DFKH&RQYHUWHU�&DFKH&DWDORJ�&DFKH&DWDORJ�&DFKH&DWDORJ�&DFKH

64/�5ROOEDFN�&DFKH64/�5ROOEDFN�&DFKH64/�5ROOEDFN�&DFKH

/2*

n The above parameters are given default values during installation. These values can be adapted to thespecific requirements of the customer system. Storage-related parameters are adapted in units of 8Kbytes, which is the smallest storage unit on disk and in memory. Changes to kernel parametersbecome effective only after liveCache has been stopped and restarted.

n Parameter OMS_HEAPLIMIT is important for a proper functioning of the liveCache. It representsan upper limit for heap allocation of COM routines. 50% of allocatable shared memory should beavailable for heap memory of COM routines. Set OMS_HEAPLIMIT to 0 (parameter disabled) toallow for maximum ressource usage by the COM routines.

n Performance-related liveCache parameters include:

é DATA_CACHE: the data cache stores data pages using an LRU mechanism. Recommendation:use a value equivalent to 60% of the physical memory available for liveCache. The configureddatabase size in pages must exceed 2*DATA_CACHE. The physical memory required for yourliveCache server should be the result of a sizing.

é MAXCPU: Usually,this parameter determines the number of UKTs with user tasks. If supportparameter _TASKCLUSTER_02 contains the string 1*us, MAXCPU parameter is disabled and 1UKT is created for each configured user task. Sufficient hardware ressources must be available.

é MAXUSERTASKS: determines the maximum number of simultaneous liveCache sessions.

é CONVERTER_CACHE: the converter holds information about the disk location of logical datapages. Recommendation: use a value equivalent to 0.05% of configured liveCache size.

© SAP AG BC555 5-10

SAP AG 1999

+DUGZDUH�5HFRPPHQGDWLRQV�IRU�$32�6\VWHPV

1HWZRUN�&RQQHFWLRQ- High speed (FDDI,

High PerformanceSwitch)

- Ethernet or equivalent

$32�6\VWHP��6WDQGDUG�&RQILJXUDWLRQ

APO DB serverl Database with BW

-like configurationl APO SAP instance

APO OLYHCacheserverl OLYHCachel COM routines

$32�)URQWHQGlAPO GUI with OCX

functionality, knownWAN issues

$32�)URQWHQGl APO GUI with OCX


$32�)URQWHQGlAPO GUI with OCX


APO serverlAPO SAP

instance

On separate serversl SNP Optimizerl PP/DS Optimzerl CTM Optimizer

n liveCache requires adequate main memory to support fast response times, and scales very well withthe available CPU resources.

n Allow 30% of the available CPU and RAM resources for the COM routines, which run on theliveCache server.

n The other components of an APO system ideally reside on servers separate from the liveCache andinclude:

é SAP application instances. These usually require at least 1 Gbyte of RAM and are highly scalablewith respect to the CPU power they can provide to the application users who are logged on.

é SAP RDBMS, which consumes between 500 Mbyte and 2 Gbyte of RAM and is also highlyscalable with respect to CPU power.

é SNP, PP/DS and CTM optimizers. These are standalone programs consuming 1 CPU and around512 Mbyte of RAM per active SNP, PP/DS and CTM optimizer.

n Install and configure RFC SAPOSCOL on the servers without SAP instances as described in SAPNotes 19227, 202934, 20624, 210890 and 20624 to allow for operating-system monitoring withtransactions OS07 and RZ20 in the SAP system.

© SAP AG BC555 5-11

SAP AG 1999

<RX�DUH�QRZ�DEOH�WR�GHVFULEH�

l 7KH�OLYH&DFKH�LQWHUIDFH�ZLWK�WKH�$32�6$3LQVWDQFHV

l OLYH&DFKH�FDFKH��WKUHDG�DQG�WDVNWHFKQRORJ\

l 7KH�OLYH&DFKH�GLUHFWRU\�VWUXFWXUHl ,PSRUWDQW�OLYH&DFKH�SDUDPHWHUVl +DUGZDUH�UHTXLUHPHQWV�IRU�OLYH&DFKH

6XPPDU\��OLYH&DFKH�$UFKLWHFWXUH�DQG5HTXLUHPHQWV

© SAP AG BC555 5-12

�([HUFLVHV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�To perform the following exercises, you will again need to logon to the APO system OMO. Todo this, please follow the instructions given to you by your course instructor. Unless directedotherwise, whenever you are requested to extract OLYHCache information, please use transaction“ LC10“ specifying logical liveCache “ LCA“

1R� ([HUFLVH� OLYH&DFKH�SURFHVV�DUFKLWHFWXUH�1.1 Display the threads and active tasks of�OLYHCache.

� OLYH&DFKH�PHPRU\�DUFKLWHFWXUH2.1 List all the cache types in a OLYHCache. How can you see cache types in transaction

LC10?

2.2 In which cache is information stored about the physical location of logical data pageson disk?

2.3 Where are the contents of the Converter cache stored during a checkpoint?

2.4 Where are the contents of the Data cache stored during a checkpoint?

� OLYH&DFKH�SURILOH�SDUDPHWHUV3.1 What is the value of the OLYHCache parameter “ OMS_HEAP_LIMIT” ?

3.2 What does the parameter in the previous exercise control?

3.3 What is the path name of the directory containing the OLYHCache kernel diagnosticfiles?

� OLYH&DFKH�GLVN�DUFKLWHFWXUH4.1 What is the size (in KB) of the data area?

How many devspaces does it consist of?

4.2 What is the size (in KB) of the log area?

How many devspaces does it consist of?

4.3 What block-size is used to store information in all devspaces?

� OLYH&DFKH�RSHUDWLRQ5.1 What logmode is being used by the OLYHCache? Can you explain why?

© SAP AG BC555 5-13

�6ROXWLRQV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�To perform the following exercises, you will again need to logon to the APO system OMO. Todo this, please follow the instructions given to you by your course instructor. Unless directedotherwise, whenever you are requested to extract OLYHCache information, please use transaction“ LC10“ specifying logical liveCache “ LCA“

1R� 6ROXWLRQ�1.1 Select pushbutton “ OLYHCache console” .

To display db threads, select the radio button “ ProcessOverview” and press theENTER key.

To display active tasks, select the radio button “ Active tasks” and press the ENTERkey.

�2.1 The main caches are:

“ Data“ , “ SQL Log Queue“ , “ SQL Rollback“ ,“ Converter“ ,“ Catalog“ , “ FBM“ ,“ USM“ , and “ Sequence“ . To access this information, select pushbutton “ OLYHCachemonitor“ from the initial screen of transaction “ LC10“ , then select the “ Caches“ tab.

2.2 Converter cache.

2.3 System devspace.

2.4 Data devspace(s).

�3.1 Select pushbutton “ OLYHCache configuration” , then select pushbutton “ Parameter” and

read the value of the given parameter.

3.2 This parameter limits the maximum amount of heap memory allocated by all COMroutines. Recommendation: disable, but other memory parameters (DATA_CACHE)must allow for sufficient amount of heap memory for COM rotines.

3.3 Select pushbutton “ OLYHCache configuration” , then select pushbutton “ Parameter” .The value of parameter RUNDIRECTORY contains the required pathname.

© SAP AG BC555 5-14

�4.1 Select pushbutton “ OLYHCache configuration” , then select tab “ Data area” .

The required information can be found in the section “ Size of data area” .

4.2 Select pushbutton “ OLYHCache configuration” , then select tab “ Log area” .

The required information can be found in the section “ Size of log area” .

4.3 8KB.

�5.1 Select pushbutton “ OLYHCache configuration” , then select tab “ Log area” .

The required information can be found in the section “ Size of log area” attached tofield “ Log mode” .

© SAP AG BC555 6-1

SAP AG 1999







OLYH&DFKH�$GPLQLVWUDWLRQ

© SAP AG BC555 6-2

SAP AG 1999

l 'HVFULEH�OLYH&DFKH�RSHUDWLQJ�PRGHVl ([SODLQ�WKH�VWDUWLQJ�DQG�VWRSSLQJ�SURFHGXUHV�IRU

OLYH&DFKHl 'HVFULEH�WKH�SXUSRVH�RI�WKH�OLYH&DFKH�LQLWLDOL]DWLRQ

SURFHVVl 2XWOLQH�WKH�IXQFWLRQV�RI�'%0*8,l $GPLQLVWHU�OLYH&DFKH�UHPRWHO\�DQG�IURP�ZLWKLQ�WKH

6$3�V\VWHP


OLYH&DFKH�$GPLQLVWUDWLRQ

© SAP AG BC555 6-3

SAP AG 1999

5HPRWH�OLYH&DFKH�$GPLQLVWUDWLRQ

l'DWDEDVH�0DQDJHU��'%0��FOLHQW�LQWHUIDFH�FRPPDQGV dbmcli -d <SID> -n <lc server> [-i script file] [-V]

• db_warm• db_offline• show <SHOW command>• exec_command <command>• help <command>

l'DWDEDVH�0DQDJHU��'%0��JHW�ILOH�FRPPDQGV dbmgetf -d <lc name> -n <lc server> -k <file id>

file id:• KNLDIAG• KNLDIAGOLD• KNLDIAGERR• LCTRC#<token>

n liveCache can be administered remotely using the client-server based liveCache tool DBM, with itscomponents DBM GUI and DBM server. Commands are transmitted from a remote DBM GUI viathe interface dbmapi to the DBM server. The DBM server runs on the liveCache server.

n dbmapi consists of 2 interfaces:

é dbmcli: a command-line based interface that transmits administration commands

é dbmgetf: a command-line based interface that gives access to liveCache diagnosis files like“knldiag” and “knltrace”

n The DBM server distinguishes between the DBM user and the operating system user as follows:

é The DBM user has the default user ID “control” with password control. This user permits theinterface dbmcli to connect to the DBM server (with the option “-u control,control”). The DBMuser settings are stored in the registry on the client. Use the option “-us control,control” to storethe DBM user registry entry for the liveCache instance (the syntax of releases before 7.1.3 Build 6is “-uDBMs control,control”).

é The operating system user has the default user “<SID>adm” with his/her operating systempassword. This user permits the DBM server to run operating system commands via the command“exec_command”. To store the settings in the file %DBROOT%\conf\<SID>.upc, use the option“user_put control SYSTEMNAME=<SID>adm SYSTEMPASSWORD=< ospwd>” (the oldsyntax is “-uOSs <SID>adm,<password>”).

© SAP AG BC555 6-4

SAP AG 1999

OLYH&DFKH�$GPLQLVWUDWLRQ�LQ�WKH�6$3�6\VWHP

n liveCache can be administered and monitored using Transaction LC10, and entering the logical nameof the liveCache. Table DBCON correlates the logical and physical names of the liveCachesaccessible from the SAP system.

n liveCache connection info can be created and maintained using the Edit button

n From the initial screen of transaction LC10, you can access the:

é “liveCache administration” menu (for liveCache administration)

é “liveCache configuration” menu (for changes to liveCache configuration)

é “liveCache console” menu (for liveCache monitoring)

é “liveCache monitor” (for statistics about calls to database procedures)

é “liveCache performance” menu (for monitoring the performance of the liveCache)

© SAP AG BC555 6-5

SAP AG 1999

6WDUWLQJ��,QLWLDOL]LQJ��DQG�6WRSSLQJ�WKH�OLYH&DFKH

n To start, stop and initialize the liveCache, use transaction LC10 and choose “liveCacheadministration”.

é Starting liveCache only starts liveCache into warm mode. liveCache has the state of the latestcheckpoint (usually the one connected to the liveCache shutdown).

é Initialization deletes the complete contents of the liveCache. The next slide describes theinitialization process in more detail.

é Stop stops the liveCache. Before liveCache memory and processes are deleted, a checkpoint istriggered. As a result all information contained in the caches is written to disk.

n If the SAP system is not available and liveCache shall be restarted for maintenance purposes only,you can use the dbmcli command exec_lcinit. No application can use the liveCache after such arestart as additional activities are required to make the liveCache fully functional..

n Note that without proper shutdown, all changes to liveCache objects since the last successfulcheckpoint is lost.

© SAP AG BC555 6-6

SAP AG 1999

6WDUWLQJ��,QLWLDOL]LQJ��DQG�6WRSSLQJ�WKH�OLYH&DFKH

n The liveCache initialization process involves:

é Stopping liveCache without saving data

é Restarting liveCache into warm mode

é Registering user sapr3 and also the DCOM routines which load the database procedures

é Deleting all SQL and object data stored persistently in the liveCache devspaces

é Deleting information about references to orders previously contained in the liveCache in thedatabase of the APO system and reloading of master data from the APO database into liveCache with the help of ABAP report /sapapo/delete_lc_anchors.

é Writing a checkpoint, which becomes a restart point for the next start.

n LC10 allows to define Preparation and Postprocessing steps using ABAP reports for Start, Stop andInitialization actions.

n liveCache initialisation usually is required after an upgrade of COM routines, if the structure ofobjects called by COM routines has changed from the old to the new release.

© SAP AG BC555 6-7

SAP AG 1999

6+87'2:1�&2/'7�7�7�7�

&2/'&2/'

OLYH&DFKH�2SHUDWLRQ�0RGHV

6+87'2:1�2))/,1(7�7�7�7�

&2/'&2/' 2))/,1(2))/,1(

��

��

��

��

��

��

��

��

��

��

n It is strongly recommended that you use transaction LC10 to start, stop and initialize the liveCache.

n If the APO system is not available, you can use DBMGUI to change the liveCache operation modes.There are three liveCache operating modes:

é OFFLINE: liveCache kernel processes and caches do not exist.

é COLD: The liveCache kernel is active, but data and log are not yet synchronized. Only in thisoperating mode can you initialize or alter the configuration, or restore disk areas.

é WARM: The liveCache kernel is active and data and log information is synchronized. Users canconnect to the liveCache.

n The command “Shutdown cold” switches the liveCache server to cold mode after all opentransactions have completed. Then a checkpoint is written and all data is flushed from the caches tothe devspaces. New transactions are not allowed when this command has been issued.

n Without “Shutdown cold”, all changes to liveCache data that occurred after the last checkpoint wasperformed are lost. Such a loss of data can, e.g., occur if the liveCache crashes because of hardwareerrors.

© SAP AG BC555 6-8

SAP AG 1999

OLYH&DFKH�,QVWDOODWLRQ

l (QWHU�WKH�QDPH�RI�WKH�OLYH&DFKH�LQVWDQFH�WR�EH�LQVWDOOHGl (QWHU�WKH�SDWK�RI�WKH�'%5227�GLUHFWRU\��7KH�LQVWDOODWLRQ

ZLOO�FRS\�WKH�OLYH&DFKH�VRIWZDUH�WR�WKLV�GLUHFWRU\l 5HERRW�WKH�V\VWHP��5HTXLUHG�HQYLURQPHQW�YDULDEOHV�ZLOO

EH�VHW�E\�WKH�LQVWDOODWLRQ�URXWLQH�l 6WDUW�/&6(783l (QWHU�WKH�QDPH�RI�WKH�OLYH&DFKH�LQVWDQFH�WR�EH�LQVWDOOHGl (QWHU�WKH�QDPH�RI�WKH�ORFDO�PDFKLQHl &RQILJXUH�SDUDPHWHUV�IRU�GLVN��SURFHVV��DQG�PHPRU\

n liveCache can be installed with the help of file lcsetup.bat in directory livecach/<OS>/common theon Kernel CD. Installation is carried out with installation tool LCSETUP.

n During liveCache installation, the following information has to be entered with the help ofinstallation tool:

é Password of the owner of the liveCache software (<sid>adm)

é NT only: specify, if you want to enable PSE (36bit extension) support

é Number of data devspaces.

é For each data devspace, dialog boxes appear in which you must specify the:

- Path for the data devspace, for example, “ /sapdb/<SID>/sapdata”

- Size in MB of the data devspace. LCSETUP shows the free space of the drive.

é Path for the system devspace, for example, “ /sapdb/<SID>/dbsys. liveCache”

é Path for the log devspace, for example, “ /sapdb/<SID>/saplog”

é Size in MB of the log devspace. LCSETUP suggests the free space of the drive.

é Main memory in MB used by liveCache. LCSETUP proposes a reasonable value. This adaptsparameters DATA_CACHE and CONVERTE_CACHE.

© SAP AG BC555 6-9

SAP AG 1999

,QVWDOOLQJ�D�1HZ�OLYH&DFKH�3DWFKl *HW�QHZ�OLYH&DFKH�SDWFK�IURP�VDSVHUY[l /RJ�RXW�$32�XVHUV��ORDG�GDWD�IURP�OLYH&DFKH�WR�$32�'%�IRU�LQLWLDOLVDWLRQ�

VHH�XSJUDGH�QRWH�l 6WRS�WKH�OLYH&DFKH��WKHQ�VWRS�WKH�$32�V\VWHPl 6WRS�WKH�5HPRWH�64/�6HUYHU

with command “[BVHUYHU�VWRS´l 8QLQVWDOO�WKH�5HPRWH�64/�6HUYHU

with command “[BVHUYHU�UHPRYH´l %DFNXS�WKH�ROG�DQG�WKHQ�LQVWDOO�WKH�QHZ�OLYH&DFKH�VRIWZDUH��&20�URXWLQHV�

in directory DBROOT (DBROOT/sap)

l 0LJUDWH�OLYH&DFKH�SDUDPHWHUV�IRU�WKH�QHZ�NHUQHOwith command “[BSDUDP��X�FRQWURO�FRQWURO��G��OF�QDPH!�%&+(&.´

l ,QVWDOO�WKH�QHZ�5HPRWH�64/�6HUYHUwith command “[BVHUYHU�LQVWDOO´

l 6WDUW�WKH�5HPRWH�64/�6HUYHUwith command “[BVHUYHU�VWDUW´

l 5HVWDUW�WKH�6$3�V\VWHPl 5HVWDUW��,QLWLDOL]H��VHH�XSJUDGH�QRWH��OLYH&DFKH�ZLWK�WUDQVDFWLRQ�/&��

n liveCache patches are usually part of an APO Support Package. You should never upgrade yourliveCache version without checking the compatibility of the upgrade with the registered COMroutines.

n The upgrade note tells you whether you have to initialize or simply restart liveCache after anupgrade of the COM rotines. An initialization is only required if new COM routines expect adifferent object structure.

n SAP Note 325449 describes the installation of a new liveCache patch (APO 3.0A SP3 and SP4).

n SAP Note 157265 describes the installation of a patch for the COM routines (APO 3.0A).

© SAP AG BC555 6-10

SAP AG 1999

OLYH&DFKH�'LDJQRVLV��)LOH�NQOGLDJ

n The knldiag file logs messages about current liveCache activities. The actions logged includeliveCache start, user logons, writing of checkpoints, and liveCache shutdown. To access the data, inthe Control menu choose Diagnose ® Operating messages.

n The knldiag file resides in “ DBROOT\wrk\<SID>\knldiag” and is recreated at liveCache start. Theold copy is saved under “ knldiag.old” . A knldiag file containing a fatal error is deleted after twoconsecutive startup failures. To avoid losing this information, the errors are also appended to file“ knldiag.err” in the same directory.

n To view “ knldiag” , “ knldiag.old” , and “ knldiag.err” , use Transaction LC10. Alternatively, from themain APO system menu, choose: liveCache performance ® Detail Analysis ® System Messages.

© SAP AG BC555 6-11

SAP AG 1999

OLYH&DFKH�'LDJQRVLV��.HUQHO�7UDFH

l 6ZLWFK�RQ�WKH�NHUQHO�WUDFH��'%0*8,��&KHFN��.HUQHO�7UDFH��2Ql 5HSURGXFH�WKH�SUREOHPl 7KHQ�³IOXVK´�WKH�NHUQHO�WUDFH�ZLWK�WKH�)OXVK�EXWWRQl 8VH�WKH�IXQFWLRQV�LQ�WKH�3URWRFRO�VHFWLRQ�RI�'%0*8,�WR�SUHSDUH�D�UHDGDEOH�RXWSXW�RI�WKH�NHUQHO�WUDFHl 6HQG�WKH�RXWSXW�ILOH�WR�WKH�VXSSRUW�WHDP

n Kernel trace is a function for analyzing liveCache kernel problems during user transactions. Theoutput of the kernel trace is intended for the SAP development support team and is typically not ableto be interpreted by liveCache users or even administrators.

n Thus, to enable the support team to provide you with an efficient analysis in case of liveCacheproblems or system crashes, you must be able to:

é switch on the kernel trace

é flush it to disk

é locate the flushed file

é prepare it for transfer it to the support team

© SAP AG BC555 6-12

SAP AG 1999

6XPPDU\��OLYH&DFKH�$GPLQLVWUDWLRQ

<RX�DUH�QRZ�DEOH�WR�l 'HVFULEH�OLYH&DFKH�RSHUDWLQJ�PRGHVl 'HVFULEH�WKH�GLIIHUHQFH�EHWZHHQ�OLYH&DFKH

LQLWLDOL]DWLRQ�DQG�VWDUWl 6WDWH�WKH�VWDUWLQJ�DQG�VWRSSLQJ�SURFHGXUHV�IRU

OLYH&DFKH

© SAP AG BC555 6-13

�([HUFLVHV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�1R� ([HUFLVH� %DVLF�IXQFWLRQDOLW\�RI�'%0*XL�

,Q�RUGHU�WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVHV��\RX�ZLOO�QHHG�WR�VWDUW�WKH�'%0*XL�3OHDVH�XVH�WKH�LQVWUXFWLRQV�RXWOLQHG�LQ�WKH�VROXWLRQV�IRU�8QLW��RI�WKLV�FRXUVH�3OHDVH�HQVXUH�\RX�XVH�RQO\�<285�OLYH&DFKH�IRU�WKH�IROORZLQJ�H[HUFLVHV�

1.1 Register YOUR OLYHcache for use by DBMGui.

1.2 What is the operational state of your OLYHCache?

1.3 Start your OLYHCache

1.4 How can you Start / Stop / Initialise the OLYHcache used by your APO system fromwithin the APO system

Do NOT do this in APO system OMO but wait until you have configured yourOLYHCache <LNN> for usage with LC10

� 8VH�'%0*XL�WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVHV�2.1 Initialise your liveCache <LNN>.

2.2 What is the version and build level of the OLYHCache kernel.

2.3 What is the size (in KB) of the data area? How many devspaces does it consist of?

2.4 What is the size (in KB) of the log area? How many devspaces does it consist of?

2.5 What are the values of the OLYHCache kernel parameter that definea) the maximum number of DATA Devspacesandb) the maximum size of the database.Remember these values for a later exercise.

2.6 What logmode is being used by the OLYHCache?

2.7 Examine the database message file. Find the messages pertaining to the startup ofyour liveCache.

What message indicated that the system is in state WARM?

What are the values of:- kernel shared memory size (KB)- available physical memory?

2.8 Start trace of OLYHCache kernel.

� ([WHQG�OLYHFDFKH�GLVN�VL]H�E\��<RX�FDQ�DOWHUQDWLYHO\�SHUIRUP�WKLV�H[HUFLVHLQ�FKDSWHU��ZLWK�/&��

3.1 Check the current size of the data area and ensure there is enough space on that diskto increase.

3.2 Add another devspace to the data area in order to increase the total size of the dataarea by approximately 10%.

© SAP AG BC555 6-14

3.3 Check whether the parameter values noted above for MAXDATAPAGES andMAXDATADEVSPACES changed. When do the modifications at the parametersbecome actively?

� OLYH&DFKH�SURILOH�SDUDPHWHUV�4.1 Check and adapt the value of the OLYHCache parameter “MAXUSERTASKS”?

� &RPPDQG�/LQH�FOLHQW�,QWHUIDFH5.1 How can you issue commands directly to the OLYHCache instance?

5.2 Get complete list of valid DBMCLi commands.

5.3 Get the current value of parameter MAXUSERTASKS.

© SAP AG BC555 6-15

�6ROXWLRQV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�1R� 6ROXWLRQ�1.1 Use menu path “ File Å Register“ or click on the “ Register“ icon.

Your instructor will tell you the name of the server on which your OLYHCache isrunning, together with the associated user name and password..

Input this name in the field “ List database from server“ and click on the “ !“ button.Select your OLYHCache by clicking the box on the LHS of the relevant entry, then clickon the “ Register“ button.

A pop-up will now appear. Input the relevant values in the fields “ Userid name“ and“ Password“ (control, control) and click on the OK“ button.

Your OLYHCache is now registered for use by DBMGui. Click on the “ Close“ button toexit the regsitration function. You will now see a graphic appear in the top RHSwindow, representing your OLYHCache.

1.2 Method 1:The state of your OLYHCache will be shown in the top RHS window under column“ State“ on the line for your OLYHCache entry.

Method 2:Check the colour of the traffic light attached to the graphic for your OLYHCache.

A value of “ Warm“ (colour GREEN) means it is online and ready for use.

A value of “ Cold“ (colour YELLOW) means it is online but shutdown.

A value of “ Offline“ (colour RED) means it is offline.

A value of “ Not Connected“ (no traffic light) means your registration failed – checkuser name and password.

1.3 Select your OLYHCache by clicking on its graphic.

Use menu path “ Instance Å Restart Å Warm“orselect the “ Set Database Warm“ icon (GREEN traffic light).

The state will show “ WARM“ when it has been successfully started.

1.4 Start transaction LC10, input the name of the logical OLYHCache and select pushbutton“ OLYHCache administration“ . The resulting screen has a pushbutton for each of theabove-mentioned functions.

© SAP AG BC555 6-16

�2.1 In command line mode of DBMGUI, execute the command lc_init.

2.2 Method 1:Use menu path “Instance Å Information Å Versions”.

Method 2:Click on the “Information” pushbutton on the LHS of the screen, then click on“Versions”.

2.3 To determine size of data area:Method 1:Use menu path “Instance Å Information Å Data”, then read value from field “TotalSpace (KB)”.

Method 2:Use menu path “Instance Å Configuration Å Data Devspace”, then calculate valuefrom sum of values in “Size” column for entries with Name of form “DATAnnnn”.

To determine how many devspaces are allocated to the data area, use the above-mentioned Method 2 and count the number of non-empty entries with Name =“DATAnnnn”.

2.4 To determine size of log area:Method 1:Use menu path “Instance Å Information Å Log”, then read value from field “Max.Size (KB)”.

Method 2:Use menu path “Instance Å Configuration Å Log Devspace”, then calculate valuefrom sum of values in “Size” column for entries with Name of form “LOGnnn”.

To determine how many devspaces are allocated to the log area, use the above-mentioned Method 2 and count the number of non-empty entries with Name =“LOGnnn”

2.5 MAXDATADEVSPACES: _________

MAXDATAPAGES: ________

2.6 Use menu path “Instance Å Information Å Log”, then read value from field “LogMode”.

2.7 To access the database message files, use menu path “Instance Å Check Å Files”,the double-click on file “Database Messages”.

The database is in state WARM when you can log on to it. Check for messages.

The information concerning memory allocation by the OLYHCache instance isdisplayed via a series of messages with label INFO in the Database Message file. Therequired values can be found associated to fields “Kernel shared data size” and“Available physical memory”.

2.8 Use menu path “Instance Å Check Å Kernel Trace”. Mark the required traceoptions and click on icon “Selected Items ON” to activate trace of all selectedoptions.

Notice the GREEN traffic light associate with each active trace element.

© SAP AG BC555 6-17

�3.2 Use menu path “Instance Å Configuration Å Data Devspace” and click on the last

entry. This entry should have a Name of format “DATAnnnn” and should not yet beassociated with any disk location.Click on the “edit” icon, then specify size of the new allocation and confirm thedefault path in which to allocate the new file associated with the new devspace.Finally click on the “OK” button to allocate the new data component.

�4.1 Select Parameters in the section &RQILJXUDWLRQ”, read the value of the given

parameter. Modify the parameter. When will the parameter change become active.

�5.1 Method 1:

From DBMGui, select menu path “Instance Å Command Line“.Method 2:Assuming the relevant program directory is defined to your PATH variable, select“Start Å Run” from the Windows NT task bar, then input “DBMCLI” and click onthe “OK” button.

5.2 Use either of the previous methods to start up the Command interface. Input “HELP“and press the ENTER key to display a complete list of all valid commands, togetherwith their syntax.

5.3 In the command line of DBMGUI enterparam_getvalue MAXUSERTASKS and execute

© SAP AG BC555 7-1

SAP AG 1999







OLYH&DFKH�0RQLWRULQJ

© SAP AG BC555 7-2

SAP AG 1999

l 8VH�7UDQVDFWLRQ�/&��WR�PRQLWRU�YDULRXV�DVSHFWV�RIOLYH&DFKH�SHUIRUPDQFH

l 8VH�WKH�'DWD�FDFKH�PRQLWRUl 0RQLWRU�WKH�UROOEDFN�FDFKH


OLYH&DFKH�0RQLWRULQJ

© SAP AG BC555 7-3

SAP AG 1999

0RQLWRULQJ�WKH�OLYH&DFKH��0DLQ�0RQLWRU

n liveCache can be monitored in the SAP system using the Performance Monitoring functionsavailable in Transaction LC10.

n The initial screen is the main monitor. This displays a performance overview of the various areas ofthe liveCache.

é A Refresh button lets you update the current screen, whereas System messages leads you toknldiag files and and the initialization log

é Section liveCache attributes lists the main attributes like liveCache SID, server, status and version

é Section Cache hit rates shows the usage and hit rates of object and converter cache

é Section liveCache disk accesses informs about disk I/O in the log and data devspaces

é Section I/O Activity lists the physical and logical I/O requests executed by liveCache.

é Section liveCache status informs you about data cache usage, availability of monitoring features,trace activity and whether a checkpoint is running

é Scan and sort activity helps you to detect inefficient accesses to tables

n To obtain more detailed information about liveCache performance, choose one of the buttons insection “Detailed analysis”.

© SAP AG BC555 7-4

SAP AG 1999

0RQLWRULQJ�WKH�OLYH&DFKH��'HWDLO�$QDO\VLV

n In the Detailed analysis section of the liveCache performance monitor (Transaction LT10), thebuttons you can use for further liveCache performance monitoring include:

é &RQILJXUDWLRQ; displays the liveCache disk and memory configuration

é 'DWD�FDFKH; displays usage and hit rates in the data cache

é /RJ�FDFKHV; displays accesses and hit rates on the rollback caches

é 'HYVSDFH�VWDWLVWLFV; provides information regarding I/O

é $FWLYH�SDUDPHWHUV; displays current values of liveCache kernel parameters

é 206�YHUVLRQV�DQG�$YDLODEOH�'%�SURFHGXUH; displays information regarding available COMroutines

é 7UDQVDFWLRQV; displays the transactions currently active in the liveCache

© SAP AG BC555 7-5

SAP AG 1999

0RQLWRULQJ�OLYH&DFKH�'DWD�&DFKH

n The Data cache monitor is one of the options featured in the Detailed analysis menu of TransactionLC10. It enables you to monitor the effectiveness of the data cache.

n Data cache monitor displays the state of the data cache. A hit rate of close to 100% in the data cachein a running system is a prerequisite for an effectively working liveCache.

n If the portion of the data cache used by OMS data reaches 100%, the entire cache is being used. If,additionally, the hit rate is below 100%, an extension of the data cache may be required.

© SAP AG BC555 7-6

SAP AG 1999

0RQLWRULQJ�OLYH&DFKH�5ROOEDFN�&DFKHV

n The Log cache monitor is another of the options featured in the Detailed analysis menu ofTransaction LC10. When you enter, push the button SQL Log to obtain information about the sql logcache regions, including the rollback cache.

n The upper area of the Log cache monitor screen describes the configuration of the rollback cache andthe log queue.

n Accesses to the SQL rollback cache and the SQL log queue are displayed in the lower section.

n SQL activity in the liveCache is minimal, only anchor tables /sapapo/ordkey and /sapapo/ordmap arestored in the SQL section of liveCache.

n In later liveCache releases, object logging in the liveCache might become available. You will then beable to monitor activity in the corresponding log regions as well.

© SAP AG BC555 7-7

SAP AG 1999

6XPPDU\��OLYH&DFKH�0RQLWRULQJ

<RX�DUH�QRZ�DEOH�WR�l 8VH�7UDQVDFWLRQ�/&��WR�PRQLWRU�YDULRXV

DVSHFWV�RI�OLYH&DFKH�SHUIRUPDQFHl 'HWHUPLQH�ZKHWKHU�WKH�GDWD�FDFKH�LV

VXIILFLHQWO\�ELJ

© SAP AG BC555 7-8

�([HUFLVHV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�1R� ([HUFLVH� 3UHSDUH�/&��LQ�V\VWHP�'(9�IRU�XVDJH�ZLWK�\RXU�OLYH&DFKH�

3OHDVH�HQVXUH�\RX�XVH�RQO\�<285�OLYH&DFKH�IRU�WKH�IROORZLQJ�H[HUFLVHV�1.1 Is /&��is already fully functional for your OLYHCache?

1.2 Use the DBMCLI command available in SM49 to store the DBM user info for OSuser devadm.

1.3 Use the DBMCLI command available in SM49 to store the operating system userand password info of user lNNadm for OS user devadm. Only then user devadm isable to execute dbmcli commands coded in the ABAPs of transaction LC10.

1.4 Is /&��is fully functional for your OLYHCache?

� 8VH�/&��WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVHV�2.1 Start, stop and initialise your OLYHCache.

� 8VH�/&��WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVHV�3.1 What is the version and build level of the OLYHCache kernel.

3.2 What is the size (in KB) of the data area? How many devspaces does it consist of?

3.3 What is the size (in KB) of the log area? How many devspaces does it consist of?

3.4 What are the values of the OLYHCache kernel parameter that define

a) the maximum number of DATA Devspaces

and

b) the maximum size of the database.

Remember these values for a later exercise.

3.5 What logmode is being used by the OLYHCache?

3.6 Examine the database message file. Find the messages pertaining to the startup ofyour liveCache.

What message indicated that the system is in state WARM?

What are the values of:- kernel shared memory size (KB)- available physical memory?

� ([WHQG�OLYHFDFKH�GLVN�VL]H�E\��'R�QRW�SHUIRUP�WKLV�H[HUFLVH�LI�\RX�KDYHDOUHDG\�H[WHQGHG�\RXU�OLYH&DFKH�LQ�FKDSWHU��ZLWK�'%0*8,�

4.1 Check the current size of the data area and ensure there is enough space on that diskto increase

4.2 Add another devspace to the data area in order to increase the total size of the dataarea by approximately 10%.

© SAP AG BC555 7-9

4.3 Check whether the parameter values for MAXDATAPAGES andMAXDATADEVSPACES noted above changed. When do the modifications at theparameters become actively?

� OLYH&DFKH�SURILOH�SDUDPHWHUV�5.1 Check and adapt the value of the OLYHCache parameter “MAXUSERTASKS”?

� &KHFN�WKH�IROORZLQJ�&20�LQIR�LQ�$32�V\VWHP�2026.1 Which DB Procedure has been called the most?

6.2 Which DB Procedure has the highest average run-time?

� 'HVFULEH�KRZ�WR�UHFRJQLVH�FDOOV�WR�&20�URXWLQHV�IURP�6$3�DSSOLFDWLRQV�7.1 How are COM routines initiated from ABAP?

7.2 How can you recognise calls to COM routines in an SQL Trace?

7.3 What is the name of the SQL routine with, in average, the longest elapsed time in thegiven SQL trace?

© SAP AG BC555 7-10

�6ROXWLRQV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�1R� 6ROXWLRQ�1.1 Execute /NLC10 and check whether central functionality is available.

1.2 Execute /NSM49 in the command window. Locate and double click the DBMCLIcommand. In section Additional Parameters, enter:-d <LNN> -n <liveCache servername> -us control,control

1.3 Execute /NSM49 in the command window. Locate and double click the DBMCLIcommand. In section Additional Parameters, enter:-d <LNN> -n <liveCache servername> user_put controlSYSTEMNAME=<lNN>adm SYSTEMPASSWORD=<lNN>adm

1.4 Execute /NLC10 and check whether central functionality is now available.

�2.1 In LC10. enter your OLYHCache ID

Use pushbutton “OLYHCache administration“. The resulting screen has a pushbuttonfor each of the above-mentioned functions.

�3.1 Use pushbutton “OLYHCache administration“. /LYHCache version is displayed in the

upper section

3.2 Use pushbutton “OLYHCache configuration“. Data devspace configuration is displayedwith the tab 'DWD�$UHD

3.3 Log devspace configuration is displayed with the tab /RJ�$UHD3.4 MAXDATADEVSPACES: _________

MAXDATAPAGES: ________

3.5 Use menu path “OLYHCache performance”, then "Configuration" Read value from field“Log Mode”.

3.6 To access the database message files, use LC10 button “liveCache administration“then “Database Messages”.

The database is in state WARM when you can log on to it. Check for messages..

The information concerning memory allocation by the liveCache instance isdisplayed via a series messages with label INFO in the Database Message file. Therequired values can be found associated to fields “Kernel shared data size” and“Available physical memory”.

© SAP AG BC555 7-11

�4.2 Use LC10 button “ liveCache Configuration” and push button "Change

Configuration". This entry should have a Name of format “ DATAnnnn” and shouldnot yet be associated with any disk location.

Then specify size of the new allocation and confirm the default path in which toallocate the new file associated with the new devspace. Finally click on the “ OK”button to allocate the new data component.

�5.1 Select pushbutton “ OLYHCache configuration” , then select pushbutton “ Parameter” and

read the value of the given parameter. Modify the parameter. When will theparameter change become active.

�6.1 Select pushbutton “ OLYHCache monitor” .

Click on the column header “ Calls” and select the pushbutton “ Sort in descendingorder” . The first entry in the resulting list is the DB Procedure with the highestnumber of calls.

6.2 Select pushbutton “ OLYHCache monitor” .

Click on the column header “ Runtime (average in ms)” and select the pushbutton“ Sort in descending order” . The first entry in the resulting list is DB Procedure withthe highest average run-time.

�7.1 Via ABAP’s dynamic SQL interface – “ EXEC SQL” .

7.2 Via entries with statements like “ DBPROC SAPR3,” SAPAPO_……….”

7.3 Start transaction ST05 by inputting “ ST05” into the command line and pressing theENTER key. Switch on the trace for your own user by pushing the Trace on for userbutton. Perform some activity in the system, for instance by executing severalmonitors of LC10. Then select the “ Trace List” pushbutton and on the resultingscreen, use Goto��6WDHPHQW�6XPPDU\��6RUW�E\��7LPH�H[HF��

© SAP AG BC555 8-1

SAP AG 1999







OLYH&DFKH�%DFNXS�DQG�5HVWRUH�7HFKQLTXHV

© SAP AG BC555 8-2

SAP AG 1999

l 'HVFULEH�KRZ�WR�SHUIRUP�OLYH&DFKH�EDFNXSVl 'HILQH�EDFNXS�PHGLDl 3HUIRUP�OLYH&DFKH�EDFNXSl 3HUIRUP�OLYH&DFKH�UHVWRUH


OLYH&DFKH�%DFNXS�DQG�5HVWRUH�7HFKQLTXHV

© SAP AG BC555 8-3

SAP AG 1999

&KHFNSRLQWV

[��%ORFN�FKDQJHG�LQ�GDWD�FDFKHEHIRUH�FKHFNSRLQW��

��

W

'DWD�&DFKH�DIWHU�FKHFNSRLQW��

&KHFNSRLQW�� &KHFNSRLQW��

�

��

�

��

�

��

�

��

�

��

�

��

�

��

�

��'DWD�&DFKH'DWD�&DFKH'DWD�&DFKH

�

��

�

��

�

��

�

��

�

��

�


�

��

�


n During a checkpoint, liveCache takes pages that have changed in the data and converter caches andwrites them to the data and system devspaces. This can be regarded as a backup of data andconverter cache to disk te recover liveCache after a crash.

n The writing of changed pages occurs in three phases:

é Phase one: changed pages are written to disk from the converter and data caches

é Phase two: the version number assigned to changed page is incremented

é Phase three: cache pages changed in phases one and two are written to disk

n During a checkpoint, pages that are marked as “changed” in the caches are written to disk.

é When a checkpoint has been signaled, no new change transactions are admitted, and activetransactions can finish. “Read only” actions are not affected by a checkpoint.

é The end of a checkpoint is reached when all active transactions have committed and thecorrsponding data and converter cache information has been written to disk.

é When long running transactions are active during a checkpoint, wait situations occur and persistuntil the last open transaction has issued a commit.

n After a checkpoint, liveCache is in a state of logical consistency. At the end of a checkpoint,information contained in the caches, the log and in the data and system devspaces are synchronized.The liveCache contains only the data of committed transactions.

© SAP AG BC555 8-4

SAP AG 1999

OLYH&DFKH�%DFNXS

6$9('$7$

&RPSOHWH�'$7$�%$&.83

'$7$�'$7$� '$7$�Q'$7$�Q��'$7$�'$7$�

%DFNXSGHY�

5LQJEXIIHU

%DFNXSGHY�

0$;%$&.83'(96� ��

n From a technical viewpoint liveCache backup is very similiar to a standard database data backup.Information contained in the liveCache Archive Log is currently not backed up as logging of theactivities of the OMS is not available

n SAVE DATA performs a complete backup of all pages used on liveCache. In addition liveCacheconfiguration is saved in the backup to allow for a fast restore of the original liveCacheconfiguration. Converter pages are not part of the backup.

n Make sure that the liveCache was shut down regularly when performing a backup in COLD mode.

n If you follow SAP recommendations regarding the disk configuration and liveCache backup strategy,loss of data is very unlikely.

n SAVEDATA allows you to save to several backup media at the same time. This improves theruntime of backups. In a best case scenario, backup runtime will be only a third when you perform aparallel data backup to 3 instead of only 1 backup device.

n The maximal number of parallel backup media is determined by kernel parameterMAXBACKUPDEVS (1 - 32). Changes to this parameters become effective after a liveCacherestart.

n Internally a memory region is provided in the form of a ring buffer, which takes the Write I/O of theserver tasks and the Read I/O of the asDev threads, which are temporarily created during backup.

© SAP AG BC555 8-5

SAP AG 1999

'DWDEDVH�0DQDJHU��0HGLD�0DQDJHU

n Media Manager is used to define the properties of your backup media.

n General characteristics of a backup medium are:

é Name of the medium

é Type:

- File

- Tape

- Pipe

é Path of the device driver, file or named pipe

n Extended characteristics are

é Size of the medium in 8k pages

é Overwrite capability

é Automatic Tapeloader uses OS command as specified in OS Cmd to load a new tape

n A media group has to be defined, if you want to perform parallel backup. You have to define theproperties of each separate member of the media group.

n Database Manger manual describes the complete procedure.

© SAP AG BC555 8-6

SAP AG 1999

/RJLFDO�FRPPDQG��60��GEPFOL

3UHUHTXLVLWH�'HILQH�VXLWDEOH�EDFNXS�PHGLXP

([DPSOH�GEPFOL��Q�S��G�/&$��X87/�FRQWURO�FRQWURO��XFRQWURO�FRQWURO�EDFNXSBVWDUW�IRUGDWD�UHFRYHU\�GDWD&DOO�WKH�DERYH�FRPPDQG�IURP�$%$3��6$3$32�20B&+(&.32,17B:5,7(,I�$UFKLYLQJ�RI�WKH�OLYH&DFKH�ORJJLQJ�LV�HQDEOHG��GHOHWH�DUFKLYHG�ORJ�ZLWK�WKHKHOS�RI�UHSRUW��6$3$32�20B$5&+,9(B/2*$5($B'(/�DIWHU�WKH�VXFFHVVIXOEDFNXS�RI�OLYH&DFKH

6FKHGXOLQJ�OLYH&DFKH�%DFNXSV��%DFNJURXQG

6FKHGXOH��6$3$32�20B&+(&.32,17B:5,7(ZLWK�WKH�KHOS�RI�6$3�EDWFK�VFKHGXOLQJ�V\VWHP��60��

n liveCache backups can be scheduled with the help of the SAP batch scheduling system. You mustdefine a suitable backup medium before you can make use of this possibility. Use database managerfor this.

n The dbmcli is used to execute the required command on operating system level. Dbmcli is availableas a logical command (transaction SM49).

n The following command is used

n dbmcli -d <SID> -n <servername> -u control,control -uUTL -c backup_start <Backup MediumName> RECOVERY DATA

n This command can be added to a user exit available in report/SAPAPO/OM_CHECKPOINT_WRITE, which you should schedule to run hourly. In this way it isensured that the backup is performed after the completion of a checkpoint. We recommend that youschedule the report at least daily, better yet, schedule it hourly. Consider to perform different actionsin the user exit depending on the time of day.

© SAP AG BC555 8-7

SAP AG 1999

5HFRYHU\�&DVHV

n Restore the liveCache from a backup if you completely loose a liveCache devspace, because one ormore disk devices have suffered physical damage.The latest available liveCache backup usually isthe basis for such a recovery.

n You can also restore a mirrored devspace in the Recovery menu of DBMGUI.

n In order to restore the liveCache after a disk crash or data corruption on one of the devspaces, youmust first provide new disk spaces and determine and eliminate possible causes for future errors.

é Use the Backup History provided by DBMGUI to restore the latest available backup. Restore iscarried out in operating mode COLD with the help of the Restore functionality of DBMGUI.

é Restart Warm from LC10 finishes liveCache restore.

n Recommendation:To prevent loss of backup history information we recommend that youperiodically backup the RUNDIRECTORY of your liveCache.

© SAP AG BC555 8-8

SAP AG 1999

5XQWLPH�(QYLURQPHQW5XQWLPH�(QYLURQPHQW NQOGLDJNQOGLDJ�HUU 581',5(&725<

6$3�'%�.HUQHO6$3�'%�.HUQHO NQOWUDFH 581',5(&725<

*OREDO*OREDO6KDUHG6KDUHG0HPRU\0HPRU\

NQOGXPS6KDUHG�0HPRU\$E]XJ

581',5(&725<

'%0*8,�'%0*8,�,QIRUPDWLRQ,QIRUPDWLRQ

%DFNXS�+LVWRU\%DFNXS�+LVWRU\GEP� � 581',5(&725<�

�6,'!� �XVU�VSRRO�VTO�FRQILJ

'LDJQRVWLFV�)LOHV

5HVXOWV�RI�ODVW�FKHFN5HVXOWV�RI�ODVW�FKHFNRI�NHUQHO�SDUDPHWHUVRI�NHUQHO�SDUDPHWHUV [SFKHFN�SURW� �581',5(&725<�

n The following files, located under RUNDIRECTORY, contain information to help you recognize thecauses of liveCache problems.

n The diagnosis file knldiag logs messages between the liveCache runtime environment and thedatabase. This file is recreated during each start of the liveCache kernel.The existing file is backedup using the name <filename>.old. After a crash and two subsequently failed restarts, you will loseall information, unless you back up the knldiag, which may contain relevant information about thedatabase crash. Knldiag.err only logs error messages and is written to in append mode. Take care toregulary backup and delete this file.

n The trace file knltrace logs messages between layers of the liveCache kernel, provided the traceoption is switched on. Trace size should not be less than 1000 pages in the SAP environment. Thetrace is cyclically overwritten.

n You can switch the trace on or off using Database Manager. DBMGUI converts the trace into areadable format for analysis.

n Files dbm.knl. dbm.log, dbm.mmm, and dbm.mdf contain information about the backup history andusage of media and labels. Database manager uses this information to assist you with performingrestore.

© SAP AG BC555 8-9

SAP AG 1999

&KHFNSRLQW6$9(�/&��&KHFNSRLQW6$9(�/&��

&+(&.32,17&+(&.32,17

&+(&.32,17&+(&.32,17

&+(&.32,17&+(&.32,17

&+(&.32,17&+(&.32,17

&+(&.32,17&+(&.32,17

,QVWDOO�QHZ�GLVN5(67$57�&ROG5(6725(�6$9(�/&��

7HFKQLFDO�5HFRYHU\�6WUDWHJ\

&KHFNSRLQW6$9(�/&��&KHFNSRLQW6$9(�/&��

� ��

��

��

��

5(67$57�:DUP�IURP�/&��,QIR�PLVVLQJ�LQ�OLYH&DFKHDIWHU�UHVWRUH�GDWD

,QIR�PLVVLQJ�LQ�OLYH&DFKHDIWHU�&UDVK�DQG�VXEVHTXHQW5(67$57�:$50

n If no disk information was lost during the liveCache crash, simply use LC10 to restart liveCache.Usually you do not want to lose information from the latest checkpoint contained in the liveCache,so you should not perform a liveCache initalization, as this will delete all data stored in theliveCache.

n If a logical error is committed in the APO system, it might be required to reset the system to a pointin time before the error occurred. A liveCache backup is then required in combination with a suitableAPO database backup to reset the system.

n To be prepared for such a recovery case we recommend that you train at least 2 people who cancompletely recover liveCache and the entire SAP system connected to liveCache . Server landscapecomparable to that of your production system is required for the testing of your recovery procedures.

© SAP AG BC555 8-10

SAP AG 1999

6XPPDU\��OLYH&DFKH�%DFNXS

<RX�DUH�QRZ�DEOH�WR�l 8VH�'%0*8,�WR�GHILQH�EDFNXS�PHGLDl 'HVFULEH�WKH�VWHSV�UHTXLUHG�WR�SHUIRUP�OLYH&DFKH

EDFNXSVl 'HVFULEH�WKH�VWHSV�UHTXLUHG�WR�UHVWRUH�OLYH&DFKH

© SAP AG BC555 8-11

�([HUFLVHV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�1R� ([HUFLVH� 8VH�'%0*8,�WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVH�1.1 Force a checkpoint of your liveCache. Note: Only after a checkpoint can you execute

backups of your OLYHCache.

1.1 How would you trigger a checkpoint in the APO system.

� 8VH�'%0*8,�WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVH�2.1 Define a backup medium for your OLYHCache.

� 8VH�'%0*8,�WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVH�3.1 Perform a full backup of your OLYHCache.

3.2 How would you perform a full backup of your OLYHCache in an APO system?

3.� Which additional action do you have to execute after a successful backup ofOLYHCache?

� 8VH�'%0*8,�WR�SHUIRUP�WKH�IROORZLQJ�H[HUFLVH�4.1 Perform a full restore of your OLYHCache?

4.2 How would you perform a full restore of your OLYHCache in an APO system?

4.3 What do you have to do after the OLYHCache recovery?

© SAP AG BC555 8-12

�6ROXWLRQV)RU�WKH�H[HUFLVHV�DQG�VROXWLRQV��SOHDVH�XVH�WKH�QHZH[HUFLVHV�DQG�VROXWLRQV�LQ�WKH�DSSHQGL[�RI�WKLV�FRXUVH�1R� 6ROXWLRQ�1.1 In DBMGUI menu instance, use item Command line. Execute the following 3

commands:

1) sql_connect superdba,admin

2) sql_execute call force_and_wait_for_checkpoint

3) sql_release

1.1 With SM36, schedule a job with step executing report/SAPAPO/OM_CHECKPOINT_WRITE

�2.1 Use %DFNXS�0HGLD in the &RQILJXUDWLRQ section. Use the 0HGLXP button in the lower

section and define the properties of your backup media.Name: FORDATALocation: /sapdb/wrk/<SID>/fordataDevice Type: File

�3.1 Use Complete in %DFNXS�in the %DFNXS�section. Use the 0HGLXP that you defined in

the previous exercise. Then push the Next Step button. Check the Start details andpush the Start button if the recommendations are correct.

3.2 Edit the user exit in report /SAPAPO/OM_CHECKPOINT_WRITE and addcommand dbmcli -d <SID> -n <servername> -u control,control -uUTL -cbackup_start <Backup Medium Name> RECOVERY DATA to it.

3.� After checking the success of the backup action delete archive log area in APO dbwith the help of report /SAPAPO/OM_ARCHIVE_LOGAREA_DEL

�4.1 Bring your OLYHCache to state COLD. Use 'DWDEDVH in the section 5HFRYHU\. Choose

�5HVWRUH�ODVW�EDFNXS��Push the Next step button and check the details given. If theyare correct, push the Next Step and then the Start button. Check the messagedisplayed by DBMGUI. A Restart Warm completes the Recovery.

4.2 Execute report /sapapo/om_lc_recovery with the help of Tools ��$32Administration ��OLYH&DFKH�&20�URWLQHV��5HFRYHU\��5HFRYHU\

4.3 Recover the archive log

Restart your CIF queues after you have received an express mail about success ofarchive log recovery

Re-schedule /SAPAPO/OM_CHECKPOINT_WRITE

© SAP AG BC555 9-2

SAP AG 1999

l 'HVFULEH�KRZ�WR�XVH�OLYH&DFKH�EDFNXSV�LQ�RUGHU�WR�UHVWRUHDQ�$32�6\VWHP�DQG�WKH�FRQQHFWHG�2/73�V\VWHPV

l ([SODLQ�DQG�DFWLYDWH�$32�OLYH&DFKH�ORJJLQJl ([SODLQ�$32�OLYH&DFKH�UHFRYHU\�IURP�$32�'%�ORJJLQJ

DUHDV


OLYH&DFKH�%DFNXS�DQG�5HVWRUH�IRU�$32

© SAP AG BC555 9-3

SAP AG 1999

OLYH&DFKH�%DFNXSV�DQG�/RJJLQJ�IRU�$32

$SSOLFDWLRQ

$SS

$SS �6

HUYHU

�6HUYH

U)URQWHQG)URQWHQG

/RJ�DUHD$

$32$32�'DWDEDVH�'DWDEDVH

OLYH&DFKHGHYVSDFHV


/RJ�DUHD%

)RUFH&KHFNSRLQW

1HZDFWLYH�ORJ�DUHD

$UFKLYH/RJ�DUHD

$UFKLYHROG�

ORJ�DUHD%DFNXS

OLYH&DFKHOLYH&DFKH

n As a loss of liveCache in principle does not result in loss of data but only in time required to refillliveCache, recovery prerequisites are disabled in the default. You can enable several optionsaccoriding to your demand in order to maximize APO availability. Performance is affected to acertain extent. Usage of Recovery functionality requires an optimized liveCache disk layout.

n liveCache recovery differs between the the following logging levels

é liveCache can periodically write changed cache information to the devspaces. This is achieved byperiodical writing of checkpoints. liveCache data can be recovered to the point in time when thelast checkpoint has been written.

é For a liveCache recovery of all data send and received by CIF/BAPI interfaces, logging of changesto liveCache data, which have been successfully received or transmitted through the BAPI and/orCIF interface, can be activated.

é For a full liveCache recovery, logging of changes to liveCache objects into the APO database canbe activated.

n If you are using liveCache in Demand Planning, no log for changes to liveCache objects connectedto Demand Planning is written. You can create backup infocubes in the APO DB to periodicallybackup liveCache info in the backup infocubes.

n Point in time recovery can be achieved by using a Point in time recovery of the APO database and afull liveCache recovery with the help of a suitable liveCache backup and the liveCache log. PerformliveCache backups to be prepared for the occurrence of disk crashes.

© SAP AG BC555 9-4

SAP AG 1999

(QDEOH�OLYH&DFKH�/RJJLQJ�IRU�$32

n To activate liveCache logging in APO release 3.0A: Call transaction /SAPAPO/OM06 and activatethe desired logging method.

n In addition

é Schedule a periodic (up to hourly) job that executes the report/SAPAPO/OM_CHECKPOINT_WRITE (trigger checkpoint). If this job is not scheduled, the logmight have an overflow. The liveCache can be recovered to the last state before the crashoccurred.

é If you want te be able to restore liveCache after a disk crash, you must also perform periodicalbackups and possibly activate archive logging. If you have activated the archive logging youshould delete liveCache archive logging area at least daily, preferably after a successful liveCachebackup with the report /SAPAPO/OM_ARCHIVE_LOGAREA_DEL. Use the user exit providedin report /SAPAPO/OM_CHECKPOINT_WRITE.

© SAP AG BC555 9-5

SAP AG 1999

OLYH&DFKH�5HFRYHU\�ZLWK�/RJJLQJ

$SSOLFDWLRQ

$SS

$SS �6

HUYHU

�6HUYH

U)URQWHQG)URQWHQG

/RJ�DUHD$


OLYH&DFKHGHYVSDFHV


/RJ�DUHD%

$FWLYH�ORJ�DUHD

$UFKLYH/RJ�DUHD

$UFKLYHLQDFWLYH�ORJ�DUHD

��

�

OLYH&DFKHOLYH&DFKH

n The liveCache log information is written to special tables (/sapapo/lc_log<t><v>) in the APOdatabase.

n Separate logging tables exist for order headers (type h), order data (d), pegging data (f) and keys ofchanged master data (s).

n Each of the tables exists in three versions a, b an z.

n After a checkpoint, the logging mechanism switches between version a and b. The inactive verion ofthe log is then deleted. It is therefore essential that checkpoints are trigggered periodically to avoidoverflow of the active log region.

n If archive logging is enabled, logging information in the currently inactive logging area is archivedto tables of type z, before it is deleted.

© SAP AG BC555 9-6

SAP AG 1999

$SSOLFDWLRQ

$SS

$SS �6

HUYHU

�6HUYH

U)URQWHQG)URQWHQG

OLYH&DFKH�5HFRYHU\�XS�WR�ODVW�&KHFNSRLQW


OLYH&DFKH)LOH�6\VWHP


��/RDG�ODVWFKHFNSRLQWDIWHU�UHVWDUW

��6\QFKURQL]HOLYH&DFKH�DQG$32�'%�ZLWK

�6$3$32�20��/RJ�DUHD

$/RJJLQJ

QRWDFWLYDWHG

/RJ�DUHD%

��5HVWRUH�%DFNXS

OLYH&DFKHOLYH&DFKH

n Recovery after a liveCache crash

é Stop the APO system (or at least, prevent user log-ins). CIF queues in the attached SAP systemsare automatically stopped after a liveCache crash

é After a disk crash, restore the liveCache from the latest backup

é Restart the APO system and liveCache with LC10

é Remove inconsistencies between APO database and liveCache with the help of transaction/SAPAPO/OM17

é Check for inconsistencies of transactional data between the APO system and the attached SAPsystems with the help of report /SAPAPO/CIF_DELTAREPORT

é Restart the CIF queues in the attached SAP systems

n Prerequisites to enable recovery after liveCache crash : Trigger liveCache checkpoints

é Schedule periodic job LC_CHECKPOINT (for example hourly)

é Job step: execute report /SAPAPO/OM_CHECKPOINT_WRITE

é See full description in SAP Notes 151274 and 162530

n Additional prerequisite to prevent loss of devspace information caused by a disk crash

é Define a backup medium with the help of DBMGUI

é Periodically perform liveCache backups with the following dbmcli command in a user exit ofreport /sapapo/om_checkpoint_write: dbmcli -d <SID> -n <servername> -u control,control -uUTL-c backup_start <Backup Medium Name> RECOVERY DATA.

© SAP AG BC555 9-7

SAP AG 1999

$SSOLFDWLRQ

$SS

$SS �6

HUYHU

�6HUYH

U)URQWHQG)URQWHQG

OLYH&DFKH�5HFRYHU\�ZLWK�/RJJLQJ


OLYH&DFKH)LOH�6\VWHP


��/RDG�ODVWFKHFNSRLQWDIWHU�UHVWDUW

��5HVWRUHFKDQJHV�DIWHUODVW�FKHFNSRLQWIURP�ODVW�DFWLYH

ORJ�DUHD/RJ�DUHD$

/RJJLQJDFWLYDWHG

/RJ�DUHD%

OLYH&DFKHOLYH&DFKH

n For a liveCache recovery, use report /SAPAPO/OM_LC_RECOVERY

é Job for report /SAPAPO/OM_CHECKPOINT_WRITE is deleted

é liveCache is restarted and liveCache logging info is used to recover the latest committed state ofliveCache with the help of the active log area. You are also asked whether you want to use thearchived log area.

é After an express mail has informed you about successful recovery of liveCache, activate CIFqueues in attached SAP systems

n Re-schedule report /SAPAPO/OM_CHECKPOINT_WRITE

n Prerequisites

é Trigger liveCache checkpoints

é Activate synchronous or BAPI/CIF based liveCache logging in transaction /SAPAPO/OM06

é To prevent loss of liveCache data after a disk crash, perform backups and activate archiving of theliveCache logging data to fully recover liveCache after a disk crash

n After a disk crash, restore liveCache from the latest backup

n Check for inconsistencies with transaction /SAPAPO/OM17

© SAP AG BC555 9-8

SAP AG 1999

/&%$&.83��DUFKLYHG�/&%$&.83��DUFKLYHG�/&%$&.83��RYHUZULWH�/&%$&.83��RYHUZULWH�$32�'%��/RJ�%DFNXS$32�'%��/RJ�%DFNXS

��

��

��

��*HQ��*HQ�

��*HQ��*HQ��*HQ��*HQ�

��*HQ��*HQ��$0�$32�'%�%DFNXS��&KHFNSRLQW��%DFNXS�/&��DUFKLYH��'HOHWH�/&�/RJ�$UFKLYH+RXUO\��&KHFNSRLQW2SWLRQDO��%DFNXS�/&��RYHUZULWH��

��

5HFRPPHQGDWLRQ�IRU�OLYH&DFKH�%DFNXS�6WUDWHJ\

n The outlined strategy will enable you to recover the APO system together with the liveCache in aminimized time span. The following prerequisites must be fullfilled:

é Each hour a checkpoint is triggered on the liveCache

é liveCache logging and archiving has been enabled

é Archiving of the liveCache log has been enabled

n Perform daily database data and log backups to ensure data security of the APO database. Archivethese backups for at least 4 weeks.

n Perform a daily backup of liveCache and archive this backup to be able to perform point in timerestores in connection with the APO DB backups. Keep at least four generations of the full backupsets of an entire week.

n In addition and time permitting, you can perform hourly liveCache backups to accelerate liveCacherecovery with the help of the liveCache log. These hourly backups can be overwritten.

n Outlook: In later liveCache releases, object logging in the liveCache might become available. Youwill then be able to backup liveCache object log and perform liveCache recovery using liveCachelog information.

© SAP AG BC555 9-9

SAP AG 1999

6XPPDU\��OLYH&DFKH�%DFNXS�LQ�DQ�$32�6\VWHP

<RX�DUH�QRZ�DEOH�WR�l 6FKHGXOH�OLYH&DFKH�EDFNXSVl ([SODLQ�WKH�DYDLODEOH�OLYH&DFKH�ORJJLQJ�OHYHOV�LQ

DQ�$32�V\VWHPl (QDEOH�OLYH&DFKH�ORJJLQJ�LQ�WKH�$32�'%l 'HVFULEH�WKH�VWHSV�UHTXLUHG�WR�UHVWRUH�WKH�$32

V\VWHP�DIWHU�D�OLYH&DFKH�FUDVK

© SAP AG BC555 10-2

SAP AG 1999

1RZ�\RX�DUH�DEOH�WR�l 'HILQH�$32�V\VWHP�UHTXLUHPHQWVl ,GHQWLI\�WKH�VSHFLILF�OLYH&DFKH�FRQILJXUDWLRQ

LQ�WKH�6$3�HQYLURQPHQWl 3HUIRUP�OLYH&DFKH�PRQLWRULQJ�DQG

PDLQWHQDQFHl /LVW�DQG�SHUIRUP�ZRUN�ZLWK�'%0*8,�DQG�6$3

DGPLQLVWUDWLRQ�WRROVl 8QGHUVWDQG�EDFNXS�DQG�UHFRYHU\�FRQFHSWV�RI

OLYH&DFKH�LQ�WKH�$32�V\VWHP

&RQFOXVLRQ

© SAP AG BC555 11-1

1HZ�([HUFLVHV�DQG�6ROXWLRQV6\VWHPODQGVFDSHYou will work in a group of two up to four people.

To each group an individual Windows server will be assigned. On this server a R3 system, anAPO 3.0A system, a liveCache and all optimizers are running.

Therefore every group will have it’s own SAP system landscape to perform the followingexercises and will not interfer with any actions of one of the other groups.

Your instructor will hand out all necessary data needed to logon to all your systems and yourWindows server.

([HUFLVHV&KDSWHU��

1. Log on to your APO system to retrieve the following information

1.1. Version and SID of the liveCache. (TA lc10 or TA sm49)

1.2. Version of COM routines (/sapapo/om04)

1.3. Version of Optimizers (TA /sapapo/opt09)

2. Check liveCache and COM functionality (TA /sapapo/om03)

3. Check consistency of liveCache configuration (TA /sapapo/om13)

&KDSWHU��

1. Check number of defined work processes (TA sm50)

2. Check defined liveCache tasks (TA lc10)

3. Find the file knldiag on OS level

4. Check number of datadevspaces and logdevspaces of your liveCache from within yourAPO system (TA lc10)

5. Check data cache size, maximum allowed heap memory and all other relevant liveCachekernel parameters (TA lc10)

6. Find out whether garbage collectors were already in use since your last liveCache restart(TA lc10)

7. Check number of currently active consistent views – also note their runtime (TA lc10)

© SAP AG BC555 11-2

([HUFLVHV&KDSWHU��1. Register your liveCache in your local dbmgui

2. Check the liveCache devspace configuration using dbmgui

3. Add another datadevspaces to your liveCache using dbmgui

4. Check the definitions of the two logical liveCache connections (TA lc10)

5. Which connection is used for ATP (available to promise)?

6. Store the DBM user information (TA sm49)

7. Store OS user information (TA sm49)

8. Start, stop and initialize your liveCache (TA lc10)

9. Review the file knldiag from within your APO system (TA lc10)

10. Stop and start the X_server on OS level

&KDSWHU��1. Review all important liveCache performance statistics (TA lc10)

2. Check distribution of liveCache data between OMS data, OMS history and SQL data (TAlc10)

3. Check Data Cache usage (TA lc10)

4. Check DevSpace usage from within your APO system (TA lc10)

5. Check DevSpace usage with dbmgui

6. Check for active liveCache tasks (TA lc10)

7. Check schedule of the APO job /sapapo/om_reorg_daily and adjust it if necessary (TAsm37 and TA sm36)

8. Check the following COM routine statistics (TA lc10)

8.1. Number of calls

8.2. Average runtime

8.3. Accesses to heap

8.4. Accesses to data cache

8.5. Maximum heap usage

9. Check currently used heap memory and maximum allocated heap memory since lastliveCache restart (TA se38)

© SAP AG BC555 11-3

([HUFLVHV&KDSWHU��DQG��1. Check internal data consistency (TA /sapapo/om17)

2. Check status of synchronous logging and turn it on if necessary (TA /sapapo/om06)

3. Check history of liveCache online backups from within your APO system (TA/sapapo/om11) and using dbmgui

4. Define a backup medium using dbmgui

5. Execute a liveCache online backup using dbmgui

6. Schedule a daily liveCache online backup at midnight (TA se38 and sm36)

7. Write a liveCache checkpoint (TA /sapapo/om18)

8. Schedule an automatic liveCache checkpoint every two hours (TA sm36)

9. Crash your liveCache and restore it afterwards (TA lc10)

© SAP AG BC555 11-4

6ROXWLRQV&KDSWHU��

1. Log on to your APO system to retrieve the following information

1.1. Version and SID of the liveCache. (TA lc10 or TA sm49)

Lc10 Å Enter logical connection LCA Å liveCache administration

1.2. Version of COM routines (/sapapo/om04)

/sapapo/om04 Å column changelist Å Use SAP note 326494 to get correspondingCOM routine Version

1.3. Version of Optimizers (TA /sapapo/opt09)

/sapapo/opt09 Å find support package number that corresponds to the optimizerexecutables

2. Check liveCache and COM functionality (TA /sapapo/om03)

/sapapo/om03 (executes report /sapapo/om_lccheck) Å do not change any predefinedentries – just press F8 Å liveCache and COM routines work properly, if last line ofresulting protocol says:

%%%% NO ERRORS OCCURED %%%%%%%%%

COM-routines and liveCache are working well.

If report stops because of problems with logical tests implement note 483479 or choose notto carry out logical tests on initial page of the report.

3. Check consistency of liveCache configuration (TA /sapapo/om13)

/sapapo/om13 Å checks Å all lights should be green

© SAP AG BC555 11-5

6ROXWLRQV&KDSWHU��

1. Check number of defined work processes (TA sm50)

Sm50 Å Find a list of all work processes (dialog, batch, …)

2. Check defined liveCache tasks (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache console Å choose process overviewand press F8 Å find a list of all defined liveCache tasks

3. Find the file knldiag on OS level

Logon to your server Å move to folder /sapdb/data/wrk/<LC SID> Å here you’ll find thedesired file

4. Check number of datadevspaces and logdevspaces of your liveCache from within yourAPO system (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å configuration Å onthe lower part of the screen find a list of all defined devspaces

5. Check data cache size, maximum allowed heap memory and all other relevant liveCachekernel parameters (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å active parameters Åfind a list of all active parameters and their corresponding values

To change parameter values use dbmgui or dbmcli commands.

To activate new parameter values you have to restart your liveCache.

6. Find out whether garbage collectors were already in use since your last liveCache restart(TA lc10)

If garbage collectors were already in use, you’ll find a corresponding entry in the filekrnldiag.

Lc10 Å Enter logical connection LCA Å liveCache administration Å system messages Åsearch for the word ‘gar’

© SAP AG BC555 11-6

6ROXWLRQVAttention: the size of this file is predefined – therefore old entries get overwritten at one point.

7. Check number of currently active consistent views – also note their runtime (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å OMS versions Å find atable that lists all currently running consistent view as well as their runtimes.

&KDSWHU��

1. Register your liveCache in your local dbmgui

Start dbmgui Å file Å register Å enter the liveCache host Å press on ‘!’ Å mark thedesired liveCache Å register Å enter liveCache name, user ‘control’ and password‘control’ Å OK Å close

You’ ll see a new icon for the just registered liveCache in the upper part of the screen.

2. Check the liveCache devspace configuration using dbmgui

Start dbmgui Å doubleklick on the icon for the desired liveCache in the upper part of thescreen Å on the menu on the left hand side of the screen choose configuration Å datadevspace or log devspace

3. Add another datadevspaces to your liveCache using dbmgui

Start dbmgui Å doubleklick on the icon for the desired liveCache in the upper part of thescreen Å on the menu on the left hand side of the screen choose configuration Å datadevspace Å mark the icon for the first not existing data devspace Å press edit Å entersize, location and type of the new data devspace Å press OK

Attention: Once a new data devspace is added it cannot be remove anymore. Also all datadevspaces should have the same size.

© SAP AG BC555 11-7

6ROXWLRQV4. Check the definitions of the two logical liveCache connections (TA lc10)

Lc10 Å enter the name of the logical connection Å press edit Å If the connection alreadyexists, the existing data is displayed and can be changed. If the connection does not existsso far, you can define it here.

Two connections named LCA and LDA must be defined. For further details refer to theliveCache installation guide.

5. Which connection is used for ATP (available to promise)?

ATP uses connection LDA. All other applications use connection LCA.

6. Store the DBM user information (TA sm49)

Sm49 Å doubleklick on ‘dbmcli’ Å in the field ‘additional parameters’ enter:

-d <LC SID> -n <LC Host> -u control,control –us control,control

Recommendation: execute this command two times in a row.

7. Store OS user information (TA sm49)

Sm49 Å doubleklick on ‘dbmcli’ Å in the field ‘additional parameters’ enter:

-d <LC SID> -n <LC Host> -u control,control user_put control SYSTEMNAME=<lc-sidadm> SYSTEMPASSWORD=<lc-sid adm password>

Recommendation: execute this command two times in a row.

8. Start, stop and initialize your liveCache (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache administration Å press ‘startliveCache’ , ‘stop liveCache’ or ‘initialize liveCache’

Attention: Initialisation of the liveCache deletes all liveCache data.

9. Review the file knldiag from within your APO system (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache administration Å system messages

© SAP AG BC555 11-8

6ROXWLRQV10. Stop and start the X_server on OS level

Log on to your liveCache server as user <lc-sid>adm and execute the command: ‘x_serverstop’ or ‘x_server start’ respectively.

�&KDSWHU��

1. Review all important liveCache performance statistics (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å review allinformation provided on this screen and on all screens that appear when you press on anybutton on this page.

2. Check distribution of liveCache data between OMS data, OMS history and SQL data (TAlc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å data cache Å Thetable in the middle of the screen shows the distribution of the liveCache data.

3. Check Data Cache usage (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å data cache Å Thetable in the middle of the screen shows the data cache usage.

4. Check DevSpace usage from within your APO system (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache performance Å devspacestatistics ÅThe value ‘total data space’ represents only half the disc space defined as data dev space.Also the value ‘used data space’ indicates the percentage of the disc space defined by ‘totaldata space’ used by the last checkpoint.

5. Check DevSpace usage with dbmgui

Start dbmgui Å doubleklick on the icon for the desired liveCache in the upper part of thescreen Å This time the appearing diagram shows the total amount of disc space included inthe data devspaces. And also the given value indicted as used space corresponds to thewhole amount of used disc space in all the data devspaces.

© SAP AG BC555 11-9

6. Check for active liveCache tasks (TA lc10)

Lc10 Å Enter logical connection LCA Å liveCache console Å mark ‘active tasks’ andpress shift+F1 Å The appearing table lists all currently active tasks.

The application pid is similar to the one shown in TA sm50.

7. Check schedule of the APO job /sapapo/om_reorg_daily and adjust it if necessary (TAsm37 and TA sm36)

Sm37 Å Set wildcards in the fields ‘job name’ and ‘user name’ , adust the given timeperiod, enter in the field ‘abap program name’ the report name ‘/sapapo/om_reorg_daily’and press F8 Å The lists shows all jobs that execute this report. It should run once pernight.

You can also use TA /sapapo/om13 to check this. In the category ‘checks’ there is a light,that indicates whether the job is scheduled properly or not.

8. Check the following COM routine statistics (TA lc10)

8.1. Number of calls

8.2. Average runtime

8.3. Number of accesses to heap

8.4. Number of accesses to data cache

8.5. Maximum heap usage

Lc10 Å Enter logical connection LCA Å liveCache monitor Å The table shown includesthis data in the columns ‘db procedure’ (name of come routine), ‘calls’ (Number of calls),‘runtime (average)’ (average runtime), ‘oms dereferncings’ (number of accesses to heap),‘lc dereferencings’ (number of accesses to data cache) and ‘oms cache size’ (maximumheap usage).

9. Check currently used heap memory and maximum allocated heap memory since lastliveCache restart (TA se38)

Se38 Å run report ‘/sapapo/om_lc_mem_monitor’ Å In the heather of the table shown thevalue ‘total heap’ marks the currently used amount of heap memory and the value ‘R’indicates the maximum amount of allocated heap since the last liveCache restart.

Also you can use the button ‘reset’ to delete all com routine statistics in this table and thetable mentioned in the exercise before and begin a new run of data collection.

© SAP AG BC555 11-10

6ROXWLRQV&KDSWHU��DQG��

1. Check internal data consistency (TA /sapapo/om17)

/sapapo/om17 Å F5 Å enter planversion ‘000’ and liveCache ‘LCA’ Å F8 Å the lights inthe first row of the table indicate inconsistencies

The results of the reports are only reliable, if no other application is running at the sametime. Therefore make sure, that no other user is logged on.

If inconsistencies are present, you can only correct them by deleting data. (also in/sapapo/om17)

To check external data consistency you can use TA /sapapo/ccr.

2. Check status of synchronous logging and turn it on if necessary (TA /sapapo/om06)

/sapapo/om06 Å Mark the radio button for synchronous logging and also set the flag forlog data archiving. Å Save your entries.

3. Check history of liveCache online backups from within your APO system (TA/sapapo/om11) and using dbmgui

/sapapo/om11 Å Enter the desired start date and press F8 Å The table lists all checkpointsand liveCache online backups.

Note: Only checkpoints and backups execute by a job are listed. Action taken by startingthe report /sapapo/om_checkpoint_write or in TA /sapapo/om18 are not listed.

© SAP AG BC555 11-11

4. Define a backup medium using dbmgui

Start dbmgui Å doubleklick on the icon for the desired liveCache in the upper part of thescreen Å doubleklick on ‘configuration’ and then ‘backup media’ Å press the button‘medium’ Å enter name (e.g. LCBACKUP) and location (e.g. d:\temp\backup.sav) of thenew medium Å choose device type ‘file’ and backup type ‘complete’ Å klick on‘extended’ and set the flag for ‘overwrite’ Å save your entries

The backup to this medium will be stored locally on your hard disc. Make sure you savethe file later on some external device like a tape.

Also make sure there is enough room for your backup in the given file system.

You can also connect an external backup tool like omnibackup or adsm server over‘backint for sapdb’ and ‘backint for oracle’ to save your backup.

5. Execute a liveCache online backup using dbmgui

Start dbmgui Å doubleklick on the icon for the desired liveCache in the upper part of thescreen Å press on ‘backup’ Å ‘complete’ Å mark the backup medium of your choice Å‘next step’ Å mark the ‘recovery’ radio button Å ‘start backup’

Check the return code of your backup in the backup history.

6. Schedule a daily liveCache online backup at midnight (TA se38 and sm36)

Define a variant for report /sapapo/om_checkpoint_write:

/sapapo/om18 Å ‘YES’ Å mark ‘liveCache backup’ and ‘delete archive log area’ Å enterthe name of your backup medium Å enter the name of the variant Å save the variant

Schedule the liveCache online backup job

Sm36 Å enter ‘job name’ , ‘job class’ and ‘target server’ Å ‘start condition’ Å ‘date andtime’ Å enter schedule start and time Å ‘period value’ Å ‘daily’ Å ‘save’ Å ‘save’ Å‘step’ Å ‘abap program’ Å enter name ‘/sapapo/om_checkpoint_write’ and the variantyou defined before Å ‘save’ Å ‘save’ Å Now your job is released and will run daily.

© SAP AG BC555 11-12

7. Write a liveCache checkpoint (TA /sapapo/om18)

/sapapo/om18 Å do not define a variant Å do write a checkpoint

Check checkpoint log afterwards. (log is shown automatically)

This checkpoint will not be listed in TA /sapapo/om11.

8. Schedule an automatic liveCache checkpoint every two hours (TA sm36)

Sm36 Å enter ‘job name’ , ‘job class’ and ‘target server’ Å ‘start condition’ Å ‘date andtime’ Å enter schedule start and time Å ‘period value’ Å ‘hourly’ Å ‘save’ Å ‘save’ Å‘step’ Å ‘abap program’ Å enter name ‘/sapapo/om_checkpoint_write’ but do not enter avariant Å ‘save’ Å ‘save’ Å Now you scheduled a checkpoint every hour.

9. Crash your liveCache and restore it afterwards (TA lc10)

Write a liveCache backup.

Crash and recover your liveCache in two different ways.

Crash:

Stop the liveCache in TA lc10, delete one of the datadevspace files and restart theliveCache. It won’ t be able to start but will stop in modus cold.

Recovery:

Start dbmgui Å doubleklick on the icon for the desired liveCache in the upper part of thescreen Å ‘recovery’ Å ‘database’ Å choose last backup Å ‘start recovery’ Å restart yourliveCache in TA lc10

Crash:

In TA sm49 execute the command dbmcli -d <LC SID> -n <LC HOST> -u control,controldb_stop

Recovery:

Lc10 Å restart liveCache Å include archive log areas in recovery Å check in sm50 whenrecovery job has finished

(This works only if synchronous logging a archiving of log areas is turned on.)

© SAP AG BC555 11-13

&KHFN�\RXU�WKHRUHWLFDO�OLYH&DFKH�NQRZOHGJH

4XHVWLRQV1. Via which tool(s) can you administer and monitor a OLYH&DFKH?

2. How can you tell if a particular OLYH&DFKH is active and ready to use?

3. Can a physical OLYH&DFKH be identical to the DBMS used by APO?

4. Can a physical OLYH&DFKH be identical to the DBMS used by APO, when the DBMS isSAP DB?

5. Does a physical OLYH&DFKH have to run on the same server as the APO DBMS?

6. In which cache is information stored about the physical location of logical data pageson disk?

7. Where are the contents of the Converter cache stored during a checkpoint?

8. Where are the contents of the Data cache stored during a checkpoint?

9. What block-size is used to store information in all devspaces?

10. What data cache hit rate do we want to have ?

© SAP AG BC555 11-14

$QVZHUV1. Dbmcli commands, TA lc10, dbmgui

2. Select any pushbutton except “OLYH&DFKH monitor”. The traffic light attached to field“OLYH&DFKH status” should be GREEN.

3. No. It must run in its own object oriented DBMS. This must be OLYH&DFKH.

4. No. It must run in its own object oriented DBMS. OLYH&DFKH installation is different to astandard DBMS installation.

5. No. In fact, for mid-range to large APO systems, SAP recommends that the OLYH&DFKHruns on its own server.

6. Converter cache

7. System devspace

8. Data devspace

9. 8KB

10. At least 99%.

live cache administration sap

Documents