11/20/23, 9:55 AM Document 298698.
1
PowerView is Off Last Login: November 17, 2023 1:11 PM ICT Ha (Available) (0) Contact Us Help
Dashboard Knowledge Service Requests Patches & Updates Community
Give Feedback...
Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.
Avoiding Abnormal Growth of FND_LOBS Table Due To Attachments Data In E-Business Suite Applications (Doc To Bottom
ID 298698.1)
Was this document helpful?
APPLIES TO:
Yes
Oracle Application Object Library - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2] No
Information in this document applies to any platform.
Document Details
GOAL
Type:
This document will help you to get the need of increasing the filespace for the FND_LOBS tablespace better managed HOWTO
Status:
PUBLISHED
Last Major
Apr 26, 2018
SOLUTION Update:
Sep 8, 2022
Last Update:
Related Products
Avoiding abnormal growth of FND_LOBS table
Oracle Application Object
Of all the tables that occupy very large amount of space within APPLSYSD and APPLSYSX tablespaces of Oracle Applications Library
instances, FND_LOBS is usually one of the top 10. This is because, it stores all the attachments that have been uploaded to
Oracle Applications. There is a LOB field within this table called FILE_DATA, the corresponding LOB segment (e.g., Information Centers
APPLSYS.SYS_LOB0000680397C00004$$) is where the actual attachment data is stored, and is usually very large.
Oracle Catalog: Information
Centers and Advisors for All
It is important that its size be controlled. Products and Services [50.2]
Privacy and Security Feature
Old/Expired Exports: Guidance for all Oracle
Products (On Premise) [113.2]
Some of the data that gets into this table belongs to old/expired exports. For every request for an export, an entry in the
FND_LOBS table is recorded. This data must be purged regularly. There is a purge program available to purge this data called
Purge Obsolete Generic File Manager Data (FNDGFMPR). FNDGFMPR is a PL/SQL procedure, which gets rid of old obsolete Document References
uploaded files (loaded to the database) for the programs FND_HELP, export and FND_ATTACH, these are programs that are run
No References available for
under the FNDGFU (Generic File Manager Access Utility). The Note 216541.1 - 'Concurrent Processing - How To Add The this document.
Concurrent Program "Purge Obsolete Generic File Manager Data" To The Sysadmin User.' describes how to add The Concurrent
Program "Purge Obsolete Generic File Manager Data" To The Sysadmin User.
Recently Viewed
PCTVERSION: Purging Strategy for E-
Business Suite [732713.1]
Since the LOB segments are usually very large, they are treated differently from other columns. While other columns can be How to Purge Generic or
guaranteed to give consistent reads, these columns are not. This is because, it is difficult to manage with LOB data rollback Purchasing Attachments
segments due to their size unlike other columns. So they do not use rollback segments. Usually only one copy exists, sothe from the FND_LOBS Table
queries reading that column may not get consistent reads while other queries modify them. In these cases, the other queries will [555463.1]
get "ORA-22924 snapshot too old" errors. FAQ - Performance
Considerations For
FND_LOBS [829235.1]
To maintain read consistency Oracle creates new LOB page versions every time a lob changes. PCTVERSION is the percentage
How To Manage, Reduce,
of all used LOB data space that can be occupied by old versions of LOB data pages. As soon as old versions of LOB data pages
and/or Purged The
start to occupy more than the PCTVERSION amount of used LOB space, Oracle tries to reclaim the old versions and reuse them. FND_LOBS Table?
In other words, PCTVERSION is the percent of used LOB data blocks that is available for versioning old LOB data. The [1288149.1]
PCTVERSION can be set to the percentage of LOB's that are occasionally updated. Unable to Open Attachments
when 'FND: Disable
FND_LOBS table's FILE_DATA LOB column usually gets the data uploaded only once, but is read multiple times. Hence it is not Inline Attachments =
False' [2417542.1]
necessary to keep older versions of LOB data. It is recommended that this value be changed to "0".
Show More
By default PCTVERSION is set to 10%. So, most of the instances usually have it set to 10%, it must be set to 0% explicitly. The
value can be changed any time in a running system.
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):
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=50053759155918&parent=DOCUMENT&sourceId=1288149.1&id=298698.1&_a… 1/2
11/20/23, 9:55 AM Document 298698.1
ALTER TABLE FND_LOBS MODIFY LOB (FILE_DATA) ( PCTVERSION 0 );
Please be aware :
The solution shows, how to avoid the increase of the table in future - it does not shrink the current tablespace. The only
supported way to shrink the tablespace is to export and re-import the whole Database.
Didn't find what you are looking for? Ask in Community...
Related
Products
Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library > ATTACHMENTS/ EXPORT > ATTACHMENTS/ EXPORT
Keywords
APPLICATION OBJECT LIBRARY; APPLSYSD; APPLSYSX; ATTACHMENTS; DBA_LOBS; FND_LOBS; LOB; PERCENTAGE; RECLAIM SPACE; TABLESPACE
Errors
ORA-22924
Back to Top
Copyright (c) 2023, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=50053759155918&parent=DOCUMENT&sourceId=1288149.1&id=298698.1&_a… 2/2
