SAP liveCache Transactions
This page provides information about SAP liveCache/SCM transactions.
LC10
/SAPAPO/OM01
/SAPAPO/OM02
/SAPAPO/OM04
/SAPAPO/OM11
/SAPAPO/OM13
/SAPAPO/OM16
/SAPAPO/OM17
/SAPAPO/OM19
/SAPAPO/OM01
/SAPAPO/OM02
/SAPAPO/OM04
/SAPAPO/OM11
/SAPAPO/OM13
/SAPAPO/OM16
/SAPAPO/OM17
/SAPAPO/OM19
LC10
liveCache assistent (transaction LC10) is the central tool to administrate and monitor the SAP liveCache (liveCache (SAP liveCache Technology), liveCache Assistant).
The permission concept for the usage of LC10 is described in note 452745.
If you have a problem with LC10, please check note 415376.
If you have problems with starting or stopping liveCache in batch, please check note 821200.
If you have a problem with LC10, please check note 415376.
If you have problems with starting or stopping liveCache in batch, please check note 821200.
Where transaction LC10 gets the information from, which is displayed in menu DBA History, is described here.
The system tables evaluated in some other LC10 applications (like e.g. OMS Monitor and Heap Usage) are explained here.
The system tables evaluated in some other LC10 applications (like e.g. OMS Monitor and Heap Usage) are explained here.
/SAPAPO/OM01
Using transaction /SAPAPO/OM01 you can view the LCA trace.
/SAPAPO/OM02
Using transaction /SAPAPO/OM02 the LCA trace can be activated.
/SAPAPO/OM04
Transaction /SAPAPO/OM04 shows information about the used LCA build. However, more information is displayed in transaction /SAPAPO/OM13.
Example:
Modulname Release Patch Build-Info Opsys Changelist libCOMBase 3.0-b040 001 APO 3.0A: 040-001-305-306 AIX RS6000 305306 libSAPAPO 3.0-b040 001 APO 3.0A: 040-001-305-306 AIX RS6000 305306 libSAPATP 3.0-b040 001 APO 3.0A: 040-001-305-306 AIX RS6000 305306 libSAPTS 3.0-b040 001 APO 3.0A: 040-001-305-306 AIX RS6000 305306 libSAPRPM 3.0-b040 001 APO 3.0A: 040-001-305-306 AIX RS6000 305306
/SAPAPO/OM11
Transaction /SAPAPO/OM11 is the "logging log". Here you can see e.g.
- if transaction /SAPAPO/OM17 was used to perform a consistency check,
- if the liveCache has been initialized,
- if report /SAPAPO/OM_DELETE_OLD_SIMSESS is scheduled,
- if report /SAPAPO/OM_REORG_DAILY is scheduled.
/SAPAPO/OM13
Using transaction /SAPAPO/OM13 you
- get an overview of the versions of the used components (e.g. SCM SP, DBSL, precompiler),
- can check the network,
- get an overview of the liveCache state (e.g. display of knldiag, display of cache information).
Prerequisite of the network check is the installation of tool NIPING on the liveCache server. Detail information about this can be found in notes 458221 and 500235.
As of SCM 4.1 also the different system times are displayed. This is helpful when liveCache, LCA routines and the application server work with different times and you need to analyze data from different traces.
As of SCM 4.1 also the different system times are displayed. This is helpful when liveCache, LCA routines and the application server work with different times and you need to analyze data from different traces.
/SAPAPO/OM16
Transaction /SAPAPO/OM16 is the liveCache data browser. Using this transaction you can view e.g. the size of planning versions. Only the current client is considered. The planning version specified as current planning version needs to fit into the data cache.
Using the following SQL statement you can get the size (in pages) of all planning versions:
select sum (pagecount) from classcontainers group by schema order by 2 desc
Using the following SQL statement you can get the size (in pages) of all planning versions:
select sum (pagecount) from classcontainers group by schema order by 2 desc
As of SCM 4.1 transaction /SAPAPO/OM19 is available which will replace transaction /SAPAPO/OM16.
/SAPAPO/OM17
Using transaction /SAPAPO/OM17 you can check and establish the consistency between liveCache and SCM system.
/SAPAPO/OM19
Transaction /SAPAPO/OM19 is the liveCache data browser. This transaction is available as of SCM 4.1.
No comments:
Post a Comment