# Baan IV to Infor LN Data Copy Downtime Calculator (bdbpre/bdbpost)

> Source: https://netray.co/tools/baan-iv-to-infor-ln-bdbpre-bdbpost-downtime-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Plan the downtime window for a bdbpre/bdbpost data copy from your measured throughput, parallel table lists and reorganize time.

## Category

infor-ln

## Erp

Baan IV / Infor LN

## Audience

- ERP administrator
- Migration lead
- DBA

## Tool

**Kind:** calculator

**Inputs:**

#### Data volume

**Key:** gb

**Type:** number

**Default:** 300

**Min:** 1

**Step:** 10

**Unit:** GB

**Help:** Data to dump and load, from your table list.

#### bdbpre throughput per stream

**Key:** pre

**Type:** number

**Default:** 20

**Min:** 0.5

**Step:** 1

**Unit:** GB/h

**Help:** Measure on a test run; not a vendor figure.

#### bdbpost throughput per stream

**Key:** post

**Type:** number

**Default:** 12

**Min:** 0.5

**Step:** 1

**Unit:** GB/h

**Help:** Import is usually slower than export because indexes are built.

#### Parallel streams

**Key:** streams

**Type:** slider

**Default:** 4

**Min:** 1

**Max:** 12

**Step:** 1

**Unit:** streams

**Help:** Separate table list files run at the same time.

#### Parallel efficiency

**Key:** eff

**Type:** slider

**Default:** 80

**Min:** 30

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** Below 100 because streams share disk, CPU and the database.

#### Reorganize / repair reference counters time

**Key:** reorg

**Type:** slider

**Default:** 25

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** % of import

#### Validation and sign-off

**Key:** valid

**Type:** number

**Default:** 4

**Min:** 0

**Step:** 0.5

**Unit:** hours

#### Contingency

**Key:** cont

**Type:** slider

**Default:** 20

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Outputs:**

#### Export hours (bdbpre)

**Key:** exp_h

**Expr:** gb / (pre * streams * eff / 100)

**Format:** hours

#### Import hours (bdbpost)

**Key:** imp_h

**Expr:** gb / (post * streams * eff / 100)

**Format:** hours

#### Reorganize hours

**Key:** reorg_h

**Expr:** imp_h * reorg / 100

**Format:** hours

#### Total window

**Key:** total_h

**Expr:** exp_h + imp_h + reorg_h + valid

**Format:** hours

**Primary:** true

#### Window with contingency

**Key:** window_h

**Expr:** total_h * (1 + cont / 100)

**Format:** hours

**Primary:** true

**Description:** The figure to book as downtime.

**Chart:**

#### Total window (hours) vs parallel streams

**Type:** line

**X:** streams

**From:** 1

**To:** 12

**Steps:** 12

**Series:**

- total_h

**Disclaimer:** Throughput figures are inputs from your own test copy, not Infor numbers. Parallel streams stop helping once disk or database I/O is saturated. Data conversion steps of a Baan IV to LN migration are not included and must be timed separately.

## Content

**Intro:** This calculator estimates the downtime window for moving table data with bdbpre and bdbpost, whether you are copying companies or moving Baan IV or LN data to a new server as part of a migration. It works from throughput measured on a test copy and shows how far parallel table lists shorten the window.

**Sections:**

#### Where bdbpre and bdbpost fit

**Body:** bdbpre dumps tables to sequential files and bdbpost creates tables from those files. In LN the sessions Create Sequential Dump of Table (ttaad4226m000) and Create Table from Sequential Dump (ttaad4227m000) use the same executables (bdbpre6.2 and bdbpost6.2). Infor documents a command-line method: list the tables in an ASCII file, dump them with bdbpre, load them with bdbpost. When the load runs with Ignore Referential Integrity Constraints selected, the imported records get reference counters of zero, so you must run Reorganize Tables (ttaad4225m000) with Repair Reference Counter afterwards. To import data exported from another company, first run Copy Company Data (tccom0214m000) on the sequential files to correct company number references; it needs dumps made with field separators.

#### How to use it

**Body:** Run a full test copy of a representative subset, note GB per hour for the dump and for the load per stream, and enter them. Split the table list into several files of similar size and enter how many will run in parallel. Enter reorganize time as a share of import time from the same test, add validation and sign-off hours, then a contingency.

**Bullets:**

- Export hours = GB / (bdbpre GB/h x streams x efficiency)
- Import hours = GB / (bdbpost GB/h x streams x efficiency)
- Reorganize hours = import hours x reorganize %
- Window = (export + import + reorganize + validation) x (1 + contingency)

#### Worked example

**Body:** 300 GB with 4 streams at 80 percent efficiency gives 3.2 effective streams. Export at 20 GB/h per stream takes about 4.7 hours, import at 12 GB/h about 7.8 hours, reorganize at 25 percent of import about 2.0 hours, plus 4 hours of validation, so about 18.5 hours. With 20 percent contingency, book about 22 hours. The chart shows the window falling quickly from 1 to 4 streams, then flattening, because validation is fixed and real systems hit an I/O limit.

#### Gotchas

**Body:** Put the largest tables in separate lists so one stream does not finish hours after the others. Load without referential integrity checks for speed but never skip the reference counter repair, or records that are still in use can be deleted later. If you dump with Exclude Logical Tables From Dump selected, each skipped logical table is logged in dump.err: check it. For Baan IV to LN, table structures differ, so the migration tooling and conversion runs add time beyond the raw copy.

**Cta:** If you are moving off Baan IV and want a private AI assistant over the new LN system from day one, we can plan both together.

**Faq:**

#### When does Baan IV support end?

**Answer:** Support status for Baan IV is set by Infor's product lifecycle policy and your own support contract, so check it with Infor for your release. This calculator does not depend on the date; it helps you plan the data move whenever you decide to make it.

#### Can I copy Baan IV data straight into Infor LN with bdbpre and bdbpost?

**Answer:** Only where the table structures match. Baan IV and LN tables differ, so a migration uses conversion tooling between the dump and the final load. The dump and load steps are still useful for moving data between servers and for company copies, and that is what this calculator times.

#### Why do I need ttaad4225m000 after bdbpost?

**Answer:** If tables are loaded with referential integrity ignored (the Ignore Referential Integrity Constraints check box in ttaad4227m000), imported records get a reference counter of zero. Reorganize Tables with Repair Reference Counter selected rebuilds the counters so LN does not allow deleting records still used by other tables.

#### How many parallel streams should I use?

**Answer:** Test it. Start with one stream per spare CPU core and disk path, and stop adding streams when total throughput no longer rises on your test run. Splitting large tables into their own lists usually matters more than adding streams.

## Search terms

baan iv end of support, baan iv erp, infor baan iv, bdbpre bdbpost, baan to ln migration downtime, infor ln sequential dump, ttaad4225m000 reorganize tables, baan company copy

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json