Information Lifecycle

Management for
Oracle Apps Data
Erik Jarlstrom
Director of North American Pre-sales
 Corporate Summary

Founded in 1989
Over 2000 customers in 30 Countries
Committed to providing enterprise database
archiving and test data management solutions
Reputation of high quality and reliable products
Partners with industry leading database and storage
solution providers
Recognized by Gartner, Giga, and Meta as
database archiving market leader

2
3
 Oracle Applications
Data Growth Example
5 Years (GB) 6 Years (GB) 7 Years (GB)
Entire Database 200 300 450

Financials 130 195 292.5

Modules
Accounts Payable 60 90 135

General Ledger 40 60 90

Accounts Receivable 30 45 67.5

Other Modules 70 105 157.5

4
 Related Symptoms

Application users complain their system is slow to:

Perform online account inquiries and financial period closeouts
Enter transactions and process payments
Post batches and generate reports
Process weekly/monthly/quarterly depreciation runs
Increasing operating costs
Higher hardware and software license and support costs
Longer development and test cycles
Labor intensive time and effort for system administrative tasks
Extended maintenance times for managing backup, recovery
and cloning processes
Additional headcount required to adequately manage a larger
environment
5
 Potential Solution: Ignore Database Growth

and continue to add

People
Processes
Technology
and continue to decrease
Production Performance
Database Availability
Time for other projects

6
 Traditional Approaches
Add More Capacity
Bottom line impact
Uncontrolled continuous cost
Institute rigorous database tuning
Does not directly address data growth
Reaches point of diminishing returns
Delete Data (i.e. Purge)
Legal and retention issues
Data may be needed for data warehousing
In-House Development
Complex undertaking
Application specific
Support / upgrade / maintenance /
opportunity cost
7
 Strategy: Information Lifecycle
Management
Understand data retention requirements
All data has a life cycle from acquisition to disposal
Define availability level requirements
Acquisition of Data

At various stages, data has different: Disposal Heavy Access

Business value
Access requirements
Performance requirements Rare Access Medium Access

Implement storage strategy to meet availability

requirements
Each stage should be stored on the appropriate type of storage
Segregate application data to support strategy
Data should be managed to match the business value

8
 Matching Access and Performance
to Business Value

Email / Report / Record creation,

Document receipt,
Statement print time
retrieval
retrieval

Relative
and

All retrievals from low-cost, lower -

Relative
and

performance, archival media

access

from this point forward

access

value
value
High-performance
of of

Disk purge

of of
Frequency

record
Frequency

record
Disposition

High-cost, Low-cost,
Fast response Slow response
(Sub-second) (30 seconds to days)

Retention period

2003 Enterprise Storage Group, Inc. Source: Enterprise Storage Group, May 2003

9
 Implement Storage Strategies to Meet
Availability Requirements

RDBMS and High-

Concurrency
Storage (RAID)

RDBMS,
File Systems,
NAS, Optical

Tape or Optical
Storage

10
 Segregating Application Data to
Support Storage Strategy

ORDER_DATE >
01-JAN-2002

ORDER_DATE >
01-JAN-1998 &
< 31-DEC-2001

ORDER_DATE <
31-DEC-1997

11
 Information Lifecycle Management
Archiving Strategy

On-Line Off-Line
Current History/Reporting
Archive Archive
Path 1 Archive Archive
Production
Archive Database Flat Files Tape
Database Archive Restore Restore

Years 1 - 2 Years 3 - 5 Years 6 - 7 Years 8+

(Adjust timeframes to meet internal & statutory requirements)

12
 Solution: Active Archiving
Archive
Files
Archive
Production
Database Archive
Database &
Archive Files
Restore

Data Access (locate, browse, query, report)

Reduce amount of data in the application database

Remove obsolete or infrequently used data
Maintain business context of archived data
Archive relational subsets vs. entire files
Enable easy user access to archived information
View, research and restore as needed
Support Data & Storage Management Strategies
13
 Example Active Archiving Policies

Production Archive Ongoing Archive

Database Database Processing

Company A 24 months GL, AR, AP, Older GL, AR, AP, PO, Quarterly GL, AR, AP,
PO, and FA data and FA data PO, and FA data

Company B 24 months GL and FA Older GL and FA data Yearly GL and FA

data data

Company C 24 months Order Older OM, AP, and PO Monthly OM, AP, and
Management (OM) data data PO data
12 months AP and PO
data
Company D 15 months AR, AP, PO, Older AR, AP, PO, and Quarterly AR, AP, PO,
and OM data OM data and OM data

14
 Archiving Oracle Apps Data
Archiving Historical Data
Archive
Database
GL Balances, Journals
AP Payments, Invoices, Vendors General Ledger
AR Receipts, Invoices
Payables
Production FA Depreciation, Adjustments
Database Purchasing POs, Reqs, Receivables
OM Orders,
Assets
INV - Transactions
Locate, Browse, Query, Report . . .

Data Access

15
 Transparent Access How?
Responsibility-Driven Data Access

16
 Transparent Access - Forms

Production

17
 Transparent Access - Forms

Archive

18
 Transparent Access - Forms

Archive & Production

19
 Transparent Access - Reports

Production

20
 Transparent Access - Reports

Archive

21
 Transparent Access - Reports

Archive & Production

22
 Top Requirements for
Enterprise Database Archiving
Extract subsets of related data to offload
Able to go beyond catalog-defined relationships
Selectively/relationally delete all or some
archived data
Selectively/relationally restore
Access, browse, query archived data
Preserve business context of archived data
Comprehensive archive data management
Architecture for long term enterprise-wide
strategy

23
 Challenge: Referential Complexity

24
 Manage Your Enterprise Data Smarter
Test Smarter with Store Smarter with
Relational Tools Active Archive Solutions

Pre-Production Production
(Test, Dev, Training, )
Oracle
PeopleSoft ClarifyCRM
Apps

Relational Archive Archive for

Tools for Servers DB2

Relationship Engine

SQL DB2
Oracle Sybase Informix DB2 Legacy
Server UDB

25
 Suggested Resources

Databases on a Diet: Meta - Jan 2003

Banking on Data: InformationWeek Aug 4, 2003
Bank of New York implements active archiving
Enterprise Storage Group (ESG) Impact Report on
Compliance - May 2003
The effect on information management and the
storage industry
Princeton Softechs Web site and whitepapers
www.princetonsoftech.com

26
 Questions

Erik Jarlstrom
Princeton Softech
ejarlstrom@princetonsoftech.com
916.939.8191
27