Dears,

I hv installed SCM7.0 EHP3, and want to start LiveCache for APO , but I don't know how to install Livecache & start/connection setup, could who guide me, thanks.

checked the LC10, there is LCA/SC1, but I don't know how to connect it or start it.

Great thanks for your helping.

Regards, Allen

Hi ,

Please let me know the live cache log files and location of the same.

I would need them to analyze livecache issues during the upgrade and startup/performance related problems.

any help is much appreciated.

Thanks in advance

Dear Experts,

I'm having an error everytime I start liveCache stating "lock Server not accessible"

I also checked the connection LCA in tx LC10. It displays a green light but a warning that says
"SQL access not possible". Same goes with tx DB59, there's an error while performing the test. See details below.

DB59 - Connection test:

General Connection Data
   Connection Name....: LCA
   Database Name......: LC1
   Database Server....: 10.206.110.72
   tp Profiles........: no_longer_used
   DBM User...........: CONTROL

   Test Scope
   1. Execute an external operating system command (DBMCLI)
   2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC command mode)
   3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC session mode)
   4. Test the SQL connection (Native SQL at CON_NAME)

Application Server:  MDCSAP07_AP1_00                          ( Windows NT )
   1. Connect. test with "dbmcli db_state"                         Successful
   2. Connect. test with command mode "dbmrfc db_state"            Successful
   3. Connect. test with session mode "dbmrfc db_state"            Successful
   4. Connect. test with "native SQL"  ( LCA )                     No connection
      SQL Code:
      Error creating a secondary database connection
      Set up of a secondary connection to the database system failed. It is possible that the data required for setting up the con
      SQL code:
      For detailed information, see the developer trace for work process:           23

work proccess Dev_23:

B  Loading DB library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll")
  Error 126 = "The specified module could not be found." [dlnt.c       255]
M  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll'
[dbcon.c      5672]
B  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection LCA        [dbds         862]
C     OCIAttrSet(con=0, rc ln: 0 15, -1 32, 0 3, 0 8) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C
C Thu Jul 25 14:21:53 2013
C     OCIAttrSet(con=0, rc ln: 0 32, -1 32, 0 3, 0 10) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C     OCIAttrSet(con=0, rc ln: 0 32, -1 32, 0 4, 0 10) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C
C Thu Jul 25 14:22:45 2013
C     OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 3, 0 8) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
C
C Thu Jul 25 14:22:49 2013
C     OCIAttrSet(con=0, rc ln: 0 27, -1 32, 0 3, 0 8) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
B  Loading DB library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll")
  Error 126 = "The specified module could not be found." [dlnt.c       255]
M  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll'
[dbcon.c      5672]
B  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection LCA        [dbds         862]
B  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]
C
C Thu Jul 25 14:22:50 2013
C     OCIAttrSet(con=0, rc ln: 0 32, -1 32, 0 2, 0 10) failed with SQL error 24960:
C     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

We are planning to refresh quality assurance(Q/A) systems  of ERP landscape and SCM 7.0(APO) landscape with the productive systems

(Have done on ERP on regular basis, now APO landscape was also built up and is productive, too)

I have read a lot of documents, but still have some  doubts about the best method:

Best Practise Documents systemcopy (http://service.sap.com/solutionmanagerbp) + note 88543 copy of system landscapes)

Note 457425 - Homogeneous liveCache copy using backup/restore

Note 1015489 - Connection problems after system copy

Note 1030857 - Report for additional update after system copy

According note 886103, livecache is normally also copied with SCM system.

Question 1) Could we also only copy the  SCM-PROD system to SCM Q/A and then initialise the Q/A livecache (after having changed tables in SCM system, which points to the right livecache on Q/A livecache server). I would appreciate getting experience from other customers.

If we copy the livecache, too:

We could use the method with backup/restore from note 457425.

In Bestpractise Dok  Checklist for Recovery of SAP APO liveCache >= 7.4 I found:

APO/SCM only

Do not select “Restore database until a specified time.” If the liveCache instance is not completely

recovered, inconsistencies might occur between the APO database and liveCache. SAP does not

support synchronization using time stamps.

Question 2: I am wondering if this is still valid (dokument is from 2005...) ?

Normally we copy the systems with flashcopy/online backup method, so that the source systems are online always. We deactivate rfc connections, jobs etc on target system before starting the system

If livecache doesn't support point in time recovery, how can we solve that ?  The SCM (APO) system should have the data of the same timestamp as ERP system. I would normally restore ERP, SCM and probably livecache to same timestamp, but if it is not possible to restore to a time stamp..... ?

Question 3 to Note 886103:

To adapt the liveCache table /sapapo/ordmap, you need to open a command prompt on the liveCache server and start xquery. Alternatively you could useSQL Studio.

 

Enter: username/password/system name (sapr3/../LC-Target)

Command: select LOGSYS, count(*) from "SAPR3"."/SAPAPO/ORDMAP" group by logsys

 

For each LOGSYS that is displayed, the same mapping / changes have to be done as in BDLS. For example <APO-SOURCE>M001 => <APO-TARGET>M001

 

Command: update "SAPR3"."/SAPAPO/ORDMAP" set logsys='<APOTARGET>M001'where logsys='<APO-SOURCE>M001'

 

This will change the logical system name in /sapapo/ordmap to the target system.

I only found an empty table SAPSR3./SAPAPO/ORDMAP in the SCM system but not in the livecache server.  Iis there a SAPR3 (or SAPSR3) schema  in the livecache ? I haven't found this user with the dbmgui....

Any ideas are welcome...

Dear Livecache Experts,

Need some expert advice regarding the SCM+Live cache Hetrogenous Migration.

We are planning to migration our SCM+Live cache from AIX to Linux. As this is Os Migration, we have refered the SAP note: 632357. Which Gives step by step information how to migrate the livecache.

Now the problem is that our livecache database size is 70GB and if we go as per the SAP note of migrating the data from live cache to Oracle master table. We don't know how much time it will take and we have very short downtime to do this migration. Is there any option to make this live cache migration from Live cache database to Oracle faster in source system and then target system migrate data from Oracle master table to Live cache database.

OR

I have heard we can install the fresh live cache without old database and whereas after making SCM system migration and not live cache ( Install fresh live cache), after some days again the data will get populated in live cache database ( CAN IT BE POSSIBLE, IT WILL SAVE OUR TIME OF MIGRATION). In such case we need to do only migration of SCM database and not Live Cache.

Regards,

Anil Bhandary

Dear Experts,

We facing a liveCache error in our System.

Everytime we start in tx DB02 the liveCache error "liveCache lock server not accessible" appears.

I also check transaction LC10 and found a warning that "SQL access not possible"

Here is the Connection Test Log i made:

Application Server:  MDCSAP07_AP1_00                          ( Windows NT )

   1. Connect. test with "dbmcli db_state"                         Successful

   2. Connect. test with command mode "dbmrfc db_state"            Successful

   3. Connect. test with session mode "dbmrfc db_state"            Successful

   4. Connect. test with "native SQL"  ( LCA )                     No connection

      SQL Code:

      Error creating a secondary database connection

      Set up of a secondary connection to the database system failed. It is possible that the data required for setting up the con

      SQL code:

      For detailed information, see the developer trace for work process:           25

Here's the copy of the dev_25:

Thu Jul 25 13:57:46 2013
    OCIAttrSet(con=0, rc ln: 0 31, -1 32, 0 3, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:49 2013
    OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 3, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 2, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 2, 0 8) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64
    OCIAttrSet(con=0, rc ln: -1 37, 0 22, 0 4, 0 10) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_CLIENT_INFO is greater than the maximum allowable length of 64

Thu Jul 25 13:57:50 2013
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:51 2013
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
    OCIAttrSet(con=0, rc ln: 0 22, -1 27, 0 4, 0 12) failed with SQL error 24960:
    ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:54 2013

Thu Jul 25 13:57:54 2013
     OCIAttrSet(con=0, rc ln: 0 20, -1 32, 0 2, 0 8) failed with SQL error 24960:
     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48

Thu Jul 25 13:57:57 2013
     OCIAttrSet(con=0, rc ln: 0 27, -1 32, 0 3, 0 8) failed with SQL error 24960:
     ORA-24960: the attribute  OCI_ATTR_MODULE is greater than the maximum allowable length of 48
  Loading DB library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll' ...
  *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll")
Error 126 = "The specified module could not be found." [dlnt.c       255]
  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
  *** ERROR => Couldn't load library 'C:\usr\sap\AP1\DVEBMGS00\exe\dbsdbslib.dll'
[dbcon.c      5672]
  {root-id=0015C58921771ED2BD9D22A0E0973991}_{conn-id=00000000000000000000000000000000}_0
  ***LOG BYG=> could not load library for database connection LCA        [dbds         862]
  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]

we run /SAPAPO/OM17 for Product locations combination, shipments , deliveris and stock  every week for consistency check. Each week we get some inconsistencies for product locations with the message " Entry only in livecache" showing returncode 0.

message error -

Message Number: /SAPAPO/OM_SYNC002

in the details it shows some system generated IDs in the Pegging area column. we tried to look the Pegging IDs in the table /SAPAPO/PEGKEY in column pegging area,  these ID that were detected during the OM17 run are not found even to trace the product -location combinations.

the inconsistencies are then removed by the change option. These inconsistencies return back again.

we tried running all the other consistency check programs but of no use.

Can any one please let us know what could be the source of these inconsistencies , how to track the materials -locations with issues.

Hi,

I have installed SCM 7.0 EHP1.

Also Installed Live Cache Server (Not Installed Client Software)

Please check the attached screenshot.

I am getting "DBM Access is Possible - NO" Error.

SAPDB_DBM and SAPDB_DBM_DAEMON RFCs are Failing.

Live Cache Client software need to install ??? (SCM and Live Cache are there in same host)

Need to copy any files into SCM Kernel ???

Pls provide SAPDB_DBM and SAPDB_DBM_DAEMON RFC properties.

-------------------------------------------------

[root@cgiu1104a bin]# ./dbmcli inst_enum

OK

7.7.07.10    /sapdb/IDL/db

[root@cgiu1104a bin]#

---------------------------------------------

Following Max DB Processes are running -

[root@cgiu1104a bin]# ps -ef |grep sdb

root     23112 10844  0 17:14 pts/1    00:00:00 grep sdb

sdb      27161     1  0 14:36 pts/0    00:00:00 /sapdb/programs/pgm/vserver start

sdb      27162 27161  0 14:36 pts/0    00:00:00 xserver.prt logger

sdb      27753     1  0 14:36 ?        00:00:00 /sapdb/IDL/db/pgm/kernel IDL -diagpipe 14

sdb      27758 27753  0 14:36 ?        00:00:14 /sapdb/IDL/db/pgm/kernel IDL -diagpipe 14

[root@cgiu1104a bin]#

-----------------------------------------------------------

RFC Trace -

**** Trace file opened at 20160403 170412 EDT, by disp+work

**** Versions SAP-REL 722,0,101 RFC-VER U 3 1656744 MT-SL

======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

ABAP Programm: SAPLSADC (Transaction: )

User: DDIC (Client: 800)

Destination: SAPDB_DBM_DAEMON (Handle: 2, DtConId: 570122E564B30B77E10000000A0002CE, DtConCnt: 0, ConvId: ,)

EPP RootContextId: 0A1FC68A527F1EE5BEBBAB9DB9AFD293, ConnectionId: 5701137664B00B75E10000000A0002CE, ConnectionCnt: 1

EPP TransactionId: 5701222264B30B77E10000000A0002CE

SERVER> RFC Server Session (handle: 1, 20696474, {57011376-64B0-0B75-E100-00000A0002CE})

SERVER> Caller host:

SERVER> Caller transaction code: DB59 (Caller Program: SAPLSADC)

SERVER> Called function module: DBM_CONNECT_PUR

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1732

CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

DEST =SAPDB_DBM_DAEMON

HOST =%%RFCSERVER%%

PROG =dbmrfc@sapdb

cgiu1104a:id3adm 65>

---------------------------------------------------

stderr logs

/sapdb/programs/bin/dbmrfc: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

/sapdb/programs/bin/dbmrfc: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

/sapdb/programs/bin/dbmrfc: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

-------------------------------------------

WP Logs -

M Sun Apr  3 17:25:39 2016

M  ***LOG R49=> ThReceive, CPIC-Error (020456) [thxxhead.c   8134]

M  ***LOG R5A=> ThReceive, CPIC-Error (21998193) [thxxhead.c   8139]

M  ***LOG R64=> ThReceive, CPIC-Error ( CMSEND(SAP)) [thxxhead.c   8144]

A  RFC 3730  CONVID 21998193

A   * CMRC=20 DATA=1 STATUS=1 SAPRC=456 ThSAPCMRCV

A  RFC> ABAP Programm: SAPLSADC (Transaction: DB59)

A  RFC> User: DDIC (Client: 800)

A  RFC> Destination: SAPDB_DBM (handle: 25, DtConId: 570114DA64B00B75E10000000A0002CE, DtConCnt: 1, ConvId: 21998193,{570114DB-64B0-0B75-E100-00000A0002CE})

A  RFC> Called function module: DBM_VERSION

A  *** ERROR => RFC ======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup (check that partner exists)

[abrfcio.c    9225]

A  {root-id=0A1FC68A527F1EE5BEBBAB9DB9AFD293}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3732

CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup (check that partner exists)

[abrfcio.c    9225]

A  {root-id=0A1FC68A527F1EE5BEBBAB9DB9AFD293}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => RFC Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1984

[abrfcio.c    9225]

A  {root-id=0A1FC68A527F1EE5BEBBAB9DB9AFD293}_{conn-id=00000000000000000000000000000000}_0

Hi,

We are testing migration of SCM to SCM on HANA with integrated LiveCache in our lab box & now migrating

external LiveCache to Integrated LiveCahce migration.We have done all the steps upto step 5 as specified in the note 1825703. Not able to validate step number 6. We dont see APS_ORDER_GET_DATA under "Catalog => Public Synonyms" in the SAP HANA Studio and also we dont see role AFL__SYS_AFL_LCAPPS_EXECUTE. The LC installation step number 5 completed successfully without any error. The HANA DB connection (created in step 4) from DBACOCKPIT is working fine LCA,LDA and LEA.

Thanks

Vipin

Hello,

We have a SCM system on HANA DB with embedded Livecache.

LCApps and HANA are on the same version 1.00.097 and LCApps also initialized.

SCM Release is 713 SP 10.

In LC10 and DBACOCKPIT, the connections LCA, LDA and LEA exist and show green.

DB connection also shows green.

However, we are seeing multiple issues with regards to Livecache connectivity.

1) In DB59, there is no entry displayed.

2) In DBCONUSR, there is no entry visible.

3) /SAPAPO/OM17 consistency check gives error "Connection to livecache failed".

4) LCA03 also showing some errors:

At least on liveCache-table is not Row Store. Run program

/SAPAPO/OM_CREATE_LC_TABLES. If the problem is not solved contact SAP.

Ran this program but the error still exists.

Please help.

Thanks,

Arpit

Hello Guru's,

We are facing issue in starting Live cache , due to some maintainance activity we had to stop live cache and SCM system. But after restarting SAP system we are not able to start the livecache from LC10. Start and stop tabs are greyed out and hence doesnt allow to start livecache. We are getting below errors in LC10, we have already stopped the running Maxdb processes at OS level and renamed .SHI and .SHM files in the work directory but issue still persists.Could you please let me know if anybody has faced such issue before and how it was resolved.

We are running on live cache 7.9.08.10.

Exception CX_DBA_ADBC in class CL_SDB_ADBC method DBM_EXECUTE line 82 / RC=ADBC error

Exception CX_DBA_ADBC in class CL_SDB_ADBC method DBM_EXECUTE line 82 / RC=ADBC error

SQL not possible

SQL Error: 10709

Connection failed (RTE:[5] database not running)

DBM not possible

Error when calling function module DBM_EXECUTE_SDB

Command:                                dbm_version

Function            : DBM_EXECUTE

Command             : dbm_version

Error               : DBM Error

Return Code         :         0

Regards

Prashant

Hi Support,

1. We have system copy from production to sandbox system and performed the

Upgrade of sandbox system (SCM 7.0 EHP1 to EHP2 , Live cache from 7.7 to 7.9 version

In this connection, we have upgrade the live cache from 7.7 to 7.9 version and upgrade the

build.

Now the LC kernel version is: 7.9.08 Build: 002-123-245-176.

From ABAP point of view, we dont have any issues. But from Live cache perspective , we are

encountering many dumps.

We are unable to execute the transaction: /n/SAPAPO/OM03 ,/n/SAPAPO/OM13

====================================

The error 600 occurred in the current database connection "LCA".

Error Text of Database: "POS(1) Work rolled back: tExcept 30708 in

SIM_SIMSESSION"

SQL Statement Responsible:"EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""

=================================================

The error 600 occurred in the current database connection "LCA".

Error Text of Database: "POS(1) Work rolled back: tExcept 30708 in

APS_COM_VERSIO"

SQL Statement Responsible:"EXECUTE PROCEDURE "APS_COM_VERSION_GET""

===============================================================

The error 600 occurred in the current database connection "LCA".

Error Text of Database: "POS(1) Work rolled back: tExcept 30708 in

APS_MLEVEL_ATP"

SQL Statement Responsible:"EXECUTE PROCEDURE "APS_MLEVEL_ATP_PROT_DEL""

===================================================================

Please provide us a work around to fix these dumps.

Venkat

Hi Experts,

We are planning to do SCM 7.0 EHP2 upgrade from SCM 7.0.

I have few questions regarding upgrade of SCM and Livecache 7.7 to 7.9 .

1. Is it possible to upgrade the SCM alone with out livecache upgrade .Or is it mandatory to upgrade livecache too with SCM upgrade .

2. Whether livecache should be upgraded before or after SCM 7.02 upgrade .

3.how to do Parallel upgrade of SCM and Livecache . things to do for parallel upgrade .

4. Which upgrade is best , Livecache upgrade after SCM upgrade or parallel upgrade of Livecache and SCM.

5.As per upgrade guide there are two method for livecache upgrade one is extract/load & another is inplace upgrade, which one we need to follow.

Please help me to clarify this things .

Thanks

Alok

Hello Experts,

Whenever i execute LC10, i see 3 DB connections - LCA, LDA and LEA.

I do have some basic questions which i couldnt find answers for:

1. How to find out which DB connection is used in the system - LCA, LDA or LEA.

Or all the three will be used for LC to be functional?

2. If only LCA is used, how to uninstall or remove the connections for others?

Thanks,

Subbu

Hi Expert,

I will be migrating my SCM(APO) system from Oracle to Sybase. The migration will take place on the same server. Currently, the SCM is attached to a Livecache running on MaxDB.

My question is, should I re-install the LiveCache on the new Sybase system? How can I make sure the new Sybase SCM system is connected to the existing LiveCache?

Hope to get ideas and feedback.

Thanks,

SS

HI,

We have an issue with the SAP APO Standard Background Job "/SAPAPO/OM_REORG_DAILY".

1. Job Scheduled in the Right client.

2. Job Terminating with the error as below.

Please help.

Hi Experts,

We are planning to do SCM 7.0 EHP2 upgrade from SCM 7.0.

I have few questions regarding upgrade of SCM and Livecache 7.7 to 7.9 .

1. Is it possible to upgrade the SCM alone with out livecache upgrade .Or is it mandatory to upgrade livecache too with SCM upgrade .

2. Whether livecache should be upgraded before or after SCM 7.02 upgrade .

3.how to do Parallel upgrade of SCM and Livecache . things to do for parallel upgrade .

4. Which upgrade is best , Livecache upgrade after SCM upgrade or parallel upgrade of Livecache and SCM.

5.As per upgrade guide there are two method for livecache upgrade one is extract/load & another is inplace upgrade, which one we need to follow.

Please help me to clarify this things .

Thanks

Alok

We have patched LCAPPS 70.21 PL 002 & liveCache 7.7.07.42 according to SAP Note 1751103.

After patching we started LiveCahce, and tried to connect using LC10 and its keeps on going. We are not able to get the next screen. Same thing  happens for DB59; n/sapapo/om17 --> Consistency Check LiveCache.

SCM 7.01 SP08

LiveCache: 7.7.07.42 

Bhavin

Hi Gurus,

I am getting below issue while during upgrade of Live cache from 7.7 to 7.9 version, below is the command I am running from the Upgrade guide

LCUPDATE.BAT -s <SAPSID> –d <liveCache name> -u <DBM,DBM password>

& while running the command on window server I got below error:

ERROR: The usage parameter db_name is not set.

USAGE: LCUPDATE [options]

[options] for the SAP liveCache server upgrade:

        -s       sap_name         (SAP system name)

        -d       db_name          (SAP liveCache name)

        -u       dbm,dbmpasswd    (DBM user authorization)

[options] for the SAP liveCache client upgrade:

        -s       sap_name         (SAP system name)

        -client                   (client software upgrade)

[options] optional:

        -dir     tmp_directory    (temporary working directory)

Could you please help on the same. I have already upgraded SCM 7.0 EHP1 to EHP2.

Regards

Bhupender

Hello Guru's,

We are facing issue in starting Live cache , due to some maintainance activity we had to stop live cache and SCM system. But after restarting SAP system we are not able to start the livecache from LC10. Start and stop tabs are greyed out and hence doesnt allow to start livecache. We are getting below errors in LC10, we have already stopped the running Maxdb processes at OS level and renamed .SHI and .SHM files in the work directory but issue still persists.Could you please let me know if anybody has faced such issue before and how it was resolved.

We are running on live cache 7.9.08.10.

Exception CX_DBA_ADBC in class CL_SDB_ADBC method DBM_EXECUTE line 82 / RC=ADBC error

Exception CX_DBA_ADBC in class CL_SDB_ADBC method DBM_EXECUTE line 82 / RC=ADBC error

SQL not possible

SQL Error: 10709

Connection failed (RTE:[5] database not running)

DBM not possible

Error when calling function module DBM_EXECUTE_SDB

Command:                                dbm_version

Function            : DBM_EXECUTE

Command             : dbm_version

Error               : DBM Error

Return Code         :         0

Regards

Prashant