Live cache Consistency

Hi Folks,
Seeks your help urgently.. I am executing the transaction code /n/sapapo/om17 with object type as product location combination to check the LIve Cache consistency.
But its getting stuck in the sense when it comes to Pegging Id check.. It keeps on looping at the pegging Id check and hence it doesnt proceed further and gives a time out error..Rest all of the things are fine
it would really be appreciated and would be rewarded with points if any body can provide a clue or lead to this issue.
Any OSS notes pertaining to the issue would also be appreciated....
Thanking you in anticipation..
With Regards
Sundaran Nair....

Sundaran,
Pegging area checks can be very lengthy. In this case, execute them in background, where in most systems there are no timeout limitations enforced.
Best Regards,
DB49

Similar Messages

LIve Cache Consistency Check Program

Hi All,
Is it possible to stop Live cache consistency check program /SAPAPO/TS_LCM_CONS_CHECK when it is running.
Thanks.
Bala
Message was edited by: Bala Subramainam

Hi Uma,
Actually the job finished quite fast and was unable to check this. Would probably check this in DEV and reply back to you. Thanks for your reply.
Have assigned points for you.
Regards
Bala

What is the significance of Live Cache in demand planning ?

Hi all,
Can anyone explain me significance of live cache in the demand planning. What are the issues will turn up for live cache if it is not properly maintained?
Thanks
Pooja

Hi Pooja,
SAP has come up with Live cache concept for storage and most important, quick and efficient processing of transactional data. Its a layer between data base and GUI and even the search methods and storage space has been optimized due to its structure. In DP it is used for storage of time series data whereas in SNP it can store both time series and order series data.
Regarding your second query, it is recommended to have Live cache consistency on a periodic basis for synchrinising data between LC and database tables. You can face many issues due to LC inconsistency as incorrect time series generation, Transactional data discrepancy, COM routine errors during background processing etc.
Let me know if it helps
Regards
Gaurav

Live Cache error with message number /SAPAPO/OM028

Hi Experts,
When I run RLCDEL program for deletion of obsolete SNP orders in the back ground , system shows livecache error alert with message number /SAPAPO/OM028 in the deletion job log. The details of message is "invalid order" or ABAP programming error. Live cache consistency checks are not resolving issue. Product release is 5.1 with SP08. Please suggest a resolution
Regards,
Raghav

Hi Raghav,
The sap notes 642503 & 973244 will fix your issue but they are for
versions 4.0 and 5.0 respectively.
You can write to SAP by creating a OSS message to update these
two message for version 5.1
This will resolve your issue
Please confirm
Regards
R. Senthil Mareeswaran.

Unable to delete Order does not exist in live cache but in table POSMAPN

Hi Experts,
We are facing an issue where purchase order is not available in live cache (which means no GUID) but exists in database table POSMAPN. We have tried to delete it using standard SAP inconsistent order deletion program and also using BAPI BAPI_POSRVAPS_DELMULTI but not able to delete it.
Can anybody suggest a method by which we can get rid of this order from the system.
Thanks a lot.
Best Regards,
Chandan

Hi Chandan,
Apologize me for taking your question in a wrong perspective. If you want to delete the same then you need to Re-CIF the order from ECC so that it would come and sit in Live Cache. Once done, try using the BAPI.
If you are not successful with the above approach try running the consistency report /SAPAPO/SDRQCR21 in APO system
so that it first corrects the inconsistency between ECC and APO (Live Cache + DB tables) and then use the BAPI to delete the PO.
Not sure if you have tried this way. If this does not solve your purpose you need to check SAP Notes.
Thanks,
Babu Kilari

Live cache Recovery.....

Hello all,
This is related to SAP DB version 7.4.3.32 and it is running on Windows. My DBM GUI version is 7.6.00.12. On the recovery tab of the DBM GUI there is a option called "Recovery with Initialization". I have used this option to recover my SAP DB database and it was always successful. I used this option to intialize the existing database with a good full backup. This is a new option in 7.6.00.12 DBM GUI. It was not there in 7.4.3.30 DBM GUI. Though it is not a good option all the time but it is very good if your database is crashed and if you have latest good full backup then you can use this option for recovery.
My question is that I have never tried this option (Recovery with Initialization) on our Live Cache database (SAP DB instance installed as Live Cache on Solaris). I do see this new option in DBM GUI in 7.6.00.12 DBM GUI as DBM GUI is same for both type of database.
Is it possible to use this option for our SCM 4.0 Live Cache in same way I have used it for SAP DB database. It will be a very good option for Live Cache if we have one good backup and Live Cache is crached then we can use the latest full backup to restore the Live cache.
Please let me knwo if anybody knwos about it or have tried it.
I will really appreciate your help.
Thank you.
Sume

Hi,
with liveCache it's a little bit different as opposed to an OLTP instance. The most imporant difference being that when you're using liveCache, there's always another DB instance aswell, the SCM/APO instance. The consistency between these two instances is of the utmost importance. Therefor, after every recovery of liveCache, you should run certain consistency reports to make sure the data in liveCache and SCM DB are consistent.
A normal liveCache recovery would look like this:
- you've got a (successfully saved) full data backup
- you've got several log backups
Using the above backups, you can minimize the loss of important data when experiencing crashes.
In your first case, you would recover using the last full data backup and could then continue to recover all available logbackups (either manually or automatically created).
> You could do a recovery without initialization here aswell, because all changes should still be on the logvolumes.
In the second case, you would just recover + init the data backup from Jan 1st.
In BOTH cases, you should run the consistency reports afterwards!
Regards,
Roland

Live cache upgrade on Windows 2003, IA64 clustered environment

Hi,
We are currently upgrading the Live Cache from 7.6.03,    BUILD 008-123-159-187 to 7.7.03   BUILD 023-123-174-368.
Note # 508979 is being referred to. The upgrade has completed successfuly on one Node A but is interruopted on Node B. The error log is as follows
INSTALLER_INFO: Version = 7.7.03 Build 023-123-174-368
INSTALLER_INFO: Changelist = 174368
INSTALLER_INFO: MakeId = 285415
INSTALLER_INFO: Type = kit
SYS_INFO: Host name = FMSAP457
SYS_INFO: System = Windows
SYS_INFO: Architecture = IA64
SYS_INFO: Version = NT 5.2
SYS_INFO: Subversion = Service Pack 2
CALL: SDBUPD -INSTANCE -profile APO LiveCache
STDOUT:
     SAP liveCache INSTANCE UPDATE
STDOUT:      *****************************
STDOUT: starting installation We, Oct 08, 2008 at 01:26:46
STDOUT: operating system: Windows IA64 NT 5.2 Service Pack 2
STDOUT: callers working directory: Z:/SCM_51upgradeCD/SCM5.1_SPS6/lca600011_livecache-win-64bit-i386-7_7_03_23
STDOUT: installer directory: Z:/SCM_51upgradeCD/SCM5.1_SPS6/lca600011_livecache-win-64bit-i386-7_7_03_23
MSG: InstallRegistry: space check ok: 16843616 kb on W: (17719292 kb total) available
MSG: install registry successfully locked
MSG: read 16 PACKAGES
MSG: net registry size = 133192 bytes
WRN: InstallRegistry::reserveSpace(): file >= 1024 kb
STDOUT: archive directory: Z:/SCM_51upgradeCD/SCM5.1_SPS6/lca600011_livecache-win-64bit-i386-7_7_03_23
STDOUT:
MSG: debug package SDBBAS.SDB is valid
MSG: debug package SDBKRN.SDB is valid
MSG: debug package SDBUTL.SDB is valid
MSG: no installation data to migrate
STDOUT: beginning to check sap db instances
STDOUT: existing instance:
STDOUT: 0: LCA   "O:/sapdb/LCA/db" 7.6.3.8
STDOUT: 1: none
STDOUT: please enter instance id:
STDIN: 0
STDOUT: please enter database manager operators name:
STDIN: control
STDOUT: please enter database manager operators password: STDOUT:
STDIN:
STDOUT: resume broken instance check
x_server is running
got following x_server data:
version = W64/INTEL 7.6.3    Build 008-123-159-187
dbmsrv uses db_online
dbmsrv uses db_admin
STDOUT: finding instance type...
instance type is LVC
getting catalog encoding...
catalog encoding is UNICODE
STDOUT: finding starting release...
kernel executable is O:\sapdb\LCA\db/pgm/kernel.exe
kernel version by GetBuildString 7.6.3    Build 008-123-159-187
starting release is 7.6.3    Build 008-123-159-187
STDOUT: finding apo starting release...
sapapo lib is O:\sapdb\LCA\db/sap/sapapo.dll
apo version by GetBuildInfo 5.0.0.13
apo starting release is 5.0.0.13
STDOUT: finding migration strategy...
migration is using external livecache consistency
from LVC 7.6.3    Build 008-123-159-187
and APO 5.0.0.13
to   LVC 7.7.03
and APO 6.0.0.011
STDOUT: looking for running instances...
no instances found
db_enum
OK
MSG: writing 16 packages
MSG: net install registry size = 133192 bytes
MSG: wrote install registry (156751 bytes)
STDERR: MaxDB instance "LCA" not ready to update
STDERR: looking for running instances...
no instances found
db_enum
OK
STDERR: SAP liveCache instance update exited abnormally at We, Oct 08, 2008 at 01:28:48
MSG: install registry successfully unlocked
Regards
Abraham

As a SAP customer: please open a support message for this!
regards,
Lars

Database ID is showing different host name in live cache backup

Hello All ,
While triggering the live cache backup , the database id is showing different one.
i have build the system using cloning method from production. the server name is showing correct one but database id still showing the source system.
Please help me to fix the issue . Thanks in advance .
Backlog is pasted below.
>backup_start LCD_DB_Backup
OK
Returncode              0
Date                    20140804
Time                    00081900
Server                  *********(showing correct hostname)
Database                LCD
Kernel Version          Kernel    7.9.08   Build 008-123-247-140
Pages Transferred       913824
Pages Left              0
Volumes                 1
Medianame               TH_LCD_DB_Backup
Location                /sapdb/LCD/backup/LCD_DB_Backup
Errortext
Label                   DAT_000000820
Is Consistent           true
First LOG Page          4981
Last LOG Page
DB Stamp 1 Date         20140804
DB Stamp 1 Time         00081900
DB Stamp 2 Date
DB Stamp 2 Time
Page Count              913803
Devices Used            1
Database ID             xxxxxx:LCD_20140803_103951 ( wrong database ID: xxxxx)
Max Used Data Page      0
Converter Page Count    991
Regards,

Hello,
I recommend you to create the SAP message to BC-DB-LVC component and get SAP support.
- How have you build the system using cloning method from production?
- What note/documens did you follow?
Regards, Natalia Khlopina

What are the possible live cache issues turn up for demand planning?

HI all,
Can anyone tell me the issues that may arise iin live cache and how to ensure the performance and maintenace of live cache that a planning area is utilizing it.
if the utilization is high how to bring it down!!
Can anyone pls guide me on this!!!
Thanks
Pooja

Hi Pooja,
1) Accumulation of logs created during demand planning jobs will have an impact on performance
and affect livecache and hence to be cleared periodically
2) Livecache consistency check to be performance at planned intervals
which will reduce livecache issues
3) Through om13 transaction, you can analyse the livecache and LCA objects
and act accordingly
4) You can also carry out /SAPAPO/PSTRUCONS - Consistency Check for Planning Object
Structure and /SAPAPO/TSCONS - Consistency Check for Time Series Network related to
demand planning to avoid livecache issues later
Regards
R. Senthil Mareeswaran.

Approach when the used Live cache data area crosses the threshold

Hi,
Could any of you please let me know the detailed approach when the used Live cache data area crosses the threshold in APO system?
The approach I have as of now is :
1) When it is identified that data cache usage is nearly 100%, check for hit rate for OMS data in data cache in LC10 .Because generally hit rate for OMS data in data cache should be atleaset 99.8% and Data Cache usage should be well below 100%.
2) To monitor unsuccessful accesses to data cache choose refresh and compare value now and before unsuccessful accesses result in physical disk I/O and should generally be avoided.
3) The number of OMS data pages (OMS Data) should be much higher than the number of OMS history pages (History/Undo).A ratio of 4:1 is desirable. If OMS history has nearly the same size as OMS data, use Problem AnalysisPerformanceOMS versions to find out if named consistent views (Versions) are open for a long time. Maximum age should be 8hrs.
4)If consumption of OMS heap and data cache is large, one reason may be a long running transaction simulation that accumulates heap memory and prevents the garbage collector from releasing old object images.
5) To display existing transactional simulations in LC10,use Problem AnalysisPerformanceOMS versions and SM04 to find out user of corresponding transaction and may be required to cancel the session after contacting user if the version open for long time..
Please help me by providing additional information on the issue.
Thanks,
Varada Reddy.

Hi Mayank, sorry, one basic question - are you using some selection criteria during extraction? If yes, then try extraction without the selection criteria.
If you maintain selection based on, let's say, material, you need to use the right number of zeros as prefix (based on how you have defined the characteristic for material) otherwise no records would be selected.
Is this relevant in your case?
One more option is to try to repair teh datasource. In the planning area, go to extraction tools, select the datasource, and then choose the option of repair datasource.
If you need more info, pls let me know.
- Pawan

Live Cache activation

Hi,
In my PC..every time i am manually activating Live Cache in LC10.is it possible for automatic actvation during server restart. where i have to make settings for automatic live cache activation.
Regards
Arasu

Hi Arasu,
Automatic activation, let me explore it and check any such
option is there or not like.
Some of the few consequences of automatic activation will be
1) Dependency of jobs start/end during livecache activation
2) Clearance of inbound/outbound queues
3) User lock/unlock
4) Livecache consistency check
All these needs to be taken care during restart of livecache.
Hence manual is always be preferred.
Please confirm whether your query is resolved.
Regards
R. Senthil Mareeswaran.

Transcation code to monitor the live cache usage

Hi, I wanted to know the transcation to check the live cache & optimser usage ??
Regards,
Bhavesh

Hi Bhavesh,
The following are the transaction codes as required by you.
1) LC10 - Livecache Monitoring
2) /SAPAPO/OM03 - liveCache Test Program: Start liveCache Check
3) /SAPAPO/OM04 - LCA Version
4) /SAPAPO/OM11 - Livecache Log
5) /SAPAPO/OM12 - Delete Livecache Log
6) /SAPAPO/OM13 - Analyze liveCache and LCA Objects
7) /SAPAPO/OM17 - liveCache Consistency Check
8) /SAPAPO/OPT_STOP - Terminate Optimization Runs
9) /SAPAPO/OPT12 - Optimisation Process Overview
10)/SAPAPO/OPT03 - Optimisation User Overview
11)/SAPAPO/OPT11 - Optimisation Log Display
Hope the above information is useful for you. Please confirm
Regards
R. Senthil Mareeswaran.

Detailed approach when the used Live cache data area crosses the threshold

Hi,
Could any of you please let me know the detailed approach when the used Live cache data area crosses the threshold in APO system?
The approach I have as of now is :
1) When it is identified that data cache usage is nearly 100%, check for hit rate for OMS data in data cache in LC10 .Because generally hit rate for OMS data in data cache should be atleaset 99.8% and Data Cache usage should be well below 100%.
2) To monitor unsuccessful accesses to data cache choose refresh and compare value now and before unsuccessful accesses result in physical disk I/O and should generally be avoided.
3) The number of OMS data pages (OMS Data) should be much higher than the number of OMS history pages (History/Undo).A ratio of 4:1 is desirable. If OMS history has nearly the same size as OMS data, use Problem AnalysisPerformanceOMS versions to find out if named consistent views (Versions) are open for a long time. Maximum age should be 8hrs.
4)If consumption of OMS heap and data cache is large, one reason may be a long running transaction simulation that accumulates heap memory and prevents the garbage collector from releasing old object images.
5) To display existing transactional simulations in LC10,use Problem AnalysisPerformanceOMS versions and SM04 to find out user of corresponding transaction and may be required to cancel the session after contacting user if the version open for long time..
Please help me by providing additional information on the issue.
Thanks,
Varada Reddy.

Hi Mayank, sorry, one basic question - are you using some selection criteria during extraction? If yes, then try extraction without the selection criteria.
If you maintain selection based on, let's say, material, you need to use the right number of zeros as prefix (based on how you have defined the characteristic for material) otherwise no records would be selected.
Is this relevant in your case?
One more option is to try to repair teh datasource. In the planning area, go to extraction tools, select the datasource, and then choose the option of repair datasource.
If you need more info, pls let me know.
- Pawan

Error during Live Cache Server Installation on SCM 4.1 system

Hi All,
I have an SCM 4.1 ABAP system running on MSSQL2005 and Win2003 server.I would like to install Live Cache Server on the same Server.Livecache client was installed as part of SCM 4.1 installation.
I have installed MAXDB software and now when im trying to install Live Cache Server Instance i get the below error
Im performing the installation with user root and it is an Administrator.
WARNING 2011-12-09 11:01:25
Execution of the command "change 'user' '/install'" finished with return code 1. Output: Install mode does not apply to a Terminal server configured for remote administration.
Installation start: Friday, 09 December 2011, 11:01:23; installation directory: G:\SCM_4.1_Media\Media_Live_Cache\New_Media\51031447_2\CD_SAP_SCM_4.1_liveCache_64bit\SAPINST\NT\AMD64; product to be installed: SAP SCM 4.1> Additional Services> Install a liveCache Server instance
Transaction begin ********************************************************
WARNING 2011-12-09 11:02:33
Error 3 (The system cannot find the path specified.
) in execution of a 'CreateProcess' function, line (265), with parameter (G:\SCM_4.1_Media\Media_Live_Cache\New_Media\51031447_2\CD_SAP_SCM_4.1_liveCache_64bit\NT\AMD64\SDBUPD.EXE -l).
Transaction end **********************************************************
WARNING 2011-12-09 11:02:34
The step Fill_sapdb_db_instance_context with step key LIVECACHESERVER|ind|ind|ind|ind|ind|0|LC_SERVER_INSTALL|ind|ind|ind|ind|ind|0|Fill_sapdb_db_instance_context was executed with status ERROR.
Has anyone seen this error before ? Any pointers would be helpful.
Regards,
Ershad Ahmed.

Subprocess starts at 20111209154957
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX db_enum
Execute Session Command : exit
> Subprocess stops at 20111209154957
OK
> Subprocess starts at 20111209155027
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX db_enum
Execute Session Command : exit
> Subprocess stops at 20111209155027
OK
> Subprocess starts at 20111209155221
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX db_enum
Execute Session Command : exit
> Subprocess stops at 20111209155221
OK
> Subprocess starts at 20111209155323
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX inst_enum
Execute Session Command : exit
> Subprocess stops at 20111209155324
OK
7.5.00.31    f:\sapdb\liv\db
7.6.06.10    f\sapdb\sdb\7606
7.6.06.10    C:\Program Files\sdb\7606
> Subprocess starts at 20111209155324
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX inst_enum
Execute Session Command : exit
> Subprocess stops at 20111209155324
OK
7.5.00.31    f:\sapdb\liv\db
7.6.06.10    f\sapdb\sdb\7606
7.6.06.10    C:\Program Files\sdb\7606
> Subprocess starts at 20111209161349
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX inst_enum
Execute Session Command : exit
> Subprocess stops at 20111209161349
OK
7.5.00.31    f:\sapdb\liv\db
7.6.06.10    f\sapdb\sdb\7606
7.6.06.10    C:\Program Files\sdb\7606
Regards,
Ershad Ahmed.

Live Cache Failed (DBM error)

Hi,
I am getting following error while starting live cache(LC10)
"Error DBMCLI_COMMAND_EXECUTE_ERROR when starting liveCache LC1 on server system"
Server: system
Users: SAPUSER
Logical Command: DBMRFC
Parameter: exec_lcinit restart
Name and Server     : LC1 - system
DBMRFC Function     : DBM_EXECUTE
Command             : exec_lcinit restart
Error               : DBM Error
Return Code         :     -24964
Error Message       : ERR_EXECUTE: error in program execution#
0,sap\lcinit LC1 restart -uDBM , -uDBA , -uSQL ,
liveCache LC1 (restart)
The liveCache state is OFFLINE
DBMServer 7.6.00   Build 029-123-130-265
starting LC1 into ONLINE
ERROR : restart not possible [please check knldiag!!]
ERROR : liveCache LC1 not started (see "d:\sapdb\data\wrk\LC1\lcinit.log")
In Transaction DB59 i tried connection test "Connect. test with "native SQL" ( LCA ) unsuccesful"
how to restart Live Cache again? what will be the problem?
regards
Thennarasu

Hello,
what's wrong with the hint you already got?
> ERROR : restart not possible [please check knldiag!!]
Check the knldiag and then we might be able to do something about this issue.
regards,
Lars

Live cache Consistency

Similar Messages

Maybe you are looking for