Error in LiveCache

Hello.
In open alert I can see next line (High priority) constantly:
"10014 primary key range accesses, selectivity 0.28%: 2952691 rows read, 8231 rows qualified"
How fix it?
Whether it is necessary to pay attention to it or it is possible to ignore?
Whether it influences to perfomance?
Thanks, Igor.

Similar Messages

SCM5 - SCM7 Upgrade Error during LiveCache upgrade Step C4

We are in the process of upgrading our SCM5 system to SCM7 release level. During livecache upgrade step C4 to load transaction data, we are getting error CONNE_IMPORT_WRONG_COMP_TYPE. The dump says that "when importing the object 'OT_ORDERS", the component no. 5 in the dataset has a different type from the corresponding component of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL". The data type is "P" in the dataset, but "C in the program".
Our source livecache version is 7.6.03.12 and target livecache version we are upgrading to is 7.7.04.29. We used BS 7 SR1 liveCache 7.7.04 DVD from service marketplace. We did not use the update DVD since the guide mentioned that customers on SCM5.1 or higher need to run livecache upgrade from update DVD.
All steps in A, B have already been completed.
More details from the ST22 dump -
Error analysis | | An exception occurred that is explained in detail below. | | The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was | | not caught in | | procedure "GET_DB" "(METHOD)", nor was it propagated by a RAISING clause. | | Since the caller of the procedure could not have anticipated that the | | exception would occur, the current program is terminated. | | The reason for the exception is: | | When importing the object "OT_ORDERS", the component no. 5 in the | | dataset has a different type from the corresponding component | | of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL". | | | | The data type is "P" in the dataset, but "C" in the program. Information on where terminated | | Termination occurred in the ABAP program "/SAPAPO/SAPLOM_UPGR_PARALLEL" - in | | "GET_DB". | | The main program was "SAPMSSY1 ". | | | | In the source code you have the termination point in line 3222 | | of the (Include) program "/SAPAPO/OM_UPG_CLASS_IMPCLUT". | | The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR" | | occurred in | | procedure "GET_DB" "(METHOD)", but it was neither handled locally nor declared | | in the RAISING clause of its signature. | | | | The procedure is in program "/SAPAPO/SAPLOM_UPGR_PARALLEL "; its source code | | begins in line | | 3221 of the (Include program "/SAPAPO/OM_UPG_CLASS_IMPCLUT ".
We are running AIX5.3 and Oracle 10.2.0.2.0.
Any help here will be greatly appreciated.

This is exactly the same with OSS 305147 2010. It will be answered in BC-DB-LCA area.

Errors in Livecache when running a "check database structure"

Helleo, i have the following error messages when i do a check database structure of our QA Livecache environment :
DBA Action starts:
Timestamp: 20090406141745 Function: cdb Object: DATABASE
VERIFY command:
check data
VERIFY result:
ERR
-24988,ERR_SQL: SQL error
-9053,〰〰〰〰〰〰〰〰〰〳
17,Servertask Info: because b01pverify_participant() failed
10,Job 0 (Check Data) [executing] WaitingT147 Result=OK
6,b01pverify_participant() failed, Error code 9161 "data_page_corrupted"
17,Servertask Info: because b01pverify_participant() failed
10,Job 0 (Check Data) [executing] WaitingT147 Result=OK
6,b01pverify_participant() failed, Error code 9161 "data_page_corrupted"
17,Servertask Info: because b01pverify_participant() failed
10,Job 0 (Check Data) [executing] WaitingT147 Result=OK
6,b01pverify_participant() failed, Error code 9161 "data_page_corrupted"
DBA Action ends:
Timestamp: 20090406141753 State: Failure
ANd i have the same result whether i run it from DB13 or from the database managerIs there a way to run the check database with a repair option ? How can i fix this ?
Thanks for your help.
Y.
Edited by: Youssef ANEGAY on Apr 6, 2009 3:59 PM

> I guess i'll have no choice but to restore the database ...
Yes - most like that will be the case
But before you do that, I'd check the hardware also (drivers, firmware, OS patches etc.). If the system is connected to a SAN I would also check the logs of that.
Markus

MaxDB studio - Livecache task manager SQL error -5010

Hi Experts/Gurus,
After livecache 7.9 upgrade, I am getting attached error for refreshing task manager tasks in MaxDB studio for a Livecache instance
SQL error -5010 , Missing value specification
How to find the root cause and resolve.
I would appreciate your help and guidance
Thanks in advance

But I don't see this error for Livecache 7.7
I would appreciate your help and guidance
Thanks in advance

'No LiveCache anchor found'

Hi experts,
               While I am trying to load data to PB from Infocube, its not happened. It is throughing the error "No LiveCache anchor found".
My System configuration is below.
SCM5.0
SAP_BW     700     0012     SAPKW70012
SCM     500     0007     SAPKY50007
Pleasea help on this issue. very urgent.
Thanks,
Madhuri.

Hi Madhuri,
Please reinitialize you planning area again so if any new char-combos exits getting regenerated again & data can upload properly.
I ve faced simillar problems so may times.
Please let me know if you have any problems
Hrishikesh

LiveCache anchor could not be found with the DP BOM

Hi Users,
I have a com error when trying to call up the child products in a planning book that is linked to a BOM POS.
I've chceked the CVC's and BOM information and this all appeard to be okay. I've created the TSO (without deleting the old one), run the consistency checks /SAPAPO/PSTRUCONS, /SAPAPO/TSCONS and /SAPAPO/OM17 but still no joy.
After running the consistency check for the TSO (with repair ticked) the are a lot of "No live cache anchors found" errors that don't get fixed. These appear to be all of the BOM products that error.
What other options do I have to create the livecache for these info objects. I'm REALLY stuck with this and would appreciate any help. I don't want to delete the TSO and loose data in livecache.
Thanks
Paul

Paul
Take a look at the SAP "Manage Demand Planning in SAP APO (3.x) / mySAP SCM (4.x, 5.0)" Best Practice for Solution Management document.
It says
Adapt Time Series for New Characteristic Combinations with report
/SAPAPO/TS_LCM_PLOB_DELTA_SYNC. For example, if you create a new characteristic
combination without the option 'Create time series objects' (see transaction /SAPAPO/MC62),
you get the error u201CNo liveCache anchor foundu201D when selecting this characteristic combination.
In this case, execute report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC for the basis planning
object structure of the planning area. This creates the corresponding liveCache anchors and
liveCache time series for all planning areas that use this basis planning object structure and
for all versions of these planning areas for which time series objects already exist.
/SAPAPO/TS_REALIGNMENT cannot work without the liveCache anchors. So before
executing realignment (or if missing liveCache anchors are reported), run report
/SAPAPO/TS_LCM_PLOB_DELTA_SYNC. Mark the option display error log to get a log in
case of unsuccessful execution. See also SAP Notes 492399 and 573127.
If necessary, you can determine and repair inconsistencies for the planning area by executing
report /SAPAPO/TS_LCM_CONS_CHECK and choosing the Repair option (see Maintenance
of DP Data Storage Structures). For details, see SAP Note 402046.
In another section it also says
Delete Time Series and Time Bucket Profiles having no liveCache Anchors with report
/SAPAPO/TS_LCM_REORG. This report is supplied with SAP Note 542946, SP 22 (for APO
3.0), and SP 10 (for APO 3.1) u2013 see SAP Note 425825. The report determines all liveCache
time series and time buckets profiles from a selected planning version that do not have any
'liveCache anchors', independently of planning areas. These objects do not refer to the
application data so they are not inconsistent, but they are unnecessary and consume
liveCache memory. It may be sufficient to run the report approximately once a month.
If you have selected the 'Repair' option, any such unnecessary objects are deleted.
Caution: When you run report /SAPAPO/TS_LCM_REORG, no other processes for a
planning area with key figures based on liveCache time series should be allowed to run with
the same planning version. Otherwise, liveCache objects that are still required by the other
parallel process may be recognized as unnecessary and even deleted. For this reason, we
recommend that you always run the report with the option 'Lock planning version'. In this case,
all planning areas that use the planning version to be checked are locked for the relevant
version. If you cannot activate the lock, report execution is interrupted and a list of system
users is displayed, showing users who have already set a change lock for the planning
version.
I dont know if this helps. But might be worth a try.
Rishi Menon

No LiveCache Connection not found.

Hello Experts,
While loading the Material in the planning book, above error is shown. Can anyone please help how to solve it. I dont want to run the consistency job & want to know why its happening.
Thank you .
Regards
Rahul Chitte

Hi Rahul,
As the error indicates, livecache is disconnected and needs to be brought in place. I would request to inform a basis person to check the network and connectivity. No need to carry out livecache consistency check.
Once the livecache is up, if required, you can carry out that check.
Regards
R. Senthil Mareeswaran.

Error in Starting liveCache

Hello there,
    When starting our liveCache in LC10, I encountered an error message stating that "ERROR DBMCLI COMMANDEXECUTE_ERROR when starting liveCache LC1 on server". But nevertheless, the liveCache status turned green. I read the logs in Messages --> Logs --> History and found the following messages: (i replaced the actual password with <b><password of SAPLC1>)</b>
START *****************************
liveCache LC1 (restart)
Thu 09/13/2007
01:23 PM
installation path = c:\sapdb\lc1\db
OK
OK
DBMServer 7.6.00   Build 029-123-130-265
starting LC1 into ONLINE
OK
Creating liveCache application procedures
ERR
-24964,ERR_EXECUTE: error in program execution
3,""c:\sapdb\lc1\db\bin\x_python" "c:\sapdb\lc1\db\env\lapps.py" -R "c:\sapdb\lc1\db" -d LC1 -u SUPERDBA,*"
Installing APPS
Traceback----
File "c:\sapdb\lc1\db\env\installib.py", line 410, in connectAndInstall
    installRoutine (session, options)
File "c:\sapdb\lc1\db\env\lapps.py", line 43, in install
    "APPS"
File "c:\sapdb\lc1\db\env\installib.py", line 172, in include
    install (session, options)
File "c:\sapdb\lc1\db\env\APPS.py", line 75, in install
    loaderCmd (session, 'USE USER %s %s' % (sapuser[0], sapuser[1]))
Command----
USE USER saplc1 <password of SAPLC1>
Error----
loader.LoaderError: [-25008] Logon failure; previous user's (SUPERDBA) connection was restored.
ERROR : liveCache LC1 not started
Thu 09/13/2007
01:24 PM
END ******************************
START *****************************
liveCache LC1 (shutdown)
Thu 09/13/2007
01:31 PM
installation path = c:\sapdb\lc1\db
OK
DBMServer 7.6.00   Build 029-123-130-265
stopping LC1
OK
liveCache LC1 successfully stopped.
Thu 09/13/2007
01:31 PM
END ******************************
START *****************************
liveCache LC1 (restart)
Thu 09/13/2007
01:31 PM
installation path = c:\sapdb\lc1\db
OK
OK
DBMServer 7.6.00   Build 029-123-130-265
starting LC1 into ONLINE
OK
Creating liveCache application procedures
ERR
-24964,ERR_EXECUTE: error in program execution
3,""c:\sapdb\lc1\db\bin\x_python" "c:\sapdb\lc1\db\env\lapps.py" -R "c:\sapdb\lc1\db" -d LC1 -u SUPERDBA,*"
Installing APPS
Traceback----
File "c:\sapdb\lc1\db\env\installib.py", line 410, in connectAndInstall
    installRoutine (session, options)
File "c:\sapdb\lc1\db\env\lapps.py", line 43, in install
    "APPS"
File "c:\sapdb\lc1\db\env\installib.py", line 172, in include
    install (session, options)
File "c:\sapdb\lc1\db\env\APPS.py", line 75, in install
    loaderCmd (session, 'USE USER %s %s' % (sapuser[0], sapuser[1]))
Command----
USE USER saplc1 <password of SAPLC1>
Error----
loader.LoaderError: [-25008] Logon failure; previous user's (SUPERDBA) connection was restored.
ERROR : liveCache LC1 not started
Thu 09/13/2007
01:31 PM
END ******************************
Another thing is, the actual password is not the same password I changed in DBMGUI and in Integration. Can you please help me with this error and -24964,ERR_EXECUTE: error in program execution keeps appearing in the logs.
Thank you.

Hello Deanna Mariel Marasigan,
-> please check which user you set for LCA connection in LC10 -> Integration.
    You wrote, that it's SAPLC1. Correct?
-> run the SQL statement as superdba user & check if this user is listed:
select * from domain.users
-> To make sure that the lcinit script works with the correct Standard liveCache
user then you should run the commands to check the
liveCache user in the upc container:
In a dbmcli session (e.g. in LC10 -> liveCache:Monitoring -> Tools)
sql_execute user-type=SAP select user from dual
Should return this user - SAPLC1
When an error returns ( unknown user/password ), then no user is set or wrong password.
To set the new password for Standard user in the upc container run:
dbmcli -d LC1 -n <LC-server> -u control,<control> user_sap SAPLC1,<pwd-new>
( please see the SAP note 616555 for more details ).
This sets the new user/pwd in the upc container.
After that the above command should return the user.
Restart the liveCache in the LC10 transaction.
Thank you and best regards, Natalia Khlopina

While running the livecache server test a native sql error occures

We are using scm4.1 livecache 7.5.0 And every time we are running the livecache test program he is dumping
whith the following dump
patch level scm & scm_basis is 8
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          31.10.2005 16:50:55
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error 600 occurred in the current database connection "LCA".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "Work rolled back: DbpError -28814 in
APS_ORDER_CH"
Database error code .......: 600
Triggering SQL statement...: " ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? or'"
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"/SAPAPO/SAPLOM_PLANNING" or "/SAPAPO/LOM_PLANNINGU08"
"/SAPAPO/OM_ORDER_CHANGE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"/SAPAPO/OM_ORDER_CHANGE"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bebruap2"
Network address.......... "195.213.49.227"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "BEBRUAP2"
Database type............ "MSSQL"
Database name............ "APD"
Database owner........... "apd"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 23 2005 00:00:49"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "87"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 24040336
Heap..................... 0
Page..................... 1687552
MM Used.................. 1516920
MM Free.................. 572032
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "CGRAULS"
Language key........ "E"
Transaction......... "/SAPAPO/OM03 "
Program............. "/SAPAPO/SAPLOM_PLANNING"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" in
"/SAPAPO/OM_ORDER_CHANGE".
The main program was "/SAPAPO/OM_TB_FLOW_QUANTITY ".
The termination occurred in line 91 of the source code of the (Include)
program "/SAPAPO/LOM_PLANNINGU08"
of the source code of program "/SAPAPO/LOM_PLANNINGU08" (when calling the
editor 910).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "/SAPAPO/OM_ORDER_CHANGE" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "/SAPAPO/SAPLOM_PLANNING ". Its source code
starts in line 5
of the (Include) program "/SAPAPO/LOM_PLANNING$08 ".
Source Code Extract
Line
SourceCde
61
is_gen_params-simversion
62
is_gen_params-dont_set_netchg_flag
63
space.
64
65
Kontrollstruktur IS_GET_CHANGED_OPTIONS anpassen.
66
IF NOT et_changed_orders IS REQUESTED.
67
is_get_changed_options-send_chg_top_order = gc_false.
68
ENDIF.
69
IF NOT et_changed_cap_reqs IS REQUESTED.
70
is_get_changed_options-send_chg_cap_req = gc_false.
71
ENDIF.
72
IF NOT et_changed_io_nodes IS REQUESTED.
73
is_get_changed_options-send_chg_ionode = gc_false.
74
ENDIF.
75
IF NOT et_changed_io_pp_nodes IS REQUESTED.
76
is_get_changed_options-send_chg_io_pp = gc_false.
77
ENDIF.
78
IF NOT et_changed_pegids IS REQUESTED.
79
is_get_changed_options-send_chg_pegid = gc_false.
80
ENDIF.
81
IF NOT et_deleted_fix_pegging IS REQUESTED.
82
is_get_changed_options-send_del_fix_peg = gc_false.
83
ENDIF.
84
start_function 'OM_ORDER_CHANGE'.                         "#EC *
85
Verbindung zum liveCache aufbauen
86
check_server.
87
connect_to_livecache.
88
COM-Routine zum Anlegen bzw. Überschreiben eines Zeitstrahls
89
90
EXEC sql.
>>>>>
execute procedure                  "APS_ORDER_CHANGE" (
92
in :ls_gen_com_params,
93
out :lv_rc,
94
in :et_rc,
95
in :it_order_method,
96
in :it_ordkeys,
97
in :it_ordmaps,
98
in :it_orders,
99
in :it_activities,
100
in :it_mode,
101
in :it_cap_reqs,
102
in :it_positions,
103
in :it_inputs,
104
in :it_outputs,
105
in :it_prodflow,
106
in :it_intern_constraints,
107
in :it_extern_constraints,
108
in :it_charact_val_acts,
109
in :it_charact_req_inpnode,
110
in :it_charact_val_outnode,
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Flow Quantity Test
SY-MSGTY
S
SY-MSGID
/SAPAPO/OM_TEST
SY-MSGNO
001
SY-MSGV1
Create transSim
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
3 FUNCTION     /SAPAPO/SAPLOM_PLANNING             /SAPAPO/LOM_PLANNINGU08                91
/SAPAPO/OM_ORDER_CHANGE
2 FORM         /SAPAPO/OM_TB_FLOW_QUANTITY         /SAPAPO/OM_TB_FLOW_QUANTITY           802
CHANGE_DATA
1 EVENT        /SAPAPO/OM_TB_FLOW_QUANTITY         /SAPAPO/OM_TB_FLOW_QUANTITY            11
START-OF-SELECTION
Chosen variables
Name
Val.
No.       3 Ty.          FUNCTION
Name /SAPAPO/OM_ORDER_CHANGE
IS_ATP_INFO
01ATP0000001~CGRAULSXX##
334553333333744545455500
011400000001E37215C38800
000000000000000000000000
000000000000000000000000
IS_CONTROLPARAMETERS
霁က#ం̂⍱㔒鲔#####
2222222222222222222222001007190000022
0000000000000000000000100221240000100
0000000000000000000000910002390000000
0000000000000000000000700C335C000C000
IS_GEN_PARAMS
01PLV0000001~CGRAULS
3354533333337445454522222
010C60000001E37215C300000
0000000000000000000000000
0000000000000000000000000
IS_GET_CHANGED_OPTIONS
2222222
0000000
0000000
0000000
IT_ACTIVITIES
Table IT_274[1x256]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ACTIVITIES
Table reference: 41
TABH+ 0(20) = 5087FFDF00000000000000002900000012010000
TABH+ 20(20) = 0100000000010000FFFFFFFF0487000000290000
TABH+ 40( 8) = 10000000C1308000
store        = 0x5087FFDF
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 41    (0x29000000)
label        = 274   (0x12010000)
fill         = 1     (0x01000000)
leng         = 256   (0x00010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000205
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x180112E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 126   (0x7E000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CAP_REQS
Table IT_276[1x112]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_CAP_REQS
Table reference: 39
TABH+ 0(20) = 48BB06E000000000000000002700000014010000
TABH+ 20(20) = 0100000070000000FFFFFFFF04870000C0290000
TABH+ 40( 8) = 10000000C1308000
store        = 0x48BB06E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 39    (0x27000000)
label        = 276   (0x14010000)
fill         = 1     (0x01000000)
leng         = 112   (0x70000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000209
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x188D04E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 124   (0x7C000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CHARACT_REQ_INPNODE
Table IT_418[0x140]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_REQ_INPNODE
Table reference: 32
TABH+ 0(20) = 00000000000000000000000020000000A2010000
TABH+ 20(20) = 000000008C000000FFFFFFFF04870000301D0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 32    (0x20000000)
label        = 418   (0xA2010000)
fill         = 0     (0x00000000)
leng         = 140   (0x8C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000142
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CHARACT_VAL_ACTS
Table IT_417[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_ACTS
Table reference: 50
TABH+ 0(20) = 00000000000000000000000032000000A1010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 50    (0x32000000)
label        = 417   (0xA1010000)
fill         = 0     (0x00000000)
leng         = 156   (0x9C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000144
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CHARACT_VAL_OUTNODE
Table IT_419[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_OUTNODE
Table reference: 60
TABH+ 0(20) = 0000000000000000000000003C000000A3010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 60    (0x3C000000)
label        = 419   (0xA3010000)
fill         = 0     (0x00000000)
leng         = 156   (0x9C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000144
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_EXTERN_CONSTRAINTS
Table IT_416[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_EXTERN_CONSTRAINTS
Table reference: 71
TABH+ 0(20) = 00000000000000000000000047000000A0010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 71    (0x47000000)
label        = 416   (0xA0010000)
fill         = 0     (0x00000000)
leng         = 124   (0x7C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000215
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_INPUTS
Table IT_278[1x420]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_INPUTS
Table reference: 63
TABH+ 0(20) = 087400E0C0E303E0000000003F00000016010000
TABH+ 20(20) = 01000000A4010000FFFFFFFF04870000202A0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x087400E0
ext1         = 0xC0E303E0
shmId        = 0     (0x00000000)
id           = 63    (0x3F000000)
label        = 278   (0x16010000)
fill         = 1     (0x01000000)
leng         = 420   (0xA4010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000211
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x78DC11E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 123   (0x7B000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x2029FFDF
hsdir        = 0x00000000
ext2         = 0x00000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_INTERN_CONSTRAINTS
Table IT_415[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_INTERN_CONSTRAINTS
Table reference: 49
TABH+ 0(20) = 000000000000000000000000310000009F010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 49    (0x31000000)
label        = 415   (0x9F010000)
fill         = 0     (0x00000000)
leng         = 124   (0x7C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000215
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_MODE
Table IT_275[1x164]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_MODES
Table reference: 52
TABH+ 0(20) = A03C00E000000000000000003400000013010000
TABH+ 20(20) = 01000000A4000000FFFFFFFF0487000060290000
TABH+ 40( 8) = 10000000C1308000
store        = 0xA03C00E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 52    (0x34000000)
label        = 275   (0x13010000)
fill         = 1     (0x01000000)
leng         = 164   (0xA4000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000207
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xC8F611E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 125   (0x7D000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_ORDERS
Table IT_293[1x320]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDERS1
Table reference: 47
TABH+ 0(20) = 20B403E000000000000000002F00000025010000
TABH+ 20(20) = 0100000040010000FFFFFFFF0400000030380000
TABH+ 40( 8) = 01000000C1308000
store        = 0x20B403E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 47    (0x2F000000)
label        = 293   (0x25010000)
fill         = 1     (0x01000000)
leng         = 320   (0x40010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000286
occu         = 1     (0x01000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x9080FFDF
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 1     (0x01000000)
lineAlloc    = 1     (0x01000000)
store_id     = 130   (0x82000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_ORDER_METHOD
Table IT_268[2x62]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDER_METHOD
Table reference: 51
TABH+ 0(20) = 8882FFDF0000000000000000330000000C010000
TABH+ 20(20) = 020000003E000000FFFFFFFF04000000B0360000
TABH+ 40( 8) = 10000000C1248000
store        = 0x8882FFDF
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 51    (0x33000000)
label        = 268   (0x0C010000)
fill         = 2     (0x02000000)
leng         = 62    (0x3E000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000278
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0868FFDF
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 122   (0x7A000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_ORDKEYS
Table IT_271[1x332]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDKEYS
Table reference: 29
TABH+ 0(20) = 80E303E000000000000000001D0000000F010000
TABH+ 20(20) = 010000004C010000FFFFFFFF04870000E0270000
TABH+ 40( 8) = 10000000C1308000
store        = 0x80E303E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 29    (0x1D000000)
label        = 271   (0x0F010000)
fill         = 1     (0x01000000)
leng         = 332   (0x4C010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000199
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0

Hi,
the error DbpError -28814 denotes that an object cannot be found.
Can you maybe tell me your exact liveCache version (incl. Build level) and LCA Build?
Additionally, please copy the relevant error information from the file (/sapdb/data/wrk/<SID>/)knldiag.err into this thread.
Which exact 'liveCache test program' are your referring to (which of the /SAPAPO/... transactions)?
Kind regards,
Roland

Error while accessing Livecache from LC10

We had a problem on our APO system that dialog work processes are hanging on the central instance showing semaphores 26 (enqueue table) and 43 (rspo cache).
The dwstat logfile indicates that the enqueue process is running (with the longest processing time of all processes), while the spool process is stuck with semaphere 26 on "global actions".
The problem is mostly likely caused by a bug in SAP and two recent SAP notes were found that describe the situation: note 1293472 and note 661487.
The first one states to update the kernel and set rspo/event_update_nocsec = 1, the second one to add an entry to the table TSPOPTIONS.
now we are upgrading the SAP Kernel to Patch Level 221 that was released on Aug 28.
kernel release 700 - 64 BIT - Non-Unicode
But after upgrading the kernel to the patch 221 we are not able to access livecache through LC10, LC10 hangs for a while and then fails with a RFC error
Name and Server : LS5 u2013 plsapas500
DBMRFC Function : DBM_CONNECT
Error: Communication Error
Error Message: Error when opening a RFC connection
further we found that the RFC connection SAPDB_DBM_DAEMO is not registered for program dbmrfc@sapdb.
tried to register it but no success....
this problem was not faced with old Kernel havin patch 185
kindly suggest
thanks & regards,
Deepak

hello,
Can you check the connection test in db59 and check the detailed log.
check this if helpful: Re: LC10: system error
thanks,
Prasanna Kulkarni

Error when Starting LiveCache

Hello all,
The restart of LiveCache is works fine, but I checked the LCTRC#init.log file and I saw the following error:
Installation successfully finished
==================================
11455 2009-01-13 16:21:03.000 ERROR: Could not write to 'teo110_PipeBase::eo110_WritePipe' pipe, rc = 32 - (teo110_PipeBase::eo110_WritePipe)
liveCache LCQ successfully restarted
I did not find sap notes for it. Could you help me on this?
Thanks,
Alberto.

Hello Alberto,
1. If you have the liveCache/MAXDB questions/problems please post
    them at the correct forum Expert Forums » Database & OS Platforms » MaxDB/liveCache :
2. As SAP customer you have option to open the ticket at the component 'BC-DB-LVC'
    to check the system and get the answer from SAP support.
3. May be the problem as in PTS 1145968 , www.sapdb.org/webpts -> Advanced Search & use the PTS number. Please post more details:
       What is the OS of the liveCache server?
       What is the version of the liveCache on your system?
Thank you and best regards, Natalia Khlopina

Error in SCLA_LCK_SYNCHOWNERS and starting LiveCache through LC10

When starting the livecache LCA through LC10 it immediately short dumps below:
DBIF_DSQL2_SQL_ERROR
CX_SY_NATIVE_SQL_ERROR
The error "-28534" occurring in the current database connection "LEA".
Database error text........: "POS(1) Package must be
recreated:LCK_LIST_OWNERS,"
Database error code........: "-28534"
Triggering SQL statement...: "EXECUTE PROCEDURE LCK_LIST_OWNERS"
Internal call code.........: "[DBDS/NEW DSQL]"
I can provide more detail if needed. Any ideas?

Hi Gonzalez,
Please refer to solution steps in thread Starting of LiveCache fails after patching
Hope this helps.
Regards,
Deepak Kori

SAP SCM 2007 liveCache 7.7.0 Windows Server on x64 64bit ERROR

Hi All,
OS : windows 2003 server 64 bit,
DB : Oracle 10g
APP : IDES SCM 2007
Our Requirment is need to Install SCM 2007 with LiveCache, APO.
to Install SCM 2007.. We must need to have 2 DATABASES and 2 SID
1. One Oracle or SQL Database for SCM    (one SID)
2. 2nd for ONly MaxDB Database for LiveCache         (Another SID)
Can you please advice me.... here are the steps I done as of now.
oracle 10g Installation completed.
SCM IDES 2007 Installation Complted.
   (At the time SCM Installtion its prompt me for SID's for 2 times..
   I given Both SID Same (One for [SID-SCM]) and (Another for Live Cache[SID-SCM]) Then the Installation is successfully completed. but now when I run LC 10 is not working...
Name and Server : IE6 - XXXXXX
DBMRFC Funcation : DBM_CONNECT
ERROR : DBM ERROR
Return Code : -4
Error Message : database instance not found.
to over come from this issues do we need to Installl LIVECACHE SERVER SERVER ?
1. if we need to install livecache server.. I need to go for only for MAXDB.
2. In the MAXDB Instance I have to give the Instance name same as Live cache server SID ?
3. IF we need to Install livechache server, do we need to use SID same as SCM or different one?
4. SCM IDES and Live Cache is running one the same machine.
5. After this LiveCache server.. we need to Install livecache client also install... if the SCM IDES and Livecache running on same BOX and SAME OS.
can you help me on this.

Hello,
-> As SAP customer you have the option to create the OSS ticket to the component BC-DB-LVC to get SAP support.
->
"1. if we need to install livecache server.. I need to go for only for MAXDB."
You need to install the liveCache server of the 7.7 version, as you are installing SCM 2007 with LiveCache, APO.
Please follow the liveCache server installation guide.
"2. In the MAXDB Instance I have to give the Instance name same as Live cache server SID ?"
How many MAXDB/liveCache database instances are you planning to install on the liveCache server?
"3. IF we need to Install livechache server, do we need to use SID same as SCM or different one?"
The liveCache SID for the SCM system need to be unique on the liveCache server, you have only one database instance MAXDB/liveCache with this name, also you checked the restrictions for the names at
http://maxdb.sap.com/doc/7_7/default.htm -> Glossary ->Database Name -> Conventions for Database Names
"4. SCM IDES and Live Cache is running one the same machine."
You could run SCM IDES and Live Cache on the same machine.
"5. After this LiveCache server.. we need to Install livecache client also install... if the SCM IDES and Livecache running on same BOX and SAME OS."
If the liveCache instance and application server are running on the same machine, you don't need to install the liveCache client software.
Please review the SAP notes::
822239     FAQ: MaxDB Interfaces
822271     FAQ: SAP MaxDB client software
-> Please update with output of the following commands:
     dbmcli -s inst_enum
     dbmcli -s db_enum
     sdbregview -l
     xinstinfo IE6
-> For SAP liveCache documentation see the SAP note 767598.
     The documentation available at www.sdn.sap.com/irj/sdn/livecache
Thank you and best regards, Natalia Khlopina

Livecache update - ERROR 30707 in SAPAPO_RESET_GLOBALS

Hi,
During a SCM 7.0 SR1 upgrade, we need to update the livecache to 7.7.04 (29)
This runs just fine until the LC needs to be initilialized:
switch liveCache state to ADMIN
Value of MCOD-Parameter is NO
setting up unicode liveCache...
cannot finish instance update for QU1
setting up unicode liveCache...
setting up liveCache failed
exec_lcinit init -e unicode
ERR
-24964,ERR_EXECUTE: Error in program execution
0,sap\lcinit QU1 init -e UNICODE -uDBM *,* -uDBA *,* -uSQL *,*
liveCache QU1 (init)
From lcinit.log:
ERR
-24988,ERR_SQL: SQL error
600,Work rolled back: tExcept 30707 in SAPAPO_RESET_G
ERROR : liveCache QU1 not initialized
From knlmsg:
ERR OBJECT     51000: ##### #!!# tExcept no. = 30707 ########
ERR OBJECT     51000: # in SAPAPO_RESET_GLOBALS
ERR OBJECT     51000: #
ERR OBJECT     51000: ~< tExcept 30707 curr_cl == cl - 0 [cbs__version.cpp: 314] in SAPAPO_RESET_GLOBALS >~
ERR OBJECT     51000: #
ERR OBJECT     51000: # COM build 70006.1 CL 392374 (7.0_REL)
ERR OBJECT     51000: # on WinX64
ERR OBJECT     51000: #--------------------------------------#
ERR OBJECT     51000: # omsTerminate will be triggered:
ERR OBJECT     51000: # ERROR 30707 in SAPAPO_RESET_GLOBALS
ERR OBJECT     51000: # [incident] OdT70G0000010000WnOn4m
ERR OBJECT     51000: #        --> COM trace 1
ERR OBJECT     51000: ########################################
Many more details in this link: [DETAILS|http://www.bronee.org/bronee_documents/SDBUPD_ERROR.html]
Except for the "small" fact that we cannot init the LC, the sapdb system seems to run just fine ... hmmm
Any ideas?
Cheers
Jan

Hello Jan Bronee,
During a SCM 7.0 SR1 upgrade of the system SCM 5.1 the you will be asked to run the liveCache upgrade. During the SCM 5.1 liveCache upgrade to the lSCM 7.0 liveCache will be initialized as it was pointed in the SCM 7.0 guide.
As you saw in the link provided by you the "COM libraries changelist mismatch" occurred, SAPTREX library has different CL number and may be not compatible.
=>
I recommend to create the SAP message to take a look closer on this issue.
Use SAP Note 1495739 to update the liveCache,
SAP liveCache Technology Release Information: SCM 7.0 [original link is broken]
What do you mean "the sapdb system seems to run just fine ... hmmm"?
Was you able to run the liveCache initialization to finish the liveCache upgrade before to run the upload liveCache data steps?

Error messages in LiveCache

Hello,
I have the following error messages when i check the alert monitor in dbacockpit and the bottlenecks in LC10:
Critical Logging Event    Error OM13
High : Log_WriterTaskSynchronizer::m_spinlock: collision rate 0.02%, 1 collisions, 30000 spin loops, 66356 yield loops, 5704 accesses
Does anybody know what that means ?
Thanks for your help.

Hello Youssef,
What is the version of the liveCache on your system?
1) "Critical Logging Event Error OM13"
    You have the critical LCA logging events. Please check the errors in
     //om13 transaction, Logging folder. You also could display the LCA logging events in the //om11 transaction.
2) "High : Log_WriterTaskSynchronizer::m_spinlock: collision rate 0.02%, 1 collisions,
       30000 spin loops, 66356 yield loops, 5704 accesses"
Log_WriterTaskSynchronizer class coordinates the suspend/resume of the Log_Writer .
      As SAP customer you have the option to create the SAP OSS ticket to the component 'BC-DB-LVC' and discuss the problems on your system in more details. We could login to your system via OSS to check the status of the system and problems with the writing log in liveCache.
Please use the DB Analyzer, liveCache tool, to find the bottleneck in liveCache.
         -> For SAP liveCache documentation please see the SAP note 767598.
         -> Please see the information & documents in the MAXDB Library at the link :
                 http://maxdb.sap.com/doc/7_7/default.htm
                 -> Tools Documentation -> Database Analyzer -> Database Analyzer Messages
Thank you and best regards, Natalia Khlopina

Error in LiveCache

Similar Messages

Maybe you are looking for