APO & LiveCache Move

Hello World,
another step in the never ending drama of SAP Upgrades.
After the battle for the EHP7 upgrade of your ERP servers was, finally, won, its now time to mess around with our APO/LiveCache servers.
Resource and time constraints forced us to take some unorthodox measures here.
The source servers are based on SLES9/MaxDB 7.7.
To prepare for the upgrade I installed SLES11 + MaxDB7.9 on brand new servers, then restored the MAxDB databases for APO & LC and the SAP kernels to the new servers, for a first test run of the upgrade.
APO came up just fine, so did LC.
XUser setup, DB59, RFC connections, all seems "hanky dory", except in LC10 the system complains about "LiveCache lock server unreachable/not installed".
The strange thing is that LC10 shows LiveCache being up & running, and all connection lights are green and the x_server is likewise running.
At first I thought it was a misconfigured DB user, but I tested all connections in DB59 and they all work OK.
This is my first move of an LC system, so I surely missed something here, but what could it be?

I made a bit of progress here (even so nobody from SAP has even looked at my ticket yet).
Whenever trying to start LCA, it throws an exception of "CX_SY_NATIVE_SQL_ERROR":
Procedure LCA_LCK_LIST_OWNERS -> Synchronization of the Lock Owner of the liveCache Lock Server
I had restored the entire LC DB from source from scratch again (just in case something went wrong last time), (re)set the CONTROL, SUPERDBA and <SID>ADM passwords manually, did a systab load (Source: MaxDB v7.7; Target MaxDB v7.9) and brought the whole thing db_online w/o errors.
I double checked that I could logon with all the relevant MaxDB users with the specified password(s) on CmdLine, and sync'ed the integration data for all connections correspondingly in LC10.
Still, its all to no avail, so I start to question if LC is compatible with MaxDB 7.9???
PS: Thetests in DB59 work just fine for all connections - honestly I'd be happier if they wouldn't, cause it would help me narrow down the root cause of this mess.

Similar Messages

  • APO Livecache DB Backup and Livecache Auto Log Backup

    Hi Guys,
    Could you please help me here which tranaction code we use to  check APO Livecache DB Backup and Livecache Auto Log Backup
    Thank you

    Hi,
    Livecache DB and log back up looks like can not be accessed from SAP. Database Manager GUI is used.
    Please check the below link for helpful information.
    http://help.sap.com/saphelp_nw04/helpdata/en/f7/499e3c1fbe8c15e10000000a114084/content.htm
    Regards,
    Saravanan V

  • APO livecache logging with SCM 7

    I am trying to understand how APO livecache logging works with APO release 7.
    OSS Note 385808 suggests that, for APO DP release 3, there is no logging.
    But what is the situation with APO release 7, for DP, SNP, PP/DS, GATP?
    Thanks for any information on this point...

    Hi,
    We had upgraded SCM 4.1 to SCM 7.0. No need to change to DTP after upgrade. All the objects of previous version would be there and can be used as usual. But our BW upgrade is from 3.1 to BI 7.0.
    Regards,
    Saravanan V

  • (SCM-APO ) - LiveCache error - tp error : operable program or batch file

    Dear Gurus,
    On one our APO systems, I cannot administer liveCache, using database connection LCA, LDA, or LEA. Using LCA as an example, with
    tcode LC10> liveCache Monitoring, I get this error:
    Name and Server :    QDP - ntsapsc001
    DBMRFC Function  : DBM_CONNECT
    Error : DBM Error
    Return Code : -11
    Error Message : tp error: operable program or batch file
    Using tcode /sapapo/om13, I get these results:
    liveCache connection to LCA      (GREEN)
    liveCache Stat. from LCA     ???    (RED)
    liveCache Initialization          001   (RED)
    Using tcode SE38> program RSLVCINIT > database connection LCA, I get this error:
    Error in DBMSERVER or DBMCLI
    What is wrong ?
    Thanks and regards,
    cjperk90

    In the syslog (tcode sm21), and on the NT server's syslog,
    I also get these errors:
    Database error -10709 at CON
    > Connection failed (RTE:database not running)
    Please advise.
    Thanks,
    cjperk90

  • APO livecache

    I am faceing problem with live cache is down ....when i was checked xsercer is down then i start the xserver and check at sap level LC10 it shows down...i tryed to start the livecache at sap....but it shows error message...Error DBMCLI_COMMAND_EXECUTE_ERROR when starting liveCache DAL on server.
    please any body help on this issue....

    Hello Adil,
    Please post this question to the forum MAXDB/liveCache if you have questions about MAXDB or liveCache!!
    To get clear on your problem additional information needed:
    -> What is the version of the liveCache?
       < check the version of the liveCache in the knldiag file, for example.
         Update with the output of the command 'sdbregview -l', run it on the liveCache server. >
    -> What is the version of your SCM system?
    -> Check the lcinit.log after you restarted the liveCache in the LC10 transaction.
    -> Check errors in the current knldiag file < located in the liveCache Rundirectory.>, knldiag.err & dbm.prt.
    -> Check the errors in /nsm21<system logs> & corresponding dev log of the WP at the time you restarted the liveCache in LC10.
    If you are the official SAP customer, I recommend you to create the ticket to SAP on 'BC-DB-LVC' queue!
    Thank you and best regards, Natalia Khlopina

  • SCM/APO - Livecache client copies?

    The basis team have been asked to do a client copy (refresh) from
    production for ECC, CRM, BW & SCM. I know how to perform the client copybut am not aware of what post processing has to happen with LC(Maxdb).
    Does this have to be refreshed??? Please provide location of
    documentation to perform this. I stress this is not a system copy but a
    client copy.
    Thanks & Regards,
    Frank Magliozzi

    Hello Frank,
         So sorry, it was NOT clear for me if you are going to do a System Landscape Copy for SAP SCM   
         or a client copy on SCM => I would like to give you the following information::
    -> Please review the SAP notes::
                For the Homogenous copy of the liveCache see:
                        457425     Homogenous liveCache copy using backup/restore              
                        877203     Post steps after the Homogenous liveCache copy
                  For the heterogeneous copy of the liveCache see:
                        632357  Backing up liveCache data for SCM 4.0 or higher
             886103     System Landscape Copy for SAP SCM   
             888210       NetWeaver 7.0/7.10: System copy (supplementary note)
    -> Please review the documentation at
                    service.sap.com/scm -> SAP SCM Technology
                -> "SAP System Landscape Copy for SAP NetWeaver and mySAP Solutions "
         < Information on SCM 4.1 and prior releases
                       Information on SCM 4.1 and prior releases you will find here.
                   -> click on <here> -> Installation, Upgrade, Migration, System Copy, Client Dependencies
    ->  Please pay attention to SAP notes before to run a client copy:
                        914199      Loss of data in the liveCache after a client copy
                        894490     Client copy: Transactional data
                        900812     Client copy does not work completely
                       629660     SCM systems with clients that are not liveCache-relevant
    If you have further questions/problems with MAXDB/liveCache database, please post the question at MAXDB/liveCache forum SAP MaxDB
    Thank you and best regards, Natalia Khlopina

  • How big is SCM/APO/Livecache/TM customer base?

    Becuase these products are not used by some sectors such as finacial sector, etc., they
    used to have a small customer base.
    I have heard that now more companies start to use it.
    Is that true?   Thanks!

    Hi Jennifer,
    the answer to this depends on what you define as 'small'.
    It's correct that many of the optimization functions are based in production and supply chain management and that they are used most often for this as well.
    I'm not aware of any optimization option available for SCM that might be used for the financial/banking sectors - but hey, I'm just a database guy 
    Anyhow, there are literally thousands of active SCM/liveCache installations that are heavily used by our customers and that are and inevitable building block of their processes.
    Hope that answers your question.
    regards,
    Lars

  • How to Install an APO Livecache on Windows Using Virtual Host Names

    Hi,
    How to Install Live Cache on windows using Virtual Host names?
    we are using SCM 4.0 with  live cache build 7.4.3 on two differnt servers.
    I have checked the Live cache CD (7.4.3) is with setup.cmd, where as it need use command sapinst.exe SAPINST_USE_HOSTNAME=Virtual hostname.
    Please advise.
    Thanks
    Anil

    a possible workaround (that I have no tested) is to temporarily name your server with the same of the virtual name, install. when completed, rename server to original name.
    This is not a proven method, but it might work.

  • SCM , APO and Livecache administration

    Hi SAP Guru's
    Can any one guide me what is role and responsibilities of SCM and APO and Live cache administration as part of Basis.
    I will be great help if any one can guide me in SCM and APO and LIVE cache administration.
    Waiting for Reply
    Farooqui

    Hi Farooqui
    Since this Forum handling more application related topic, it is better to post your question in different Forum "MaxDB/liveCache ".
    Above MaxDB/liveCache is handling more basis and liveCache related topic.
    As a general information, SAP provides following documens that describe task and check point related to SCM system and liveCache. So I recommend you to check following 3 documents.
    URL : http://service.sap.com/solutionmanagerbp
    Number
    44            System Monitoring for SAP APO (3.x) / mySAP SCM (4.x/5.0)
    34            Monitoring and Administration for SCM / APO
    42            Checklist for Recovery of SAP APO liveCache >= 7.4
    Also there are some documents that describe liveCache behavior, so for better understanding,
    I also recommend you to check following 2 documents. (The information is bit old. but it might be helpful to understand liveCache).
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/66f7351f-0801-0010-96b4-f91d424b9d08
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/72cdbe90-0201-0010-6986-eae36eb6c819best regards
    Keiji  Mishima

  • Multiple LiveCache Instances Sharing the SAPDB software

    Hello
    We have two LiveCache Instances sharing the same set of executables for the SAPDB software and we are trying to apply a patch  for DBMServer 7.5.0 Build 035  to get to Build 044 for SCM 4.1
    I got the following error when I try to use SDBUPD
    beginning to check sap db instances
    existing instances:
    0:  LCT   "/sapdb/LCT/db"  7.5.0.31
    1:  LCX   "/sapdb/LCT/db"  7.5.0.31
    2:  none
    please enter instance id: 1
    no instance update supported - there are more than one instance based on instal"
    SAP liveCache instance update exited abnormally at Fr, Aug 01, 2008 at 21:25:53
    So I used SDBINST with APO LiveCache as the profile to install the software to /sapdb/LCT/db. Then I executed load_systab and load_lcapps using dbmcli for LCX. I would like to know if I am missing any of the steps. Please advise.
    Thanks
    Jay

    Hi Jay,
    sharing one dependent path for two liveCache instances is not supported - exactly due to the tight coupling of SCM and liveCache and the issues resulting from it when patching on of the two liveCaches.
    To 'move' over the LCT to the newly installed dependent path you've to unregister the instance first (aka db_drop withoutfiles) and re-register it as a new instance.
    Make sure you've a backup before you do this!
    1. bring liveCache LCT offline
    2. dbmcli -U c db_drop withoutfiles
    3. dbmcli u2013s u2013R <new_dependent_path> db_create LCT control,<password>
    4. bring liveCache LCT online again
    After that the LCT liveCache runs in its own dependent path and you can upgrade the two instances separately.
    Regard,
    Lars

  • LiveCache Consistency Check question, OM17

    I have a general question about a LiveCache Consistency Check (transaction OM17).  I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache.  But what does that mean to a functional user?  Can someone explain this in layman's terms?

    In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
    Here is a detailed documentation on each of the Object Types
    Consistency Check for Setup Matrices
    The consistency check for setup matrices contains:
    · A check whether the setup matrices exist in liveCache
    · A check whether the setup transitions exist in liveCache
    · A field comparison between the setup transitions in the database and those in liveCache
    When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
    Consistency Comparison for Block Basis Definitions
    Use
    When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
    · The existence of block basis definitions is checked.
    · The consistency of the characteristic values is checked.
    After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
    Note
    The check is performed independently of the planning version.
    Consistency Check for Resources
    The consistency check for resources contains:
    · A check that the resource and corresponding time stream exist in liveCache
    · An check that a resource's characteristic blocks exist in liveCache
    · A field comparison between the database resource and the liveCache resource
    When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
    Consistency check for downtimes caused by maintenance order
    The consistency check for maintenance downtimes contains:
    A check that the maintenance downtime has a reference to an existing maintenance order.
    A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
    When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
    Consistency Check for Product Location Combinations
    Use
    If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
    · A check for the existence of a product location combination in the database and in liveCache
    · A field comparison between product location combinations in the database and in liveCache
    · The determination of obsolete entries for product location combinations in the database
    · A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
    · A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
    After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
    Consistency Check for Stocks
    Use
    If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
    · A check for the existence of a stock in the database and in liveCache
    · A field comparison between stocks in the database and in liveCache
    · The determination of obsolete entries for stocks in the database
    · A check for the existence of characteristic value assignments in the database and in liveCache
    · A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
    After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
    After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
    Consistency Comparison of Configuration/CDP for Orders
    Use
    When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
    · In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
    · In the case of products with CDP, the system checks whether CDP characteristics exist.
    Note
    In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
    · For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
    After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
    After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
    Dependencies
    The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
    Consistency Check for Production Campaigns
    If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
    You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
    Consistency Check for Operations
    In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
    Consistency Check for Planning Matrices
    As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
    The consistency check for planning matrices checks:
    · Whether the matrices associated with each record on the database exist in liveCache
    · Whether the records associated with all the matrices in liveCache exist on the database
    · Whether the last matrix explosion was successful.
    If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
    Consistency Check for Simulation Versions
    This is a check for whether simulation versions exist in liveCache.
    Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
    Consistency Check for Product Allocations
    The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
    The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
    There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
    · Number of characteristics combinations
    · Number of periods in a time series
    · Number of sales orders that take product allocations from a time stream
    Error in the reconcile
    If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
    Check:
    · If the planning area to be checked is locked
    · If the time streams are initialized (after liveCache has been initialized)
    · If all characteristics combinations area available in the planning area
    · The wildcard indicator for collective product allocation
    · The settings for your planning area
    Due Delivery Schedules/Confirmations Consistency Check
    When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
    The following individual checks are made for active sales and distribution scheduling agreement items:
    · Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
    · Is there a confirmation in the database, but no associated liveCache object?
    · Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
    · Is there a confirmation in liveCache, without an existing confirmation in the database?
    · Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
    · Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
    If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
    · Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
    · Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
    Consistency Check for Production Backflushes
    Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
    Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
    Consistency Check for iPPE Objects
    The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
    The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
    It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
    Consistency Check for Procurement Scheduling Agreement Items
    The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
    1. Scheduling agreement schedule lines
    2. Release schedule lines
    3. Confirmations
    All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
    If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
    A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
    1. The object is not in liveCache but goods receipts exist.
    2. The number of input nodes and output nodes is different.
    3. There are no input nodes at the order, but the material exists in the source location for the order.
    4. The original quantity at the source of an order is different from that at the destination.
    5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
    6. The set process is compared with the status in liveCache.
    7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
    If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
    Consistency Check for MSP Orders
    Provides a list of maintenance and slot orders that
    ·     Exist in the database but have no corresponding orders in the liveCache
    ·     Exist in the liveCache, but have no corresponding orders in the database
    Procedure
    From within the list, you can either
    ·     Correct the inconsistencies
    If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
    You receive a message that the selected order(s) have been deleted.
    ·     Leave the inconsistencies in the database and/or liveCache
    Such inconsistencies place an unnecessary load on the database and/or liveCache.  Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
    Hope this helps
    Regards
    Kumar Ayyagari

  • SAP liveCache instance update exited abnormally

    Hi MaxDB/Livecache,
    While applying LIvecache patch from 07 to 13 i got this error.
    checking unpacked archive... ok
    installation of SAP liveCache APO LiveCache finished successfully Tu, Feb 05, 2008 at 17:14:33
    finding instance type...
    checking mmap support...
    starting release already known
    apo starting release already known
    migration strategy already known
    running finalize check...
    current liveCache state is OFFLINE
    checking parameters...
    switch liveCache state to ADMIN
    switch liveCache state to ONLINE
    loading system tables...
    checking catalog...
    registering liveCache application procedures...
    registering lcapp routines failed
    load_lcapps
    ERR
    -24964,ERR_EXECUTE: error in program execution
    768,/sapdb/LCA/db/bin/x_python /sapdb/LCA/db/env/lapps.py -R /sapdb/LCA/db -d LCA -u SUPERDBA,*
    Installing APPS
    Installing APPS
    Traceback----
      File "/sapdb/LCA/db/env/installib.py", line 401, in connectAndInstall
        installRoutine (session, options)
      File "/sapdb/LCA/db/env/lapps.py", line 34, in install
        "APPS"
      File "/sapdb/LCA/db/env/installib.py", line 163, in include
        install (session, options)
      File "/sapdb/LCA/db/env/APPS.py", line 36, in install
        loaderCmd (session, 'USE USER %s %s' % (sapuser[0], sapuser[1]))
    Command----
    USE USER SAPLCA MANAGER
    Error----
    loader.LoaderError: [-25008] Logon failure; previous user's (SUPERDBA) connection was restored.
    cannot finish instance update for "LCA"
    checking catalog...
    table SYSDBA.SYSCHECKCATALOGERRORS does not exist
    registering liveCache application procedures...
    registering lcapp routines failed
    load_lcapps
    ERR
    -24964,ERR_EXECUTE: error in program execution
    768,/sapdb/LCA/db/bin/x_python /sapdb/LCA/db/env/lapps.py -R /sapdb/LCA/db -d LCA -u SUPERDBA,*
    Installing APPS
    Installing APPS
    Traceback----
      File "/sapdb/LCA/db/env/installib.py", line 401, in connectAndInstall
        installRoutine (session, options)
      File "/sapdb/LCA/db/env/lapps.py", line 34, in install
        "APPS"
      File "/sapdb/LCA/db/env/installib.py", line 163, in include
        install (session, options)
      File "/sapdb/LCA/db/env/APPS.py", line 36, in install
        loaderCmd (session, 'USE USER %s %s' % (sapuser[0], sapuser[1]))
    Command----
    USE USER SAPLCA MANAGER
    Error----
    loader.LoaderError: [-25008] Logon failure; previous user's (SUPERDBA) connection was restored.
    SAP liveCache instance update exited abnormally at Tu, Feb 05, 2008 at 17:15:27

    Hi Rolland,
    As you told is right, there was a problem in the password,
    we changed that password and we have tested the DB connection in db59, this was ok. and we ran the command user_sap SAPLCA,<password>
    this was ok.
    After the registration has been succefully from LC10 ..
    Thanks for your inputs,
    Mahesh Chedde

  • Does the Livecache SID always have to be LCA ?

    We have installed APO Livecache with SID other than LCA and I'm being told that it has to be LCA always ?
    Is this true ?
    If it is, why is the install tool gives the option to pick a SID ?
    Or is there a config setting in SAP to change this default setting ?
    Thank you

    Hello Ravi,
    Please check the SAP Note No. 829963.
    Please review the documents at service.sap.com/scm ->mySAP SCM Technology:
    "mySAP SCM Technology" & "liveCache overview " .
    In case of a new installation of the liveCache/LCA, you have to create the connections LCA/LDA/LEA 
    as described in the  installation documentation for the SAP liveCache technology - using    
    Transaction LC10. For example, review the document at                                                    
    service.sap.com/instguides -> mySAP Business Suite Applications->
    mySAP SCM -> Using SAP SCM 5.0 Server->
    "Installation - SAP liveCache Technology …" in the section
    "Common Post-Installation Activities" - "Setting Up the Connection to the liveCache Instance".
    Please review the information at service.sap.com/liveCache ->Release Information ->
       SAP LC/LCAPPS 5.0
    You could  run /n/sapapo/om13 -> checks & see the status for LCA & LDA  & LEA 
    connections. If the connection is marked by the red  semaphore => check errors in /nsm21.  
    You could run the test connection for LCA & LDA & LEA in db59 transaction and review the results.   
    Please open the OSS ticket to the component 'BC-DB-LVC' or 'BC-DB-LCA' if you have further
    questions on this issue.
    Thank you and best regards, Natalia Khlopina

  • LiveCache Backup

    Dear all,
    Im a beginner in Livecache administration
    I would like to schedule backup of livecache from LC10 .
    The Following are my System Details
    Scm : SAP SCM 5.10
    Lc version :KERNEL    7.7.04   BUILD 037-123-218-794
    DBM Server : DBMServer 7.7.04   Build 037-123-218-794
    O/s : AIX
    Database : Oracle 10.2.0.4.0
    Pls tell me what should be the backup type?
    What should be the backup strategy...(frequency / incremental / differential )?
    Also would like to know the recovery process of livecache and which backtype will be helpful in recovering the complete state of livecache.?
    I appreciate your help.
    Regards,
    Kiran

    Hello Kiran,
    1. Only you could made decision about your backup/recovery strategy.
    2. There are the administration tasks that you have to perform regularly, see
    u201CRegular Administration Tasksu201D at
       http://maxdb.sap.com/doc/7_6/25/5b27401544ed01e10000000a155106/content.htm
    Also please review u201CChecklist for Recovery of SAP APO liveCache >= 7.4u201D recommended in my reply above.
    3. If you could not find the decision about your backup/recovery strategy, I recommend to create the SAP ticket to check more details on what OS resources you have, what backup tools you are using, what APO applications you run. What backup/recovery strategy you have currently on your system.
    4. The u201CBest Practicesu201D documents already recommended you ::
    u201CChecklist for Recovery of SAP APO liveCache >= 7.4u201D &&
    u201CBackup and Recovery for SAP APO (3.x) / mySAP SCM (4.x)u201D
    at
    SAP liveCache technology ->
    Best Practices for Solution Management: mySAP SCM
    Thank you and best regards, Natalia Khlopina

  • Where is the data come from when BW extract data from APO's MSP

    Hi,all.
       The APO system has many datasource,I have activated all the datasource with TCODE RSA5.
      I want to extract APO data to BW(Not APO's),where the APO data come from for BW extract,APO BW or SAP transparent table of APO or APO liveCache?
      PLZ help me,thank you very much.

    Hi,
    APO to BI Data Flow :
    1. Normally APO  DS  naming convention start with "9".
    2. Normally Planning area will provide the data for the DS.
    3. Using one T-Code ( /N/SAP/ ..... Ask APO Person) DS will be generated .In the specified T-Code you will provide the relavant 
        Planning area and DS will be generated.
    4.As you know RSA3 is for checing the data for DS.If you found there is no data for some fields then you will check the data at the planning area level (In R/3 table level).
    Regards
    Ram.

Maybe you are looking for