Livecache Monitoring

SPC150: Managing liveCacheContributing Speakers Melanie Handreck Development Support, SAP AG Ashwath Kakhandiki Development Support, SAP Labs, LLC Jörg Hoffmeister Development Manager, SAP AG  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 2 What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability SAP TechEd ’05 / SPC150: Managing liveCache / 4 .Learning Objectives As a result of this workshop. Create a system copy (standby instance) of your liveCache instance. Contents may be changed without prior notice. DISCLAIMER This presentation reflects current planning. Activate the Alert Monitor for your liveCache instances.  SAP AG 2005. Use the liveCache performance analysis tools to determine performance bottlenecks. Schedule backups and other administrative tasks using the DBA Planning Calendar. and are in no way binding upon SAP. Use transaction LC10 to administer and monitor your liveCache instances. you will be able to: Integrate your liveCache and MaxDB instances into your monitoring landscape in transaction DB59. What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability . Which Instances Can be Monitored? OLTP System APO System KW System Application Server Application Server Application Server KPRO Database OLTP Database APO Database liveCache Content Server Cache Server  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 6 . Central Monitoring Application Server Database OLTP System Application layer APO System KW System MaxDB OLTP Database MaxDB APO Database MaxDB KPRO Database liveCache Content Server Cache Server  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 7 . Anatomy of MaxDB & liveCache Instances Application MaxDB/liveCache Instance MaxDB/liveCache Kernel One Pool of DB objects Data Volume Data Volume Data Data Volume Volume Log Log Volume Volume  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 8 . MaxDB & liveCache Monitoring Memory consumption CPU consumption Expensive SQL statements Task activities Critical Regions Caches Command Analyzer SQL Interpreter & Optimizer SQL basis (B* trees) Log Files I/O buffer cache Log queue I/O SQL data & Converter Data Volume(s) Log Volume(s)  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 9 . What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability . IBM DB/2 .Oracle . SAP TechEd ’05 / SPC150: Managing liveCache / 11 .MaxDB .… (same as WebAS) Application Server Database Server SAP liveCache  SAP AG 2005.Architecture of an SCM System GUI GUI GUI GUI Application Server Available DB-Systems: . liveCache = Enhanced MaxDB ABAP code of SAP solutions (APO / WFM / . transaction handling. . ..) Low level ABAP-functions: Object Manager (OM) liveCache liveCache Applications (LCApps) Object Managment System (OMS) Kernel SQL-Interpreter Business logic. SAP TechEd ’05 / SPC150: Managing liveCache / 12 ...)  SAP AG 2005. coded in C++ (scheduler....) MaxDB Basic DBfeatures (recovery. Objects are accessed via an OID. In the liveCache. SAP TechEd ’05 / SPC150: Managing liveCache / 13 .liveCache Data Storage SQL data (B* tree) Object data (page chains) . Data volume pages SQL data is stored on SQL pages and is sorted using the B*tree algorithms.  SAP AG 2005. which are linked to build page chains... all data is stored in data volume pages regardless of the data type (SQL data or object data). In contrast object data is stored in OMS pages. All pages which contain free space to accommodate further objects are linked additionally in a free chain.Class Container Class container Chain 1 Chain 2 Chain 3 Chain 4 first free next free The liveCache data is stored in so called class containers. The class containers can be partitioned into more than one chain to avoid bottlenecks during massive parallel insert of objects.  SAP AG 2005. These containers consist of chains of double linked pages. SAP TechEd ’05 / SPC150: Managing liveCache / 14 . Memory Areas in The liveCache Data cache OMS heap OMS data pages History pages SQL pages Parameter: CACHE_SIZE  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 15 Copied OMS objects Local LCA memory Parameter: OMS_HEAP_LIMIT . SAP TechEd ’05 / SPC150: Managing liveCache / 16 .SCM: Two Database Server System SCM Application Server Separate Hardware or Advanced Planner & Optimizer Single box with 2 databases Multiple DB platforms Multiple points of consistency Multiple DB Administration SCM DB Session SCM Database Server SQL logic liveCache Session liveCache (Database) Server SQL logic liveCache logic Database buffer Database buffer SCM Core Data liveCacheData  SAP AG 2005. liveCache OneDB SCM Application Server Separate Repositories (Schemas) Less Hardware Single DB platform: MaxDB Single point of consistency Single point of DB administration Advanced Planner & Optimizer SCM DB Session liveCache OneDB liveCache Session SCM Database optionally can be integrated into the liveCache Server SQL SQL logic logic liveCache logic logic liveCache Database buffer Database buffer SCM Core Data liveCache Data liveCacheData  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 17 . SAP TechEd ’05 / SPC150: Managing liveCache / 18 .Major Advantages of liveCache OneDB All Software from one vendor Only the Operation System is not delivered by SAP Optimized Utilization of hardware resources Less processes Incorporated cache usage for SQL and OMS data Administration of 1 instance Backup & Recovery Disk Space Utilization Lower TCO  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 19 .Major Advantages of liveCache OneDB II Single Point of Consistency Recovery Point In Time Recovery MaxDB/liveCache Backups are always Consistent on Transaction Level System copy Copy of only 1 Instance MaxDB Advantages Consistency of backups Disk structure of target system can differ from the source system Target system can be smaller than the source system  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 20 .Demo Demo  SAP AG 2005. During these exercises you have the chance to use the shown transactions and to become familiar with them.  SAP AG 2005.0).they contain screenshots of the used transactions and some additional information.Most parts of this workshop will be shown live in a liveCache OneDB system (SCM 5. You will get sufficient time after the presentation to do the exercises. SAP TechEd ’05 / SPC150: Managing liveCache / 21 . The following slides are to be used as a reference book . 20 6. The integration of any SAP DB/MaxDB and liveCache instances is possible as of the mentioned SPs.  SAP AG 2005.40 7.but liveCache instances can be monitored in any SAP system using the mentioned Basis SPs. NA: not available DB50 and DB50N work exclusively with SAP DB/MaxDB instances (as of version 7.10 6. To start/stop/initialize the liveCache this transaction should only be used in the corresponding APO/SCM system .6C 4. SAP TechEd ’05 / SPC150: Managing liveCache / 22 .Transaction Availability DB50 4. LC10 works exclusively with liveCache instances.00 GA GA GA GA GA GA DB59 / DB50N Basis SP 44 Basis SP 33 Basis SP 32 Basis SP 21 GA GA LC10 GA GA GA GA GA GA RZ20 Basis SP 44 Basis SP 33 Basis SP 32 Basis SP 21 GA GA DB13C NA NA Basis SP 28 Basis SP 18 GA NA – new: DBACOCKPIT GA: general available.6C.3). RZ20 is database independent and available as of SAP release 4. DB59 and DB13C are database independent.6D 6. What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability . To be able to monitor other MaxDB instances within this system.in case of an APO/SCM system . SAP TechEd ’05 / SPC150: Managing liveCache / 24 .e. you have to integrate the corresponding database instance .0 the connection identifier LEA is used as well. As of SCM 5.  SAP AG 2005.i. you have to enter the user information to connect to this database instance.Central Monitoring – Transaction DB59 Initially transaction DB59 contains only an entry for the system's own MaxDB instance and .the two liveCache connection identifiers LCA and LDA. Make sure that the checkbox for the central authorization is marked. which for SAP applications is SAPR3 or SAP<SID> as the default. Default: control with password control.  SAP AG 2005. that the connect information is stored in tables DBCON and DBCONUSR of the monitoring system. This is the user used to connect to the Database Manager GUI or CLI.Database Integration To be able to connect to the database instance you have to enter: the name of the database instance the hostname or IP address of the server on which the database instance runs the DBM operator and his password. SAP TechEd ’05 / SPC150: Managing liveCache / 25 . the Standard Database User. You'll get a list of all application servers. if the entered connect information works.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 26 . mark the entry of the concerning database instance and choose Connection Test. Select one and choose Connection Test to check one after another if the connection works from all application servers.Connection Test To check. If everything is OK.Connection Test The connection test first checks the DBMCLI connection. then the command and session mode of DBMRFC and afterwards the SQL connection.  SAP AG 2005. Then you have to check the log file. a green check mark appears for this application server. otherwise a red cross is shown. SAP TechEd ’05 / SPC150: Managing liveCache / 27 . X-Server not Running One possible problem is that the X-Server is not running on the database server.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 28 . The X-Server is the TCP/IP listener of MaxDB which handles remote connections to the database instance.  SAP AG 2005.Wrong DBM Operator Password The connection test also fails if the DBM Operator user and/or password has not been entered correctly. SAP TechEd ’05 / SPC150: Managing liveCache / 29 .  SAP AG 2005. In this case you can find more information in the corresponding dev_w# file. Error -4008 (Unknown user name/ password combination) indicates that the user data for the standard database user is not correct.Wrong Standard Database User Password If the DBM Operator and his password have been entered correctly. SAP TechEd ’05 / SPC150: Managing liveCache / 30 . Then the native SQL test may fail because the standard database user has not been entered correctly. the DBMCLI and DBMRFC connection work. Remote Monitoring Transaction DB59: central entry point to monitor MaxDB & liveCache instances MaxDB Monitoring DB50 Monitoring of remote instances is possible. SAP TechEd ’05 / SPC150: Managing liveCache / 31 liveCache Monitoring LC10 . Even stand-alone databases like small test databases can be monitored in the SAP system.  SAP AG 2005. What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability . A lot of tasks explained in this chapter are also available in transaction DB50 – except some liveCache specific tasks. DB50  SAP AG 2005.LC10 <-> DB50 LC10 While transaction DB50 is used to monitor MaxDB instances. transaction LC10 is used to monitor and administer liveCache instances. SAP TechEd ’05 / SPC150: Managing liveCache / 33 . Transactions DB50 and LC10 are very similar. SAP TechEd ’05 / SPC150: Managing liveCache / 34 .  SAP AG 2005.Starting Transaction LC10 After you entered the connect information for your database instance you can start the liveCache assistant. Select the newly created entry in the list of databases and choose Assistant. the database version and the operational state of the database instance. SAP TechEd ’05 / SPC150: Managing liveCache / 35 .Transaction LC10 – Properties This is the Properties section of transaction LC10.  SAP AG 2005. In the properties section you can find some general information like the database name. the database server. No user can use the database. Users can connect to the database. Only the DBM operator can connect and perform administrative tasks.Operational States There are three possible operational states of liveCache and MaxDB: OFFLINE: liveCache kernel processes and caches do not exist. SAP TechEd ’05 / SPC150: Managing liveCache / 36 . ADMIN: The liveCache kernel is active (processes are started. caches are initialized). ONLINE: The liveCache kernel is active and ready to work.  SAP AG 2005. Users cannot connect to the database. kernel).  SAP AG 2005.g. The InstallationPath contains the server software that depends on the database version (e. The IndepData directory contains the configuration data and rundirectories of liveCache/MaxDB instances.liveCache And MaxDB Directory Structure The IndepPrograms directory contains programs and libraries shared by the liveCache/MaxDB instances and applications. The rundirectory contains the status files of a liveCache/MaxDB instance. Several dependent directories can exist alongside each other. Database Software and Configuration Data /var/opt sdb data wrk config <db_name> bin pgm env etc lib incl misc sap Temporary data /opt sdb programs pgm bin 7500 The location of these directories is specified during the first installation of liveCache/MaxDB software. They exist only once on the server. SAP TechEd ’05 / SPC150: Managing liveCache / 37 . These programs are downwards compatible. contains all error messages since database installation UTLPRT .contains all (administrative) commands sent to the dbmserver LCINIT – contains information about the latest liveCache start/initialization  SAP AG 2005.contains status and error messages of the database kernel KNLDIAGERR .contains administrative commands sent to the database kernel (e. BACKUP.liveCache Status And Log files Most important log files: KNLDIAG . SAP TechEd ’05 / SPC150: Managing liveCache / 38 .g. VERIFY) including their return code(s) BACKHIST . SHUTDOWN.contains all backup and recovery actions DBMPRT . It is initialized when the database is started.current write position --.Database Messages File knldiag has a fixed size. The current write position is marked with '--. This part is overwritten cyclically. SAP TechEd ’05 / SPC150: Managing liveCache / 39 .  SAP AG 2005.' In case of problems with the database you should always check file knldiag for error messages. The last version of this file is then copied to knldiag.old. Knldiag consists of two parts: the first part contains information about the database start and is not overwritten. In the second part information is logged during the runtime of the database. All other messages are error messages . including a back trace which can be used by the developers to find the cause of the crash.  SAP AG 2005.Starting…' whenever the database has been started from state OFFLINE to state ADMIN. information about a crash. SAP TechEd ’05 / SPC150: Managing liveCache / 40 .Database Error Messages File knldiag.g.err contains message '--.e. Database Terminations If the database is not stopped correctly the most important log files are saved in the DIAGHISTORY folder during the next start of the database instance. SAP TechEd ’05 / SPC150: Managing liveCache / 41 . This ensures that they are not overwritten and can still be analyzed to determine the cause of the crash. As a default only two sets of log files are held in the diaghistory.  SAP AG 2005. These files can be seen in the Terminations section. SAP TechEd ’05 / SPC150: Managing liveCache / 42 . including the error code (if an error occurred). when a start or stop command has been executed. You can see.Database Manager Messages File dbm.  SAP AG 2005.prt contains statements sent to the dbmserver. Whenever an administrative command has been executed using Database Manager GUI or CLI this is logged in this file. for example. SAP TechEd ’05 / SPC150: Managing liveCache / 43 .prt has a fixed size. including an environment dump. There you can see the relevant environment variable settings of the user who started the X-Server. This part is not overwritten. The first part of this file contains startup information of the X-Server. The second part contains runtime information like e.Remote SQL Server Messages File xserver.g. connect errors.  SAP AG 2005. Operation Log File Each time the liveCache is started. stopped or initialized. The tab Control File displays the script LCINIT. The log file of the previous starts.LOG) is written. stopped or initialized successfully you can find a message liveCache <connection name> successfully started/stopped/initialized at the end of the log file. Whenever the liveCache is started.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 44 . a log file (LCINIT. stops or initializations is displayed in Logs -> Operating -> History.BAT which is used to start. stop and initialize the liveCache. information about executed backup and recovery actions or consistency checks. SAP TechEd ’05 / SPC150: Managing liveCache / 45 . You can display a detailed log file for each of these actions. for example. You can see.DBA History: Backup/Restore (DBMServer) The DBA History contains information about administrative tasks.  SAP AG 2005. DBA History: Backup/Restore Log File The log file of a backup contains the backup command and its return code and detailed information like: the creation date of the backup the number of pages transferred the backup label the location of the backup file  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 46 . e. The HISTLOST entries are created whenever the log volumes are initialized .each of the size of one log segment. Then you have to create a complete backup again to start a new backup history.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 47 . during the installation.DBA History: Backup/Restore (Kernel) This is the backup history from the point of view of the database kernel. Each log backup action might create several log backup files .g. consistency checks and starts/stops of the database instance including the return codes of these commands.Kernel Administration Log File File dbm. This log file is written by the database kernel itself.utl contains information about all administrative tasks sent to the database kernel. SAP TechEd ’05 / SPC150: Managing liveCache / 48 . It contains information about backups.  SAP AG 2005. the monitored data may not reflect a representative workload of a production SCM system. SAP TechEd ’05 / SPC150: Managing liveCache / 49 .Activity Overview A reliable analysis of the liveCache for a productive system is only possible if a sufficient number of LCA routines have already been executed.  SAP AG 2005. If less than about 50 000 LCA routines have been executed.  SAP AG 2005. In a running system. Vsleep – task is in kernel code of MaxDB and waiting for a free slot in its thread (UKT) LogIOWait – task waits for completion of its log request by archive log writer IOWait (R) or IOWait (W) – task waits for data I/O completion (read or write) Vbegexcl or Vsuspend – task waits to acquire an internal lock in MaxDB Vwait – task waits for an SQL lock held by another application process to be released (locks are released after a COMMIT or ROLLBACK) DComObjectCalled – task is executing code of the LCA procedure. SAP TechEd ’05 / SPC150: Managing liveCache / 50 . possible states are: Running – task is in kernel code of MaxDB and uses CPU Runnable.Task Manager The Task Manager shows the status of all currently active database tasks. To monitor failed accesses to the data cache.  SAP AG 2005. an extension of the data cache may be required. SAP TechEd ’05 / SPC150: Managing liveCache / 51 . choose Refresh. Each failed access results in a physical disk I/O and should be avoided.Cache Overview In a wellconfigured system Data cache usage should be well below 100% Data cache hit rate should be above 99% If the portion of the data cache used reaches 100%. and the hit rate is below 99%. Heap Usage Size is the memory that was allocated for heap from the operating system. It reflects the maximum heap size that was needed by the LCA routines since start of liveCache. Currently Used is the currently used heap. When additional memory is needed, liveCache uses the already allocated heap until Size is reached. It is important to monitor the maximum heap usage. When Size reaches OMS_HEAP_LIMIT (see note 337445), errors in LCA routines may occur due to insufficient memory. This should be avoided. To handle error conditions due to insufficient heap, an emergency heap will be used. The emergency heap is allocated when the liveCache is started. Detailed values are displayed for all configured sub heaps (parameter OMS_HEAP_COUNT). If this parameter is not set to 1, accumulate the heap values.  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 52 Memory Areas: Data Area The data area can consist of several data volumes. The Total Size shows the sum of the sizes of all data volumes. You can see the filling level of the data area as well as the proportion of temporary data. The data is automatically distributed to all volumes equally. You don't have to define table spaces. Empty data pages are reused by the database automatically. No reorganization is necessary.  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 53 Memory Areas: Log Area The log area can consist of several log volumes however they are used as one single log area. The Log Segment Size determines how large the log backups are created by the autosave log. Whenever Log Segment Size log pages are written, they are copied to the log backup file and the pages in the log volume can be overwritten. For test or demo systems it is possible to activate an overwrite mode for the log volumes then you don't have to take log backups before the information on the log volume can be overwritten. It is also possible to switch off the writing of log information. Both of these possibilities are not recommended for productive systems as you won't be able to restore the database to the latest state.  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 54 The ID is an internal identifier. SAP TechEd ’05 / SPC150: Managing liveCache / 55 . The name of the schema contains the client. The size information available in /SAPAPO/OM16 (in KB) is the same as the size information here (in Pages. 1 Page = 8 KB).  SAP AG 2005. Date and time specify the creation timestamp of the Schema.Schemas liveCache Schemas correspond to the SCM Planning Versions. Class GUID: external unique identifier of the class. SAP TechEd ’05 / SPC150: Managing liveCache / 56 . Container size: number of data pages which are occupied by the container. Object size: size of the stored objects in bytes. Free container pages: number of pages which contain free object frames. Class name: name of the class whose instances are stored in the container. Container use: % of usable space on the data pages which is used by occupied object frames.Class Container Class ID: unique internal number for each class container. Container Number: used by the application to identify a class container. Empty container pages: number of pages which contain no occupied object frame.  SAP AG 2005. Schema: name of the schema a class container is assigned to. Key pages: number of pages which are occupied by the index. If OMS history has nearly the same size as OMS data. use OMS Versions to find out if named consistent views (versions) are open for a long time. Maximum age should be 8 hours. Memory usage: Current heap allocation (Byte) Age: Age in hours since creation Time: Time of creation Rolled out: YES if version was swapped from local cache (heap) to global data cache due to memory shortage otherwise NO Rolled out pages: number of pages in data cache used for swapped version data  SAP AG 2005.OMS Versions The number of OMS data pages in the Data Cache should be much higher than the number of OMS history pages (a ratio of 4:1 is desirable). SAP TechEd ’05 / SPC150: Managing liveCache / 57 . Furthermore check the liveCache parameters MAX_RETENTION_TIME and MIN_RETENTION_TIME. SAP TechEd ’05 / SPC150: Managing liveCache / 58 . This may lead to an infavorable cache usage.  SAP AG 2005.Example: liveCache Versions And History Growth Long running OMS versions may prevent deletion of history pages. Remember to schedule reports /SAPAPO/OM_REORG_DAILY daily (note 139558) and /SAPAPO/DELETE_OLD_SIMSESS every 30 minutes (note 591841). use transaction SM12 on the SCM server to display locks on table /SAPAPO/OMSIMSDL.  SAP AG 2005.OMS Versions: Identify The Owner Transaction LC10 Transaction SM12 To identify the user who created an OMS version. SAP TechEd ’05 / SPC150: Managing liveCache / 59 . the runtime of the different LCA routines can be seen here. SAP TechEd ’05 / SPC150: Managing liveCache / 60 .  SAP AG 2005.g.OMS Monitor The OMS Monitor is mainly used by the support group to get information in case of performance problems. E. This is necessary that the SCM system can work properly. If the registration of the LCA routines has been successful.Database Procedures Each time the liveCache is started. or initialized the LCA routines are registered. a list of all LCA routines is available in the Database Procedures section. SAP TechEd ’05 / SPC150: Managing liveCache / 61 .  SAP AG 2005. UPDATE. SAP TechEd ’05 / SPC150: Managing liveCache / 62 . It collects statistical and monitoring data as well as system messages. For long time monitoring it should be set to 900 seconds.g. It detects and reports e.120 seconds. DELETE) For a short time analysis the interval should be set to 60 . Low cache hit rates High I/O load Low hit rates of DML commands (SELECT.Starting The Database Analyzer The database analyzer is a rule-based expert system for performance analysis.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 63 .  SAP AG 2005. In the status window you can see which configuration file is used and where the log files are stored.cfg. These rules and the source of collected data are delivered in file dbanalyzer.Database Analyzer Status Database Analyzer uses a set of sophisticated rules to classify the current state of MaxDB/liveCache by analyzing several MaxDB/liveCache parameters. The log files of each day are stored in a separate directory where you can analyze them later on. medium.02% -> rows read 66928. SAP TechEd ’05 / SPC150: Managing liveCache / 64 .Database Analyzer Output The Database Analyzer rates the information and bottlenecks: I: General information. 12 rows qualified That means that the access strategies to data in SQL tables is bad because a high number of table rows have to be read internally to find a small number of rows that meet the qualification in the WHERE clause. such as the number of executed commands W1 to W3: Bottleneck warnings with low. and high priority An example for a warning might be W3 Selects and fetches selectivity 0.  SAP AG 2005. Parameters can be changed using the Database Manager GUI or transaction LC10. The most important parameters are listed in the General Parameters section.  SAP AG 2005. All other parameters should only be changed if requested by the liveCache support. the liveCache has to be restarted using transaction LC10 that the new parameter settings take effect. Whenever a parameter has been changed.Parameter Settings You can check the current parameter settings and the change history of each parameter. SAP TechEd ’05 / SPC150: Managing liveCache / 65 . Changing Parameters liveCache parameters can be changed during online operation - but the new values take only effect after a restart of liveCache! Beside the parameter name, old and new value and a short description of the parameter are shown. The parameters in the Extended Parameters and Support Parameters sections should only be changed when requested by the liveCache support group.  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 66 Important Configuration Parameters CACHE_SIZE Size of global cache in pages (8KB) OMS_HEAP_LIMIT Maximum size of OMS cache in KB - should not be set to 0! MAXCPU Maximum number of CPUs used by liveCache MAXUSERTASKS Maximum number of connections MAXDATAVOLUMES Maximum number of volumes used by the current liveCache For the newest liveCache parameter recommendations, check SAP notes 719652 and 833216.  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 67 Volume Configuration I The Volumes section shows all configured log and data volumes including their locations and sizes. You can also see, how many data volumes could be added while the database is ONLINE. This is limited by the database parameter MAXDATAVOLUMES. New volumes can be added using the Database Manager GUI and in the Administration Section of transaction LC10.  SAP AG 2005, SAP TechEd ’05 / SPC150: Managing liveCache / 68 the location and the file type of the new volume. The new volume is immediately available after you have saved and confirmed the input values. SAP TechEd ’05 / SPC150: Managing liveCache / 69 . Log volumes can be added the same way (tab Log area).  SAP AG 2005.Volume Configuration II Data volumes can be added on the fly to prevent the liveCache from a standstill due to a database full situation. After pressing the Add Volume button in the upper left corner a new dialog window appears where you have to specify the size. It is also possible to define new backup media. liveCache supports parallel backups to several files/tapes/ pipes.Backup Media The Backup Media section provides an overview of all defined backup media. The following external backup tools can be used to create backups: Tivoli Storage Manager Networker Tools which support the interface ‚BackInt for Oracle’ The backup media can also be defined with Database Manager GUI.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 70 . Therefore a media group has to be defined which consists of several single backup media. Backups are created using this tool as well.  SAP AG 2005. stop and configure the liveCache (note 452745). Start liveCache starts the liveCache into online mode. the initialization is only available in the Menu and only users with special permissions are allowed to do this. Stop liveCache shuts the liveCache down into the offline mode. In other SCM systems you can start and stop the liveCache with transaction LC10.Operating For a liveCache OneDB system it is not allowed to start or stop the liveCache from transaction LC10 as the liveCache is always started/stopped when the SCM system is started/stopped. Only SAP users with role SAP_BC_LVC_SUPERUSER can initialize the liveCache. Users with role SAP_BC_LVC_ADMINISTRATOR can start. SAP TechEd ’05 / SPC150: Managing liveCache / 71 . To prevent the liveCache from accidentally being initialized (which would delete all data). After the restart all data committed before the last shutdown (or crash) are available again.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 72 .DBA Planning Calendar Using the DBA Planning Calendar (DBACOCKPIT) you can schedule important administrative tasks like backups or consistency checks. What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability .  SAP AG 2005. the monitoring subtree for this liveCache instance will be created automatically. SAP TechEd ’05 / SPC150: Managing liveCache / 74 .Alert Monitor – Creating The Alert Subtree When you enter the Alert Monitor for your liveCache instance the first time. Green.if the data cache is filled to 100% a red alert will be created. SAP TechEd ’05 / SPC150: Managing liveCache / 75 .  SAP AG 2005.g.Alert Monitor The Alert Monitor informs you about critical situations of your liveCache instance. yellow and red alerts determine if a situation is critical – e. If the optimizer statistics are obsolete. you can update them using the DBA planning calendar.  SAP AG 2005.Alert: No Optimizer Statistics Depending on the Alert you have to take different measures to solve the problem. SAP TechEd ’05 / SPC150: Managing liveCache / 76 . In transaction LC10 choose Tools -> DBA Planning Calendar. In this case Mark tables requiring statistics update is executed immediatly – no further parameters are required.  SAP AG 2005.Solving The Problem You can schedule different actions or execute them immediately. SAP TechEd ’05 / SPC150: Managing liveCache / 77 . Solving The Problem Afterwards action Update statistics for marked tables is executed. SAP TechEd ’05 / SPC150: Managing liveCache / 78 . Now the optimizer statistics are up-to-date.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 79 .Solving The Problem Perform a double-click on the executed action to see the job and program log of this task.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 80 . You can complete the alert now by pushing the Open Alerts button.Alert: No Optimizer Statistics After the corresponding data collector has run again.  SAP AG 2005. the Optimizer Statistics node will be green. SAP TechEd ’05 / SPC150: Managing liveCache / 81 . On the next screen press Complete Alerts again.  SAP AG 2005.Alert: No Optimizer Statistics Mark the alerts to be completed and press the Complete Alerts button in the Open Alerts view. SAP TechEd ’05 / SPC150: Managing liveCache / 82 .  SAP AG 2005.Alert: No Optimizer Statistics Now the Optimizer Statistics alert is reset. What has to be monitored? liveCache OneDB Central Monitoring – Transaction DB59 liveCache Monitoring – Transaction LC10 Alert Monitor – Transaction RZ20 High Availability . SAP TechEd ’05 / SPC150: Managing liveCache / 84 .Standby Database (w/ Log Shipping) Master Standby Data Log Log Backup Log Backup Staging Log Directory Restore Log Data Initial data backup  SAP AG 2005. back up last piece of log from master Redo all 'open' log backups (there should be none) Redo final log piece Restart slave to be the new master  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 85 .Standby Database: Slave Steps Standby Mode Initialize once with complete backup from Master Redo logs as they appear Start Slave to online mode in case of emergency If possible. Standby Database: Availability A standby database can be created for MaxDB instances liveCache OneDB instances For other liveCache instances a standby database is not supported as the consistency between the APO/SCM database and the standby database cannot be guaranteed. SAP TechEd ’05 / SPC150: Managing liveCache / 86 .  SAP AG 2005. It is possible to install the complete software package or to install just the client software.  SAP AG 2005.Standby Database: Installing Database Software I MaxDB Software can be installed using the Installation Manager (SDBSETUP). SAP TechEd ’05 / SPC150: Managing liveCache / 87 . The Custom installation allows to select single software components to be installed. which is needed on SAP Application Servers. SAP TechEd ’05 / SPC150: Managing liveCache / 88 .  SAP AG 2005. You have to choose if you would like to upgrade an existing software installation of if you would like to install the software into a new directory.Standby Database: Installing Database Software II You can choose if you would like to install new software or update existing software It is possible to install a new or upgrade an existing database instance. Standby Database: Installing Database Software III If you would like to install the software into a new directory. you have to enter this directory.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 89 . Then you'll get an overview of the selected/entered information and you can start the installation. . In the Installation Wizard. you can select a configuration template so that you have to edit only a few parameter values.Standby Database: Installing Database Instance I To install the database instance for the shadow database. choose Create.  SAP AG 2005. use DBMGUI. Next you have to specify a database name.. SAP TechEd ’05 / SPC150: Managing liveCache / 90 . To open the Installation Wizard. you have to specify the Database Manager Operator. SAP TechEd ’05 / SPC150: Managing liveCache / 91 .  SAP AG 2005. Then you have to decide how to initialize the database parameters. This is the user used to connect with the DBMGUI to the database instance.Standby Database: Installing Database Instance II After you have selected the software version for your database instance. SAP TechEd ’05 / SPC150: Managing liveCache / 92 .  SAP AG 2005. you have to specify the backup medium for that. Afterwards you get a list with the parameter values that you can adapt if necessary.Standby Database: Installing Database Instance III If you would like to get the parameter values from a backup. you can create further backup media.  SAP AG 2005. Next you have to specify if you would like to create an empty database instance or if you would like to restore the data from an existing backup. SAP TechEd ’05 / SPC150: Managing liveCache / 93 .Standby Database: Installing Database Instance IV After you checked the configuration of the data and log volumes. ).Standby Database: Installing Database Instance V Before you start the installation double-check the entered information. You have to continue with the restore of the backup in the Recovery Wizard (just press Next in the Installation Wizard..  SAP AG 2005.. When the database instance has been created succesfully it is not yet startable. SAP TechEd ’05 / SPC150: Managing liveCache / 94 .  SAP AG 2005. choose Back in the Recovery Wizard to be able to restore further backups. SAP TechEd ’05 / SPC150: Managing liveCache / 95 . After you restored the complete data backup. Make sure that the backup of your master instance is available at the specified location.Standby Database: Restoring the Initial Backup Select/create a backup medium for the Recovery. Standby Database: Restoring an Incremental Backup Depending on the available backups you can now continue with the restore of an incremental backup or with the restore of log backups.  SAP AG 2005. You have to define a new backup medium for the incremental backup. choose Back to be able to restore further log backups. SAP TechEd ’05 / SPC150: Managing liveCache / 96 . After you restored the incremental backup. However. Then you have to specify with wich log backup the restore should begin. SAP TechEd ’05 / SPC150: Managing liveCache / 97 . So specify the actually needed log backup number if you know it. It is always possible to enter the number of the first available log backup file – the database will skip all log backups which are not needed for the restore.Standby Database: Restoring Log Backups I You have to define a new backup medium for the log backups. this check increases the restore time.  SAP AG 2005. Then you have to decide if you have restored all needed data. an error is reported.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 98 . Cancel aborts the restore and stops the database instance. if you would like to continue the restore later or if you can make the needed log backup file available and continue then with the restore. Attention: Back can be used to change the media definition or to start the database.Standby Database: Restoring Log Backups II All available log backup files are restored one after another automatically. When the Database Manager tries to restore a log backup which is not available. Continue tries to restore the backup file again.  SAP AG 2005. Attention: Do not start the database instance in ONLINE mode if you would like to continue the restore. SAP TechEd ’05 / SPC150: Managing liveCache / 99 .Standby Database: Restoring Log Backups III When you would like to continue with the restore. you'll have to start with the initialization and restore of a complete backup again! To continue the restore you have to specify the last log backup file which was already restored succesfully. When the database instance was ONLINE. you have to start the database instance into ADMIN mode. SAP TechEd ’05 / SPC150: Managing liveCache / 100 . To start the database select Ignore and press Continue.Standby Database: Restoring Log Backups IV When all log backups have been restored successfully and you would like to start the standby instance. you have to choose Back.  SAP AG 2005. Then the database can be used as the productive instance and it can be administered and monitored using DBMGUI or transaction LC10.  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 101 .Standby Database: ONLINE The standby instance is in ONLINE mode now. Please remember to load the system tables (Configuration -> Upgrade System Tables). Hot Standby – Standby Within Seconds Application RECONNECT IP SWITCH Master Standby After Images Data Cluster continous continous RESTART RESTART Data Archive Log Data Storage System  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 102 . so that critical situations are reported using the SAP Alert concept. SAP TechEd ’05 / SPC150: Managing liveCache / 103 . Using this transaction you can easily switch to the liveCache/Database Assistant for each of your database instances. The DBA Planning Calendar enables you to schedule important database tasks like backups or consistency checks. Database Manager (GUI) provides all necessary functions to administer existing liveCache instances and to create new instances – e.g. standby databases. Transaction LC10 is the liveCache Assistant which allows to monitor and to administer your liveCache instances.  SAP AG 2005. In transaction RZ20 a special branch for the liveCache instances can be created. LC10 and RZ20 help you to monitor and administer all liveCache database instances in your system landscape. Transaction DB59 is the central entry point where liveCache and MaxDB instances can be integrated into the monitoring system.Summary Transactions DB59. 5 (WB550) SAP APO LiveCache Monitoring (TEWA60) Related Workshops/Lectures at SAP TechEd 2005 SPC100. 1h lecture SPC151.sdn Related SAP Education Training Opportunities http://www. MaxDB – The Professional Database.sap.sdn.Further Information Public Web: www. SAP TechEd ’05 / SPC150: Managing liveCache / 104 .com/education/ Database Administration MaxDB (ADM515) MaxDB Performance Monitoring and Optimization (UMEWE60) Workshop SAP DB Internals Version 7.sdn.sap.com/sdn/developersguide.sap.sap. Managing MaxDB.com/services/ NetWeaver Developer‘s Guide: www.com Technology MaxDB & liveCache SAP Customer Services Network: www.sap.com SAP Developer Network: www. 2h workshop  SAP AG 2005. Questions? Q&A  SAP AG 2005. SAP TechEd ’05 / SPC150: Managing liveCache / 105 . SAP TechEd ’05 / SPC150: Managing liveCache / 106 . and do not take the handouts for the following session.Feedback Please complete your session evaluation. Thank You !  SAP AG 2005. Be courteous — deposit your trash. Sweden. 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. This document contains only intended strategies. Massachusetts Institute of Technology. This limitation shall not apply in cases of intent or gross negligence. Netfinity. ICA. fitness for a particular purpose. iSeries. XML. xApp. MaxDB is a trademark of MySQL AB. or other items contained within this material. Outlook. Inc. The information in this document is proprietary to SAP. OSF/1. WinFrame. This document is provided without a warranty of any kind. The information contained herein may be changed without prior notice. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. Tivoli. developments. SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. mySAP. SAP.com. MVS/ESA. graphics. Inc. text. pSeries. World Wide Web Consortium. OS/390. and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. copied. X/Open. WebSphere. Parallel Sysplex. Oracle is a registered trademark of Oracle Corporation. indirect. SAP shall have no liability for damages of any kind including without limitation direct. Windows. National product specifications may vary. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. used under license for technology invented and implemented by Netscape. Please note that this document is subject to change and may be changed by SAP at any time without notice. mySAP. links. Intelligent Miner. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. AS/400. R/3. AFP. and Motif are registered trademarks of the Open Group. either express or implied. S/390. or non-infringement. and PowerPoint are registered trademarks of Microsoft Corporation. or consequential damages that may result from the use of these materials. SAP assumes no responsibility for errors or omissions in this document. All other product and service names mentioned are the trademarks of their respective companies. HTML. VideoFrame. Citrix. Java is a registered trademark of Sun Microsystems. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. DB2. Inc. OS/2. product strategy. SAP TechEd ’05 / SPC150: Managing liveCache / 107 . No part of this document may be reproduced. UNIX.  SAP AG 2005. MetaFrame. XHTML and W3C are trademarks or registered trademarks of W3C®. DB2 Universal Database. special. Microsoft. and MultiWin are trademarks or registered trademarks of Citrix Systems.Copyright 2005 SAP AG.. AIX. and/or development. Data contained in this document serves informational purposes only. The statutory liability for personal injury and defective products is not affected. IBM. zSeries. JavaScript is a registered trademark of Sun Microsystems. including but not limited to the implied warranties of merchantability. xApps. z/OS. OS/400. SAP does not warrant the accuracy or completeness of the information. xSeries. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Program Neighborhood.