Kbase 17528: Binary Dump With Tables Larger Than 2 GB
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
Binary Dump With Tables Larger Than 2 GB
GOAL:
What files are written to when binary dumping a table bigger than 2 Gig?
GOAL:
How the binary dump files are named when binary dumping a table bigger than 2 Gig?
FACT(s) (Environment):
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
A section is a file containing a section of a table. Every binary dumped table has at minimum, 1 section. A new section is created when Progress runs out of disk space writing the previous section, or the maximum files size for the operating system is reached.
The first section is named <table>.bd. The second has a suffix of .bd2 the 3rd, .bd3 and so on. Naming of the sections is performed internally to Progress and automatically. If the directory entered is a removable device (tape drive), Progress writes directly to the device when it names the file.
When a new section must be created, a partial record might be left at the end of the previous section. Because of this, the new section starts with the same record that was partially written in the previous section. The Binary Load utility handles the partial record appropriately.
Each section can be binary loaded independently of any other section (ie. each section has enough information in it to stand alone).
You cannot specify different locations for each section on the dump. The dump is made in its entirety to the path or destination you provided.
When you are loading several sections, you must specify every section to be loaded. You can build a script to load all the sections in a process. Once the process finishes, idxbuild should be run.