Hello,

We have a SCM 7.0 system with EHP 3 with a liveCache (MaxDB 7.9.08) .

If I click the button "liveCache Monitoring with DBA Cockpit" in the TX LC10, I get the following error for each database connection (LCA, LDA and LEA) :

In the TX SM21 you can see the error message below:

     Database error -10709 at CON

     > Connection failed (RTE:[1] cannot connect to server socket)

Im Trace-File dev_w0 I found the following:

     Connect to LCA as SAPLCD with <IP-Address>-LCD

     Try to connect as SAPLCD/<pwd>@<IP-Address>-LCD on connection 1 ...

     *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] cannot conn

     bmaxsql.cpp 607]

     {root-id=54217256A7094810E1008000AC110048}_{conn-id=00000000000000000000000000000000}_0

     ***LOG BY2=> sql error -10709 performing CON [dbds         919]

     ***LOG BY0=> Connection failed (RTE:[1] cannot connect to server socket) [dbds         919]

I would like to mention, that I have maintained the liveCache Integration as follows:

     Name of Database Connection: LCA (or LDA or LEA)

     liveCache Name: LDA

     liveCache Server: here I tried with the IP-address and also with the physical hostname, but none of them worked

     DBM User:

          User Name: CONTROL

          Password:    xxx

      Standard liveCache User:

          User Name: SAPLCD

          Password:    xxx

Furthermore, I have checked at database-level, the liveCache is up and running and the passwords are correct:

     dbmcli -d LCD -u control,<password> db_state

     OK

     State

     ONLINE

     dbmcli -d LCD -u saplcd,<password>

     dbmcli on LCD>

But in the TX LC10 the buttons "Start liveCache" and "Stop liveCache" are watermarked.

I have already tried to restart the liveCache and the SCM-system, but without success.

In my opinion the cause is, that the liveCache cannot be reached from the SCM-system.

Could you please advise?

Thanks a lot in advance.

Kind regards,

Noémi

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,

Every time that Livecache is started the report SLCA_LCK_SYNCHOWNERS is executed.

Starting the livecache with the different start options (LC10, report RSLVCSTART, from O.S level) this report is always executed?

Regards.

Hello,

We face this error on our SCM system after migrating to EHP3 (from EHP2). Short DUMP details :

Error "-60" has occurred on the current database connection "LCA".

Database error text: POS(1) Work rolled back: ERROR 30709 in LCK_ENQUEUE02: S

Triggering SQL statement: "EXECUTE PROCEDURE LCK_ENQUEUE02"

LiveCache version is : 7.9.08.29 / Kernel    7.9.08   Build 029-123-252-402

SCM version is 713 SP8

Does someone faced this error before?

Hello,

I've scheduled the task Update Statistics for Selected Tables on DB13 and I'm always getting an error that says:

ERROR : SELECT schemaname, tabname FROM "/MAXDB/UPDSTATS"

rc = -942 (POS(34) Unknown table name:/MAXDB/UPDSTATS)

I've tried to looking for this table but It doesn't exist "schema"."/MAXDB/UPDSTATS" Not Found

What differente there between this task and Update All Optimizer Statistics?

Regards.

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,

we are in the situation where we will move our APO system from an inhouse server, to a server provided by an external vendor.

A question/issue has come up regarding live cache. We are on an old release 4.6 and live cache version 20, according to SAP newest version is 50 and they do not recommend to go lower than version 32.

The idea is to move APO and forget the current live cache and rebuild it with the new version. For transactional data, can this be done by simply transferring data again from connected ERP systems or will we face new problems?

Thanks,

Lars

Hello Experts,

We have plan to Migrate of SCM DB2 DB from AIX to RHEL7.

Our LiveCache LC is on SUSE Linux & will not migrate to RHEL7 as per current design unless, otherwise this combination is not supported ( Exploring more on supportability aspects).

I have below questions:(based on assumptions that LC will not be migrated)

1 - Only exporting & importing SCM DB is sufficient? If Yes, can someone outline LC related steps that I still need to perform in this      scenario.?

2 - Since I am assuming here that LC will not be migrated do I still need to runreport /SAPAPO/OM_LC_DOWNLOAD_UPLOAD            before & after SCM DB Migration to download & upload LC Objects to & from SCM DB respectively?

3 - I am checking on PAM & with SAP, meanwhile if someone already know -  Is below combination of Target is supported ?:

SAP SCM application -- SUSE Linux

SCM DB2 DB -- RHEL7.1

SCM LC - SUSE Linux

Best Regards

Sachin

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

Hi,

We are having abap dumps in APO system related to above DBIF_DSQL2_CONNECTSTR_ERROR

Details:

Runtime Errors         DBIF_DSQL2_CONNECTSTR_ERROR

ABAP Program           CL_RSDRS_SQL_QUERY============CP

Application Component  BW-BEX-OT

Short Text

    The connection identifier is not known.

What happened?

    The connection identifier points to data in table DBCON that is

    required to create a database connection for multiconnect. No entry has

    been defined with key " " however.

Error analysis

    Triggering ABAP statement: Connect to " "

This is affecting /SAPAPO/* loads, I believe this is related to livecache, but unfortunately the SAPnotes I have checked were all pointing to description of issue "... defined with key "LCA"" or with "LCA", this does not.

Anyone has experience with this issue and resolution?

Thanks

After system copy we are getting a livecache error when we want to de-initialize and initialize the planning areas.  Any ideas?

Hello,

I am trying to create a new SCM quality system by making a copy of production system using backup/restore. I am a basis person and this is my first time working on SCM system. Please note that we want to copy both SCM database and also the data in livecache database. The SIDs for both SCM and Live cache instance are changing. I have read multiple notes (1015489, 886103, 877203, 457425, 1030857, 1349272 etc) and some GREAT POSTS in this forum BY NATALIA KHLOPINA. Thanks to this info, I have done the following so far:

SCM version is 7.0 SP 11 and Livecache version is 7.7.7.

I first copied over the SCM database using backup restore.

Installed the SCM target system with the new SID

Installed Livecache instance for target system (on a separate host than SCM) using swpm

Then I initialized the maxdb instance via DB manager

then I did restore and initialize using the full backup that I had taken of source livecache system via DBM GUI (pretty much steps in note 457425)

Then ran the following command : load_systab -u superdba,admin

(ran into some issues in between but resolved one by one like upgrading kernel, re-restored the db afer change default_code to Unicode etc )

Then in LC10, LCA -  I registered LCAPPS

Then in LC10, I did the integration configuration for LCA connection (it was blank due to some reason after the copy). Also reentered the u/p for LDA and LEA connections.

The LC10 connections are coming up green to livecache

Firstly, can you verify the steps above are correct so far ?

Secondly, I am trying to follow the notes 1015489, 886103, 877203, 457425 and 1030857, 1073954 to do post copy steps and have the following issues/questions:

1) In note 1015489 (connection problems after system copy),  it says to run report SLCA_GET_SYSNAME to get system name in livecache. When I do so, It says "Table for system names does not yet exist". Is that normal ( I am on scm 7.0 SP11) ? If I go to dbmcli and try to drop table APPSYSPARAM or APPSYSNAME, it says table does not exist ?? How do I verify if correct system name is registered in livecache?

2) Note 886103 (system landscape copy for SCM) -- It says to change logical system name in /SAPAPO/ORDMAP but this table is not active in my dictionary !! same for table CIFRFCDES and table /sapapo/cifdistr does not exist ??

3) Note 886103 says that if you want to rename the user SAPR3 to SAPEL1, you run some dbmcli commands. Is this necessary ?? my Livecache id is changing from LIP to LIQ, so shall I change it ? The domain.users currently shows control , superdba and also SAPLIP user and SAPLIQ user (SAPLIQ user only started showing up after I registered LC APPS ). Do I need to do anything else or verify something ?

4) Note 877203 once again talks about SAPEL1 user and I am not sure if I need to run these steps or not

5) Note 1030857 tells to run this report zz_update_acckey to correct the external keys. Is this necessary even if we run BDLS ? Shall I ask the SCM functional person ?

6) Note 1073954 (effects of changing the standard livecache user) -- How do I know if I need to run this ? my livecache tables like /sapapo/ordmap are stil owned by SAP<OLDSID> but  in LC10 connections I have changed the three connections to use SAP<NEWSID> user and the connetions are green and connection tests in db59 are also successful !!.

The note says that "Only change the standard liveCache user if the system does not contain any data or if you initialize the liveCache directly after the change"

My copied over livecache does contain data and If I initialize the livecache after changing this user id, I guess I will loose the data. So, Can I skip this step as long as connections in LC10 and db59 are working okay ?

7 ) How can I verify that APO optimizer is also installed in Production system. I thought it was optional to install it and I don't know if this client is using it ?

Sorry for this long long post. Hope someone out there has patience to clarify my doubts.

Thanks

BV

Hi All,

Background job for program "/SAPAPO/SDRQCR21" is failing in SAP SCM 7.0 system due to below error message.

"Problems accessing SAP liveCache"

There was no dump or any error message in SM21 at the time job failure or durig the job run. I have also checked the live cache availability and live cache was up and running during this time. Trace log shows that SCM system was able to connect live cache successfully.

******************************************************************************

07:48:21 2015

B  Connect to LCA as XXXADM with XXX.XX.XXX.com

C  Try to connect as XXXADM/<pwd>@XXX.XX.XXX.com on connection 1 ...

C  Attach to SAP DB : Kernel    7.7.07   Build 045-123-247-303

C  Database release is SAP DB 7.7.07.045

C  INFO : Database 'XXX' instance is running on 'XXXXX'

C  DB max. input host variables  : 2000

C  DB uses MVCC support          : 0

C  INFO : LVC DEFAULTCODE = UNICODE

C  INFO : Connect to DB as 'XXXADM'

C  Command info enabled

C  Now I'm connected to SAP DB

C  01: XXXXX-XXX, since=20150807074821, ABAP= /SAPAPO/SAPLOM_CORE (5250)

B  Connection 1 opened (DBSL handle 1)

*******************************************************************************

But later batckground job was cancelled automatically and in next 3 seconds WP got restarted. SCM system was disconnected from Livecache.

*******************************************************************************

09:52:16 2015

M  ThNeedWpRestart: abap strategy == kill, restart

M ThWpRestart: restart wp (pid=12864) automatically

B  Disconnecting from ALL connections:

B  Wp  Hdl ConName                        ConId     ConState     TX  HC  PRM RCT FRC TIM MAX OPT Date     Time   DBHost

B  003 000 R/3                            000000000 INACTIVE     NO  NO  YES NO  NO  000 255 255 20150807 045113 YYYYY

B  003 001 LCA                            003034031 INACTIVE     NO  NO  NO  NO  NO  004 255 255 20150807 074821 XXXXX

C  Disconnecting from connection 0 ...

C  Closing user session (con=0,svchp=0x969c3d8,usrhp=0x96de3f0)

C  Detaching from DB Server (con=0,svchp=0x969c3d8,srvhp=0x969ee68)

C  Disconnected (con=0) from ORACLE.

B  Disconnected from connection 0

C  Disconnecting from connection 1 ...

C  Now I'm disconnected from SAP DB

B  Disconnected from connection 1

********************************************************************************

I suspect this is a heap memory issue. As heap memory got exausted, work process was restarted automatically and when it tried to connect Livecache, it couldn't connect and job failed with an error "Problems accessing SAP liveCache". But the log doesn't show any reference to it.

Another blog Report /sapapo/sdrqcr21 - problem accessing liv... | SCN   talks about the simliar problem, but I could not see function module /SAPAPO/OM_PEG_CAT_GET_ORDERS, so not sure whether it is relevant or not.

Kindly request you to suggest on this.

Regards,

Suhas

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

Hello,

We are experiencing long runtime with program /SAPAPO/SDORDER_DEL when we run with below options ticked

- Adjust ATP Tables with /SAPAPO/POSMAPN

- Delete Obsolete Records in the /SAPAPO/POSMAPN Table

A single instance of this job runs weekly for all locations. The runtime is typically 8 to 10 hours.

In order to reduce the runtime, we want to split the job into multiple instances and run it parallely for blocks of locations. i.e. I have 50 locations in my system and I want to run 5 instances of this program in parallel each with 10 of the locations.

Do I need to have the below two ticks only in one of these variants or I can have them in all 5 variants?

- Adjust ATP Tables with /SAPAPO/POSMAPN

- Delete Obsolete Records in the /SAPAPO/POSMAPN Table

I was referring to the note

Note 894294 - /sapapo/sdorder_del: Performance and advice (as of SCM 4.0)

This note says below:

At least for the first time you run the report, we recommend that you run it several times in succession using the following parameters:

1) "Selective deletion" with a corresponding selection of product, location and so on, it may also be necessary to run it in blocks according to product and/or location.

2) Use /SAPAPO/POSMAPN to compare ATP tables

3) Delete obsolete records in the /SAPAPO/POSMAPN table

If, however, you split the 'Selective deletion' option into selection blocks of products and/or locations, note that the other options (2 and 3) are independent of this split. Ensure that these options (2 and 3) are processed only once in each case.

Can somebody help me to understand how to use the options (2 and 3) in multiple parallel instances of the program /SAPAPO/SDORDER_DEL?

Thanks in advance

Ehsan Ahmed

Hi ,

What is ideal response time for livecache 7.9 MaxDB.on SCM 7.0 EHP3

how to find it out and navigation ..please

Thanks in advance

Hello,

We have a SCM 7.0 system with EHP 3 with a liveCache (MaxDB 7.9.08) .

If I click the button "liveCache Monitoring with DBA Cockpit" in the TX LC10, I get the following error for each database connection (LCA, LDA and LEA) :

In the TX SM21 you can see the error message below:

     Database error -10709 at CON

     > Connection failed (RTE:[1] cannot connect to server socket)

Im Trace-File dev_w0 I found the following:

     Connect to LCA as SAPLCD with <IP-Address>-LCD

     Try to connect as SAPLCD/<pwd>@<IP-Address>-LCD on connection 1 ...

     *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] cannot conn

     bmaxsql.cpp 607]

     {root-id=54217256A7094810E1008000AC110048}_{conn-id=00000000000000000000000000000000}_0

     ***LOG BY2=> sql error -10709 performing CON [dbds         919]

     ***LOG BY0=> Connection failed (RTE:[1] cannot connect to server socket) [dbds         919]

I would like to mention, that I have maintained the liveCache Integration as follows:

     Name of Database Connection: LCA (or LDA or LEA)

     liveCache Name: LDA

     liveCache Server: here I tried with the IP-address and also with the physical hostname, but none of them worked

     DBM User:

          User Name: CONTROL

          Password:    xxx

      Standard liveCache User:

          User Name: SAPLCD

          Password:    xxx

Furthermore, I have checked at database-level, the liveCache is up and running and the passwords are correct:

     dbmcli -d LCD -u control,<password> db_state

     OK

     State

     ONLINE

     dbmcli -d LCD -u saplcd,<password>

     dbmcli on LCD>

But in the TX LC10 the buttons "Start liveCache" and "Stop liveCache" are watermarked.

I have already tried to restart the liveCache and the SCM-system, but without success.

In my opinion the cause is, that the liveCache cannot be reached from the SCM-system.

Could you please advise?

Thanks a lot in advance.

Kind regards,

Noémi

Hi,

we are migrating (with DMO) our SCM (APO) system with external liveCache (SapDB) to HANA with integrated liveCache.

After SUM stops in phase "Restore liveCache" we run program /SAPAPO/OM_LC_DOWNLOAD_UPLOAD and executed steps "Load Master Data" and "UploadliveCache Data" without errors.

After performing step 6. "Compare liveCache with Download" (in Section C) we get a lot of ( about 3.000) warnings in protocol (see also attached file):

(...)

Produktionsauftrag BO2922 (Eigenf.): Dates/times changed by up to 82801 seconds

Produktionsauftrag BO2330 (Eigenf.): Dates/times changed by up to 54000 seconds

Produktionsauftrag BO1865 (Eigenf.): Dates/times changed by up to 32400 seconds

(..)

Why is there such a big gap between liveCache and download?

Kind regards

Stefan

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