Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025

 


Article

Dumplist file was not created after binary dump with -dumplist option

« Go Back

Information

 
Article Number000057322
EnvironmentProduct: OpenEdge
Version: 10.1x, 10.2x, 11.1x , 11.2x, 11.3x, 11.4x
OS: All supported platforms
Question/Problem Description
Dumplist file is not created using a threaded binary dump with the -dumplist option.
When binary dump uses a single thread a dumplist is not produced.
The dumplist is not produced when only one .bd file results from a binary dump.
When a single-thread binary dump executes, a dumplist file is not created.
Steps to Reproduce
Clarifying Information
Dumplist output is valuable information to have when attempting to automate the processing of the dump files either to load back in or ftp to a second server. 

Command used to perform the binary dump with -dumplist option: 

proutil <database_name> -C dump <table_name> <output_directory_name> -thread 1 -threadnum <num> -dumplist <dumplist_name>,
proutil sports2000 -C dump BillTo tmp -thread 1 -threadnum 14 -dumplist BillTo.dumplist 



 
Error MessageThe index tree only contains one level. Run non-thread mode. (14777)
Defect/Enhancement NumberEnhancement PSC00198289
Cause
The Multi-threaded feature on binary dump is introduced in OpenEdge 10.1A. When binary dump is run without threading (-thread 0) or when a threaded binary dump determines to use single thread mode for the binary dump, the dumplist file is not produced when only one .bd dump file results.

The -threadnum option is used by default or as specified (unless -thread 0 is used).  Even though threaded dump is specified, multi threads will not necessarily be started to dump the table.

The algorithm also checks on the following before permitting a multi-threaded binary dump:

a.)  Enterprise Database License

b.)  More than one CPU, which defaults the -threadnum to the number of operational CPU's unless otherwise specified.

c.)  Threaded binary dumps are created based on the index tree, not on the table size. The number of entries in the root block of the index used (Primary index by default or that specified by the -index parameter).  The threaded-dump algorithm splits the root block logically into up to (-threadnum) parts, this will break the index tree in different ranges according to the keys in the root block, each thread works on a range. If there is only one entry in the root block, it cannot be split so a non-threaded (regular) dump will be used.

d.) A special case that affects the number of threads used: if there are duplicate keys in the root block, the duplicate keys are ignored when building the brackets for the number of threads to be used.
Resolution
Upgrade to OpenEdge 11.5 where the threaded binary dump was enhanced for partitioned tables.  While the binary dump algorithm has not changed in determining the number of threads that will be used for the binary dump, a dumplist file will be created when the -dumplist parameter is specified irrespective of the multi-tenant feature being enabled.
 
Workaround
Notes
Attachment 
Last Modified Date1/30/2015 4:09 PM