Live cache restore issue

Hi All,
We are facing the below error while restore the LC MAXDB database.
Source version : 7.9.08.10
Target Version : 7.9.07.09
dbmcli on SU4>db_state
OK
State
OFFLINE
dbmcli on SU4>db_start
OK
dbmcli on SU4>db_state
OK
State
ADMIN
dbmcli on SU4>db_online
ERR
-24988,ERR_SQL: SQL error
-9407,System error: unexpected error
3,Database state: OFFLINE
Internal errorcode, Error code 6433 "system_error"
20017,RestartFilesystem failed with 'System error: unexpected error'
13,Could not execute migration, because migration check failed
20000,Assertion of state The software version is too old failed!
The persistent version is: Version = 7.9.8.10
dbmcli on SU4>version
OK
version,os,dbroot,logon,code,swap
"7.9.07","UNIX","/sapdb/SU4/db",True,ASCII,1
Please advice.
Regards,
Yuvaraj M B

Hello Yuvaraj M B,
first, update the target database to the vestion of the source database kernel including the LCAPPS.
Then run the copy procedure using backup/restore.
See note 457425.
Pay attention to Reason and Prerequisites section:
"4. The same liveCache version is installed on the target host and the source host."
Regards, Natalia Khlopina

Similar Messages

Live cache install issue

hello expert,
I want to install a live cache server on a separate host, but failed more times, and got a same error messge every time as below,
Some database applications are probably still running.Check the log file sdbinst.log.
and the sdbinst.log file information :
starting preparing phase of package Base 7.6.00.29 64 bit
file C:/Windows/SysWOW64/drivers/etc/services not found
installation exited abnormally at Tu, Dec 29, 2009 at 09:23:36
I install live cache server on windows 2008 64bit.
how to slove this issue? can someone help me out? thanks in advance.

Sloved.

LIve cache restore error

Hi,
Iam restoring LC backup from Production to QA system from dbmgui. during backup restore initial phase 0KB of 0 pages transferred iam getting error "-24988 SQL error[db_activate....]; -902,I/O error". Restore did not satrted.
When i went to /sapdb/data/wrk the file xserver_server.prt
it shows the error 26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.194.194.67.'
26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.216.51.138.'
2010-09-30 16:07:20 26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.216.51.138.'
2010-09-30 16:15:13 26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.216.51.138.'
2010-09-30 20:19:54 24095 ERR 11926 XSERVER Receive packet, Ref:9 - socket recv error (238:Connection timed out
2010-09-30 20:48:57 26049 ERR 11926 XSERVER Receive packet, Ref:9 - socket recv error (238:Connection timed out
2010-09-30 23:00:58 26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.194.194.67.'
2010-09-30 23:00:59 26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.194.194.67.'
2010-09-30 23:01:20 26003 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.194.194.67.'
I tried many options but no luck.If you have faced this issue then let me know.
- Shaik

Hello Shaik,
-> What are the versions of the liveCache instance of the PROD and QA systems?
-> What are the OS of the target and source liveCache servers?
-> What is the version of the DBMGUI?
-> u201Cgetting error "-24988 SQL errorhttp://db_activate....; -902,I/O error"
Please check/post the errors in dbm.prt and knldiag < or KnlMsg > messages after dbm command db_activate run.
Please post the medium definition you used for restore.
In general about u201C-902: I/O erroru201D database error see the explanation and User Response in the MAXDB library at
http://maxdb.sap.com/doc/7_7/49/2cd234d67148808c054633343e4c20/content.htm
Thank you and best 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.

SCM5.0 Live Cache issue

Hello,
I am a newer from SCM5.0. I have 2 questions regarding live cache for SCM5.0.
1) if I want to run SNP or PP/DS, the live cache is necessary. that means, we MUST install live cache for APO planning run.
2) From now on, no 32 bit live cache version for SCM5.0. I can just install 64 bit live cache version for SCM5.0. right?
Could anyone give me some comments on the 2 issue? thanks in advance.
Best Regards,
Karl

Hi Karl,
1. In APO whatever runs you take there should be liveCache. The data will be refreshed from database to livecache and is accessed.
In APO data is stored either order series or time series.
2. Yes you have to install 64 bit.
Regards,
Kishore Reddy.

Live Cache Crashed

Hello Guru's,
My Production system Live cache has been crashed. I am trying to restore the last backup which was taken yesterday night 8:00pm. I am able to restore the Live Cache however unable to restore the logs to recover PIT, as it is complaining about log sequence. I am not sure about finding the sequence number it is asking for.
Crash happened today morning 7:00am. Backup restored last night 8pm and trying to do point in time recovery. Backup has been restored and trying to apply logs.
Note;- log backup is for every 2 hours, so after the complete backup last night, we have log backup's for every 2 hours and trying to apply the same.
Kindly suggest what can be done..
Thanks,
Sravanthi.

Hello,
1.
You have questions how to solve the liveCache issues on the PROD system
=>
As already recommended Lars, please open the SAP message to the component BC-DB-LVC to get SAP support.
It will be helpful to know the SCM/APO version, liveCache version and more details about the liveCache crash.
2.
In case you had the liveCache crash due the hardware problems, and the data or log volumes or liveCache configuration files are corrupted
=>
solve the hardware issues first or use another server
Follow the SAP note to create the liveCache instance:
    457425     Homogenous liveCache copy using backup/restore
   You need to create/initialize the liveCache instance for restore or run the Restore with initialization, restore the successful databackup, then leave the liveCache in admin status and continue the restore of the incremental databackup/logbackups in sequence if needed.
*More information could be found in the SAP notes:
1377148     FAQ: SAP MaxDB backup/recovery
869267                     FAQ: SAP MaxDB LOG area
820824          FAQ: SAP MaxDB/liveCache technology
Thank you and best regards, Natalia Khlopina

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

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

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

Unable to login to Live Cache

Hi,
I've just completed an SCM 2007 Installation alongwith the live cache.
However, when I try to login to the LC using the dbmcli command (user control/superdba & the pwds. set during installation), it gives the foll. error:
-24950,ERR_USRFAIL: User Authorization failed.
Also, I'm not able to use LC10-->Live Cache Monitoring
Pls help, since it's extremely urgent.
Thanks a lot,
Saba.

Hello Saba,
-> For SAP liveCache documentation in English see the SAP note 767598.
-> In general, the error could be due the wrong password of the dbm user.
 For example, I created the database instance NLK with the control user and
 control password. If I will try to connect to the database with wrong password
 I will get this error ::
 dbmcli -d NLK -u control,test
 Error! Connection failed to node (local) for database NLK:
 -24950,ERR_USRFAIL: User authorization failed
-> You are running SCM 2007 < SCM 5.1 > system, therefore you are SAP customer.
 Please create the SAP ticket concerning this issue => we could logon via OSS and check the status of your system.
 Please set 'high' priority of the ticket, if it's extremely urgent.
 If it's the DEMO or PROD system you could escalate the message to 'VH'.
Thank you and best regards, Natalia Khlopina

Some concern about Live cache Homogeneous System copy

Hi All,
I need to do the Homogeneous system copy SCM 5.0 / Live cache 7.6.00 on AIX. Following are the Source and target System SID for Live cache. Moreover I had check the respective SAP note 457425 and 877203 but still having some concern.
Source System
Live cache SID           =      SCD
Live cache user ID      =      SAPSCD
Live Database instant software owner = scdadm
Live cache Data Size      = 8 GB ( 4 Data volume / 2 GB each / auto extend off)
Target System
Live cache SID           =      SCT
Live cache user ID      =      SAPSCT
Live Database instant software owner = sctadm
Live cache Data Size      = 4 GB ( 2 Data volume / 2 GB each / auto extend off)
For same I having following concern.
1.     Since there is difference between source system and target system size / data volume number what action I need to take on target system. Do I need to add two more data volume into the target system?
2.     After complication of database restore on target the system do I need to change the Live cache user ID (i.e. SAPSCD to SAPSCT)?
or
It is just fine to change the log on data in Integration tab in LC10.
Please let me know some more information on same.
Thanks,
Harshal

Hello Harshal,
"1. Since there is difference between source system and target system size / data volume number what action I need to take on target system. Do I need to add two more data volume into the target system?"
Please pay attention to the SAP note :: 457425    Homogenous liveCache copy using backup/restore
Please update the thread withy additional information ::
What is the version of the source liveCache? What is the version of the target liveCache?
How much data do you have in the source liveCache?
And you need to have the size data area of the target liveCache to be able to restore the databackup created in the source liveCache.
So by the size of the data volumes in the source liveCache, it's not clear how much data you have.
"2. After complication of database restore on target the system do I need to change the Live cache user ID (i.e. SAPSCD to SAPSCT)?"
Please review the SAP note 877203.
You could rename the user SAPSCD to SAPSCT using the SAP note 877203 steps
OR
You could have the user SAPSCD in the target liveCache as Standard liveCache user &
After you run the homogenous liveCache copy using backup/restore procedure you need
to change the LCA/LDA/LEA connection with user SAPSCD on target system and
set the user SAPSCD to the user containers ( please see the SAP note 616555 for more details )
Before to restart the liveCache in LC10.
PS: Please pay attention about the value of the liveCache parameter _UNICODE.
      What are the values of this parameter in the source & target liveCache?
Thank you and best regards, Natalia Khlopina

Data written to Live cache but not visible in SNP Planning Book

Hello All,
We have an issue this morning, Customer service cordinator placed a Purchase Order in SNP (VMI). Order was sent to ECC and a sales order was created. This morning when we check the sales order, it shows 4574 cases but in TLB Pur chase order, it only some 2000 something. I went to OM16 and checked the sales order and it had the entire 4574 cases written in the live cache. Any help on how to get the entire quantity to be seen is appreciated. Thank you.
Regards,
Rohit.

Hi Ada,
Thanks for the reply. The issue got resolved by itself.
Regards,
Rohit.

Data movement from R/3 DB to APO DB and to Live cache

Dear APO Experts,
I have few questions on live cache and how it works, I understand that Live cache is memory resident database. below are my questions.
1) What sought of data move from R/3 DB to APO DB and then to Live cache DB
2) When data moves from APO DB to Live cache, till how much duration that data stays in live cache
3) And how does data gets pulled in to live cache from APO DB
4) Why do we require live cache logs while data never gets commited to hard disk
5) Do we ever add a datafile to Live cache DB
any info that you provide on this will be really helpfull to me
Thanks,
Chetan

Hello Chetan,
As you know, itu2019s MAXDB/liveCache forum.
What is the version of your system?
The is documentation available at:
 SAP liveCache technology
< Please review document u201CWhat is SAP liveCache technology?u201D >
Sap documents at service.sap.com/scm -> Technology:
u201CliveCache overviewu201D and u201CIntegration overviewu201D
For SAP liveCache documentation also see the SAP note 767598.
Go to SAP link Best Practices for Solution Management: mySAP SCM at SAP liveCache technology ...
And Review the document u201CManage APO Core Interface in SAP APO (3.x) / mySAP SCM (4.x/ 5.0)u201D
1. As you saw in the reference documents the data transferred from the connected R/3 system to APO.
And the transactional data could be uploaded to the liveCache, if you downloaded them
to the APO database cluster tables first. This procedure steps are running during the
system upgrade < for example, from SCM 5.0 to SCM 7.0 ) u2013 report /SAPAPO/OM_LC_UPGRADE_70 steps. Or you want to migrate the
liveCache to another operating system or convert your system to Unicode,
and therefore you want to back up the liveCache data first so that you
can reload it into the liveCache afterwards - SAP Note No. 632357.
2. Could you collaborate more on this sentence. Could you give examples?
3. u201CAnd how does data gets pulled in to live cache from APO DBu201D
 The data are not pulled from the APO DB to liveCache.
 When you changed the APO data on the system the LCA procedures have been called from ABAP. The objects stored in the class containers in liveCache can be accessed and manipulated only via LCA routines. The registration of the LCA routines is done automatically when the liveCache is started by the LC10. The LCA procedures in the LiveCache are written in C++
and shipped to the customers as binary LCA libraries(LCA build) together with the LiveCache.
< See more details in SAP Note No. 824489 or 1278897 as of SCM 7.0 >
4. See the SAP notes:
 869267 FAQ: SAP MaxDB LOG area
 1377148 FAQ: SAP MaxDB backup/recovery
5. You could run the quicksizer & estimate how much data you are planning to have in liveCache.
 Also the amount of data could be increased by the creation of the new data in APO by users
 Or another reason u2026
 In general you will add the datavolume to solve or prevent the DB_FULL issue,
 See u201C17. What do I do if the data area is full? u201C in SAP note 846890.
Thank you and best regards, Natalia Khlopina

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

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 restore issue

Similar Messages

Maybe you are looking for