Effect of SAP R/3 upgrade on Delta Queue

Hi Gurus,
We have our SAP upgrade scheduled to go-live in some time. My problem is that we have 2 loads based on Direct Delta queue concept.
As per my understanding, the approach that we need to follow is that we should get all the users locked and then load the data into BW system from delta queue. Once this is done and the delta queue is cleared, we can bring the R/3 system down for upgrade.
The approach adopted for Upgrade is Downtime minimised, wherein for most part of upgrade, system will be down and for some part of upgrade the production will be up and running. In such a scenario where system will be up and upgrade will be running simultaneously, will there be any impact on the delta queues or rather shall I say that 'Will the delta queues affect upgrade process'

Hey.  In my experience, you never want the system to be "up" during an upgrade.  You will, or have, probably run accross the problem in dev or QC with doing the upgrade while the delta queues are populated.  You will often get an error message that queues still have data to be transfered.
So I guess the simplest answer is that you do run the risk of having problems with the upgrade.  If thre is no choice but to do the upgrade partially doing productive hours, I would just clear all the queues and hope for the best.  Not a great answer, but not sure what the best answer would be in your scenario.
Thanks

Similar Messages

  • How to flush Delta queue for future SAP upgrades/support pack !

    Guys,
    I'm making documentation regards to " How to flush Delta Queues" in case SAP wanted to upgrade the system or any support pack. Please anyone let me know the effective way to flush out the delta queue in step by step methods. I really appreciate your help.

    1.  Run V3 for associated application(s), this will load any potential delta data to the delta queues.
    2.  Run the delta load for each datasource twice.  The second load will clear the delta repeat data so that there should not be any more data in the delta queues defined with the format of the current datasources.
    Does this help?

  • Things to do in BW Production for SAP BI7.0 upgrade

    Dear Experts,
    If somebody is aware for the things to do in BW Prod. before starting BI7.0 upgrade i.e. (before client copy to new dev. , renaming system by BDLS etc.) , pl help urgently.
    Thanks in advance. Points will be rewarded instantly ..............
    Best Regards,
    Sharad

    Hi,
    Its always better to drain the delta queues before an upgrade.
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Page 17
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    upgrade preparation and postupgrade checklist
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    Effect on BW of R/3 Upgrade   
    How To Tackle Upgrades to SAP ERP 6.0
    Start with the Why — Not the How — When You Upgrade to SAP ERP 6.0
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
    Rapid SAP NetWeaver 7.0 BI Technical Upgrade
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
     https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
    thanks,
    JituK

  • Impact of database upgrade in Bw delta queue

    Hi Gurus,
    We are going to upgrade the R/3 oracle database. I suppose that it have an impact in the BW delta queue, and that before the upgrade the logistics queues should be uploaded to BW.
    I'm right? exits some note or some checklist about wihch activities should be performed in BW due to the database upgrade?
    Thanks in advance for your help.

    Hi,
    This speaks about support pack upgrade. But i think this also applies for DB upgrade too.
    Its always better to drain the delta queues before an upgrade.
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Page 17
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    upgrade preparation and postupgrade checklist
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    /message/3221895#3221895
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    /thread/804820
    Effect on BW of R/3 Upgrade   
    How To Tackle Upgrades to SAP ERP 6.0
    /people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
    thanks,
    JituK

  • Critical issue - delta queues for LIS empty after upgrade BW3.5

    The delta queue in R/3 for LIS sources (S260-261-262) remains empty,
    even after a successful init delta. Hence I cannot extract delta
    records.
    BW3.5
    PI2004.1
    Does the BW upgrade has an effet on the delta queue management in R/3 ?
    The previous configuration BW2.0B PI2004.1 did work fine in that
    respect.
    Laurent Querella
    BI Consultant ALTI

    Laurent,
    from OSS Note 534296 'LBW0: DataSource generation possible for SAP info str.' you can read:
    "(...)it is no longer possible to generate DataSources for info structures (transfer) Snn delivered by SAP (where nnn is between 001 and 500) in the BW interface for LIS info structures (TR: LBW0) in the OLTP. (...)The corresponding DataSources are delivered with the Business Content."
    I think this is the issue...
    However, are you saying that all infostructures are empty ?
    And from where your init is taking data ?
    After an init your delta tables have to be empty...did you empty all these tables before doing your upgrade ?
    Bye,
    Roberto

  • R/3 Delta queues in support package upgrade

    Hi gurus,
    Our team needs to apply a support package upgrade to our BI 7.0 (without an upgrade in R/3 source system).
    Do I need to worry about SM13 and RSA7 in my source system R/3 or just my data marts inside 7.0?
    Or do I need to empty R/3 delta queues before BI upgrade to prevent data loss?
    Best regards,
    Enric

    You may wish to take a look at below for few insights -
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    https://forums.sdn.sap.com/click.jspa?searchID=10299818&messageID=3221895
    Hope it Helps
    Chetan
    @CP..

  • Follow up activities after SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4

    Dear Friends
    We have completed SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4.
    We refereed the upgrade guide for follow activities and we required confirmation before performing the activities.
    Could you please help us what needs to be done immediately after upgrade.
    Regards,
    Bharathi

    Dear Nils,
    Thanks for the support.
    Yes, we are following the same document 'CUUC46C_to_NW701SP07' for unicode conversion after the upgrade from the note 928729.
    Please suggest us in that document which are the steps should be carried out after ECC6.0 EHP4 upgrade,
    1. Preparation
    2. Unicode Preconversion Phase in SAP Basis 4.6C
    3. Upgrade Process
    4. Unicode Conversion Phase
    5.  Unicode Conversion Completion Phase
    6. SAP Notes
    Regards,
    Bharathi

  • SAP R/3 Upgrade to ECC 6.0 - Protection of BSI data

    Hello,
    We are upgrading SAP R/3 to ECC 6.0. We have BSI and Vertex installed and functional in the landscape. I have 4 queries, seen below.
    1- During a SAP R/3 Upgrade, BSI product leaving the .exe directory u2013 what are the steps that he needs to taken, so that they donu2019t get overlaid over during the upgrade? 
    2- Does SAP provide anything to protect (BSI)?
    3- Does SAP provide anything to protect (VERTEX)?
    4- What action should be taken on BSI and Vertex during R/3 Upgrade? Is there a checklist or document?
    Thanks for help in advance.

    > 1- During a SAP R/3 Upgrade, BSI product leaving the .exe directory u2013 what are the steps that he needs to taken, so that they donu2019t get overlaid over during the upgrade? 
    Create a file "protect.lst" in the kernel directory. The programs listed within are not deleted then. Neverless, take a backup of the kernel directory.
    > 2- Does SAP provide anything to protect (BSI)?
    > 3- Does SAP provide anything to protect (VERTEX)?
    > 4- What action should be taken on BSI and Vertex during R/3 Upgrade? Is there a checklist or document?
    >
    See you other (almost identical query):
    Protection of Key SAP HR tables in SAP R/3 Upgrade
    Markus

  • BW Upgrade - Down time - Delta queue

    Hello Experts,
    We are in the process of upgrading the BW system from 3.1 to BI7 but not the R3.
    Do we need to drain the delta queue from R3 before the upgrade or we can only go ahead about the BW Delta queue only?
    As per the note: 506694, its talks about the BW alone when we are performing the BW upgrade but not R3.
    Also let me know whether we need to take R3 down time when we do the BW upgrade alone?
    Thanks
    Raman

    Dear Kedar,
    Can we perform the left out steps directly in production? As per my understanding there wont be any issues if we perform the left over steps in production.as this will checks for the consistency check alone.
    Interestingly I tried checkcing this program(RSUPGRCHECK).. for the infoobjects in my dev system. its trying to activate some of the infoobjects as well.
    It showed a message like this: Activate all Dictionary objects ( 1422 )
    I tried checking the number of objects in the system using RSDIOBJ.. where I can see that there are 2600 objects are in A version.!!
    Does this message tells that this program has activated this many number of the infoobjects out of 2600?  I tried this after the upgrade in the D.
    Can you please clarify me on this.?
    Final Question: How much period that we need to maintain the Down time in R3. Is it till the Upgrade starting from the PREPARE and till the end of the Post Upgrade activities and the Unicode? I will close this thread after this.
    Many thanks again..
    Raman
    Edited by: Raman R on Aug 28, 2008 3:16 PM

  • Question about Note 886102 - Empty the delta queue of the connected SAP source systems

    Dear expert
    I'm doing the system refresh from ECC PRD to QAS using the hot backup of PRD
    Before i start the database restore i was told to do the following step since this ECC has connection with one BW system
    -----------------------Step -----------------------------
    2.17 SAP note 886102 scenario C3
    Empty the delta queue for all of the connected BW systems.
    Execute all delta info packages two times on BW side, to clean up the delta queue in the source system. This is needed, because BDLS cannot rename the still available LUW-s in the qRFC queue.
    ----------------------Step-----------------------
    But unfortunately i missed to execute this step
    And the Q11 is now retoreing the backup of the database
    My quesion
    1. what will be bad consequence due to not execute this step? any way to makeup this error?
    Best regards,

    Hi Kate,
    The probably issue which I could forsee is data getting wrongly updated into production if RFC connection from ECC to BW is not stopped.
    Solution here could be to disable or deletethe RFC connections between ECC and BW before starting the SAP system at database level.
    delete from sapr3.rfcdes where rfcdest = '<name>';
    Once the system is up and running you can recreate them if required.
    Also before starting SAP set the number of batch processes to 0 on the profile at OS level so that any released jobs don't start as soon as SAP is up.
    Once the SAP system is up execute BDLS and change the logical system name.
    Hope this helps.
    Regards,
    Deepak Kori

  • R/3 Delta queue during 3.5 upgrade

    Greetings Experts,
    We're upgrading from BW 3.1 to 3.5, and the documentation calls for clearing the R/3 delta queue before the upgrade.  My first question is...how do I do this?  If I run all of our delta loads to clear the queue, they will start filling up again almost immediately.  Do I have to cancel all my delta loads, then reinitialize after the upgrade?
    Also, should I time clearing the delta queue with the BW 3.5 upgrade, or should I time it with the upgrade to the PI 2004 in the R/3 system?
    Thank you very much

    Hi,
    I am still in doubt if it is necessary to stop the productive work in the R3 system during the upgrade or if it is enough to stop the collector jobs (RMBWV3*) and empty the delta queues?
    If the R3 system would be up then the MCEX queues would be filled during the upgrade. So there would be entries in LBWQ but no entries in RSA7.
    Has onyone left the R3 system in production mode during the upgrade?
    Thanks,
    Timo

  • After Effects CC 2014 will not upgrade?  Gets to 100% and then says application failed.  Why does this not upgrade?

    After Effects CC 2014 will not upgrade?  Gets to 100% and then says application failed.  Why does this not upgrade?

    We can't know anything. You have not provided any useful details like system information or the install logs.
    Mylenium

  • SAP EPR6.0 Upgrade (Downtime).

    Dear Sir/Madam,
    Currently we are doing SAP ERP6.0 Upgrade, Can you please guide me what are the steps we need to adapt in order to Minimize System downtime.
    Regards.
    Hubert.

    Hi Hubert,
    Regarding the upgrade times, there are a lot of factors like the table
    contents, DB size, tp and R3trans versions and so on that can affect the
    performance. As to my experience, it depends mostly on database performance.
    Please refer to the following SAP notes:
    838725  - Oracle 10.2: Dictionary and system statistics
    830576 -  Parameter recommendations for Oracle 10g
    1171650 - Automated Oracle DB parameter check
    983548 -  Long runtimes during SAP Upgrade using Oracle 10
    558197 - upgrade hangs in PARCONV_UPG, XPRAS_UPG, SHADOW_IMPORT_UPG2
    Additional information:
    1. if the location of the datafiles (upgrade directory) is a local
       directory or a mounted remote directory. For a remote directory
       the connection speed to it is important;
    2. Even if the upgrade directory is local, network layer is used and
       thus network configuration is important. A typical difference
       between production and test systems can be that production is often
       high availability and thus can use e.g. virtual hostnames or other
       methods. Maybe the network setup is then different to non-production
       systems;
    3. Also hardware issues, e.g. if the database or the upgrade directory
       are on fast disks and if caches are used are important;
    4. the database speed (parameters, memory, disks, ....);
    5. if the database is on the host where SAPup and R3trans run or on a
       different host might influence the speed but even a local database
       access uses network layer and thus network configuration for the
       database host is also an issue.
    Best Regards
    Julia

  • After recent patch upgrade, BW delta Data loads for 2LIS_02_ITM failing

    Hi All
    We have patched our BW 3.5 system from 16 to 25. After updating patches, I am geetting delta load issues.
    2lis_02_itm and 2lis_02_scl delta loads are taking long long time. Deltas are failing even for 3000  records . some time it is taking 14 hours .  Delta loads are failing  and I am getting below message. Please advise.
    I am still getting below dump and i could not find any errors in
    ST22. Please see below error.
    Processing in Warehouse timed out; processing steps mising
    Diagnosis
    Processing the request in the BW system is taking a long time and the
    processing step Update rules has still not been executed.
    System response
    <DS:DE.RSCALLER>Caller is still missing.
    Procedure
    Check in the process overview in the BW system whether processes are
    running in the BW system under the background user.
    If this is not the case, check the short dump overview in the BW system.
    Thanks
    Pramod

    Hello Pramod,
    Is this load is to load to initial level ODS? If Yes I understand that you have issue in loading but not at activation of the ODS?
    Normally this kind of issue comes during the activation of ODS.
    1. If you are getting this during the data loads, then try to check loading only to PSA first and then from PSA to target? And check how much time that it's taking as this will help to track the issue whether its present in Source or in BW?
    2. If the load is fine till PSA then try loading the same to ODS and then check whether this issue is present or not?
    3. At the same you need to check the source side the system load and the number of processors which are available?
    4. Did you perform the delta queue draining before the stack upgrade in R/3 or not? Normally as a pre-requisite this needs to be done if not then you will have issues in extracting the data!
    5. Finally this can be avoided by having Initwithout data transfer and then performing the Delta loads. BUt for this need to first extract all the data from Source to BW and then take a down time in R/3 for few min and perform this activity so that the Init Timstamp will be reset properly and the Delta should work fine for you.
    Do get back to us with more details.
    Thanks
    Murali M

  • How to deal with delta queue when importing Support Package/Kernel Patch

    Hi,
    From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
    But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
    Do we need to clear down the delta queue every time we import support package?
    Anyway, is there anyone have any suggestions or steps regarding this question?
    Many Thanks
    Jonathan

    Hi,
    Delta queues during support package upgrade
    Its always better to drain the delta queues before an upgrade.
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Page 17
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    upgrade preparation and postupgrade checklist
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    /message/3221895#3221895
    OSS notes 328181 and 762951 as a prerequisites.
    Failure to follow the instructions in those notes may probably result in data loss.
    https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
    /thread/804820
    Effect on BW of R/3 Upgrade   
    How To Tackle Upgrades to SAP ERP 6.0
    /people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
    Start with the Why — Not the How — When You Upgrade to SAP ERP 6.0
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
    Rapid SAP NetWeaver 7.0 BI Technical Upgrade
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
     https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
    Hope this helps.
    Thanks,
    JituK

Maybe you are looking for

  • EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d641e26, pid=3376, tid=354

    # An unexpected error has been detected by HotSpot Virtual Machine: # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d641e26, pid=3376, tid=3540 # Java VM: Java HotSpot(TM) Client VM (1.5.0_02-b09 mixed mode, sharing) # Problematic frame: # C 0x6d6

  • Can't convert flv to mp4 when I publish to html5

    Hi I have a project that  incorpporates FLV files which where imported succesfully.  When I publish to HTML5, the flv files fail to convert to Mp4.  Ironically, if I publish the entire project to mp4 it works? Has anyone got any ideas. Cheers Mark Ps

  • I have a workaround - but it seems an overkill

    I finally have got something to work.. but surely this can't be the way - can someone from the BC4J/uiXML group confirm that this is the only way --- My update page definition has changed - I added the usesCurrency clause - <bc4j:registryDef> <bc4j:r

  • Restore deleted photos on my ipad

    Hi I have done a stupid thing and deleted my photos from my ipad ! no iCloud yet set up. how can I restore them? HELP

  • Assignment of Profit center in cost center

    Hello Friends, What is the significance of assignment of profit center in cost center ?  System does not allow me to post activity prices in KP26 without assignment of profit center to cost center. It gives error that "Profit center 1000/DUMMY_PCA do