Live Cache Administration SAP

Full text

(1)BC555 liveCache Administration. liveCache Administration. R/3 R/3 Release Release 4.6C 4.6C  SAP AG 1999. R/3 Release 4.6 C Material Number 5004 0750. 50040750 50040750.

(2) Copyright. Copyright 2002 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. All rights reserved..  SAP AG 2002. 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..

(3) 6$3%DVLV$GPLQLVWUDWLRQ7UDLQLQJ ([SHUW&RPSHWHQFH. &RUH&RPSHWHQFH. ))%$%. 3 days Database Administration Oracle. &'("$. 2 days R/3-Technical Implementation and Operation Management. )+*,,. Technical Core Competence. )#"-%. ))%/... !#"$%. 3 days Advanced R/3 System Administration. 5 days. 3 days. Workplace. 3 days. Workload Analysis. Software Logistics. j @=`=_e/:7CII4 ))"%$=. !#"/.%. 3 days. TCC Workplace. WYX I3 MEZ797; M=C8H[012 3/01\]6835N 3E98MI3^ 3E2 4E; 1T984 AD0@E_[`ba#; 9=:T1=G4Uc X ?Ed2 CIM=H 3 AD0@E_[eba#; 9=:T1=G4Uc X ?EOEPJ(fA AD0@E_hgia#; 9=:T1=G4Uc Xkj O!OTlnmUO382 o83E2 AD0@E_[prq a; 97:817G4sc X ?7tcu vKw8?7fAKe AD0@=xI`ytcDu vR?8d2 C=M8H 3 AD0@=x8_ztcDu vR?7u 98{ 12\]; S AD0@=xIeytcDu vR?8OPJ(fDA AD0@=pI`yu A j POg=Ì` AD0@=|I`yu A j ? @I|=` W}W AD0@=~I`ba!1T2YVI6EH C=MI3n DTI. 5 days Database Administration Informix ))%/.% 2 days Database Administration SAP DB ))%-$ 3 days Database Administration MS SQL Server ))%-% 3 days Database Administration DB2/400 ))%"$ 5 days Database Administration DB2/390 ))%"% 3 days Database Administration DB2 UDB. ))%%%. 0122 354768198:; 9=<(> ? @BADC54E; 4 F 9818G/H 3I:7<73BJK2 17:L8M5N7C89E:=? 12 OPJRQ7S76=382 N F 9E1=G/H 3I:T<E3UAK171V. 2 days. LiveCache Administration. .

(4) .  SAP AG 1999. © SAP AG. BC555. 1-1.

(5) 6$3µV.QRZOHGJH7UDQVIHU0RGHO t u v w x y zy u { | z } zy ~ x ~ z } x z} z} O P QR O P S T RUR V W R X Y T R QU O P S T RUR V W R ] KL Z[ K L M[M K L MNM K LZ[M K L ^_ _ \ 2 #%-434'5 -764!2C)Í65 5 &Î6 $ ³K L Z Â s M ´µ µ µ Ã ¶ º Ä · Å ¸ Æ º ¹ ¶ º »» ¼ ½ ¶ ¹ ¾ ¿ À ¶ µ ¿ Á Â µ µ Ã º Ä Å Æ º ¶ » Å » Ç È ¹ ¶ K ¿ L ¿ M s [ ÏÐ>)D0'3%*=/0 K L MZM ³ ´ µ ¶ · ¸ ¹ º» ¼ ½ ¶ ¹ ¾ ¿ À ¶ µ ¿

(6) > ÑÒÓ : Ô Õ

(7) Ö × Ô

(8) \ £ ¡ ¬ ¡ ² ¯ ° ° É £ Ê ¡ ¬ Ë ¯ ¡ ¢ ¡ ¦ ± ± ¡ ¤ L ` a b c d ` e f g e h i j Z K k c g c ¥ ¤ £ l e ` m nb f h b o a ` fp qr ¥ § ¡ ¦ ¥ ® ¯ ° ¥ ¬ ¥ ¡ ¡ ©¨ ¥ ¥ Ì ª ¡ ¢ ¥ ª « ¢ ¦ ¡ 2 days R /3-Techni cal I mp lementa tion and O pe rati on M an agem ent. Techni cal C ore Com petence. 3 days D atabase Administrat ion O RAC LE. 3 days Advanced R /3 System Admi nis tratio n. 5 days. 2 days D atabase Administrat ion SA P DB 3 days D atabase Administrat ion M S SQ L S erver. 3 days. Soft wa re L ogis tics. 3 days D atabase Administrat ion D B2 UD B. (SD). 2 d a ys. ( PP). 2 da y s. ( C O). 2 da ys. Techn i cal C or e Co mp ete nce Ve rsi o ns (SD) 2 d a ys. B C3 10 W in do ws NT / Oracl e BC3 14 Wi n dow s NT MS SQL Se rv er BC3 17 (W ind ow s N T / U N IX ) / D B2 (SD) 2 d a ys BC3 60 UNI X / Ora cle BC3 62 UNI X / SAP DB.  SAP AG 1999 fi lena me (autho2r)da / 2y s ( SD). ( SD). 1 day. ( SD). 1 day. ( SD).  SAP AG. 1 day. ( PP). 2 da y s. ( SD/ PP ). 2 da y s. (PP/ CO) 2 da ys. ; > < =%#) .?@ A! #%$&# BC*DFEG#4)5 #70

(9) > HI J. ( SD/ PP ) 2 da ys. ( SD). 2 da ys. KTM mySAP.com for Techn. Imp l., IT Cons. ,Sys. I ntegration UH / 7. E>ÚÛ(ÝÜFG5 %&*Þ45 ß%# 8 3/#- D.

(10) > à Ô áâ Ô ×

(11) ã7

(12) J. E>ÚÛ(ä;6):! å/Ïæ6/.+-43çE*#4)Íß'5 -/#.

(13) > Ñ Ö è éêë . E>ÚÛ(ä;6):! å/Ïæ6/.+-43Úì! #)Í..

(14) > Ñ ê@í. E>ÚÛ(. 8 G%04,'! .5 &ÎEG#) ß>5 -7#I0. 2'#/6 îAE'ÚÛ(ÎE,'==%G)1..

(15) > ã7 Ó è Ô á Õ

(16) Ö × Ô

(17)

(18) >

(19) >ÕíÙ Ó Ö .

(20) ' HI Ô ØI ÙÖ Ò "! #%$'&# (*)+ $*,%-/.10. 2'#%-434'5 -764! 8 #4)1.5 95 -/67.5 */0

(21) : .  SAP AG 1999. © SAP AG.

(22)

(23)

(24) . BC555. 2-1.

(25) &RXUVH3UHUHTXLVLWHV7DUJHW*URXS'XUDWLRQ. l &RXUVH3UHUHTXLVLWHV. %&RUVLPLODU6$3V\VWHPDGPLQLVWUDWLRQFRXUVH DOWHUQDWLYHO\'DWDEDVH$GPLQLVWUDWLRQFRXUVHOLNH%& %&«. l 5HOHDVHGHSHQGHQF\. $325HOHDVH$DQGOLYH&DFKHUHOHDVH. l 7DUJHW*URXS. 3URMHFWWHDPPHPEHUVUHVSRQVLEOHIRUWKHLQVWDOODWLRQDQG PDLQWHQDQFHRIDOLYH&DFKH. l 'XUDWLRQGD\V.  SAP AG 1999. © SAP AG. BC555. 3-1.

(26) &RXUVH*RDO. 7KLVFRXUVHZLOOHQDEOH\RXWR. l 'HILQH$32V\VWHPUHTXLUHPHQWV. l ,GHQWLI\WKHVSHFLILFOLYH&DFKH FRQILJXUDWLRQLQWKH6$3HQYLURQPHQW l 3HUIRUPOLYH&DFKHPRQLWRULQJDQG PDLQWHQDQFH. l /LVWDQGSHUIRUPZRUNZLWK'%0*8,DQG 6$3DGPLQLVWUDWLRQWRROV l 8QGHUVWDQGEDFNXSDQGUHFRYHU\ FRQFHSWVRIOLYH&DFKHLQWKH$32 V\VWHP.  SAP AG 1999. © SAP AG. BC555. 3-2.

(27) &RXUVH&RQWHQWV. &RXUVH2YHUYLHZ. Unit 1. OLYH&DFKH&RQFHSWV. Unit 4. OLYH&DFKH0RQLWRULQJ. Unit 2. OLYH&DFKH$UFKLWHFWXUH DQG5HTXLUHPHQWV. Unit 5. OLYH&DFKH%DFNXSDQG 5HVWRUH7HFKQLTXHV. OLYH&DFKH $GPLQLVWUDWLRQ. Unit 3. Unit 6. OLYH&DFKH%DFNXSDQG 5HVWRUHIRU$32. &RQFOXVLRQ.  SAP AG 1999. © SAP AG. BC555. 3-3.

(28) OLYH&DFKH&RQFHSWV. OLYH&DFKH&RQFHSWV OLYH&DFKH$UFKLWHFWXUH DQG5HTXLUHPHQWV OLYH&DFKH$GPLQLVWUDWLRQ OLYH&DFKH0RQLWRULQJ OLYH&DFKH%DFNXSDQG 5HVWRUH7HFKQLTXHV OLYH&DFKH%DFNXSDQG 5HVWRUHIRU$32  SAP AG 1999. © SAP AG. BC555. 4-1.

(29) OLYH&DFKH&RQFHSWV. $WWKHFRQFOXVLRQRIWKLVXQLW \RXZLOOEHDEOHWR l 'HVFULEHWKHSXUSRVHRIOLYH&DFKH. l 'HVFULEHWKHDUFKLWHFWXUHRI6$3V\VWHPV. XVLQJOLYH&DFKHWHFKQRORJ\. l 'HVFULEHKRZOLYH&DFKHLQWHUIDFHVZLWK. 6$3EDVLVWHFKQRORJ\. l ([SODLQZKLFKGDWDDUHVWRUHGLQOLYH&DFKH. DQGKRZWKH\JHWWKHUH.  SAP AG 1999. © SAP AG. BC555. 4-2.

(30) $SSOLFDWLRQDQG%DVLV&RPSRQHQWVRI6$3$32 6XSSO\&KDLQ $YDLODEOH 'HPDQG 7R 3ODQQLQJ &RFNSLW 3URPLVH XVHV%:

(31). . 9HQGRU 0DQDJHG ,QYHQWRU\. 6XSSO\ 1HWZRUN 3ODQQLQJ. &DSDEOH 3URGXFWLRQ 7R 3ODQQLQJ 0DWFK 'HWDLOHG 6FKHGXOLQJ. . 'DWDEDVH ZLWK%:WHFKQLTXHV DYDLODEOH. OLYH&DFKH. $32 2SWLPL]HUV. 4XHXHG5)& T5)&

(32) 6\QFKURQRXV5)& V5)&

(33) %$3, Model Generator, mapping, connectivity. 5 53,. 6$3 %:. /HJDF\ 2/73. 1RQ6$3 2/73. 1RQ6$3 2/73.  SAP AG 1999. n. liveCache is a component of the SAP New Dimension Product APO (Advanced Planner and Optimizer).. n. As of Release 4.5A, the SAP system can connect to multiple databases. The APO system utilizes this functionality 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 is comparable to the RDBMS of a standard SAP system. It provides Business Information Warehouse (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 which also communicate with the liveCache. These programs provide sophisticated optimization algorithms.. n. SAP R/3 uses the APO-CIF interface to handle data transfer to APO. APO-CIF is part of R/3 Plug In, a collection of interfaces to the different components of the mySAP.com system landscape. The APO 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, used by ATP) calls with SAP systems. This allows for a seamless integration of APO functions into the customer’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-3.

(34) OLYH&DFKH7HFKQRORJ\ OLYH&DFKH7HFKQRORJ\ OLYH&DFKH6HUYHU. $SSOLFDWLRQ6HUYHU. $%$3 $%$3. &. !PV. µV. 5'%06 5'%06 OLYH&DFKH OLYH&DFKH. 'DWDEDVH6HUYHU. l OLYH&DFKHLVDQREMHFWRULHQWHGGDWDEDVHPDQDJHPHQWV\VWHP GHYHORSHGE\6$3WKDWUHVLGHVLQDYHU\ODUJHPHPRU\. l 2SWLPL]HG&SURJUDPVUXQRQWKHOLYH&DFKHVHUYHUDQGKDYH DFFHVVWROLYH&DFKHGDWD l 7KHPDLQREMHFWLYHLVWRRSWLPL]HSHUIRUPDQFH. OLYH&DFKHUHVLGHVLQPDLQPHPRU\DQGWKHUHIRUHDYRLGVGLVN,2. . 2EMHFWRULHQWDWLRQHQDEOHVHIILFLHQWSURJUDPPLQJWHFKQLTXHV . . OLYH&DFKH &DFKHSURFHVVHVSURYLGHVVFDODELOLW\.  SAP AG 1999. n. In a standard SAP system, typical database request times are above 1 ms. For data intensive applications, a new technology is required in order to achieve better response times. liveCache has been developed to reduce typical database request times to below 10 µs. Key factors in achieving these 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 the liveCache 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 various applications. APO does not yet use this possibility. Currently two logical connections to liveCache are 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-4.

(35) &RPPDQGDQDO\]HU. 1DWLYH64/

(36). 1DWLYH64/

(37). 2SWLPL]HUV613&70DQG33'6. 'DWDEDVHLQWHUIDFHRI6$3NHUQHO. $FFHVVLQJOLYH&DFKH. O L Y H & D F K H. 64/ FODVV 64/ 64/EDVLV % WUHHV

(38). )UDPHZRUN IRUPHWKRG HPEHGGLQJ. 206. 206EDVLV. SDJHFKDLQV

(39). 7\SHOLEUDU\ &20REMHFWV '//

(40). 5HJLVWU\. 'DWD&DFKH. 64/GDWD 2EMHFWGDWD. 64//RJ.  SAP AG 1999. n. ABAP Programs and the APO optimizers use native SQL for communicating through the standard SAP database interface to liveCache. liveCache has an SQL interface that is used to communicate with the SAP instances. With native SQL, ABAP programs call stored procedures in the liveCache that point to Component Object Model (COM) routines written in C++. An SQL class provides access 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 string DBPROC SAPR3."SAPAPO_.. n. The COM routines are part of a dynamic link library that runs in the process context of the liveCache instance. In the Windows NT implementation of liveCache, COM routines and their interface are registered 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 Object Management 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 called pages.. n. liveCache stores the OMS objects in page chains, the pages in the chain linked by pointers. SQL table data are stored in the form of B* trees. SQL and OMS data reside together in the data cache of the liveCache. Each page in liveCache is marked as an SQL page or an OMS page.. © SAP AG. BC555. 4-5.

(41) OLYH&DFKH3URJUDPPLQJ&RQFHSWV l 7UDQVDFWLRQ&RQFHSW /RFNLQJ. . 5ROOEDFN . &RPPLW . OLYH&DFKH OLYH&DFKH. 5HDGFRQVLVWHQF\. . l OLYH&DFKHVXSSRUWVWKHIROORZLQJREMHFWRULHQWHGFRQFHSWV (QFDSVXODWLRQ. . 8QLTXHREMHFWLGHQWLW\ . 0HWKRGVVXFKDVLQVWDQFHDQGFODVVOHYHO. . l 7KHIROORZLQJFRQFHSWVDUHLPSOHPHQWHGLQWKH& DSSOLFDWLRQOD\HU $EVWUDFWFODVVHV. . ,QKHULWDQFH . 3RO\PRUSKLVP . . $JJUHJDWLRQ.  SAP AG 1999. n. The transaction concept common to relational database systems is also available for liveCache objects. liveCache supports read-consistency, that is, the data returned by liveCache represent the state of the data at the time, when the transaction that issued the read operation was started, even if some of these data have changed during retrieval by liveCache.. n. The liveCache concept incorporates both SQL data access and object orientation. The COM routines have direct access to the objects stored in the liveCache and can manipulate them. This manipulation includes 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-6.

(42) $32'DWDLQOLYH&DFKH $32. OLYH&DFKH6HUYHU. $SS6HUYHU 6HUYHU $SS. )URQWHQG. $SSOLFDWLRQ OLYH&DFKH OLYH&DFKH 'DWDPXVWEH FRQVLVWHQW. 0DVWHUGDWD. 7UDQVDFWLRQ GDWD. OLYH&DFKH GHYVSDFHV. $32'DWDEDVH  SAP AG 1999. n. Some APO data only exist in the APO DB, others only in liveCache, some data are stored in APO database and liveCache. Data in APO DB and liveCache have to be in a consistent state. It is not acceptable, 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 Demand Planning.. é liveCache stores master data in compressed form (information like material texts is not required by COM routines). Transaction data (e. g. sales order, confirmed shipments, purchase orders including 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 BOM explosion 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-7.

(43) /RDGLQJ'DWDLQWROLYH&DFKH $32. OLYH&DFKH6HUYHU. $SS6HUYHU 6HUYHU $SS. )URQWHQG.

(44) ,QLWLDOL]H OLYH&DFKH.

(45) 5HORDGPDVWHUDQG WUDQVDFWLRQGDWDIURP$32 $SSOLFDWLRQ '%WROLYH&DFKH

(46) 5HORDG '3GDWD. OLYH&DFKH OLYH&DFKH. 0DVWHUGDWD. 7UDQVDFWLRQDO GDWD

(47) 'HOHWHGHUHIHUHQFHG GDWDLQ$32'%. $32'DWDEDVH. OLYH&DFKH GHYVSDFHV.  SAP AG 1999. n. liveCache can be re-initialized. As a result, all data in liveCache are deleted. This is, e.g., required if a 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 database and 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 from planning areas in liveCache into a pre-defined backup info cube. If you have backed up Demand Planning data into such a backup infocube, reload these data into liveCache.. © SAP AG. BC555. 4-8.

(48) OLYH&DFKH$GPLQLVWUDWLRQ'%0*8,DQG/&.  SAP AG 1999. n. liveCache, like the standard SAP RDBMS, can be administered from within the SAP system. You can 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 available without 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. Both DBMGUI and dbmcli can be used for all liveCache administration tasks including backup and restore.. 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-9.

(49) OLYH&DFKH&RQFHSWV8QLW6XPPDU\. <RXDUHQRZDEOHWR. l 'HVFULEHKRZOLYH&DFKHFRQFHSWVDUHXVHGWR DFKLHYHIDVWUHVSRQVHWLPHVLQDSSOLFDWLRQVZLWKD KLJKGDWDYROXPH l ([SODLQWKHREMHFWRULHQWDWLRQRIOLYH&DFKH. l 'HVFULEHKRZOLYH&DFKHLQWHUIDFHVZLWKWKH6$3 V\VWHP l 1DPHWKHOLYH&DFKHDGPLQLVWUDWLRQWRROV.  SAP AG 1999. © SAP AG. BC555. 4-10.

(50) ([HUFLVHV6HUYHU/DQGVFDSH. 8QL[6HUYHU __________ R/3 System '(9(4.6C) Check, if bc555-NN exists. If not: Copy user training/bc555 to bc555-NN L01: l01adm LC10: user bc555-NN attaches LNN. L02: l02adm . .. 7UDLQLQJJURXSV NN 01 02 telnet: user l02adm password l02adm. . .. 15 Register. L15: l15adm. Start DBMGUI using TS Client. 177HUPLQDO6HUYHU ________ APO System 202(3.0A) Check, if bc555-NN exists. If not: Copy User Training/bc555 to bc555-NN LCA OMO DBMGUI.  SAP AG 1999. n. Each group NN logs on to unix server ___________ with telnet and lNNadm/lNNadm as user password/combination. On this server, é a liveCache LNN is available for the group NN, lNNadm is the <SID<adm> liveCache administration user.. é 1 R/3 system DEV is available, administered by devadm user. Attach your liveCache to transaction LC10 and make user and password for user lNNadm known to R/3 adminstrator devadm.. n. Each group calls DBMGUI application. The NT application DBMGUI actually runs on the terminal server _________ and is called with the help of a terminal server client. Register your liveCache LNN in DBMGUI. Depending on the terminal server setup, you will have to repeat this registration after 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 available users for operating system and SAP systems.. © SAP AG. BC555. 4-11.

(51) ([HUFLVHV. )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH Due to the particular requirements of this course, its actual implementation may vary between individual training centres. Before commencing the following exercises, please ensure your instructor has explained in detail the network and hardware topology in place for your particular training environment. You will be assigned a number that uniquely identifies the resources that are assigned to you during 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), the SAP system DEV (Rel 4.6C) is available. In addition, 15 OLYHCaches with SID ranging between L01 and L15 are available for the groups. On a Windows NT terminal server, program DBMGUI is available for administration of the OLYHCaches installed on the Unix server. In addition, APO system OMO (APO release 3.0A) is available for APO specific topics. Each two course attendees that share a training PC, form a group. Each group is assigned a number ranging from 01 to 20 in the following way Group 01 is the rightmost group in the first row (as seen from the instructor). Example of group number assignment in other rows: If group 04 is the leftmost group in row 1, then the rightmost group in row 2 is assigned number 05. $VVHHQIURPWKHWUDLQHU. $VVHHQE\FRXUVHDWWHQGHHV. 07 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 with password lNNadm (Example for group 01: user l01adm, password l01adm). On this server a liveCache LNN is available and will be administered by group NN (Example: group 01 will administer OLYHCache L01) Logon to Windows Terminal server: Simply click the DBMGUI server icon and DBMGUI will be started in a separate window. Group NN has to register OLYHCache LNN for administration purposes. SAP Systems DEV and OMO: You can log on info with user training, password bc555. After loging on, copy user training to user BC555-<NN> (Example BC555-01 for group 01) with the help of transaction SU01. If user BC555-NN is already defined, change the password to bc555NN. Group NN has to register OLYHCache LNN for administration with transaction LC10. © SAP AG. BC555. 4-12.

(52) ([HUFLVHV )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH To perform the following exercises, you will need to logon to the SAP systems OMO and DEV. To do this, please follow the instructions given to you by your course instructor. 1R . 1.1 1.2 1.3 1.4 . ([HUFLVH. 6KRZEDVLF$32OLYH&DFKHUHODWLRQVKLS. What OLYHCache(s) are defined to APO system OMO?. Which logical OLYHCache is used by the majority of APO application components? Which logical OLYHCache is used by ATP (Available To Promise)?. On what server is logical OLYHCache “ LCA“ of the APO system OMO running?. OLYH&DFKHDGPLQLVWUDWLRQPRQLWRULQJWRROV8VH6$3V\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 fully functional for your OLYHCache? If not: see exercises for chapter 4.. 2.4. Start DBMGui. . 7KHIROORZLQJTXHVWLRQVDUHLQWHQGHGWRVKRZ\RXKRZWRH[WUDFWVRPHEDVLF LQIRUPDWLRQDERXWWKHOLYH&DFKH. )RUWKHPRPHQWSUHIHUDEO\XVH$32V\VWHP202&DOOWUDQVDFWLRQ/&IRU ORJLFDOOLYH&DFKH³/&$³. 3.1 3.2 3.3 3.4 3.5. How can you tell if a particular OLYHCache is active and ready to use? What is the version and build level of the OLYHCache kernel.. Can a physical OLYHCache be identical to the DBMS used by APO?. Can a physical OLYHCache be identical to the DBMS used by APO, when the DBMS is SAP DB? Does a physical OLYHCache have to run on the same server as the APO DBMS?. © SAP AG. BC555. 4-13.

(53) 6ROXWLRQV )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH To perform the following exercises, you will need to logon to the SAP systems OMO and DEV. 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 to display the contents of this table. Method #1: Run transaction SE16 from the command line (“ /NSE16” ) or use menu path “ Menu Å SAP menu” , then select from the resulting menu tree "Tools Å ABAP/4 Workbench Å Overview Å Data Browser” . then Input “ 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 the pushbuttons. The server name can be found in field “ OLYHCache server” at the top LHS (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. 2.4. 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\VLFDOOLYH&DFKH1DPH and OLYH&DFKHVHUYHUQDPH. On your desktop, double click the Icon called GEPJXL,&$. © SAP AG. BC555. 4-14.

(54) 3.1 3.2. Select any pushbutton except “ OLYHCache monitor” .. The traffic light attached to field “ OLYHCache status” should be GREEN. 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 a standard DBMS installation. 3.5. No In fact, for mid-range to large APO systems, SAP recommends that the OLYHCache runs on its own server.. © SAP AG. BC555. 4-15.

(55) OLYH&DFKH$UFKLWHFWXUHDQG5HTXLUHPHQWV. OLYH&DFKH&RQFHSWV OLYH&DFKH$UFKLWHFWXUH DQG5HTXLUHPHQWV OLYH&DFKH$GPLQLVWUDWLRQ OLYH&DFKH0RQLWRULQJ OLYH&DFKH%DFNXSDQG 5HVWRUH7HFKQLTXHV OLYH&DFKH%DFNXSDQG 5HVWRUHIRU$32  SAP AG 1999. © SAP AG. BC555. 5-1.

(56) OLYH&DFKH$UFKLWHFWXUHDQG5HTXLUHPHQWV. $WWKHFRQFOXVLRQRIWKLVXQLW \RXZLOOEHDEOHWRGHVFULEH l $32EDVLVDUFKLWHFWXUH. l OLYH&DFKHSURFHVVHVDQGWDVNV l OLYH&DFKHPHPRU\UHJLRQV. l OLYH&DFKHGLVNDUFKLWHFWXUH. l ,PSRUWDQWOLYH&DFKHSDUDPHWHUV. l +DUGZDUHUHTXLUHPHQWVRIDQ$32V\VWHP.  SAP AG 1999. © SAP AG. BC555. 5-2.

(57) %DVLV$UFKLWHFWXUHRI6$3$32. 3UHVHQWDWLRQOHYHO 6$3*8, 'LVSDWFKHU. 6$3*8, 'LVSDWFKHU. $SSOLFDWLRQOHYHO :3. 'DWDEDVHOHYHO. :3.

(58) !#"$ % $&% '. :3. :3. :3. $32 2SWLPL]HUV. OLYH&DFKH OLYH&DFKH.  SAP AG 1999. n. The 3-tier client/server architecture of a standard SAP system consists of presentation, application, and database levels. On the SUHVHQWDWLRQOHYHO, SAP users communicate with the SAP system using the SAP GUI. Events like the user choosing ENTER or Save, trigger the execution of a dialog step. On the DSSOLFDWLRQOHYHO, the SAP dispatcher process receives the user’s request for the processing of 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 the ABAP instructions corresponding to the dialog step. The work process sends ABAP SQL database instructions 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 the user' 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 a single user, called SAPR3. Work processes connect to the relational database at SAP instance startup and 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 is no longer required. Work processes use such an additional database connection to communicate with liveCache.. n. APO optimizers communicate via RFC with the SAP instance. Some, but not all, optimizers directly communicate with liveCache by establishing a liveCache session.. © SAP AG. BC555. 5-3.

(59) 7KH6$36\VWHPDQGOLYH&DFKH&RPPXQLFDWLRQ. 6$3LQVWDQFHV. OLYH&DFKH WKUHDGV. 'LVSDWFKHU. 'LVSDWFKHU. :3. :3. :3. :3. 8VHUWDVNV &RRUGLQDWRU. 5HTXHVWRU. (*) ,+.-/102) 3 5 4 'DWD&DFKH +.3637989:;0<)63 . OLYH&DFKH PHPRU\DUHDV. &RQYHUWHU&DFKH. 64/5ROOEDFN&DFKH 64//RJ,24XHXH.  SAP AG 1999. 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 the hard disks. Changes to objects are logged into transaction specific rollback and history files in data cache. ‘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 log I/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 units called tasks. Each of the tasks performs specialized functions. The thread hosting tasks is called user kernel thread (UKT). The UKT can coordinate its own tasks more efficiently than the operating system.. n. Tasks called user tasks are used to establish and maintain liveCache sessions. As soon as liveCache functionality is required, an SAP work process logs on to liveCache and is assigned to a user task in a UKT.. © SAP AG. BC555. 5-4.

(60) 8VHU

(61) 8VHU

(62) 8VHU

(63) 8VHU

(64) 8VHU

(65) 8VHU

(66) 8VHU Q

(67) 8VHU Q

(68) 8VHU Q

(69) 8VHU 8VHU 6HUYHU

(70) 8VHU 8VHU 6HUYHU

(71) 8VHU 8VHU 6HUYHU Q

(72) 8VHU 8VHU 'DWD:ULWHU

(73) Q

(74) 'DWD:ULWHU

(75) Q

(76) 8VHU 8VHU $ORJ:ULWHU 8VHU 8VHU *DUEDJH&ROOHFWRU 8VHU 8VHU &RQY6FDQQHU 8VHU 8VHU 7UDFH:ULWHU 8VHU 8VHU 8WLOLW\ 6HUYHU 6HUYHU 6HQGHU 6HUYHU 6HUYHU 5HFHLYHU GDWDZULWHU GDWDZULWHU 7LPHU. &RRUGLQDWRU Initialization / UKP coordination 5HTXHVWRU Connect processing. 8VHU.HUQHO7KUHDG8.7. 8VHU.HUQHO7KUHDG8.7. 8VHU.HUQHO7KUHDG8.7. OLYH&DFKH7KUHDGVDQGWKHLU7DVNV. &RQVROH Diagnosis &ORFN Time monitoring 'HY7KUHDG Master for forI/O on DEVSPACE 'HY,!VODYHWKUHDGV $V'HYLWKUHDGV $V\QF!WKUHDGI/O $V\QF!WKUHDGI/O on DEVSPACE.  SAP AG 1999. n. Coordinator controls initialization of the liveCache. During runtime, the Coordinator coordinates the user 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 the operating system level. On Windows NT, the console thread provides information for the x_cons diagnosis 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. Dev0 coordinates the Dev threads. The liveCache starts a configurable number of dev processes for each devspace.. n. One or more user kernel threads (UKTs) can be configured (with parameter MAXCPU) to establish and maintain user sessions.. n. The AsDev processes are created temporarily during a backup to perform backup-related I/O operations. Their number depends on the number of data devspaces and backup devices. They are coordinated by an additional thread called Async0.. © SAP AG. BC555. 5-5.

(77) 8.77DVN'HVFULSWLRQ 8VHU 8VHU 8VHU 8VHU 6HUYHU 6HUYHU $/RJ:ULWHU

(78) $/RJ:ULWHU

(79). 2/RJ:ULWHU

(80) 2/RJ:ULWHU

(81). 'DWD:ULWHU

(82) Q

(83) 'DWD:ULWHU

(84) Q

(85) &RQY6FDQQHU 7UDFH:ULWHU 8WLOLW\ 7LPHU *DUEDJH&ROOHFWRU

(86) *DUEDJH&ROOHFWRU

(87) *DUEDJH&ROOHFWRU Q

(88) *DUEDJH&ROOHFWRU Q

(89). 8.77DVNV. ([HFXWHVFRPPDQGVIURPDSSOLFDWLRQVDQG LQWHUDFWLYHFRPSRQHQWV 3HUIRUPV,2GXULQJEDFNXSV :ULWHVWKHORJVWRWKHORJGHYVSDFHV :ULWHVWKHORJVWRWKHORJGHYVSDFHV :ULWHVGLUW\SDJHVIURPWKHGDWDFDFKHWRGLVN 6FDQVIRUIUHHFRQYHUWHUSDJHV. :ULWHVWKHNHUQHOWUDFHWRWKHNHUQHOWUDFHILOH +DQGOHV DGPLQLVWUDWLRQ +DQGOHVOLYH&DFKH OLYH&DFKHDGPLQLVWUDWLRQ. 0RQLWRUV/2&.DQG5(48(677,0(287V 0RQLWRUV/2&.DQG5(48(677,0(287V. 5HPRYHVKLVWRU\ILOHV RIRXWGDWHG RXWGDWHGREMHFW REMHFWGDWD 5HPRYHVKLVWRU\ILOHVRI.  SAP AG 1999. 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 dynamically over the configured UKTs according to defined rules. Task distribution is controlled by support parameters like, e.g., _TASKCLUSTER_02.. n. UKT tasks allow for a more effective synchronization of actions involving several components of the liveCache, and minimize expensive process-switching.. © SAP AG. BC555. 5-6.

(90) OLYH&DFKH5RRW'LUHFWRU\. ELQ6KHOOVFULSWVIRUOLYH &DFKHV\VWHPSURJUDPV 6KHOOVFULSWVIRUOLYH&DFKHV\VWHPSURJUDPV SJP OLYH&DFKHV\VWHPSURJUDPVWRROV OLYH&DFKHV\VWHPSURJUDPVWRROV HQY0HVVDJHDQGKHOSILOHV PLVF0LVFILOHV FRQILJ SJP ELQ HWFOLVWRILQVWDOOHGILOHV <SID>. VDSGE ZUN. Y9Z5[ ]\. YHUV!. 6,'!. OLE/LEUDULHVIRUSUHFRPSLOHUFDOOLQWHUIDFHV F$N<G@GIH HJ@J@K KL2L<MM O PRQ6Q N<GIH S6Q L<T<P N<G@H J@U@VXW LQFO,QFOXGHILOHVIRUSUHFRPSLOHU & =>? @" A % & B% C ?ED ? B = GHPR'HPRQVWUDWLRQSURJUDPV ZUN'HIDXOWGLUHFWRU\IRU581',5(&725<DQG%$&.83',5(&725< FRQWDLQVFRQILJXUDWLRQGLUHFWRU\³FRQILJ´DQG'LDJQRVLVGLUHFWRU\'%1$0(!. VDS6$3VSHFLILFOLYH &DFKHXWLOLWLHV 6$3VSHFLILFOLYH&DFKHXWLOLWLHV  SAP AG 1999. n. The path to the DBROOT directory is assigned to the environment variable DBROOT which is defined for the operating system user "<liveCache SID>adm".. n. In its standard subdirectories, the DBROOT directory contains all the operating system files necessary 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 are stored 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 is copied to “knldiag.old” é Trace file “knltrace” contains the liveCache developer trace that can be switched on for low level diagnosis é 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 with the name <SID>. This file can be found under: /sapdb/config. Previous versions are available under the name <SID>.<version#>. © SAP AG. BC555. 5-7.

(91) OLYH&DFKH'LVN5HJLRQV. ^`_9acb`3 dèfhgi/j k3 +`lman+ò ho ap+ ZXq!Zsr ûtv*^w Z5x`y{z ^ ]io o mb8 y{ry *^`wEe y{ry *^`w5f y{ry *^`w5} g!^`wEej4]`) oe. |k}~ bl bl bl bl bl. }. &RQYHUWHU 6<67(0. y -,89`) 9 +ml. 'DWD&DFKH 'DWD&DFKH ',6.'. &RQYHUWHU&DFKH &RQYHUWHU&DFKH. ',6.' ',6.'. Converter Page Header: Version # data page# devno offset type filler Converter Page Header: Version # 4711 1 240 f 0 data page# devno offset type filler 4712 3 219 t 1 4711 3 140 p 0 4712 2 191 t 1.  SAP AG 1999. n. The entire liveCache disk area is divided into 8 Kbytes blocks called pages. Disk areas used by liveCache 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 liveCache onto existing data devspaces using a 64 Kbyte striping mechanism to ensure balanced I/O. Data pages are cached in the data cache in main memory.. n. liveCache administers the disk storage location of the logical pages in the converter. The logical pages are consecutively numbered data pages that are available to store data. Each logical page can exist in two versions on disk. Different versions are stored in different converter pages. For each version of a logical page, a converter entry describes the location on a data devspace. Since a converter entry is 35 bits long, 2000 converter entries make up one converter page. Converter version numbers are incremented by a checkpoint.. n. The size of the system devspace is approximately 0.1% of the size of the liveCache. When you extend 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-8.

(92) &DFKHVDQG.HUQHO3DUDPHWHUV. 8.77KUHDGVDQG7DVN&RQILJXUDWLRQ 0$;&38 8.7 8.7 8.7Q 8.7Q 0$;86(57$6.6 B7$6.&/867(5B &ORFN &ORFN 'HY 'HY &DFKHVDQG0HPRU\6L]HV '$7$B&$&+( &$7B&$&+(B6833/< &219(57(5B&$&+( 206B+($3/,0,7. 'HY 'HY 'HYQ 'HYQ &RQVROH &RQVROH. 'DWD&DFKH 'DWD&DFKH &RQYHUWHU&DFKH &RQYHUWHU&DFKH. &DWDORJ&DFKH &DWDORJ&DFKH 64/5ROOEDFN&DFKH 64/5ROOEDFN&DFKH 6<67(0 'DWD. . /2*. 8SSHUOLPLWV 8SSHUOLPLWV 0$;'$7$'(963$&(6 'DWD1 0$;'$7$3$*(6. . . 5HTXHVWRU 5HTXHVWRU &RRUGLQDWRU &RRUGLQDWRU. $1$/<6,6 581',5(&725<. .  SAP AG 1999. n. The above parameters are given default values during installation. These values can be adapted to the specific requirements of the customer system. Storage-related parameters are adapted in units of 8 Kbytes, which is the smallest storage unit on disk and in memory. Changes to kernel parameters become effective only after liveCache has been stopped and restarted.. n. Parameter OMS_HEAPLIMIT is important for a proper functioning of the liveCache. It represents an upper limit for heap allocation of COM routines. 50% of allocatable shared memory should be available for heap memory of COM routines. Set OMS_HEAPLIMIT to 0 (parameter disabled) to allow 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 configured database size in pages must exceed 2*DATA_CACHE. The physical memory required for your liveCache server should be the result of a sizing. é MAXCPU: Usually,this parameter determines the number of UKTs with user tasks. If support parameter _TASKCLUSTER_02 contains the string 1*us, MAXCPU parameter is disabled and 1 UKT 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 data pages. Recommendation: use a value equivalent to 0.05% of configured liveCache size.. © SAP AG. BC555. 5-9.

(93) +DUGZDUH5HFRPPHQGDWLRQVIRU$326\VWHPV 1HWZRUN&RQQHFWLRQ - High speed (FDDI, High Performance Switch) - Ethernet or equivalent $326\VWHP6WDQGDUG&RQILJXUDWLRQ APO DB server l Database with BW -like configuration l APO SAP instance. APO server l APO SAP instance. $32)URQWHQG l APO GUI with OCX functionality, known WAN issues. On separate servers l SNP Optimizer l PP/DS Optimzer l CTM Optimizer. $32)URQWHQG l APO GUI with OCX functionality, known WAN issues. APO OLYHCache server l OLYHCache l COM routines. $32)URQWHQG l APO GUI with OCX functionality, known WAN issues.  SAP AG 1999. n. liveCache requires adequate main memory to support fast response times, and scales very well with the available CPU resources.. n. Allow 30% of the available CPU and RAM resources for the COM routines, which run on the liveCache server.. n. The other components of an APO system ideally reside on servers separate from the liveCache and include: é SAP application instances. These usually require at least 1 Gbyte of RAM and are highly scalable with 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 highly scalable with respect to CPU power. é SNP, PP/DS and CTM optimizers. These are standalone programs consuming 1 CPU and around 512 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 SAP Notes 19227, 202934, 20624, 210890 and 20624 to allow for operating-system monitoring with transactions OS07 and RZ20 in the SAP system.. © SAP AG. BC555. 5-10.

(94) 6XPPDU\OLYH&DFKH$UFKLWHFWXUHDQG 5HTXLUHPHQWV <RXDUHQRZDEOHWRGHVFULEH l 7KHOLYH&DFKHLQWHUIDFHZLWKWKH$326$3. LQVWDQFHV. l OLYH&DFKHFDFKHWKUHDGDQGWDVN. WHFKQRORJ\. l 7KHOLYH&DFKHGLUHFWRU\VWUXFWXUH l ,PSRUWDQWOLYH&DFKHSDUDPHWHUV. l +DUGZDUHUHTXLUHPHQWVIRUOLYH&DFKH.  SAP AG 1999. © SAP AG. BC555. 5-11.

(95) ([HUFLVHV )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH To perform the following exercises, you will again need to logon to the APO system OMO. To do this, please follow the instructions given to you by your course instructor. Unless directed otherwise, whenever you are requested to extract OLYHCache information, please use transaction “ LC10“ specifying logical liveCache “ LCA“ 1R. ([HUFLVH. . OLYH&DFKHSURFHVVDUFKLWHFWXUH. 1.1. Display the threads and active tasks ofOLYHCache.. . OLYH&DFKHPHPRU\DUFKLWHFWXUH. 2.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 pages on 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&DFKHSURILOHSDUDPHWHUV. 3.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 diagnostic files?. . OLYH&DFKHGLVNDUFKLWHFWXUH. 4.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&DFKHRSHUDWLRQ. 5.1. What logmode is being used by the OLYHCache? Can you explain why?. © SAP AG. BC555. 5-12.

(96) 6ROXWLRQV )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH To perform the following exercises, you will again need to logon to the APO system OMO. To do this, please follow the instructions given to you by your course instructor. Unless directed otherwise, 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 the ENTER key. To display active tasks, select the radio button “ Active tasks” and press the ENTER key. 2.1. The main caches are: “ Data“ , “ SQL Log Queue“ , “ SQL Rollback“ ,“ Converter“ ,“ Catalog“ , “ FBM“ , “ USM“ , and “ Sequence“ . To access this information, select pushbutton “ OLYHCache monitor“ 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 COM routines. 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-13.

(97) 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 5.1. 8KB. Select pushbutton “ OLYHCache configuration” , then select tab “ Log area” . The required information can be found in the section “ Size of log area” attached to field “ Log mode” .. © SAP AG. BC555. 5-14.

(98) OLYH&DFKH$GPLQLVWUDWLRQ. OLYH&DFKH&RQFHSWV OLYH&DFKH$UFKLWHFWXUH DQG5HTXLUHPHQWV OLYH&DFKH$GPLQLVWUDWLRQ OLYH&DFKH0RQLWRULQJ OLYH&DFKH%DFNXSDQG 5HVWRUH7HFKQLTXHV OLYH&DFKH%DFNXSDQG 5HVWRUHIRU$32  SAP AG 1999. © SAP AG. BC555. 6-1.

(99) OLYH&DFKH$GPLQLVWUDWLRQ. $WWKHFRQFOXVLRQRIWKLVXQLW \RXZLOOEHDEOHWR l 'HVFULEHOLYH&DFKHRSHUDWLQJPRGHV. l ([SODLQWKHVWDUWLQJDQGVWRSSLQJSURFHGXUHVIRU. OLYH&DFKH. l 'HVFULEHWKHSXUSRVHRIWKHOLYH&DFKHLQLWLDOL]DWLRQ. SURFHVV. l 2XWOLQHWKHIXQFWLRQVRI'%0*8,. l $GPLQLVWHUOLYH&DFKHUHPRWHO\DQGIURPZLWKLQWKH. 6$3V\VWHP.  SAP AG 1999. © SAP AG. BC555. 6-2.

(100) 5HPRWHOLYH&DFKH$GPLQLVWUDWLRQ. l'DWDEDVH0DQDJHU '%0

(101) FOLHQWLQWHUIDFHFRPPDQGV. dbmcli -d <SID> -n <lc server> [-i script file] [-V] • db_warm • db_offline • show <SHOW command> • exec_command <command> • help <command>. l'DWDEDVH0DQDJHU '%0

(102) JHWILOHFRPPDQGV. dbmgetf -d <lc name> -n <lc server> -k <file id>.  SAP AG 1999. file id: • KNLDIAG • KNLDIAGOLD • KNLDIAGERR • LCTRC#<token>. n. liveCache can be administered remotely using the client-server based liveCache tool DBM, with its components DBM GUI and DBM server. Commands are transmitted from a remote DBM GUI via the 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 the interface dbmcli to connect to the DBM server (with the option “-u control,control”). The DBM user settings are stored in the registry on the client. Use the option “-us control,control” to store the DBM user registry entry for the liveCache instance (the syntax of releases before 7.1.3 Build 6 is “-uDBMs control,control”). é The operating system user has the default user “<SID>adm” with his/her operating system password. 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 old syntax is “-uOSs <SID>adm,<password>”).. © SAP AG. BC555. 6-3.

(103) OLYH&DFKH$GPLQLVWUDWLRQLQWKH6$36\VWHP.  SAP AG 1999. n. liveCache can be administered and monitored using Transaction LC10, and entering the logical name of the liveCache. Table DBCON correlates the logical and physical names of the liveCaches accessible 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-4.

(104) 6WDUWLQJ,QLWLDOL]LQJDQG6WRSSLQJWKHOLYH&DFKH.  SAP AG 1999. n. To start, stop and initialize the liveCache, use transaction LC10 and choose “liveCache administration”.. é Starting liveCache only starts liveCache into warm mode. liveCache has the state of the latest checkpoint (usually the one connected to the liveCache shutdown). é Initialization deletes the complete contents of the liveCache. The next slide describes the initialization process in more detail.. é Stop stops the liveCache. Before liveCache memory and processes are deleted, a checkpoint is triggered. 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 a restart 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 successful checkpoint is lost.. © SAP AG. BC555. 6-5.

(105) 6WDUWLQJ,QLWLDOL]LQJDQG6WRSSLQJWKHOLYH&DFKH.  SAP AG 1999. 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 the database 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 and Initialization actions.. n. liveCache initialisation usually is required after an upgrade of COM routines, if the structure of objects called by COM routines has changed from the old to the new release.. © SAP AG. BC555. 6-6.

(106) OLYH&DFKH2SHUDWLRQ0RGHV. 6+87'2:1&2/' 7 7 7 7 &2/'. 6+87'2:12))/,1(.

(107)

(108) . 7 7 7 7. . . . . . . &2/'.  SAP AG 1999. 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 this operating 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 can connect to the liveCache.. n. The command “Shutdown cold” switches the liveCache server to cold mode after all open transactions have completed. Then a checkpoint is written and all data is flushed from the caches to the 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 was performed are lost. Such a loss of data can, e.g., occur if the liveCache crashes because of hardware errors.. © SAP AG. BC555. 6-7.

(109) OLYH&DFKH,QVWDOODWLRQ. l (QWHUWKHQDPHRIWKHOLYH&DFKHLQVWDQFHWREHLQVWDOOHG. l (QWHUWKHSDWKRIWKH'%5227GLUHFWRU\7KHLQVWDOODWLRQ ZLOOFRS\WKHOLYH&DFKHVRIWZDUHWRWKLVGLUHFWRU\ l 5HERRWWKHV\VWHP5HTXLUHGHQYLURQPHQWYDULDEOHVZLOO EHVHWE\WKHLQVWDOODWLRQURXWLQH l 6WDUW/&6(783. l (QWHUWKHQDPHRIWKHOLYH&DFKHLQVWDQFHWREHLQVWDOOHG l (QWHUWKHQDPHRIWKHORFDOPDFKLQH. l &RQILJXUHSDUDPHWHUVIRUGLVNSURFHVVDQGPHPRU\  SAP AG 1999. n. liveCache can be installed with the help of file lcsetup.bat in directory livecach/<OS>/common the on Kernel CD. Installation is carried out with installation tool LCSETUP.. n. During liveCache installation, the following information has to be entered with the help of installation 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 adapts parameters DATA_CACHE and CONVERTE_CACHE.. © SAP AG. BC555. 6-8.

(110) ,QVWDOOLQJD1HZOLYH&DFKH3DWFK l *HWQHZOLYH&DFKHSDWFKIURPVDSVHUY[. l /RJRXW$32XVHUV ORDGGDWDIURPOLYH&DFKHWR$32'%IRULQLWLDOLVDWLRQ VHHXSJUDGHQRWH

(111) l 6WRSWKHOLYH&DFKHWKHQVWRSWKH$32V\VWHP l 6WRSWKH5HPRWH64/6HUYHU with command “[BVHUYHUVWRS´. l 8QLQVWDOOWKH5HPRWH64/6HUYHU with command “[BVHUYHUUHPRYH´. l %DFNXSWKHROGDQGWKHQLQVWDOOWKHQHZOLYH&DFKHVRIWZDUH &20URXWLQHV

(112) in directory DBROOT (DBROOT/sap) l 0LJUDWHOLYH&DFKHSDUDPHWHUVIRUWKHQHZNHUQHO with command “[BSDUDPXFRQWUROFRQWUROGOFQDPH!%&+(&.´ l ,QVWDOOWKHQHZ5HPRWH64/6HUYHU with command “[BVHUYHULQVWDOO´ l 6WDUWWKH5HPRWH64/6HUYHU with command “[BVHUYHUVWDUW´ l 5HVWDUWWKH6$3V\VWHP. l 5HVWDUW,QLWLDOL]H VHHXSJUDGHQRWH

(113) OLYH&DFKHZLWKWUDQVDFWLRQ/& SAP AG 1999. n. liveCache patches are usually part of an APO Support Package. You should never upgrade your liveCache version without checking the compatibility of the upgrade with the registered COM routines.. n. The upgrade note tells you whether you have to initialize or simply restart liveCache after an upgrade of the COM rotines. An initialization is only required if new COM routines expect a different 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-9.

(114) OLYH&DFKH'LDJQRVLV)LOHNQOGLDJ.  SAP AG 1999. n. The knldiag file logs messages about current liveCache activities. The actions logged include liveCache start, user logons, writing of checkpoints, and liveCache shutdown. To access the data, in the Control menu choose Diagnose ® Operating messages.. n. The knldiag file resides in “ DBROOT\wrk\<SID>\knldiag” and is recreated at liveCache start. The old copy is saved under “ knldiag.old” . A knldiag file containing a fatal error is deleted after two consecutive 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 the main APO system menu, choose: liveCache performance ® Detail Analysis ® System Messages.. © SAP AG. BC555. 6-10.

(115) OLYH&DFKH'LDJQRVLV.HUQHO7UDFH. l. 6ZLWFKRQWKHNHUQHOWUDFH'%0*8,&KHFN.HUQHO7UDFH2Q. l. 7KHQ³IOXVK´WKHNHUQHOWUDFHZLWKWKH)OXVKEXWWRQ. l l l. 5HSURGXFHWKHSUREOHP. 8VHWKHIXQFWLRQVLQWKH3URWRFROVHFWLRQRI'%0*8,WRSUHSDUH DUHDGDEOHRXWSXWRIWKHNHUQHOWUDFH 6HQGWKHRXWSXWILOHWRWKHVXSSRUWWHDP.  SAP AG 1999. n. Kernel trace is a function for analyzing liveCache kernel problems during user transactions. The output of the kernel trace is intended for the SAP development support team and is typically not able to 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 liveCache problems 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-11.

(116) 6XPPDU\OLYH&DFKH$GPLQLVWUDWLRQ. <RXDUHQRZDEOHWR. l 'HVFULEHOLYH&DFKHRSHUDWLQJPRGHV. l 'HVFULEHWKHGLIIHUHQFHEHWZHHQOLYH&DFKH LQLWLDOL]DWLRQDQGVWDUW. l 6WDWHWKHVWDUWLQJDQGVWRSSLQJSURFHGXUHVIRU OLYH&DFKH.  SAP AG 1999. © SAP AG. BC555. 6-12.

(117) ([HUFLVHV )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH 1R . ([HUFLVH. %DVLFIXQFWLRQDOLW\RI'%0*XL. ,QRUGHUWRSHUIRUPWKHIROORZLQJH[HUFLVHV\RXZLOOQHHGWRVWDUWWKH'%0*XL 3OHDVHXVHWKHLQVWUXFWLRQVRXWOLQHGLQWKHVROXWLRQVIRU8QLWRIWKLVFRXUVH 3OHDVHHQVXUH\RXXVHRQO\<285OLYH&DFKHIRUWKHIROORZLQJH[HUFLVHV. 1.1 1.2 1.3 1.4. 2.1. Register YOUR OLYHcache for use by DBMGui.. What is the operational state of your OLYHCache? Start your OLYHCache. How can you Start / Stop / Initialise the OLYHcache used by your APO system from within the APO system Do NOT do this in APO system OMO but wait until you have configured your OLYHCache <LNN> for usage with LC10 8VH'%0*XLWRSHUIRUPWKHIROORZLQJH[HUFLVHV 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. 2.6 2.7. 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. What logmode is being used by the OLYHCache?. Examine the database message file. Find the messages pertaining to the startup of your 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.. . ([WHQGOLYHFDFKHGLVNVL]HE\<RXFDQDOWHUQDWLYHO\SHUIRUPWKLVH[HUFLVH LQFKDSWHUZLWK/&. 3.1. Check the current size of the data area and ensure there is enough space on that disk to increase.. 3.2. Add another devspace to the data area in order to increase the total size of the data area by approximately 10%.. © SAP AG. BC555. 6-13.

(118) 3.3. Check whether the parameter values noted above for MAXDATAPAGES and MAXDATADEVSPACES changed. When do the modifications at the parameters become actively?. . OLYH&DFKHSURILOHSDUDPHWHUV. 4.1 . Check and adapt the value of the OLYHCache parameter “MAXUSERTASKS”?. &RPPDQG/LQHFOLHQW,QWHUIDFH. 5.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-14.

(119) 6ROXWLRQV )RUWKHH[HUFLVHVDQGVROXWLRQVSOHDVHXVHWKHQHZ H[HUFLVHVDQGVROXWLRQVLQWKHDSSHQGL[RIWKLVFRXUVH 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 is running, 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 click on 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 to exit the regsitration function. You will now see a graphic appear in the top RHS window, 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 – check user name and password.. 1.3. Select your OLYHCache by clicking on its graphic.. Use menu path “ Instance Å Restart Å Warm“ or select 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 the above-mentioned functions.. © SAP AG. BC555. 6-15.

(120) 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 “Total Space (KB)”. Method 2: Use menu path “Instance Å Configuration Å Data Devspace”, then calculate value from 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 abovementioned 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 value from 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 abovementioned Method 2 and count the number of non-empty entries with Name = “LOGnnn”. 2.5. MAXDATADEVSPACES: _________ MAXDATAPAGES: ________. 2.6 2.7. Use menu path “Instance Å Information Å Log”, then read value from field “Log Mode”.. 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 is displayed via a series of messages with label INFO in the Database Message file. The required 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 trace options and click on icon “Selected Items ON” to activate trace of all selected options. Notice the GREEN traffic light associate with each active trace element.. © SAP AG. BC555. 6-16.

No results found