Backup to Livecache

Hi,
We are trying to take a backup of livecache and restore it. I know this is more a Livecache/Max db question but trying my luck if any here can help me.
This is what we did:
1. created forecast in SDP94
2. Took a backup
3. Made changes to the forecast data
4. Crashed the live cache(system)
5. Restored the data from live cache.
The intention is to find out if the livecache was successful. After my backup, if the see old numbers that were in DP94 at the time I took backup, the test is pass but if I see new that I changed after backup the test is fail.
We tried this exercise 3 times We always go the new numbers making the test fail.
Am I making a mistake in the procedure?
Are the numbers saved some where other than the livecache and keep coming back after recovery?
Please advise.
Thanks.

Hi,
Are we talking of DP planning books being backed  up into an infocube? If so, did you re-load the data back from the infocube to the planning area. Back-up of livecache time series data is done to an infocube and we usually restore data from the back-up cube - not sure if that helps, but if it is a standard back-up - would be good  to check the best practice document for livecache backup on the SAP site.
An extract:
Backups are typically created online either as incremental backups (daily) or as full backups (weekly).
Perform backups using
– liveCache administration tools
– CCMS Database Planning Calendar ( as of SAP Basis Release 6.20 )
– A job from within the SAP APO system that
o Starts report RSLVCBACKUP - see SAP Note 455154
o Starts an external command using DBMCLI
– Third party tools using backup interfaces
Log backups can be made in parallel to online liveCache backups either
– Manually by an administrator or
– Periodically by CCMS Database Planning Calendar ( as of SAP Basis Release 6.20 ) or
– Automatically in liveCache mode Auto Log
Make sure log backups are performed regularly to prevent liveCache standstills due to log overflow.
For details on how to perform backups, see SAP liveCache documentation.
Regards
Vinod

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

  • 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

  • Livecache 7.7 patch - backups needed

    Hello community,
    we are planning a Livecache 7.7 patching from version 7.7.04.25 to version 7.7.04.32 on Unix as described in SAP note 998966
    I want to be able to roll back the activity to the actual kernel version as I usually do in SAP R/3 environment.
    In the case of SAP kernel I make a simple backup of directory /sapmnt/<SID>/exe
    What do I need to backup in Livecache? Is it correct and enough to backup the following directories?
    /sapdb/<SID>/db
    /sapdb/programs
    Regards,
    Valerio

    > we are planning a Livecache 7.7 patching from version 7.7.04.25 to version 7.7.04.32 on Unix as described in SAP note 998966
    >
    > I want to be able to roll back the activity to the actual kernel version as I usually do in SAP R/3 environment.
    > In the case of SAP kernel I make a simple backup of directory /sapmnt/<SID>/exe
    >
    > What do I need to backup in Livecache? Is it correct and enough to backup the following directories?
    > /sapdb/<SID>/db
    > /sapdb/programs
    No it isn't.
    You have to have the old installation set to be able to resinstall the older version.
    In case you need to "rollback" this upgrade, you will need to uninstall the newer version via SDBUNINST/SDBSETUP and reinstall the older version via SDBINST/SDBSETUP again.
    Copying the binaries back and forth will only lead to registration inconsistencies - don't go down that road.
    regards,
    Lars

  • We unable to connect to livecache database

    Hi All,
    We have restored SCM along with Live cache successfully.
    After restore we are unable to connect live cache to R3....
    our source system versions are NW 2004s R2 and live cache version is 7.6.04.09
    We didn't find the same version software in the SAP Market Plece... So we upgraded to higher version 7.6.06.20 and then we restore the backup successfully from the source live cache to target live cache but while initialising and activating the datebase with R3 system it is throwing error.
    Error:
    Can not connect to live cache database.
    even we validated the passwords for the each user which are working fine.
    Please give me the solution.
    Thanks in advance.
    Regards
    Karthik

    Hello Orkun Gedik,  SAP Note No. 1015489 is for SCM systems as of SCM 5.1, so NOT relevant for this thread.
    Hello  Karthik,
    First let me know what was done by you since I posted:
    1. You are SAP customer => for the reported issue will be best for you, if you will create the SAP message and get SAP support.
    2. "SAP Livecache/LivecacheApplication 5.0 SP15 " released with liveCache version 7.6.04.09, more details in the SAP Note 1154718. LC760409A5015_7-XXXXX.SAR package is available on the SAP market place for SAP customers.
    3. Read the SAP note:
    457425 Homogenous liveCache copy using backup/restore
    If you followed this note the liveCache/LCA versions has to be the same on source and target, also the same OS platform of the liveCache servers.
    4. Please review the SAP note:
    886103 System Landscape Copy for SAP SCM
    The LCA routine error 40,134 means "Key Figure does not exist".
    If the error occurred after System Landscape Copy for SAP SCM, then let us know if you created the SCM DB backup and liveCache backup on the source system
    To be restored on the target in sync or there was time gap between backups, when the TS data were changed on source system.
    for the reported issue will be best for you, if you will create the SAP message and get SAP support.
    Regards, Natalia Khlopina

  • Live Cache Backups

    Any suggestions on building a backup strategy for Live Cache,
    ie; What to backup, what medium works best, how often etc.
    ERP/SCM platform is iSeries/AS400

    I suggest you backup the livecache as often as you backup your SCM system.
    The "best working medium" can be everything from a disk to tape to storage, everything that´s supported by the operating system works. I depends on what size your LC is and how familiar you are with different mediums.
    Markus

  • Live cache backup question

    Hello Experts,
    Iam new to Livecache and AP0  and was trying to understand the process of backups reason i need to perform complete SCM 7.0 systemcoopy . In past i have done system copies and well aware of the procedures .
    Here it goes Presently we are on SCM 7.0
    Question  :--> I see our Livecache is installed on one machine and AP0 on another machine. Iam not aware how Livecache
                           was integrated with AP0.
                           Iam trying to understand how to take backup of livecache and then restore the same in Target.
    In LC10
    LCA --> ProblemAnalysis --> Logs --> DBA History
    i can see that the live cache backups are in getting successfully everyday.
    I see that Backup Label as DAT_000000<xxx> and Backup Template as bac214<xxx>.
    Where can i see this Backup Template defined ( the path ) .
    Can someone provide an insight regarding the live cache backups.
    Checked SAP Note 457425 .
    --> After system copy how would i integrate Livecache and AP0 .
    Thanks in Advance.
    Medha

    Hello Medha,
    1.
    a)
    Please review all recommended steps in the SAP note:
    886103     System Landscape Copy for SAP SCM
    when you are planning to do the SCM system copy.
    For SAP liveCache documentation please see the SAP note 767598.
    b)
    SAP link:
    SAP liveCache technology
    -> Best Practices for Solution Management: mySAP SCM
    review:
    "Checklist for Recovery of SAP APO liveCache >= 7.4"
    < It will be helpful to practice the steps of the document on the test liveCache instance first >
    2.
    Sessions: http://maxdb.sap.com/training/   
    =>
    Session 2: Basic Administration with Database Studio
    Session 3: CCMS Integration into the SAP System
    Session 11: SAP MaxDB Backup and Recovery
    Those sessions will help you. If you still have some questions after that => update the thread.
    4.
    Took classes for the MAXDB database administration or get the SAP consulting support.
    Regards, Natalia Khlopina

  • Deactivating Automatic log backup

    Hello All,
    I have a query.
    How can we check when automatic log backup of livecache log area has been deactivated. and Why?
    Any log file registring this?
    Thanks.
    Regards,
    Tushar

    Hello Melanie,
    Thanks a lot.
    I checked dbm.prt file which does not mention autolog_off command means it has been deactivated by error.
    So checked knldiag.err file, which mentioned the error:
    ========================================================
    2007-11-11 06:08:47   156 ERR 11000 d0_aopen Cannot open device, Permission denied
    2007-11-11 06:08:47   156 ERR 11000 d0_aopen Device name '/sapdb/OEM/lcbackup/log/<b>autolog.003'</b>
    2007-11-11 06:08:47    83 ERR     1 Backup   Backupmedium #1 (/sapdb/OEM/lcbackup/log/autolog.003) Could not open volume
    2007-11-11 06:08:47    83 ERR     6 KernelCo  +   Backup error occured, Errorcode 3700 "hostfile_error"
    2007-11-19 08:42:52   189 ERR 11000 d0_aopen Cannot open device, Permission denied
    ===========================================================
    -rw-rw----   1 oemadm     sapsys     349765632 Jun 26  2006 autolog.002
    -rw-rw----   1 oemadm     sapsys     57540608 Jul 21 10:58 <b>autolog.003</b>
    ===========================================================
    I checked <b>autolog.003</b> file which has permission as owner (<livecache_sid>adm) and group sapsys.
    It also has overwrite option as NO:
    Corrosponding entries in the  KNLDIAG file are :
    =========================================================2007-11-11 06:08:43    28     12929 TASKING  Task T5 started
    2007-11-11 06:08:43    28     20018 Pager    Start TaskId: 5
    2007-11-11 06:08:43    28     20019 Pager    First DataCacheSegment:31
    2007-11-11 06:08:44    12         3 RunTime  State changed from STARTING to ADMIN
    2007-11-11 06:08:44    24        31 SrvTasks Permanently reserved 10 servertasks for <b>'Backup / Restore'</b>.
    ======================================= end of startup part ====================
    2007-11-20 23:23:17    14     11561 COMMUNIC Connecting T95 local 29873
    2007-11-20 23:23:17   118     12929 TASKING  Task T95 started
    2007-11-20 23:23:17   118     11007 COMMUNIC wait for connection T95
    =========================================================
    <b>So it owner:group is wrong or is it due to overwrite option?
    What should be owner and group sdb:sdba for backup medium of file type?</b>
    Thanks for your help.
    Regards,
    Tushar
    Message was edited by:
            Tushar Chavan
    Message was edited by:
            Tushar Chavan

  • Livecache recovery from cold backup  with raw devspaces

    We are recovering the Livecache database from code backup to  a database with raw devspaces. We gave the following raw parameters to DATA and LOG devspaces:
    DATA Devspace: /dev/vx/rdsk/azdevdg/lvlzddisk1
    LOG Devspace: /dev/vx/rdsk/azdevdg/lvlzddisk3
    We are getting the following errors during initialization:
    2005-04-29 09:13:14    68 ERR 11000 devio    read error (fd = 24): No such devic
    e or address
    2005-04-29 09:13:14    68 ERR    15 IOMan    Unknown Data volume 1: Could not re
    ad
    Any Ideas ?

    Hi,
    as for all liveCache issues, I'd have to ask you too to open an OSS message on queue BC-DB-LVC.
    A thing you could try:
    try to read using 'dd' from your devices. If 'dd' can't read from the devspaces, then you've got a misconfiguration somewhere, i.e. an operating system issue and not a liveCache issue. In that case, we (BC-DB-LVC) wouldn't be responsible for the error.
    The 'dd' command could look like:
    dd if=/dev/vx/rdsk/azdevdg/lvlzddisk1 of=<filename> <blocksize>
    Regards,
    Roland

  • Restore LiveCache backup to another System -AIX

    Dear SAP Gurus,
    1. How can I restore full backup of Live Cache to another system.
       How can I do Live cache system copy?Rename SID's.
    2. How can I rename the existing live cache to a dirrent name, example LC1 to LC4 and restore another system's backup to LC1.
    Thanks,
    Naren

    Hello Sithambaram,
    1) Please provide more information:                                                           
    -> Are you going to do Homogeneous or Heterogeneous System Copy?                          
    -> What are the OS of the source & target servers?                                         
    < please provide this information for the liveCache servers too.>                          
    -> What are the liveCache version & SCM SP on your system?                                                                               
    Please take a look in the SAP notes:                                                   
    886103     System Landscape Copy for SAP SCM
    210564     Copying a complete APO system                                                                               
    For the Homogenous liveCache copy please follow the SAP notes:                                                                          
    877203     Post steps after the Homogenous liveCache copy using                             
    457425     Homogenous liveCache copy using backup/restore                                                                               
    Please see the SAP note for Heterogeneous liveCache copy procedure :                          
       632357     Backing up liveCache data for SCM 4.0   
    2) Information about the steps to rename the existing live cache to
       a different name, example LC1 to LC4, could be found in the SAP note:                     
       604680     Renaming a SAP DB or liveCache instance
    Thank you and best regards, Natalia Khlopina

  • SAP Livecache automatic log backup turning off

    Hi,
    We have set automatic log backup ON for our livecache. Recently, it got turned off automatically.
    We found that our filesystem to which the archive files were getting generated during log backups had got full.
    My question is, if the filesystem where log backups are archived gets full does the setting of automatic log backup gets turned
    OFF automatically? Please suggest,
    Rg,
    Sandeep.

    >  We have set automatic log backup ON for our livecache. Recently, it got turned off automatically.
    >  We found that our filesystem to which the archive files were getting generated during log backups had got full.
    >  My question is, if the filesystem where log backups are archived gets full does the setting of automatic log backup gets turned
    > OFF automatically? Please suggest,
    Yes, that is expected behaviour. If the database can't back up logs to a directory it gets turned off. You'll have to release space and turn it on manually.
    Markus

  • LiveCache DB backup failure due to error code "903".

    LC DB BACKUP was failed due to backup devices issue '903'. When I did the
    BACKUP to FILE instead of PIPE, it worked well. Pls suggest. Thanks.
    Base on the configuration 'dbm.mmm'. Here is the definition for PIPE
    'BACKTSM', which is the current BACKUP device.
    [BACKTSM]
    LOCATION=/sapdb/backup/dummy
    TYPE=PIPE
    SAVETYPE=DATA
    SIZE=0
    BLOCKSIZE=8
    OVERWRITE=NO
    AUTOLOADER=NO
    OSCOMMAND=
    BACKUPTOOL=BACK
    CREATED=20061101171214
    MODIFIED=20061101171214

    Attach dem.ebp for reference. Is it possible that the tools '/sapdb/LCT/db/bin/backint' have problems?
    2010-12-30 10:35:13
    Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.
    Using environment variable 'TMP' with value '/var/tmp' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2010-12-30 10:35:13
    Checking existence and configuration of Backint for MaxDB.
        Using configuration variable 'BSI_ENV' = '/home/lctadm/bsi.env' as path of the configuration file of Backi
    nt for MaxDB.
        Reading the Backint for MaxDB configuration file '/home/lctadm/bsi.env'.
            Found keyword 'BACKINT' with value '/sapdb/LCT/db/bin/backint'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword an
    d is ignored:
            Found keyword 'INPUT' with value '/home/lctadm/dba/backint4SAPDB.in'.
            Found keyword 'OUTPUT' with value '/home/lctadm/dba/backint4SAPDB.out'.
            Found keyword 'ERROROUTPUT' with value '/home/lctadm/dba/backint4SAPDB.err'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword an
    d is ignored:
            Found keyword 'PARAMETERFILE' with value '/home/lctadm/backint.par'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword an
    d is ignored:
            Found keyword 'TIMEOUT_SUCCESS' with value '600'.
            Found keyword 'TIMEOUT_FAILURE' with value '300'.
        Finished reading of the Backint for MaxDB configuration file.
        Using '/sapdb/LCT/db/bin/backint' as Backint for MaxDB program.
        Using '/home/lctadm/dba/backint4SAPDB.in' as input file for Backint for MaxDB.
        Using '/home/lctadm/dba/backint4SAPDB.out' as output file for Backint for MaxDB.
        Using '/home/lctadm/dba/backint4SAPDB.err' as error output file for Backint for MaxDB.
        Using '/home/lctadm/backint.par' as parameter file for Backint for MaxDB.
        Using '600' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using '/sapdb/data/wrk/LCT/dbm.knl' as backup history of a database to migrate.
        Using '/sapdb/data/wrk/LCT/dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2010-12-30 10:35:13
    Checking medium.
    Check passed successfully.
    2010-12-30 10:35:13
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call '/sapdb/LCT/db/bin/backint -u LCT -f backup -t file -p /home/lctadm/bac
    kint.par -i /home/lctadm/dba/backint4SAPDB.in -c'.
        Created temporary file '/home/lctadm/dba/backint4SAPDB.out' as output for Backint for MaxDB.
        Created temporary file '/home/lctadm/dba/backint4SAPDB.err' as error output for Backint for MaxDB.
        Writing '/sapdb/backup/dummy #PIPE' to the input file.
    Prepare passed successfully.
    2010-12-30 10:35:13
    Creating pipes for data transfer.
        Creating pipe '/sapdb/backup/dummy' ... Done.
    All data transfer pipes have been created.
    2010-12-30 10:35:13
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '/sapdb/backup/dummy' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKTSM'' f
    rom db-kernel.
    The database is working on the request.
    2010-12-30 10:35:13
    Waiting until database has prepared the backup.
        Asking for state of database.
        2010-12-30 10:35:13 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2010-12-30 10:35:14 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2010-12-30 10:35:14
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/sapdb/LCT/db/bin/backint -u LCT -f backup -t file -p /home/lctadm/bac
    kint.par -i /home/lctadm/dba/backint4SAPDB.in -c >>/home/lctadm/dba/backint4SAPDB.out 2>>/home/lctadm/dba/back
    int4SAPDB.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2010-12-30 10:35:14
    Waiting for end of the backup operation.
        2010-12-30 10:35:14 The backup tool is running.
        2010-12-30 10:35:14 The database is working on the request.
        2010-12-30 10:35:19 The backup tool is running.
        2010-12-30 10:35:19 The database is working on the request.
        2010-12-30 10:35:21 The backup tool process has finished work with return code 2.
        2010-12-30 10:35:21 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-8020
            Date                  :20101230
            Time                  :00103514
            Database              :LCT
            Server                :mdt2ds41
            KernelVersion         :Kernel    7.6.06   Build 009-123-225-492
            PagesTransfered       :131072
            PagesLeft             :25509
            MediaName             :BACKTSM
            Location              :/sapdb/backup/dummy
            Errortext             :end of file
            Label                 :DAT_000000970
            IsConsistent          :true
            FirstLogPageNo        :2676033
            DBStamp1Date          :20101230
            DBStamp1Time          :00081359
            BDPageCount           :156557
            DevicesUsed           :1
            DatabaseID            :mdt2ds09:LCD_20070908_000004
            Max Used Data Page   
            Converter Page Count  :99
    The backup operation has ended.
    2010-12-30 10:35:21
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            Date                  :20101230
            Time                  :00103514
            Database              :LCT
            Server                :mdt2ds41
            KernelVersion         :Kernel    7.6.06   Build 009-123-225-492
            PagesTransfered       :131072
            PagesLeft             :25509
            MediaName             :BACKTSM
            Location              :/sapdb/backup/dummy
            Errortext             :end of file
            Label                 :DAT_000000970
            IsConsistent          :true
            FirstLogPageNo        :2676033
            DBStamp1Date          :20101230
            DBStamp1Time          :00081359
            BDPageCount           :156557
            DevicesUsed           :1
            DatabaseID            :mdt2ds09:LCD_20070908_000004
            Max Used Data Page   
            Converter Page Count  :99
    The backup operation has ended.
    2010-12-30 10:35:21
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2010-12-30 10:35:21
    Cleaning up.
        Removing data transfer pipes.
            Removing data transfer pipe /sapdb/backup/dummy ... Done.
        Removed data transfer pipes successfully.
        Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (/home/lctadm/dba/backint4SAPDB.out)----
            Have encountered error -24919:
                The file '/home/lctadm/dba/backint4SAPDB.out' does not exists.
    End of output of Backint for MaxDB (/home/lctadm/dba/backint4SAPDB.out)----
        Have encountered error -24919:
            Could not move output of tool from file /home/lctadm/dba/backint4SAPDB.out to protocol file.
        Not removing Backint for MaxDB's temporary output file (/home/lctadm/dba/backint4SAPDB.out).
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (/home/lctadm/dba/backint4SAPDB.err)----
            Have encountered error -24919:
                The file '/home/lctadm/dba/backint4SAPDB.err' does not exists.
    End of error output of Backint for MaxDB (/home/lctadm/dba/backint4SAPDB.err)----
        Have encountered error -24919:
            Could not move output of tool from file /home/lctadm/dba/backint4SAPDB.err to protocol file.
        Not removing Backint for MaxDB's temporary error output file (/home/lctadm/dba/backint4SAPDB.err).
    Could not clean up all correctly.

  • SCM Livecache kF backup to InfoCube

    Hi Users,
    We're using SCM 7.0 and we set up the struture to export key figures from DP into an Infocube.
    We are succussefully copying some KF's to the Infocube. But I have a problem that some of my KF's are not copying into the the infocube. In fact, they have not copied into the replicated datasource either.
    All the transfer rules and update rules are set up correctly.
    The Datasource
    is NOT suppressing the KF's and these KF's are not set up any differently to the KF's that are transferring data to cube.
    The Planning Area.
    The KF's that are NOT transferring are a macro reuslt. Whereas the KF's that are in the cube are enetered in manually (except for the statistical forecast).
    Is there something that I need to set in the macro or change how the KF's have been set up?
    Have I missed a setting in the InfoSource or DataSource?
    Thanks
    Paul

    Hello Paul,
    maybe I did not understand the problem correctly. So let me ask one thing to clarify. Are the key figures that are not updated in the infocube present in the datasource or are they missing in the datasource as well?
    What I suggested should have solved the problem that the key figures were missing in the datasource.
    If the key figures are in the datasource, but still not updated into the cube, you could check the transfer rule from datasource into the infocube for the not updated key figures. Check if there is a direct mapping and if "sum" is set in the field mapping of these key figures.
    If the key figures are still not in the datasource, try to create a new datasource or delete the exising one and create a new one.

  • No username of Source system is avbl after livecache system copy

    Hi Experts
    I have done a livecache system copy from the source system to target system. Here the steps are
    Assume my Source SYstem Livecache is RP1 and Target System livecache is RS1.
    1. Taken Source system livecache DATA and LOG Area backup RP1.
    2. Defined the same source system backup medium name in Target System (RS1 and moving the Source system Liveacache backuped files to Target system and defined the medium name as per that)
    3. put the livecache db_admin mode
    4. db_activate RECOVER <medium_name>.
    5. recover_start <log_medium_name> LOG <nnn>
    6. db_online.
    Here we faced that
    ERR
    -24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
    -24907,ERR_DBAWRONG: Wrong database system administrator
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    So we activated the SUPERDBA as " db_activate SUPERDBA,<password>
    then it came to online. and afterwards we have used the load_systab command to load the tables.
    BUT we could not find any Source System name like "RP1ADM" in the tables of the livecache database. Only there are CONTROL,SUPERDBA username availbale. Usually there will be also the source admin name . I dont know why it is missing
    Before a month we have done livecahe restore same as now in that time we got the source system name admin also. ( RP1ADM) and also tables which owned by RP1ADM. alos i could find APPSYSPARAM table and the instance also registered.
    But now in this restore we could not find the above.
    We followed the same procedure and there is no change in the steps also.
    Could anyone help me...
    Regards
    bala

    Hello Bala,
    1. As I wrote you already, the notes:
    886103 System Landscape Copy for SAP SCM
    877203     Post steps after the Homogenous liveCache copy using backup/
    457425     Homogenous liveCache copy using backup/restore
    has all recommended steps to do, when you will run the u201CSystem Landscape Copy for SAP SCMu201D
    2. If you run the u201CHomogenous liveCache copy using backup/restoreu201D you should pay attention to the note 457425. After you imported the complete data backup < step 2. > you need to update the system tables.
    To update the system tables you need to know the correct database SYSDBA user & password.
    After you restored the databackup of the source database, start the database online & run u201Cselect * from usersu201D SQL command to see the SYSDBA user. Then check that you know the DBA user ( DataBase Administrator ) & password of the source database instance => Open the SQL session with this
    user & password.
    Example:
    after db_activate recover <medium_name>
    login as control,password
    db_online
    sql_execute select * from users
    sql_connect  superdba,<password of source system>
    If you didnu2019t get error with the last command, then you could update the system tables with the superdba,<password of source system> using load_systab command.
    The system tables will be updated & the correct SYSDBA user & password will be updated in *.UPC file.
    3.     
    user_sysdba:
    You make the database system administrator known to Database Manager. It is only necessary to use this DBM command if the database administrator is not known or is incorrectly known to Database Manager.
    u201CI have tried like this
    after db_activate recover <medium_name>
    login as control,password
    db_admin
    user_sysdba superdba,<password of source system>
    db_onlineu201D
    You could update the .upc files with the wrong SYSDBA user password u2026
    You was lucky, that you knew the correct SYSDBA user and password of the source database.
    Example  < NLK is my local database >:
    A.     I could update the .upc file with wrong password of SYSDBA user:
    dbmcli -d NLK -u control,control
    dbmcli on NLK>user_sysdba superdba,test
    OK
    dbmcli on NLK>db_online
    OK
    dbmcli on NLK>load_systab
    ERR
    -24909,ERR_DBAUNKNOWN: SYSDBA unknown
    dbmcli on NLK>exit
    B.  I could update the .upc file with wrong SYSDBA user:
    dbmcli -d NLK -u control,control
    dbmcli on NLK>user_sysdba test,test
    OK
    dbmcli on NLK> user_get test
    OK
    u2026
    dbmcli on NLK>sql_connect test,test
    ERR
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    dbmcli on NLK> dbmcli on NLK>sql_connect superdba,admin
    OK
    I could connect as test,test; but the test user is NOT SYSDBA user u2026
    dbmcli -d NLK -u test,test
    dbmcli on NLK>
    Itu2019s recommended to user the load_systab command, so the .upc files will be updated with the correct SYSDBA user/password or
    you will get error.
    4. http://maxdb.sap.com/doc/7_7/86/68627a1bc642e6a6f73d3bc7a55fe1/content.htm
    You got error:
    ERR
    -24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
    -24907,ERR_DBAWRONG: Wrong database system administrator
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    The automatically updating the system tables, according to the default value, is switched on.
    After you will run the update system tables with the correct SYSDBA user & password the *.UPC file will be updated,
    and with the next liveCache restart you will not get this error.
    5. See more information in the MAXDB library:
    http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
    Thank you and best regards, Natalia Khlopina
    Edited by: Natalia Khlopina on May 19, 2010 2:58 PM

  • LiveCach problem with log Area

    In LiveCache monitoring I can see the message: "Log area full - back up log!"
    I use the RSLVCBACKUP interactively with the parameter "Complete Data Backup". After running an error is displayed:
    "Failed to determine media (Database connection: LCA)
    Message no. LVC505 ".
    Is it true I'm doing taking such measures for Log Area Backup. And if all true, how can I avoid mistakes LVC505?

    Sounds like you did not configure a backup medium for your liveCache.
    To get rid of the log-full situation you may just use DBMGUI now and take a full backup and activate autolog backup afterwards.
    Once this is done you may check what's wrong with your report usage.
    regards,
    Lars

Maybe you are looking for