Salesforce

Dump/Export of clob and blob fields generates different file names for the same lob file every time

« Go Back

Information

 
TitleDump/Export of clob and blob fields generates different file names for the same lob file every time
URL Name000044736
Article Number000166347
EnvironmentProduct: OpenEdge
Version: 10.x,11.x, 12.x
OS: All supported platforms
Other: BLOB, CLOB
Question/Problem Description
When table that contains LOB fields is dumped with the Dictionary tool or when the record is EXPORTed via ABL separate .blb files are generated for each LOB data.
ASCII Dump or the EXPORT statement writes CLOB and BLOB fields to uniquely named .blb files.
The unique .blb file names are re-generated and therefore different every time a record is exported with it's associated LOB.
ASCII Dump or EXPORT of clob or blob fields generates different file names for the same lob file.

Data Administration dump of LOB objects with the associated table, generate different .blb file names for the same lob file every time that table is dumped.
File names for .blb files are different every time they are dumped from a new EXPORT session, even when data has not changed.

When the dump directory is not emptied before each dump session it fills with duplicate data files with different names 
Duplicates cannot be identified by relating a specific .blb file to a specific table
Cannot use a specific lob .blb dump file name to associate with a specific table record unless the related data dump (.d) is parsed for the lob field value.
Steps to Reproduce1. Find a record in a database with a LOB field that holds data
a. Dump the table through Data Administration > Dump Data .. > Table Contents > select Include LOB, (Optionally) LOB Directory
b. EXPORT the record contents with ABL multiple times from the same session, or from different sessions.

OUTPUT TO "file.txt".
FIND FIRST <table> WHERE <...> NO-LOCK.
EXPORT <table>.
OUTPUT CLOSE.
Clarifying Information
CLOB and BLOB fields are written to uniquely named .blb files:
CLOB: <field name> + <codepage> + <PID of dumping process> + <sequence>.blb
BLOB: <field name> + <PID of dumping process> + <sequence>.blb
Error Message
Defect Number
Enhancement Number
Cause
Resolution
This is expected behavior. In the current implementation, to generate unique file names the AVM uses the current process' PID and a sequence counter. It was determined that the Progress Product is functioning as designed.
 
An enhancement request has been submitted as an Idea on the Progress Community.  To promote the Idea, click on this link:
     
OPENEDGE-I-150, Dump CLOB/BLOB with same file-names
https://openedge.ideas.aha.io/ideas/OPENEDGE-I-150

Customer feedback is valuable and Idea submissions are monitored by our Product Management team.  Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release.  
 
For detailed information on how to submit your Idea, please refer to Article  How to submit an enhancement request for a Progress product?
Workaround
Write a custom export/dump routine. The following Article provides an example of a dynamic function to use as a starting point:
Notes
Keyword Phrase
Last Modified Date11/20/2020 6:55 AM

Powered by