Can you update the three plans using the guidance below an send another version? Start with the archival segment... get a level of comfort with details.. and then attempt the remaining two?
a) Each of the three segments should be a stand-alone plan. i.e. A manager from DDM should be able to take the plan to his team or vendor and ask them to execute with minimal guidance.
b) Plan should address people, process and technology dimensions.
Examples: PEOPLE: Identify/confirm team members. Confirm scope with stakeholder. Confirm validation with business team etc.
PROCESS: Identify metadata and reference tables associated with transaction tables.
TECHNOLOGY: Conduct capacity planning for target environment. Confirm environment readiness (prior to data movement)
c) Most of the tables will have referential integrity defined. Our plan should include sequence of tables movement to target. This sequence should be leveraged for retrieval and purge
d) Do we foresee any points of failure when we archive or retrieve data ? If so, we should include the steps to detect/mitigate the issues
e) All the three segments need some form of reporting. How many tables were archived? How much data is archived or retrieved?
f) We need control tables to keep dates and metrics of data movement
g) Assuming this is a batch environment, we need schedulers to run the scripts. Do we need a workflow or standard cron jobs?
h) Include error detection and notification for data identification, data movement and data validation
i) What other Oracle features can we leverage for data archival. Can we copy data to select tblsp and then move tblsp? How do we make this efficient? Can you discuss with other DBA practitioners and see if they have documented plans similar to what we are doing? May save quite a bit of time. Check for State HIX projects that deal with large volumes.
1. Archive data from production based on thresholds to target archive repository
Development Team and Design Team along with Production Administrators, Engineers
Perform Data volume estimates for production data.
Implement storage strategy to meet availability requirements
Segregate application data to support strategy
Classify data into classes and specify volume of each class
Retain the referential integrity of data across related tables and applications
The archival period is 3 hours
Required hard drive capacity is approximately 50 GB
Oracle stores task data in following tables:
Before initiating archival backup of these tables should be created
Following are tables which are usually achieved
When the Requests Archival utility is run for the first time, a corresponding archival table is created for all the tables that are to be archived. The archival tables are created in a separate tablespace named OIM_REQUEST_ARCH. This tablespace must be created before running the utility.
2. Retrieve data from archive repository and release for ...
Data archival plan is examined.