Live cache lock handler not available

Hi we are frequently getting this error Live cache lock handler not available and this causes our process chains to fail.
Can anyone please explain in details what this error refers to and direct to any good links for error resolution.

Hello,
1. As SAP customer, you could create the SAP message to the component BC-DB-LCA and get SAP support.
2. If you set the flag 'activate livecache lock' in tcode /SAPAPO/MSDP_ADMIN for your planning area on SCM system, please run the connection test for the LEA connection in /ndb59 to check the LEA connection settings.
The liveCache installation guide has additional information about LEA connection.
Regards, Natalia Khlopina

Similar Messages

Livecache lock handler not available in APO

Hello Experts,
We are getting the error "Livecache lock handler not available" error when we are running planning jobs in SAP APO.
We are using parallel processing profiles for DP background processing jobs (Macro calculations) and I am getting this error only when a job is run with PP profile.
Below are the parameters of the parallel processing profiles:
Application: DP background processing
No of parallel processes: 2
Block Size: 500
The error message is written in the spool generated for the background job and the job fails. Eventually the process chain fails in which the job is included.
Please provide some pointers if anyone has come across the same error.
Regards,
Raghu

Hi JB,
Thanks for the note, Basis check the solution in the note and system seems to have met the requirements.
But one thing is likely to increase the MaxSQLLocks in the system as the demand of the locks is more than the availability. So basis is looking at this dimension to increase the number of locks in the system.
Will update soon in case of any conclusion.
Regards,
Raghu

Livecache lock handler not available

Hello Experts,
We are getting the error "Livecache lock handler not available" error when we are running planning jobs in SAP APO.
We are using parallel processing profiles for DP background processing jobs (Macro calculations) and I am getting this error only when a job is run with PP profile.
Below are the parameters of the parallel processing profiles:
Application: DP background processing
No of parallel processes: 2
Block Size: 500
The error message is written in the spool generated for the background job and the job fails. Eventually the process chain fails in which the job is included.
Please provide some pointers if anyone has come across the same error.
Regards,
Raghu

Hi JB,
Thanks for the note, Basis check the solution in the note and system seems to have met the requirements.
But one thing is likely to increase the MaxSQLLocks in the system as the demand of the locks is more than the availability. So basis is looking at this dimension to increase the number of locks in the system.
Will update soon in case of any conclusion.
Regards,
Raghu

Activate Live Cache Lock in PA

Hi,
Can somebody explain to me the Locking Logic of "Activate Live Cache Lock in PA" in SAP APO v5.0? Will flagging this selection prevent the job from cancelling even though someone is using the PA?
Thanks

Dear 'abinashp12' and Ann,
Can somebody explain to me the Locking Logic of "Activate Live Cache Lock in PA" in SAP APO v5.0?
Read SAP online help to understand the choices available to you.
http://help.sap.com/saphelp_scm70/helpdata/EN/77/d4103d2669752de10000000a114084/frameset.htm
Will flagging this selection prevent the job from cancelling even though someone is using the PA?
No. There will always be locks of some kind when data is being changed, this is inherent to the design of any database, including the types of databases manged within Planning areas. 'Livecache lock' is a special kind of lock. Deselecting this checkbox will only result in a different type of lock instead.
Best regards,
DB49

Live Cache Locks

Dear Friends,
What does Live Cache Lock mean? How do we use this and what is it for? How to manage in APO? Can anyone let me know answers pls. Thanks in advance.
Regards
Bala

Hi Bala,
When you create, change and delete orders, rows in relational tables are changed or deleted in the liveCache. The corresponding records stay locked until the end of the transaction. The maximum number of locks on relational records is determined with parameter MAXLOCKS.
If a transaction requires more than 10% of the lock list for locks onto a table, all the multiple row locks are converted into a single table lock (this is called an 'escalation'). If several transactions escalate at the same time, wait situations occur since only one transaction can set the table lock.
There is no 'management' of locks required in APO. If you are seeing many lock escalations in liveCache, an increase in the MAXLOCKS parameter might be necessary.
Thanks,
Ashwath

Error handling not available with linked servers

Hello,
I have a stored procedure which inserts data to a linked mysql Server. The table in mysql has a unique key and I try to insert a new record with a conflicting key.
My problem is that I am not able to do an error handling because my script stops immediatly when the error in the SP occurs.
The error message itself is ok. But why is the script cancelled? So I don't have a possibility to do some error handling. I am working against SQL Server 2000. No TRY CATCH is available.
Here is my code:
DECLARE @RC int
DECLARE @ItemNr nvarchar(255)
DECLARE @Hostname nvarchar(255)
DECLARE @IpAdresse nvarchar(255)
DECLARE @LogLevel int
DECLARE @Message nvarchar(1000)
DECLARE @LocalError int
-- Error handling is working as expected
PRINT 1/0
SELECT @LocalError=@@ERROR
IF @LocalError<>0
PRINT 'Error'
ELSE
PRINT 'Success'
SELECT @ItemNr='AN12326m', @Hostname='hostname' ,@IpAdresse='ipadresse', @LogLevel=99, @Message='Test', @RC=0
-- Error handling does not work
EXECUTE [Asset].[dbo].[p_kapaya_DbSync_InsertMySqlRecord]
@AssetNr, @Hostname, @IpAdresse, @LogLevel, @Message OUTPUT, @RC OUTPUT
-- The following code is not reached, when an error occurs because the execution of the script is cancelled
SELECT @LocalError=@@ERROR
IF @LocalError <>0
PRINT @LocalError
ELSE
PRINT 'Success'
Error Message
Der OLE DB-Anbieter 'MSDASQL' für den Verbindungsserver 'MySQL' hat die Meldung '[MySQL][ODBC 5.1 Driver][mysqld-5.0.67-community-nt]Duplicate entry 'AN12326m' for key 1' zurückgeben.
Meldung 7343, Ebene 16, Status 2, Prozedur p_kapaya_DbSync_InsertMySQLRecord, Zeile 57
Der OLE DB-Anbieter 'MSDASQL' für den Verbindungsserver 'MySQL' konnte INSERT INTO für die [MSDASQL]-Tabelle nicht ausführen.
Kind regards
Patrick

This is not unique to linked servers. When an error occurs, there are several actions that SQL Server can take. It can abort the batch, it can abort the current scope or it can just termintate the current statement. Any active transaction may or may not
be rolled back. And this is not all.
Which of these actions, SQL Server takes it is hard to predict, becuase the developers have to have rolled a dice on deciding which action to take. Although, if you have SET XACT_ABORT ON, it is more consistent: in this case, most errors aborts the batch
and rolls back the transaction.
To trap the error, you need to use TRY-CATCH which permits you to trap most (not all) errors. See here for a quick introduction:
http://www.sommarskog.se/error_handling_2005.html
Erland Sommarskog, SQL Server MVP, [email protected]

HTTP live streaming: BBC iPlayer not available as ...

are there any plans to bring this standard to WP8? This is available to iOS, Android, Blackberry and Symbian but not Windows Phone 8. As a result, BBC cannot produce iPlayer for this OS as it would not be cost effective to re-encode all their video to a Windows Phone only format.. Especially with so few users.
Will there be a planned update to incorporate HLS in the future?
Long Live Nokia OS!

As this is an OS feature it is a question that only Microsoft can answer. All I know about the iPlayer is on your other post.
Ask Microsoft here:
http://answers.microsoft.com/en-us/winphone

'Never' auto lock setting not available.

My iPhone 3G doesn't have 'Never' listed as an option under the Autolock settings. It has 1,2,3,4, and 5 minutes listed, but Never is not there. I'm on software 3.0.1 and hardware model MB702LL. Could there be a setting in another menu that is disabling that option? I'd appreciate any ideas on how to fix this, thanks.

I just added an email account to my iphone through Microsoft Exchange. I couldn't figure out why on my auto lock I didn't have the "never" setting any longer. Only 1 thru 5 minutes. I searched on here and find out through your posts that it has something to do with the Exchange. I disabled it and sure enough the "never" setting came back. My question is this, Is there a way to have the email account through Microsoft Exchange on and keep the "never" setting in auto lock? Can I override it somehow so to speak? Any help would be greatly appreciated. Thanks.

Auto-Lock "Never" not available

I added an Exchange mail account and I found that the "Never" option is no longer available in *Settings > General > Auto-Lock*. This is a well-documented issue as in this article:
http://www.macworld.com/article/152642/2010/07/noneverautolock.html
I emailed my IT, but they are slow to respond to this kind of non-critical issues. But, the inability to choose "Never" under Auto-Lock is truly annoying in certain situations.
Is there anything I can do on my iPhone to bring back the "Never" option?

If I were to change the Exchange account to a regular account and let iPhone "Fetch" email, then the Never option returns as expected.
I contacted the IT Department at my school again. This time, they don't even reply.

Live chat in Europe not available anymore?

I used live chat to solve some of my problems 1 month ago, and now I can't find the live chat button anymore, on swiss french or UK website, did apple delete this service? Or it's just today? Thx.

Sorry, but no one here can help, since no one here works for Apple. If chat isn't available in your location, then it isn't available and you'll have to call Apple. Apple has experimented with support via chat on occasion, but it was never widely or consistently available and I haven't seen it in a while (except for the Apple Store), so it's quite possible that they've decided that it wasn't efficient and have stopped.
Regards.

RFC Debugging and Cache Admin not available in PPM 5.0

Hi Experts,
RFC Debugging and Cache Administration is not available in PPM 5.0 as compared to RPM 4.5. Is it due to single ABAP stack model of PPM 5.0 ? Complete transformation from java to ABAP webdynpro components ? Any idea on this ?
Best Regards,
Siva

Siva,
Yes, you are right, As enerything is moved to ABAP stack in SAP PPM 5.0. RFC Debugging and Cache Administration is not required in SAP PPM 5.0.
Cheers
Amit

Live cache error while correctingg inconsisitency in Resource

Dear Expert
While correcting inconsistency in live cache inconsistency is not getting corrected .
Error is Bucket vector does not exist in Live cache for resource WR201_1000_008
we are using Block planning in PPDS . I have checked SAPAPO/RST02 But resource is there in live cache it status is green
I am attaching error file
Thanks & Regards
Virender

Hi Virender,
The problem is a SCM issue, so I already triggered "alert moderator" to forward SCM forum.
Best regards,
James

Installing Live Cache Server on SCM 4.1 system

Hi All,
I have installed an SCM 4.1 Abap + Java System and Live cache client was installed during SCM 4.1 installation.
I would like to install Live cache server and i have problems with it.
I have downloaded the following installation guide
SAP liveCache 7.5.0 For SAP SCM Server 4.1
Document Version 1.02 u2013 April 8th, 2005
Guide tells us to use installation master CD for installating Live cache Server but note 708118 tells us to use the CD 51031447
04 Nov 05 Windows AMD64: Start Installation from liveCache CD
Start the installation of the liveCache server or client from the liveCache
CD (number 51031447) and not from the installation master CD (number
51031443)
Upon checking the cd 51031447 i see SDBINST.exe and upon clicking it i get the following screen
Installation of SAP LiveCache Software
existing profiles
0: APO Livecache
1: Runtime for SAP AS
2: DB Analyzer
3: JDBC
4: Server
5: Loader
6: ODBC
7: All
8: None
Please enter profile id :
I select profile 0 and it comes back with another user input option
Im searching for a document which gives me the procedure for installing Live cache using SBDINST.exe
Regards,
Ershad Ahmed.

Hi All,
I went ahead with Option 0 and it asked me for Kernel file and i provided the files.
I checked logs in /sapdb/wrk directory and i see that Installation of SAP livecache finished successfully.
From LC10 i gave database connection name (LCA) and clicked on live cache monitoring and it comes back with an error
Name and Server : LCA - XXXXXXX (XXXXX = Server Name)
DBMRFC Function: DBM_EXECUTE
Command: dbm_version
Error: DBM Error
Return Code : -4
Errror Message: database instance not found.
Application Server: XXXXXX                     ( Windows NT )
1. Connect. test with "dbmcli db_state"
     Error! Connection failed to node XXXXXXX for database LCA: database instance not found
     External program terminated with exit code 2
2. Connect. test with command mode "dbmrfc db_state"
     Name and Server     : LCA - XXXXXXX
     DBMRFC Function     : DBM_EXECUTE
     Command             : db_state
     Error               : DBM Error
     Return Code         :         -4
     Error Message       : database instance not found
3. Connect. test with session mode "dbmrfc db_state"
     Name and Server     : LCA - XXXXXXXX
     DBMRFC Function     : DBM_CONNECT
     Error               : DBM Error
     Return Code         :         -4
     Error Message       : database instance not found
4. Connect. test with "native SQL" ( LCA )
     For detailed information, see the developer trace for work process:          1
From the OS level i gave command dbmcli db_enum and i get OK as reply.
Can someone please let me know how to resolve this issue.
Regards,
Ershad Ahmed.

A killed session is still waiting for "library cache lock" for hours

Hello everybody
Today on my environment I killed a session while compiling a procedure that was taking too much time. Now, after more than a couple of hours that session is still there waiting for "library cache lock". I really can't understand why it's taking that much. Can anyone give me some hints about this. I already read the docs to find something to explain this case but I haven't been able to find the source of this lock.
Down here I past a description of what that procedure has been doing.
Processing ...
SELECT saddr, SID, command,taddr,lockwait,status,action
FROM v$session
WHERE SID = 636
Query finished, retrieving results...
      SADDR      SID     COMMAND         TADDR      LOCKWAIT   STATUS              ACTION
C00000023C7A2438     636        24 C000000238FB1650          KILLED   Main session
1 row(s) retrieved
Processing ...
SELECT *
FROM v$session_wait
WHERE SID = 636
Query finished, retrieving results...
SID SEQ# EVENT               P1TEXT         P1                   P1RAW            P2TEXT       P2                   P2RAW            P3TEXT             P3 P3RAW            WAIT_CLASS_ID WAIT_CLASS#   WAIT_CLASS   WAIT_TIME SECONDS_IN_WAIT STATE
636 247 library cache lock handle address 13835058063333980008 C0000001DFECF768 lock address 13835058064378433728 C00000021E2E10C0 100*mode+namespace 301 000000000000012D 3875070507     4             Concurrency 38        6089            WAITED KNOWN TIME
1 row(s) retrieved
Processing ...
select *
from v$session_event
where sid = 636
Query finished, retrieving results...
SID EVENT                         TOTAL_WAITS TOTAL_TIMEOUTS TIME_WAITED AVERAGE_WAIT MAX_WAIT TIME_WAITED_MICRO   EVENT_ID WAIT_CLASS_ID WAIT_CLASS# WAIT_CLASS
636 db file sequential read                 3              0           4          1,5        3             44994 2652584166    1740759767           8 User I/O
636 library cache lock                     58             57       16737       288,56      293         167366653 916468430    3875070507           4 Concurrency
636 SQL*Net message to client              94              0           0            0        0                46 2067390145    2000153315           7 Network
636 SQL*Net more data to client            25              0           0            0        0               294 554161347    2000153315           7 Network
636 SQL*Net message from client            94              0        2848         30,3     2246          28480966 1421975091    2723168908           6 Idle
636 SQL*Net more data from client          28              0           0         0,02        0              4471 3530226808    2000153315           7 Network
636 SQL*Net break/reset to client           2              0           0         0,01        0               194 1963888671    4217450380           1 Application
7 row(s) retrieved                            Thanks
Bye Alessandro
Edited by: Alessandro Rossi on 11-nov-2008 11.37

Alessandro Rossi wrote:
At the end I decided to kill the server process and now everything goes fine. i don't know why but the problem seems associated to the client application used to compile the procedure, because every time the developer tried to compile it using plslqldeveloper 7.14 through "edit-procedure" from his host the behavior was always like I just described before while the compilation of that procedure with other tools or from other hosts runs just fine.
Actually I haven't been able to find the reason for this, there was no view, among the ones I queried, telling me who was holding the resources, other than the blocked session, and it seems very hard that such a behavior may depend on the client tool used.
Thanks anywayAlessandro,
you may want to check the settings of this particular PL/SQL Developer installation. If I remember correctly then there are several settings in PL/SQL Developer related to how the tool connects to the database and compiles objects, e.g. "Safe compilation (using temporary compilation object)", "Background compilation", "Multi-Session" support etc. that might lead to situations where the tool could block itself for instance.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

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 lock handler not available

Similar Messages

Maybe you are looking for