SAP Data Archiving in R/3 Ecc6.0, MS-SQL 2008 Server:

We are using MS-SQL 2008 Database, these days our production database growing quite faster. I want to setting up Data Archiving using T'Code DB15. Can anyone give steps to setup Data Archinving using DB15?
Edited by: Ahsan's on Jul 19, 2010 11:44 AM

Archiving data is bound to legal things depending on the country and the company you work. Setting up archiving is not following a few steps, you'd need to have a system where to put the archiving data.
Markus

Similar Messages

  • SAP Data Archiving in R/3 4.6C and ECC 6.0.

    Hi Guys,
        Need some suggestions,
    We currently working on SAP R/3 4.6 and have plans to upgrade it to ECC 6.0,
    In the mean time there is an requirement for SAP Data Archiving for reducing the database size and increase system performance.So wanted to know if its better to do Data Archiving before upgrade or after. Technically which will be comfortable, Also wanted to know if any advanced method available in ECC 6.0 compared to SAP R/3 4.6.
    Please provide your valuable suggestion.
    Thanks and Regards
    Deepu

    Hi Deepu,
    With respect to archiving process there will be no major difference in 4.6 and ECC 6.0 system. However you may get more advantage in ECC6.0 system because of Archive routing and also upgraded Write, Delete programs (upgraded program will depend on your current program in 4.6 system). For example In 4.6 system for archive MM_EKKO write program RM06EW30, archiving of purchase document is based on company code in the selection criteria and there is no preprocessing functionality. In ECC 6.0 you can archive by purchase organization selection criteria and preprocessing functionality will additional help in archiving of PO.
    In case if you archive documents in 4.6 and later upgrade it to ECC 6.0, SAP system will assure you to retrieve the archived data.
    With this i can say that going with archiving after upgrade to ECC 6.0 system will be better with respect to archiving process.
    -Thanks,
    Ajay

  • New to SAP Data Archiving

    Hi,
    Is it a must to have third party tool/ software for SAP Data Archiving
    OR
    SAP has its own solution for (CREATE archive files, WRITE archive files and DELETE from database).
    Any pointers for some more information on different stages of SAP Data Archiving project. (Any links to how-to documents would be great help.)
    Regards,
    Rehan

    You have posted your query in a wrong forum.
    This space is for discussion on SAP TDMS topics.
    You may check in the forum Information Lifecycle Management
    for any available information.

  • Access SAP Data Archival file from outside SAP

    Hello Everyone,
    I have a requirement to archive the SAP data, dump that outside SAP in some other system like ILM or BI and build a reporting tool on top of that data.
    So, basically customer want to shutdown the SAP and want to retain data for legal and audit pourpose.
    I was doing some RnD and done archiving of MM_EKKO using SARA. the file got generated with extention .ARCHIVE. I donwnloaded teh file but it is encoded file with all special character in it.
    My question is:
    1. How can I read the archieved SAP data from outside SAP system.
    2. Can we decode the .ARCHIVE file to get it in .DAT format?
    3. Or Is there any other way to access the SAP data outside SAP in a report format.
    Thanks,
    Chintan SOni.

    Hi Chintan,
    1. How can I read the archieved SAP data from outside SAP system.
    For this you could refer SAP Note   460620 - Migrating archive files
    2. Can we decode the .ARCHIVE file to get it in .DAT format?
    As per my knowledge,it's not possible to decode or move to .DAT format.
    3. Or Is there any other way to access the SAP data outside SAP in a report format.
    Refer my first response & the SAP note.
    Hope this will help you.
    Good luck !!
    Gaurav

  • SAP Data Archival Project Documentation Report

    hi,
    Do any one can send me the documentation report on Data Archival .It ll be more helpful 2 me...Plz send me ASAP...
    Thanx in advance..

    Hi Kota,
    Check this link
    http://www.opentext.com/2/sol-products/sol-pro-extensions-sap/pro-ll-sap-dataarchiving.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
    <b>Regards,
    Jackie.</b>

  • SAP Data Archiving

    I have question on Archiving Statistics.
    I get some statistical information in the spool file of the archive run. And also I can see some additional statistical information when clicked on the "Statistics" button under the SARA transaction.
    I am trying to understand the relation, primarily, among:
    1) Size of Archiving Session in MB
    2) Occupied Database space in MB
    3) Deleted Database space in MB
    Which of these numbers or a combination would reflect the actual disk space emptied by the Archiving run from Database?
    This information is critical for the upper management.
    Your help is highly appreciated.
    Regards,
    Srinivasa

    Hi Juan,
    Appreciate your inputs. Even though the performance improvements is the primary objective for implementing archiving, containing the data growth as well is an objective. I am not sure if there are any methodoligies to quantify the performance improvements resulting from archiving. Currently I am concerned about quantifying the containment of data growth as a result of archiving.
    I have been also looking at documentation on archiving statistics. SAP says data archiving does a 5:1 compression for non-cluster tables, and no further compression for cluster tables.
    When SAP is providing the statistical information (from the spool file of an archive session and also the "Statistics" button under the SARA transaction), I believe that should be CORRECT. And I am confused as to what the numbers in the statistics really reflect.
    Here are the numbers from a production run of CO_ML_IDX (which archives data from CKMI1 table):
    From the spool file the numbers are:
    Size of Archiving Session in MB   -    700.900
    Occupied Database Space in MB     - 10,827.569
    From the statistics display the numbers are:
    Disk Space         -   700.9
    DB Space (Write)   - 10827.57
    DB Space (delete)  -     0
    Did this archive run free up 3504.5 MB (which is 5*700.9)
    or 10827.57 MB (the DB Space written)? Should the "DB Space (Delete)" not reflect the space deleted from the database? If so it should have some non zero value.
    How are these three values related to actual disk space freed up in the database as a result of this archive run?
    Appreciate for sharing your findings.
    Regards,
    Srinivasa

  • Error: SAP installation of ERP Sr3 with ORACLE 10g on Windows 2008 server

    Dear all,
    while installaing SAP ERP SR3 with ORACLE 10g on windows 2008 server...
    we are getting error as not support.
    please confirm wether this version of OS is uspported or not.
    thanking you in all,
    by
    Animesh

    actualy we tried to change Oraparam.ini file in the installation folder...
    edited ...  windows= 5.0, 5.1, 6.0
    we had entered 6.0
    Yes - that is necessary.
    and started ... but after starting we are getting ERROR like unKNOWN and installation popup (OUI popup) exiting with .. error popup.
    Yes - because Oracle delivers its own Java version - which is too old to run on Windows 2008.
    if you suggest us to use 2003 64 bit for temporaray .... purpose.
    and is there any specified procedure to UPgrade OS.
    like... DB should be updated before OS upgradation.
    You can run 10.2.0.4 on Windows 2003 x64 nicely and upgrade to Windows 2008. Since there is no "upgrade" (it is the highest version supported) there´s no need to do anything.
    The question you have to ask is:
    Why do you need Windows 2008? Is there any technical implication?
    Markus

  • Date parameter does not work in SharePoint 2010 report using SQL 2008 Server Reporting Service

    Here is the settings:
    SharePoint 2010 with SQL server 2008 reporting services configured
    When create a report for a SP list using SQL server report builder (3.0) the date parameter does not work.
    The data parameter is set as "date and time" type and field name equals the col name in the SP list
    When run the report, the whatever dates I select, the result is always the same, so the parameters do not take any effect.
    Is any step missing?
    Thanks for any advice !

    Hi ,
    How did you configure you "date and time" type parameter and field name equals the col name in the SP list?
    Have you tested if other type parameter worked?
    Have you tried typing the date format as 20140722 in your date parameter filed before run the report?
    http://whitepages.unlimitedviz.com/2012/02/using-sharepoint-filters-with-reporting-services-parameters-for-personalized-reports/
    Thanks,
    Daniel Yang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Daniel Yang
    TechNet Community Support

  • Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

    A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice  but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management.  Our consultants come with significant global experience implementing projects for the worlds largest corporations.
    Archiving before Upgrade
    It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
    It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
    Archiving also yields Long-term Cost Savings
    By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

    Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

  • SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

    Dear All,
    I am planning to do SAP Upgrade from 4.6C to ECC 6.0 EHP5, in the source system customer is using SAP DATA ARCHIVING. As per some of the SAP Notes before downtime phase we need to disable all the dataarchiving jobs .
    1) My question is do we need to do any presteps before starting the upgrade related to SAP DATA ARCHIVING ?
    2) After the upgrade if customer wants to use the old archiving objects etc... whether they will able to do it. For this do we need to raise any message with SAP regrading the dataarchiving before the upgrade
    Please let me know if you have any ideas on the above questions.
    Thanks & Regards
    Ravikiran

    Hi,
    I would suggest you to do the data archiving after upgrade project or finish data archiving before upgrade project. As lots of new archiving objects has been delivered in ECC.
    Also, its true that before starting downtime project you need to stop all your jobs. Also, SAP has recently introduced new retention management technique for data archiving starting from EHP4 onwards to manage data archiving more efficiently. If you are interested, you can explore this further on http://sdn.sap.com/irj/sdn/ilm or http://service.sap.com/ilm.
    Thanks
    Sunny

  • SAP Support for Data Archiving

    Hello,
    We just wanted to confirm if SAP will support issues if we encounter issues while restoring data archived via SARA. For example, if in the process of restoring archived data a defect is found, is this still supported by SAP?

    Hi
    Supported and the SAP Data Archiving Support Tools  are SARA , DART and SARI
    SARA --- SAP Archive Administration
    All data archiving activities commence with Archive administration (transaction SARA). SARA provides the overall administration of archiving schedules and manages the archiving sessions. The process includes customization of objects, their conversion to archived sequential archived files and most importantly, their overall management. In addition to these, the archive administration process also retrieves the archived files and converts the data through an automated process, if there is a change in software, hardware or the data structure. The data archiving process is streamlined and simplified through the Central command of archiving administration
    DART --- Data Retention Tool
    A data retention strategy is required for retaining enterprise information for long periods of time. The Data Retention Tool (DART) provides this functionality. It is capable of extracting data, which is period-specific as well as any supporting information. DART transforms database objects into flat files that can be read by any third-party software designed for flat files. It is available as an add-on for older versions of SAP R/3, but is an integrated feature of the recent versions of SAP R/3.
    SARI --- SAP Archive Information System
    SARI provides much-needed retrieval capabilities against previously archived data. It requires the archive files be loaded into new tables in the database. In this approach, AS requires detailed, technical knowledge of the database table structure and field layouts. Database structure of an enterprise needs to be flexible and dynamic to be able to quickly adapt to organisational changes. It might happen that the current database structure is not compatible with the structure of database when archive files were initially generated. Archive Information System is a standard tool delivered by SAP that facilitates customized access to the archived data
    Regards
    Venkat

  • CS-MARS, data archiving issue.

    Hello at all.
    I'm using CS-MARS-20.
    Reimaged, restored and upgraded to software version 6.1.8, I'm not able to start data archiving successfully.
    I have configured data archiving using a remote SFTP server, click Apply, Start and Activate: data archiving status is running, service is enabled and remote server is available.
    But MARS doesn't archive nothing!
    Using another SFTP remote client with the same account used from appliance, I can create folders, files and remove.
    Any ideas?
    Thanks.
    Regards.
    Andrea

    Now we are moving to a NFS solution.
    Data archiving status is running, archiving service is enabled and remote server is available but events, incidents and configuration are not exported.
    I can use CLI (pnexp command) to export configuration successfully.
    Any ideas?
    Why data archiving doesn't work?
    Thanks.
    Andrea

  • Windows 2008 Server R2 & SAP Business One

    Does anyone have any experience, good or bad, with SAP Business One and Terminal Service on Windows 2008 Server R2?  We are finding a number of issues with this configuration and we are looking for any feedback that is out there.
    Here is the situation - our customer is running SAP Business One v2007 SP01 PL09 Hotfix4 on a Windows 2008 Server R2 machine.  All users (15 max) access SBO via Terminal Service to this machine, which also holds the databases (SQL Server 2005).  The machine currently has 20GB of RAM.
    What we are finding is:
    1) When any process related to SBO (SBO core or add-ons) consumes some portion of memory, none of that memory is ever released back to the O/S until SBO is completely closed.  So over the course of a day each user ends up simply consuming more and more memory as forms are opened for transactions.  While we do see this in Windows 2003 Server to some extent, at least some memory is released when a given form is closed.
    2) Once the system hits a point where around 75% of RAM is consumed the users start seeing application "hangs" and are forced to manually terminate SBO (via Task Manager) and restart.  There doesn't seem to be any paging or use of virtual memory (if my terms are right) in use.
    3) If the system is busy and a new window/form is opened the new window immediately (within one or two seconds) presents the "Not Responding" message on the new window.  Depending on the circumstances the application is simply waiting for resources and will continue opening normally.
    I would appreciate feedback from anyone who has experience with Windows 2008 Server R2; and especially using it for Terminal Services.  My personal feeling is that it is a platform that should be avoided but we would certainly like to hear what other folks have to say.
    Regards,
    Ross Unger
    Third Wave Business Systems

    I believe the supporting of this OS is still on Planned basis.  You may check with SAP support to give them a good user case to fight with any non-compatible issues.
    Thanks,
    Gordon

  • What is data archiving and DMS(Data Management System) in SAP

    what is data archiving and DMS(Data Management System) in SAP
    Welcome to SCN. Before posting questions please search for available information here and in the web. Please also read the Rules of Engagement before further posting.
    Edited by: kishan P on Aug 31, 2010 1:06 PM

    Hi,
    Filtering at the IDoc Level
    Identify the filter object (BD59)
    Modify the distribution model
    Segment Filtering
    specify the segments to be filtered (BD56)
    The Reduced IDoc Type
    Analyze the data.
    Reduce the IDoc type (BD53)
    Thanks and regards.

  • Data extraction from Non-Unicode ECC6 to Unicode SAP BI system

    Hi,
    We have an existing non-unicode ECC6 system. Currently we are installing SAP BI unicode system. Can anyone tell me are there any issues in data extraction for SAP BI from a non-unicode ECC6 system to an Unicode SAP BI system ?
    Please also note that our data consists of Asian (korean, Japanese & Chinese) fonts.
    Regards,
    Anirban

    Hi Des Gallagher,
    Thank you for your reply.
    I have gone through the notes suggested by you, but they suggest issues related to BW 3.x versions. We are currently on SAP_BW 700 - SP16. Also, among other notes i found note 510882 which might be helpful for custom developments.
    But i am still wondering whether we are going to face major issues related to data extraction from non-unicode ECC6 system to unicode SAP_BW 700 system.
    Incase you have any further details, please let me know.
    Thanks in advance.
    Regards,
    Anirban Kundu

Maybe you are looking for