Archive Purge Best Practices v3 PDF

E-Business Suite Archive and Purging
Best Practices
David M. Heisler
Senior Principal Technical Support Engineer
Oracle E-Business Suite Proactive Support - Advanced Technologies
September 25, 2018
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |

E-Business Archive and Purging Best Practices
1 Archive and Purge Basics.

2 Product Specific Purging Requests.
3 What’s available in Oracle Applications Manager.
4 Database Archiving and Purging.
5 Q&A.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 3

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.


5 Q&A.

Oracle-supplied solutions to managing Applications database size fall into
two categories: data growth control methods and data management
methods.
Reducing Your Oracle E-Business Suite Data Footprint using Archiving,
Purging, and Information Lifecycle Management
• Growth Control Methods
• Archiving and purging
• Database compression
• Data Management Methods
• Database Partitioning
• Oracle Information Lifecycle Management (ILM)
• Can You Use Third-Party Tools to Modify Your EBS Database?

• Our official policy on direct modifications to EBS databases
• Do Not Use Database Tools to Modify Oracle E-Business Suite Data
• Why are these tools dangerous? They claim that they're safe.
• What are the support implications of using third-party tools?

Reasons for exponential growth of data
• - Consolidation: Many customers have consolidated their front and back

office systems into fewer systems or one large global single instance.
• - New software features: These features often provide a new user
experience with detailed transaction level information and hundreds of
cross-industry capabilities spanning enterprise resource planning, customer
relationship management, and supply chain planning products.
• - Increased data volume : Many customers now operate globally and are
experiencing an increased growth in transactions.

E-Business Archive and Purging Challenges
• How to keep up with the demand of rapid storage growth.

• Trying to reduce the costs and complexities associated with storage.
• Meet your service level agreements (SLA) with your business community.
• Other challenges when it comes to having such a large data footprint such
as upgrades.

Archive and Purge Best Practices – Data Lifecycle

Archive and Purge Best Practices – Data Life Cycle

E-Business Suite Typical Data Types
• Transient – In general, data that will be held for a short amount of time; for
example, login information or concurrent request information.
• Transactional – This is fiscal or non-fiscal data, typically related to entities
within the Oracle E-Business Suite, such as invoices or employee HR
information.
• Seed – Typically this would be lookup or reference data and in most cases
would help to contextualize transient or transaction data with regards to a
particular state or type.

• The Oracle supplied solutions fall into two categories, data growth control
methods and data management methodologies.
• Growth Control Methods
– Archive/Purge
– Database Compression
• Data Management Methods

– Database Partitioning
– Information Lifecycle Management (ILM)

• Pure archive and purge strategy where any important data is initially
archived and then finally purged when it is no longer needed.
• Implement a combination of an archive/purge and ILM strategy
• Do not use ILM but instead use database partitioning.

• Fully implement ILM and place less frequently accessed data, that would
ordinarily be archived and purged, onto cheaper and less expensive storage
devices.
• Use a 3rd Party archiving product with Oracle’s ILM product.

Factors that influence your archiving and purging policies
There are several :

Archive:
• Are there any statutory requirements that you must conform to?
• Are there any business requirements that you need to consider?
• Is there a possibility that you will ever need to import the data once it has
been archived?

Factors that influence your archiving and purging policies
Purging:
• Are you trying to stabilize the growth of your database?
• Are you purging to improve performance e.g. reduce the amount of data
prior to an upgrade?

Data retention policy and disposal schedule
• Identify records that need preserving permanently.

• Retain records according to their purpose. For example, consider whether
you need to keep invoices online, which were paid over 8 years ago.
• Ensure that records are kept to comply with legislation requirements.
• Prevent changes to, or the premature destruction of records, which need to
be retained for a specified period to satisfy legal and/or financial
requirements.

Where to Start?
• Get an idea of the data volumes involved and what are your largest
business objects.
• Consider the forecasted growth of these objects.
• Assess the current impact on performance, availability and cost of storing
data.
• Define purge/archive rules – What criteria, e.g. business rules, are you
going to use, and do you need to consider cross-product dependencies.
• Identify which solution you are going to use; .e.g., standard Oracle E-
Business Suite archive/purge programs, third-party vendor, or a custom
solution

Define validation process and prerequisites for archive purge
• What is your purging and archiving architecture? If you will use a custom
solution, such as using database partitioning to hold the archived data,
then how will you delete data?
– It may be advisable to use the standard Oracle APIs. Also for a custom solution, you
will need to consider your reporting requirements.
• Define roles and responsibilities, to specify who does what task. This step
includes business users, DBAs and technical resources.
• If you need an audit trail, what are your requirements for it?
– Create structure for archive media tables – for standard Oracle E-Business Suite
supplied programs, these will already have been defined.
• What are your reporting requirements? Are there any standard reports
available?
Would it better to archive the data first and hold it with a
reduced set of attributes?
• Hold data with a reduced set of attributes.

• Partition old data onto slower disks and compress the data.
• Use a third-party archiving product.

Functional/End User Requirements
• Identifying the business objects, e.g. sales order, payment, contract, or
inventory item that a table holds
• Reviewing needs of the business and the impact on business and end user
requirements if an entity is archived or purged
• Forecasting growth - Estimate the growth of the data volume for the
business object
• Defining purging criteria (business rules + database integrity)
• Defining purging selection criteria (list of parameters)
• Defining the validation process and prerequisites for purging
• Analyzing cross-product dependencies. How are they handled?

Functional/End User Requirements
• Checking if the product has archive/purge programs
• What are the business reporting requirements of archived data?
• How can their users access data that has been archived?
– Which reports are run and which screens are accessed for historical data
– Data retention requirements
– Define creation and destruction schedules
• - How should the archiving process take into account the differing
requirements such as those for governmental compliance?

Technical Considerations
• Assessing the impact of archiving and purging on performance and system

availability
• Considering the tables that need to be examined as potential candidates
for archiving or purging
• Helping evaluate the cost of storing data
• Considering database structure/size – What is impact on architecture by
actions such as resizing the database files or using table compression?

Technical Considerations
• Recovery – How and to where will the archived data be recovered ?

• Availability of Archive or Purge features – Which modules have
archive/purge features?
• Data access methods and security – Who will have access to the archived
information; who purges data?
• Operational: What data can I remove?

Can You Use Third-Party Tools to Modify Your EBS Database?
• Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser,
database triggers, or any other tool to modify Oracle E-Business Suite data unless
otherwise instructed.
• Some third-party tools reduce the size of EBS databases by deleting data. Some use
database links, aliases, and other approaches to separate older data into other
databases.
• You should never use these tools to reduce the size of your production EBS database.

Why are these tools dangerous? They claim that they're safe.
• EBS data dependencies are implemented through seed data, business logic, and other
undocumented areas. These hidden and undocumented dependencies mean that only
current EBS Development staff are qualified to determine whether data can be safely
removed.
• It is certain that third-party tools will violate EBS database referential integrity in some
manner. This is true even for third-party tools that are produced by people who used to
work for Oracle EBS development. EBS products continue to evolve and new
dependencies are introduced on a regular basis. These new dependencies may be
undocumented.

Conclusions – Archive and Purge
• Data is one of a businesses primary assets

• Maintaining the deployment of an organization’s ERP system can be quite
challenging to balance cost and complexity.
• How to handle storage, architecture, design, and performance.
• Runaway database growth.

Conclusions – Archive and Purge
• Oracle Database features - Oracle ILM Assistant, database partitioning,

table compression
• Oracle E-Business Suite features - Standard archive or purge programs that
come with the Oracle E-Business Suite


5 Q&A.

• Oracle General Ledger (GL)
• Oracle Payables/Oracle Purchasing (AP/PO)
• Oracle Receivables (AR)
• Oracle Fixed Assets (FA)
• Oracle Projects (PA)
• Oracle Cash Management (CE)
• Oracle Cost Management (CST)
• Order Management (ONT)
• Oracle Application Object Library (FND) and Workflow (WF)

• (DOC ID 390353.1) – General Ledger Archive/ Purge FAQ

• (DOC ID 144431.1) – Fixed Assets Archive/ Purge FAQ
• (DOC ID 1073185.1) – Receivables Archive/ Purge FAQ
• (DOC ID 136919.1) – General Ledger Archive/ Purge Setup and Usage

E-Business Archive and Purging – Purge Responsibilities

E-Business Archive and Purging - Accounts Receivable
Receivables User’s documentation guide archive and purge features

• Clear archive tables (standard Archive and Purge only)
– Tables R_ARCHIVE_HEADER and AR_ARCHIVE_DETAIL
• Ensure no other users are on the system (standard Archive and Purge only)
• Run the Oracle Sales Compensation interface.
– Tables A_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES and RA_CUSTOMER_TRX_LINES_SALESREPS
• Run Intrastat.
• Verify AutoInvoice tables are empty (optional, but recommended)
– Tables A_INTERFACE_LINES, RA_INTERFACE_SALESCREDITS and RA_INTERFACE_DISTRIBUTIONS

• Verify Lockbox tables are empty (optional, but recommended)

– Table R_PAYMENTS_INTERFACE
• Verify QuickCash tables are empty (optional, but recommended)
– Tables R_INTERIM_CASH_RECEIPTS and R_INTERIM_CASH_RECEIPT_LINES
• Run Tax Reports
• Always perform a backup before purging and archiving.

What are the tables that are purged but not archived as part of the Archive/Purge process



Product Archive and Purge Options – Payables
Payables User’s documentation guide archive and purge features
• Payables Open Interface Purge Program
• Used after you submit the Payables Open Interface Import program.
• Purges records from the Payables Open Interface tables.
– Tables AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE
• Purge only invoices that you successfully imported, or enter Yes for Purge
All to purge all records in the table that match the Source and Group
program parameters you enter.

E-Business Archive and Purging - Payables

E-Business Archive and Purging - Payables

Purging Records features:

• Optimize database storage.
• Purged records can no longer be queried or viewed.
• System maintains summary information of deleted records.
• Best Practice – create special responsibility for purging.

Invoice Purge criteria:
• Last Update Dates of the invoice and its distributions, and the Invoice Date, are on or
before the Last Activity Date
• Invoice is fully paid or is a zero-amount invoice
• Invoice is transferred to general ledger
• Invoice is not a prepayment, and no prepayments have been applied to the invoice
• All of the invoice's payments meet the Payment Purge Criteria
• No open encumbrances are associated with the invoice
• All purchase orders referencing the invoice meet the Purchase Order Purge Criteria
• If Oracle Assets is installed, all of the invoice's distributions were tested by Mass
Additions

Payment Purge criteria:
• Payment is transferred to general ledger

• All of the invoices paid by the payment meet the Invoice Purge Criteria
• Payments that are not reconciled and referenced by Oracle Cash
Management. If you do use Oracle Cash Management, then you have
already purged related records in Cash Management.

Supplier Purge criteria:
• Supplier is inactive, and the values of Inactive On and Last Update Date are on or before
the Last Activity Date you specify
• Supplier is not a parent company or subsidiary of another supplier
• Supplier is not referenced by records in any operating unit in Oracle Payables, Oracle
Purchasing, or Oracle Assets
• All invoices and payments for the supplier meet the Invoice and Payment Purge Criteria
• Supplier is not present on any active or inactive sourcing rule. Before purging the
supplier, you must first purge the sourcing rule that is associated with the supplier.
• Supplier is not referenced on any planning or shipping schedule
• The RCV Open Interface tables can contain no rows referencing the supplier (intransit
shipments through ASNs or barcoded receipts awaiting processing)

Requisition Purge criteria:
• Requisition is cancelled or finally closed
• All purchase orders referencing the requisition meet the Purchase Order
Purge Criteria
• Requisition must be supplier (rather than internally) sourced. Payables will
not purge invoices sourced by Oracle Inventory.
• If Oracle Supplier Scheduling is installed, the requisition cannot be
referenced on a supplier schedule, nor can the approved supplier list or
planning sourcing rules be impacted
• Requisition is not Oracle Projects related

Purchase Order Purge criteria:
• You have not updated the header, line, shipment, or distribution after the Last Activity Date.
• You have not updated any releases for a blanket agreement that meets the purge criteria after the Last
Activity Date.
• Purchase order is cancelled or finally closed.
• Any contract referenced on a standard purchase order meets the purge criteria.
• All online requisitions and all receipts referencing the purchase order meet the purge criteria.
• All invoices referencing the purchase order meet the Invoice Purge Criteria.
• No invoices match the purchase order.
• Purchase order is not referenced in Oracle Inventory or Oracle MRP.
• If Oracle Supplier Scheduling is installed, the blanket release is not referenced on a supplier schedule.
• Purchase order is not referenced on an ASL.
• Purchase Order is not Oracle Projects related.

Supplier Schedules Purge criteria:
• The schedule must be for the organization specified in the Submit Purge
window.
• The schedule header Last Update Date must be on or before the Last
Activity Date.
• All releases of blanket purchase orders referenced on the schedule must be
either closed or eligible for purging.
• For organizations in which CUM Management is enabled, schedules must
have a horizon start date before the current defined CUM Period.
• The e-Commerce Gateway interface table does not contain the schedule.

CUM Period Purge criteria:
• CUM Management is enabled for the organization specified in the Submit
Purge window. For multi-org schedules, we purge the schedule line that
meets the purge criteria. Once all lines associated with a schedule are
purged, the whole schedule is purged.
• The Last Activity Date must be after the CUM Period end date for the purge
organization. All previous CUM Periods are purged.
• The system date cannot be within the CUM Period
• When a CUM Period is purged, all CUM Period items, all data for supplier
planning and shipping schedules, CUM Period high authorizations, and
CUM Period adjustments are also purged.

Submitting Purges:
• To purge the most complete set of records, first choose the Invoices and
POs category and then initiate a second purge for the Suppliers category.
• Submit a purge when users are least likely to update records in the
database.
• The purge process can take several hours to complete, depending on the
number of records in the purge and the resource capacity of your system.
• Make sure that the database rollback segments you create are large
enough so that you have sufficient memory to perform the purge.

E-Business Archive and Purging – Payables Purge

• FINANCIALS_PURGES - Stores the criteria and status of a single purge process. The table also records the
number of records you successfully purge from other tables
• PO_HISTORY_VENDORS - Stores summary information of the suppliers your Oracle Purchasing application
purges
• PO_HISTORY_POS - Stores summary information of the purchase orders your Oracle Purchasing
application purges
• PO_HISTORY_RECEIPTS - Stores summary information of the receipts your Oracle Purchasing application
purges
• PO_HISTORY_REQUISITIONS - Stores summary information of the requisitions your Oracle Purchasing
application purges
• PO_PURGE_PO_LIST - Stores PO_HEADER_IDs temporarily during the purchase order purge process
• PO_PURGE_REQ_LIST - Stores REQUISITION_HEADER_IDs temporarily during the requisition purge
process

• PO_PURGE_VENDOR_LIST - Stores VENDOR_IDs temporarily during the supplier purge process

• AP_PURGE_INVOICE_LIST - Stores INVOICE_IDs temporarily during the invoice purge process
• AP_HISTORY_CHECKS - Stores summary information of the invoice payments that Payables purges
• AP_HISTORY_INVOICES - Stores summary information of the invoices that Payables purges
• AP_HISTORY_INVOICE_PAYMENTS - Stores the relationship between invoices and payments that Payables
purges
• CHV_PURGE_CUM_LIST - Stores CUM-IDs temporarily during the CUM purge process
• CHV_PURGE_SCHEDULE_LIST - Stores SCHEDULE_IDs temporarily during the schedule purge process

• PO_PURGE_VENDOR_LIST - Stores VENDOR_IDs temporarily during the supplier purge process

• AP_PURGE_INVOICE_LIST - Stores INVOICE_IDs temporarily during the invoice purge process
• AP_HISTORY_CHECKS - Stores summary information of the invoice payments that Payables purges
• AP_HISTORY_INVOICES - Stores summary information of the invoices that Payables purges
• AP_HISTORY_INVOICE_PAYMENTS - Stores the relationship between invoices and payments that Payables
purges
• CHV_PURGE_CUM_LIST - Stores CUM-IDs temporarily during the CUM purge process
• CHV_PURGE_SCHEDULE_LIST - Stores SCHEDULE_IDs temporarily during the schedule purge process

Product Archive and Purge Options – General Ledger
General Ledger User’s documentation guide archive and purge features
• Average balance processing – Archiving and Purging
• A large volume of data accumulates in your General Ledger database.
– You can archive and purge any information you no longer need.
• General Ledger also provides some related safety and security features.
– Produces reports you can review to verify that your archiving and purging processes
complete successfully.
– Ensures that only archived data can be purged.

E-Business Archive and Purging - General Ledger

Mass Maintenance Workbench :
• Use Mass Maintenance to move balances by period from one

account to another.
• Use Mass Maintenance to merge balances by period from
multiple accounts into a single account.
• You can also use Mass Maintenance's mass creation feature to
create new accounts automatically based on existing accounts.

To purge the interim move/merge tables:
• Navigate to the Mass Maintenance Workbench window.
• Query the move/merge request whose interim tables you want to

purge.
• Choose the Purge

E-Business Archive and Purging - General Ledger

E-Business Archive and Purging – Fixed Assets
To archive and purge transaction and depreciation data:
• Change Responsibilities to Fixed Assets Administrator.
• Open the Archive and Purge window.
• Enter the Book and Fiscal Year you want to archive. You must archive and
purge in chronological order.
• Choose Archive to submit a concurrent request that changes the status
from New to Archived and creates temporary archive tables with the data
to be purged.

E-Business Archive and Purging - Fixed Assets

• Export the archive tables to a storage device.

• Return to the Archive and Purge window and use the Archive Number to
find the archive you want to purge.
• Choose Purge to submit a concurrent request that changes the status from
Archived to Purged and removes the archived data from Oracle Assets
tables.


Mass Additions Purge Report:

• Provides a list of the purged mass additions.
• Oracle Assets automatically prints this report when you run the Purge Mass
Additions program.
• If you run this report from the Submit Requests form, you must enter the
mass additions post Batch Number for which you want to purge the audit
trail.


• Archive and Purge Programs Available for Sysadmin responsibility

E-Business Archive and Purging - Projects
Instructions for Archiving and Purging Projects
The following steps provide detail instructions for purging (or archiving and purging) in
Oracle Projects.
Step One: Create a Purge Batch
– You can populate a purge batch either by providing selection criteria or by selecting specific projects to
purge. You can remove projects from the purge batch at any time before you release the batch.
– You can define as many purge batches as you want. Each batch can contain either open or closed
projects, but not both.
To create a purge batch:
– Log in using the Projects Implementation Superuser responsibility.
– Navigate to the Purge Batches window. To navigate to the Purge Batches window, log on with the
Projects Implementation Superuser responsibility and choose Purge Project Data.
– Create a purge batch by completing applicable fields (described in the following table) in the Purge
Batches window.



Create a list of projects to purge:
– If you want to select each project to include in the batch, choose Enter Details. In the Purge Batch
Details window, use the list of values in the Project Number or Project Name fields to select each
project you want to purge, and then skip to Step 2: Review and Refine the List.
– If you want to generate a list of projects based on a set of criteria that you define, choose Generate
Details.
– In the Generate Details window, set the criteria for the list of projects you want to purge by filling in
the fields shown in the following table:
If you make a mistake, choose Clear.

Choose Generate to display a list of the projects that meet the criteria. The Purge Batch
Details window opens
After you create the purge batch, review the list of projects to be purged.
To review and refine the list:
• Examine the list of projects to purge and further refine the list as shown in the following
table.
• If you want to change purge options at the project level, then change the poplist from
Project Information to Purge Options. Change the options for each project as
appropriate.
• Save the list of projects and close the Purge Batch Details window.
To validate a purge batch:
• Choose Validate from the Purge Batches window.
• The system starts the ADM: Validate Purge Batch process.
• You can also validate the batch by running the process from the Submit
Requests window.
• When the process is complete, review the Purge Validation Report.
– If the Validation Exceptions section lists any errors, return to the Purge Batch Details
window and correct the errors.
– If the system validates the purge batch, you can release the purge batch

• After all the projects in the batch are validated (required), you release the
batch for purging. You cannot release a batch that contains errors.
To release a purge batch
– From the Purge Batches window, Choose Release. This sets the batch status to
Released.
Note: After a batch is released, you must choose Rework if you want to make
any changes in the batch. When you choose Rework, the batch status
changes from Released to Working.

• When you are ready to purge (or archive and purge) a batch, run the ADM:
Purge Project Data process.
To start the purge process:

• From the Purge Batches window, Choose Purge. The ADM: Purge Project
Data process starts.
Note: You can also run the purge process from the Submit Requests
window.


3 Oracle Applications Manager and FND_LOBS.
5 Q&A.

• R12 Oracle Applications Manager FND Purge options examples:
– Purge Concurrent Request and/or Manager Data
– Purge Logs and Closed System Alerts Concurrent
– Purge Obsolete Workflow Runtime Data Concurrent
– Purge Signon Audit data Concurrent Program Details
• Indepth review of Products with Purge Utilities in OAM and how to use
them.
– ASO, BOM, CCT, CS, CZ, EDR, IBW, JTF, MSC, MSD, OKC, ONT, OZF, PER, PON,
PQH, PSP, SQLGL, WSM, OZF
• FND_LOBS maintenance.

BREAKOUT SESSION USING APPLICATIONS MANAGER PURGE PORTAL

E-Business Archive and Purging Best Practices – FND_LOBS
Avoiding abnormal growth of FND_LOBS table

• Stores all the attachments that have been uploaded to Oracle Applications.
• Size must be controlled.
• Old and expired exports.
• Note.604458.1 How to Limit The Attachment File Size?

Use the following query to find out currently set value for PCTVERSION:
select PCTVERSION from dba_lobs where TABLE_NAME = 'FND_LOBS' and
COLUMN_NAME='FILE_DATA';
PCTVERSION
----------
10
PCTVERSION can be changed using the following SQL (it can be run anytime in a running
system):
ALTER TABLE FND_LOBS MODIFY LOB (FILE_DATA) ( PCTVERSION 0 );

• Stores information about all LOBs managed by the Generic File Manager.
• File data is a binary LOB.
• Non-Browser sources have to be prepared.
• Use program name and tag for purging purposes if possible.
• You can set expiration date on objects that do not have one

• To reclaim space in FND_LOBS Note 829235.1 FAQ - Performance Considerations For
FND_LOBS
alter table fnd_lobs MODIFY LOB (file_data) (SHRINK SPACE);
alter table fnd_lobs modify lob (FILE_DATA) (allocate extent (size 131072k));
• You can see the contents of fnd_lobs through this query:
select file_name, file_id,
to_char(upload_date,'dd-mon-rr hh24:mi:ss'),
to_char(expiration_date ,'dd-mon-rr hh24:mi:ss'),
file_content_type,
dbms_lob.getlength(file_data) size_byte
from applsys.fnd_lobs
• Optimizing Database disk space using Alter table shrink space/move compress (Doc ID
1173241.1)

• Patch 22536174 (R12.FND.C) - After the patch program Purge Obsolete
Generic File Manager Data will expire orphaned attachment data to be
purged. Run "Purge obsolete generic manager data" with "Purge Orphaned
Data" yes, program name FNDATTACH and it will delete the obsolete data
from both fnd_lobs and fnd_documents
• Patch 11869163 (R12.FND.B)
• Patch 15892371 (R12.FND.B)
• Patch 9454616 (R12.FND.A)
• Refer to Note 1163933.1 for more details.

• As you know, FND_LOBS will have domain index ( fnd_lobs_ctx ); therefore, the
correct EBS 12.2 steps should be:
• a) Drop this index ,
• b) Enable row movement,
• c) Shrink space
• d) Re-create index.

• How to Purge Generic or Purchasing Attachments from the FND_LOBS Table (Doc ID
555463.1)
For more information on FND_LOBS issues, you may review the following MOS
documents:
• How To Manage, Reduce, and/or Purged The FND_LOBS Table? (Doc ID 1288149.1)
• FAQ – Performance Considerations For FND_LOBS (Doc ID 829235.1)
• Orphaned Records In FND_LOBS Table When Uploading Attachments Using FNDATTACH
Form (Doc ID 963222.1)
• How To Download Attachment File From fnd_lobs (Doc ID 1457782.1)
• How To Extract attachments From The Database When a URL Is in The APPLSYS
FND_LOBS Table Under The Heading of File_Name (Doc ID 800973.1)


5 Q&A.

In-depth Database Discussions
• Information Center: Advanced Compression (Doc ID 1526780.2)

• Using Database Partitioning with Oracle E-Business Suite (Doc ID 554539.1)
• Optimizing Database disk space using Alter table shrink space/move
compress (Doc ID 1173241.1)
• Implementing Information Lifecycle Management Using the ILM Assistant

Database Partitioning

tables containing columns with LONG or LONG RAW data types
Database Partitioning - What is Partitioning?
• Partitioning enhances the performance, manageability, and availability of a wide variety

of applications
• Reduces the total cost of ownership for storing large amounts of data.
• Allows tables, indexes, and index-organized tables to be subdivided into smaller pieces,
enabling these database objects to be managed and accessed at a finer level of
granularity.
• Tables containing columns with LONG or LONG RAW data types can not be partitioned.

Database Partitioning – When to Partition a Table
• Tables are greater than 2 GB.

• Tables that contain historical data, in which new data is added
into the newest partition.
• Tables whose contents must be distributed across different types
of storage devices.

Database Partitioning - What is Custom Partitioning?
Custom partitioning applies when:
• A customer partitions an existing standard Apps product table is not partitioned using
various methods, including the range, list, hash, or composite partitioning methods; or,
• A customer modifies the partition scheme and/or partitioning method of an existing

standard product table which is already partitioned by Oracle.

Database Partitioning – Common Usage


• For example, many users partition the table GL_BALANCES by either

period_name or set_of_books_id, depending on their implementation:
– Some customers have a large number of books for which partitioning by
set_of_books_id makes sense.
• Other customers use a single or a few set of books for which period_name
makes sense.
• Since the majority of the GL runtime SQL includes the filters period_name
or set_of_books_id, these columns are logical choices for the partition key.

Database Partitioning – Why Partition an Index?
• Avoid index maintenance when data is removed.

• Perform maintenance on parts of the data without invalidating
the entire index.
• Reduce the effect of index skew caused by an index on a column
with a monotonically increasing value.

Database Partitioning – Index Partitioning
• Indexes can be partitioned like tables

• Partitioned or non-partitioned indexes can be used with partitioned or
non-partitioned tables
• Partitioned indexes can be
– Global or local
– Prefixed or non-prefixed

Database Partitioning – Index Partitioning
• Index Partitioning Methods

– Global Non-partitioned (prefixed)
– Global Partitioned (prefixed)
– Local Partitioned Prefixed
– Local Partitioned Non-Prefix

Database Partitioning – Useful Dictionary Views

• DBA_TABLES Table structure, Partition Y/N
• DBA_PART_TABLES Partition type, default values
• DBA_TAB_PARTITIONS Partitions detail
• DBA_PART_KEY_COLUMNS Partition keys
• DBA_PART_HISTOGRAMS Histogram Statistics
• DBA_PART_COL_STATISTICS Column and Histogram Stats.
• DBA_SUBPART_KEY_COLUMNS Sub-partition key Information
• DBA_IND_PARTITIONS Index Partition details
• DBA_IND_SUBPARTITIONS Index Sub-partition details
• DBA_PART_INDEXES Partitioned Index Definition
Database Partitioning – Advantages
• Table availability
– Significantly reduce recovery times of key transaction tables by
recovering the current partitions first.
• Table manageability
– Backup, restore, and rebuild at the partition level.
– Index rebuilds can be performed at the partition level.
– Partition aware operations such as MOVE, EXCHANGE, REBUILD can be
used without affecting active partitions.
• Performance
– Improves access path of most queries since the majority of the access
involves current data as opposed to historical data.
• Optimizer automatically prunes unnecessary partitions.
–Analytical reports or period close jobs/reports improve by scanning the
current partition as opposed to all the partitions.
–Improves purge performance.
–Significantly improves upgrade performance
• Minimizes upgrade downtime.
• CBO is partition aware and employs partition pruning at runtime.

– Eliminates partitions which are not needed by the SQL statement.
– Joins are also partition aware and benefit from pruning.
• Parallel operations can occur at the partition level.
• Utilizes the Information Lifecycle Management (ILM) infrastructure to allow
partitions containing historical Applications data to be placed on lower cost
storage devices.
Advanced Compression
• Advanced Row Compression uses a unique compression algorithm

specifically designed to work with OLTP applications.
• Advanced Compression is completely transparent to the E-Business Suite.
• Easy to implement
• No additional database or E-Business Suite patches are required.
• No special configuration options are required.
What to Expect:
• Enabling compression doesn't compress existing data.

• The time required to do any reorganizations will depend upon the amount
of real data that you have.
• EBS performance is expected to improve.
• The compression ratio achieved depends on the data being compressed.
Advanced Compression includes:
• OLTP Table Compression
• SecureFiles Compression
• CREATE TABLE images (image_id NUMBER, image BLOB)
LOB(image)STORE AS SECUREFILE
(TABLESPACE lob_tbs COMPRESS);
• SecureFiles Deduplication
• CREATE TABLE images (image_id NUMBER, image BLOB)
LOB(image) STORE AS SECUREFILE
(TABLESPACE lob_tbs DEDUPLICATE);
• Compression for Backup Data

– Syntax for setting the RMAN compression algorithm:
• RMAN> SET COMPRESSION ALGORITHM ‘LOW|MEDIUM|HIGH’;
– Syntax for taking a compressed RMAN backup:
• RMAN> backup as COMPRESSED BACKUPSET database archivelog all;
Information Lifecycle Management
E-Business Archive and Purging Best Practices - ILM
• Information Lifecycle Management (ILM) is the practice of applying policies
for the effective management of information throughout its useful life
Considerations when creating an information lifecycle management
framework for Apps data.
• ILM includes every phase of a “row” from its beginning to its end.
• Consists of the policies, processes, practices, and tools used to align the
business value of information with the most appropriate and cost effective
IT infrastructure.
Typical Data Life Cycle
Implementing ILM for Oracle
• Step 1 – Define Your Data Classes

• Step 2 – Create Storage Tiers for Data Classes
• Step 3 – Create Data Migration Policies
• Step 4 – Define and Enforce Compliance Policies
Heat Map and Automatic Data Optimization
• Gathers and maintains system-generated data usage statistics

• Automate compression and storage tiering policies.
• Segment level Heat Map tracks the time of last modification and
access of tables and partitions.
• Row level Heat Map tracks modification times for individual rows.
Heat Map and Automatic Data Optimization
Limitations and Restrictions With ADO and Heat Map
• ADO and Heat Map are not supported with a multitenant container
database (CDB).
• Custom policies (user-defined functions) for ADO are not supported if the
policies default at the tablespace level.
• ADO does not perform checks for storage space in a target tablespace
when using storage tiering.
• ADO is not supported on tables with object types or materialized views.
• ADO is not supported with index-organized tables or clusters.
• ADO has restrictions related to moving tables and table partitions.
Flashback Data Archive
• Provides a mechanism for tracking changes to production
• Allows organizations to configure historical data capture in a matter of
minutes
• Flashback Data Archive consists of one or more tablespaces or parts
thereof.
• Flashback Data Archive is configured with retention time
• Use Flashback Data Archive to view or restore the data as of a time in the
past.
In-Database Archiving
• Allows users and applications to set the archive state for individual rows.
• Rows marked as archived stay where they are, but are not visible, unless
the session is enabled to see archived data.
• Enabling in-database archiving causes the addition of a system generated
hidden column.
• In-database archiving utilizes an added hidden column to a table to specify
the visibility of each
Key Benefits Summary
• Heat Map automatically tracks modification and access at the row and
segment levels.
• ADO automatically moves, and compresses, data according to user-defined
policies based on Heat Map gathered information.
• ADO enables automated storage tiering and compression tiering.
• Flashback Data Archive securely tracks and stores transactional changes to
a table over its lifetime.
• In-Database Archiving archives rows in-place, rows that have been marked
as archived stay where they are but are not visible unless the session is
enabled to see archived data.
Information Lifecycle Management Assistant

5 Q&A

Archive Purge Best Practices v3 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Archive Purge Best Practices v3 PDF

Загружено:

Авторское право:

Доступные форматы

E-Business Suite Archive and Purging

September 25, 2018

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |

1 Archive and Purge Basics.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 3

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 4

1 Archive and Purge Basics.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 5

• Can You Use Third-Party Tools to Modify Your EBS Database?

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 7

• - Consolidation: Many customers have consolidated their front and back

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 8

• How to keep up with the demand of rapid storage growth.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 9

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 10

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 11

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 12

• Data Management Methods

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 13

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 14

• Use a 3rd Party archiving product with Oracle’s ILM product.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 15

There are several :

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 16

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 17

• Identify records that need preserving permanently.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 18

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 19

• Hold data with a reduced set of attributes.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 21

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 22

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 23

• Assessing the impact of archiving and purging on performance and system

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 24

• Recovery – How and to where will the archived data be recovered ?

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 25

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 26

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 27

• Data is one of a businesses primary assets

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 28

• Oracle Database features - Oracle ILM Assistant, database partitioning,

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 29

1 Archive and Purge Basics.

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 30

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 31

• (DOC ID 390353.1) – General Ledger Archive/ Purge FAQ

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 32

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 33

Receivables User’s documentation guide archive and purge features

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 34

• Verify Lockbox tables are empty (optional, but recommended)

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 35

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 36

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 37

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 38

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 39

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 40

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 41

Purging Records features:

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 42

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 43

• Payment is transferred to general ledger

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 44