Data Archiving suggestions

Hi- we have an HFM application with 8 years of data in it. Obviously this increases the size of our database and causes database copies with HFMcopyapp to take longer. We are trying to come up with an archiving strategy to move old data into a mirrored application or ?????. Just looking for some input on anyone's experience with this and how to keep the metadata in sync when changes are made to the current application that impact archived years..
Thanks
We are on 9.2.1
Jeff

assuming the historical data is static, why would you need to apply current metadata changes? Still if this is the case why not just load metadata in replace mode on the archived app? A move up to a later releases will give you more options from the EPM architect.

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

A question on different options for data archival and compression

Hi Experts,
I have production database of about 5 terabyte size in production and about 50 GB in development/QA. I am on Oracle 11.2.0.3 on Linux. We have RMAN backups configured. I have a question about data archival stretegy. To keep the OLTP database size optimum, what options can be suggested for data archival?
1) Should each table have a archival stretegy?
2) What is the best way to archive data - should it be sent to a seperate archival database?
In our environment, only for about 15 tables we have the archival stretegy defined. For these tables, we copy their data every night to a seperate schema meant to store this archived data and then transfer it eventualy to a diffent archival database. For all other tables, there is no data archival stretegy.
What are the different options and best practices about it that can be reviewed to put a practical data archival strategy in place? I will be most thankful for your inputs.
Also what are the different data compression stregegies? For example we have about 25 tables that are read-only. Should they be compressed using the default oracle 9i basic compression? (alter table compress).
Thanks,
OrauserN

You are using 11g and you can compress read only as well as read-write tables in 11g. Both read only and read write tables are the candidate for compression always. This will save space and could increase the performance but always test it before. This was not an option in 10g. Read the following docs.
http://www.oracle.com/technetwork/database/storage/advanced-compression-whitepaper-130502.pdf
http://www.oracle.com/technetwork/database/options/compression/faq-092157.html

Regarding data Archiving

Hi,
       All
               my client needs to archive Data in SAP 8.8 each year having only 1 year completed.Can we archive data
               less than 3 year?
Thanks in Advance

There will not be any technical problem if the archiving is done as per the instructions set by SAP (I suggest you go through DATA Archiving Session from SAP), What I meant was that any data which is less than 3 year old may still be considered as new data and if this is archived you are left with no choice to modify anything in this data as this becomes read-only. If the client is looking for extra space on server by Data Archiving you can suggest other step as well . Again as I said it is the client's call afterall.
regards
johnson

Data archival and purging for OLTP database

Hi All,
Need your suggestion regarding data archival and purging solution for OLTP db.
currently, we are planning to generate flat files from table..before purging the inactive data and move them to tapes/disks for archiving then purge the data from system. we have many retention requirements and conditions before archival of data. so partition alone is not sufficient.
Is there any better approach for archival and purging other than this flat file approach..
thank you.
regards,
vara

user11261773 wrote:
Hi All,
Need your suggestion regarding data archival and purging solution for OLTP db.
currently, we are planning to generate flat files from table..before purging the inactive data and move them to tapes/disks for archiving then purge the data from system. we have many retention requirements and conditions before archival of data. so partition alone is not sufficient.
Is there any better approach for archival and purging other than this flat file approach..
thank you.
regards,
varaFBDA is the better option option .Check the below link :
http://www.oracle.com/pls/db111/search?remark=quick_search&word=flashback+data+archive
Good luck
--neeraj

Best Practise for Data Archiving

Hi All,
I have query in SAP that when business will do the data archving in their R3 systems.
On which basis they will do data archiving?
Is there any minimum period that data need's to be archived?
before doing the data archiving what they will do ?
Regards
Srini

Hi Srini,
1. SAP suggestes to implement data archiving strategy as early as possible to manage database growth .
However pople think of archiving when they realise the problems like large data volumes,slow system resonse time,performance issues etc...
2. There is a proper way to implement Data Archiving . Database has to be anaylzed first for getting the top DB tables and Archiving objects.
3. Based on the DB analysis ,Data archiving plan has to be implenemted according to data management guide.
4. There is a minimum period known as residence time has to be completed before any data to be archived. Once the document is business completed and serverd its minimum required period in the Database ,it can be archived.
5, Before going for data archiving there are many steps to be followed like analysis,configuration etc that you can see in details at the link below :
http://help.sap.com/saphelp_47x200/helpdata/en/2e/9396345788c131e10000009b38f83b/frameset.htm
let me know if this helps you .
-Supriya
Edited by: Supriya Shrivastava on May 4, 2009 10:38 AM

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

Microsoft Dynamic CRM Data Archiving solution

Hi,
How can i archive data in dynamic CRM.
e.g. If i have last 20 years data in dynamic CRM then i wants to archive data in another organization and then retrieve in same organization.
If this process is available in dynamic CRM or how can i create this tool for the same.
Please suggest me for this.
Thanks

Hi Narendra,
Recently i implemented the Data Archiving in CRM 2011 in supported way.
We identified the entities where the volume of data is very high over the period like case, opportunity, activity, system jobs, lead etc.
I am using "SSIS Integration Toolkit v5.1 for Microsoft Dynamics CRM" from KingswaySoft to create and delete the data.
I created a new organization same as main organization. In new organization i create the closed case, opportunity, activity, lead from main organization and once done i delete them from main organization. This exercise we execute in every 3 months. We always
delete the completed system jobs from main organization. And we provided the access to new organization only to few admin users just for reporting purpose.
Chandan - http://mscrm-chandan.blogspot.in/ I hope this helps. If my response answered your question, please mark the response as an answer and also vote as helpful !!!

What are different Data archival approaches available in SharePoint 2013?

I want to know what are the different Data archival approaches available in SharePoint 2013 apart from Record Management?

Record center is the best template available for data archival.
You can also use IRM for Data Archiving
Also I would suggest you to use BLOB stoage which will reduce addional burden on SQL server:
http://blogs.technet.com/b/wbaer/archive/2012/11/12/introduction-to-shredded-storage-in-sharepoint-2013.aspx

HR PA Data Archiving

Hi,
We are undergoing the archiving project for HR module. For PD data, we can use object BC_HROBJ, for PCL4 data, we can use PA_LDOC. What about 2000 series infotypes data, such as PA2001, PA2002, PA2003, etc.? Because all changes to these infotypes are stored in PCL4 cluster LA, we only need to purge the data from these tables. What is the best way to purge PA2xxx data? We cannot use transaction PA30/PA61 to delete records because user exit edits prevent any action against old data beyond certain time frame.
Thanks very much,
Li

This is not directly related to SAP NetWeaver MDM. You may find more information about data archiving on SAP Service Marketplace at http://www.service.sap.com/data-archiving or http://www.service.sap.com/slo.
Regards,
Markus

Business Partner Data Archiving - Help Required

Hi,
Am New to Data Archiving and need help to Archive Business Partner in CRM. I tried to Archive some BP's but it was not archiving. Kindly throw some light on it.
Problem we face are:
1) When we try to write a Business Partner to an Archive File the Job Log Shows finished but no files are created in the System.
2) When we try to delete the BP from Data Base it doesn't show the Archived BP's that could be deleted (I guess this is because there are no archived file).
Archive Object Used is CA_BUPA. We have created a Variant and set the Time as Immediate and Spool to LOCL.
Kindly let us know if there is any step we are missing here and if we are on the wrong track.
All answers are appreciated.
Thanks,
Prashanth
Message was edited by:
        Prashanth KR

Hi,
To archive a BP following steps are to be followed.
A. Mark the BP to be archived in transaction BP >status tab
B. Run dacheck
FYI : Steps on how to perform dacheck :
1. In transaction DACONTROL change the following parameter to the
values : for CA_BUPA .
No. calls/packages   1
Number of Objects   50
Package SizeRFC     20
Number of Days       1 (if you use mobile client it should be more)
2.If a business partner should be archived directly after the
archiving note was set, this can be done by reseting the check
   date with report CRM_BUPA_ARCHIVING_FLAGS.
   here only check (set) the options :
   - Archiving Flag
   - Reset Check Date
Reset all options should be unchecked.
3. go to dacheck and run the process
4. This will change the status of the BPs to 'Archivable'
   *Only those bp's which are not involved in any business transactions,
    install base, Product Partner Range (PPR) will be set to archivable
The BP's with status 'Archivable' will be used by the archiving
     run.
Kindly refer note 646425 before goint to step C ***
C.Then run transaction CRM_BUPA_ARC.
- Make sure that the "selection program" in transaction "DACONTROL"
   is maintained as " CRM_BUPA_DA_SELECTIONS"
Also create a variant, which can done by excecuting
CRM_BUPA_DA_SELECTION and enter the variants name for the field
Variant. This variant is the buisness partner range.
- Also please check note 554460.
Regards, Gerhard

Data archiving for Write Optimized DSO

Hi Gurus,
I am trying to archive data in Write Optimized DSO.
Its allowing me to archive on request basis but it archives entire requests in the DSO(Means all data).
But i want to select to archive from this request to this request.(Selection of request by my own).
Please guide me.
I got the below details from SDN.Kindly check.
Archiving for Write optimized DSOs follow request based archiving as opposed to time slice archiving in standard DSO. This means that partial request activation is not possible; only complete requests have to be archived.
Characteristic for Time Slice can be a time characteristic present in the WDSO, or the request creation data/request loading date. You are not allowed to add additional infoobjects for semantic groups, default is 0REQUEST & 0DATAPAKID.
The actual process of archiving remains the same i.e
Create a Data Archiving Process
Create and schedule archiving requests
Restore archiving requests (optional)
Regards,
kiruthika

Hi,
Please check the below OSS Note :
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_whm/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313338303830%7d
-Vikram

Vendor Master Data Archiving

Hi,
I wanted to archive vendor master data. I got program - SAPF058V which gives FI,Vendor Master Data Archiving: Proposal list.
This program checks whether and which Vendor Master data can be archived or not. I am getting error message after running this program with selection of one of the Vendor saying that "Links stored incompletely". Can someone pls help on this
Thanks...Narendra

Hi,
Check if you have an entry in table FRUN for PRGID 'SAPF047'. Other option is set the parameter 'FI link validation off'' with the flag on (ie: value 'x'). Check the help for this flag, surely this vendor have a code of customer. Perhaps you must try to delete this link in customer and vendor master before.
I hope this helps you,
Regards,
Eduardo

Data Archiving - System Prerequisites

Hi,
We are planning to ARCHIVE some of the tables to reduce the TCO. (Total cost of Ownership)
In this regard, I would like to know the following:
On the Basis side, I want to check for any prerequisites etc (like Minimum SP LEVEL, Kernel version, Import Notes to be applied etc)
Are there any document which clearly talks about these prequisites for preparing the System in order to be able to carry out the Archive work without any issues.
(Note: We are not using ILM solution for Archiving)
I am mostly concerned with the SAP Notes that are considered to be the prerequisites.
Best Regards
Raghunahth L
Important System information :
Our system version is as follows :
System -> ERP 2005 (Production Server)
OS      -> Windows 2003
DB      -> Oracle 10.2.0.2.0
SPAM    -> 7.00 / 0023
Kernel -> 7.00 (133)
Unicode -> Yes
SP Info:
SAP_BASIS 700(0011)
SAP_ABA 700(0011)
PI_BASIS 2005_1_700(0003)
ST-PI 2005_1_700(0003)
SAP_BW 700(0012)
SAP_AP 700(0008)
SAP_HR 600(0003)
SAP_AP 700(0008)
SAP_HR 600(0013)
SAP_APPL 600(0008)
EA-IPPE 400(0008)
EA-DFPS 600(0008)
EA-HR 600(0013)
EA-FINSERV 600(0008)
FINBASIS 600(0008)
EA-PS 600(0008)
EA-RETAIL 600(0008)
EA-GLTRADE 600(0008)
ECC-DIMP 600(0008)
ERECRUIT 600(0008)
FI-CA 600(0008)
FI-CAX 600(0008)
INSURANCE 600(0008)
IS-CWM 600(0008)
IS-H 600(0008)
IS-M 600(0008)
IS-OIL 600(0008)
IS-PS-CA 600(0008)
IS-UT 600(0008)
SEM-BW 600(0008)
LSOFE 600(0008)
ST-A/PI 01J_ECC600(0000)
Tables we are planning to archive
AGKO,     BFIT_A,     BFIT_A0,     BFO_A_RA,     BFOD_A,     BFOD_AB,     BFOK_A,     BFOK_AB,     BKPF,     BSAD,     BSAK,     BSAS,     BSBW,     BSE_CLR,     BSE_CLR_ASGMT,     BSEG_ADD,     BSEGC,     BSIM,     BSIP,     BSIS,     BVOR,     CDCLS,     CDHDR,     CDPOS_STR,     CDPOS_UID,     ETXDCH,     ETXDCI,     ETXDCJ,     FAGL_BSBW_HISTRY,     FAGL_SPLINFO,     FAGL_SPLINFO_VAL,     FAGLFLEXA,     FIGLDOC,     RF048,     RFBLG,     STXB,     STXH,     STXL,     TOA01,     TOA02,     TOA03,     TOAHR,     TTXI,     TTXY,     WITH_ITEM,          COFIP,     COFIS,     COFIT,     ECMCA,     ECMCT,     EPIDXB,     EPIDXC,     FBICRC001A,     FBICRC001P,     FBICRC001T,     FBICRC002A,     FBICRC002P,     FBICRC002T,     FILCA,     FILCP,     FILCT,     GLFLEXA,     GLFLEXP,     GLFLEXT,     GLFUNCA,     GLFUNCP,     GLFUNCT,     GLFUNCU,     GLFUNCV,     GLIDXA,     GLP0,     GLPCA,     GLPCP,     GLPCT,     GLSP,     GLT0,     GLT3,     GLTP,     GLTPC,     GMAVCA,     GMAVCP,     GMAVCT,     JVPO1,     JVPSC01A,     JVPSC01P,     JVPSC01T,     JVSO1,     JVSO2,     JVTO1,     JVTO2,     STXB,     STXH,     STXL,     TRACTSLA,     TRACTSLP,     TRACTSLT,
in addition we have some Z Tables to be archived.

Hi,
Pre-requisites for search OSS notes or BC Sets depends upon the program that is used in archive, delete or read.
If there is no proper selection criteria in write variant selection,
If the program is getting terminated due to long processing time,
If percentage of data archived for your selection is less even after data meeting minimum criteria,
If system allows user to change archived data,
With all the above scenarios we will search for OSS notes. If SAP has released BC sets then we will implement these.
If you have any problem while archiving and based on the archiving experience if you think that some of the oss notes will help then take a call on implementing it.
With the tables you have mentioned i can say that archiving objects such as FI_DOCUMNT, FI_SL_DATA, EC_PCA_ITM, EC_PCA_DATA, CHANGEDOCU, ARCHIVELINK.
You have to search any latest release BC sets or OSS notes for your system application.
-Thanks,
Ajay

Can I add multple tables to a single Flashback Data archive

Hi ,
I want to add mutilple tables of a schema to a single Flashback Data archive . Is this possible ?
I dont want to create multiple Flash back archives for each table
Also can i add an entire schema or a tablespace to a flash back archive created ?
Thanks,
Sachin K

Do adding multiple tables to a single flashback archive feasible in terms of space ?Yes, you can use. Multiple tables can share the same policies for data retention and purging. Moreover, since an FBDA consists of one or more tablespaces (or subparts thereof), multiple FBDAs can be constructed, each with a different but specific retention period. This means it’s possible to construct FBDAs that support different retention needs. Here are a few common examples:
90 days for common short-term historical inquiries
One full year for common longer-term historical inquiries
Seven years for U.S. Federal tax purposes
20 years for legal purposes
How is the space for archiving data to a flashback archive generally estimated ?[url http://docs.oracle.com/cd/E18283_01/server.112/e16508/process.htm#BABGGHEI]Flashback Data Archiver Process (FBDA)
FBDA automatically manages the flashback data archive for space, organization, and retention. Additionally, the process keeps track of how far the archiving of tracked transactions has occurred.
It (FBDA) wakes up every 5 minutes by default (*1), checks Tablespace quotas every hour, creates history tables only when it has to and rests otherwise if not called to work. The process adjusts the wakeup interval dynamically based on the workload.
(*1) *1 Contradicting observations to MOS Note 1302393.1 were made. The note says that FBDA wakes up every 6 seconds as of Oracle 11.2.0.2, but a trace on 11.2.0.3 showed:
WAIT #140555800502008: nam='fbar timer' ela= 300004936 sleep time=300 failed=0 p3=0 obj#=-1 tim=1334308846055308
5.1 Space management
To ease the space management for FDA we recommend following these rules:
- Create an archive for different retention periods
o to optimally use space and take advantage of automatic purging when retention expires
- Group tables with same retention policy (share FDAs)
o to reduce maintenance effort of multiple FDAs with same characteristics
- Dedicate Tablespaces to one archive and do not set quotas
o to reduce maintenance/monitoring effort, quotas are only checked every hour by FBDA
http://www.trivadis.com/uploads/tx_cabagdownloadarea/Flashback-Data-Archives-Rechecked-v1.4_final.pdf
Regards
Girish Sharma

Data Archiving suggestions

Similar Messages

Maybe you are looking for