Skip to content

Run Datapump

Instructions to run Datapump manually:

What you need: * DatapumpOCLGUI.exe * DatapumpOCLGUI.ini * Source database, user and password * Destination database, user and password * path to tabledefinitions.xml * Tabledefinitions.xml * contains settings for each job.

Open DatapumpOCLGUI.exe * check TableDefinitions.xml path * Source db and target file * Source db Source Database * Target file Destination Database * Table ➝ select table * Selection Default or Range30, 60, 90, 365 days * if you need to run specific dates, select Default and pick dates from Date interval -section * Operation Update, Recreate, Trim * Normally use update * Trim's are running everyday, so don't need to trim manually * Recreate works by drop table, create it and pump all columns from scratch. 

datapump dashboard datapump errors log dash

If datapump has errors or has not completed the pumping process (check dashboard | Ahola will inform)

Most important datapumps are here in the datapump server:

C:\Datapump\AholaTransport\Nightly
  • if there is errors, copy and paste those to #road-ao-aholasupport
  • check report for uncomplete table → \report -folder
    • if the .csv doesn't show numbers on the latest line, you know that pumping has stopped for some reason
  • Check log file from \lLog -folder
    • note that there is 2 logs for each table from every night.
    • usually we are interested in about update operation. Second operation is TRIM
  • You will find the operation in the log file shows below:
2026-02-03 00:10:03:643 (4240) Table: ParcelData, Selection: Range90, Operation: Update
2026-02-03 06:30:05:726 (6928) Table: ParcelData, Selection: Default, Operation: Trim
  • to be sure that datapumping has completed successfully, you need check is there any exception / errors and check if it has completed
  • Each pumping start like this, there is Table, Selection, Operation and number of Fetched IDs:
2026-02-03 00:10:03:643 (4240) Table: ParcelData, Selection: Range90, Operation: Update
  • if it has completed successfully → log will end like this:
2026-02-03 03:41:47:273 (4240) Index (52000 - 52714) ID (569018359 - 566783641) Dates (27.1.2026 10:36:23 - 2.1.2026 12:40:25)
2026-02-03 03:41:47:879 (4240) Starting system shutdown.
2026-02-03 03:41:53:518 (4240) Shutdown complete.
2026-02-03 03:41:53:518 (4240) Activating system...
2026-02-03 03:41:54:038 (4240) Preparing Server Start Up...
2026-02-03 03:41:54:038 (4240) Done preparing Server Start Up.
2026-02-03 03:41:54:038 (4240) Starting Server...
2026-02-03 03:41:54:518 (4240) Server started.
2026-02-03 03:41:54:518 (4240) Done activating DataModule.
2026-02-03 03:41:54:587 (4240) Starting system shutdown.
2026-02-03 03:41:54:773 (4240) Shutdown complete
  • Fetched IDs match with processes indexes ^ (52714)

If there is need to pump manually, start DatapumpOCLGUI.exe * Select table from dropdown * Set Date intervall (start date & end date) * → Run

Common case is to run something about 2 weeks, but if it has stopped early you need to run more. There is couple small tables, which run can execute from Task Scheduler. You can check table "size" from the report, there is runtime time at the end of the line [HH-MM-SS]:

StartTime;Operation;Total;Processed;Matching;Missing;MissingUpdated;MissingFailed;Changed;ChangedUpdated;ChangedFailed;Runtime
2026.02.03 04:20:04;Trim;108429;108429;0;3456;0;0;0;0;0;(00:09:32 108429)/(00:09:32 108429)
2026.02.02 23:45:04;Update;111885;111885;108413;3472;3472;0;0;0;0;(00:19:40 111885)/(00:19:40 111885)
  • so if the runtime is less than 1 hour, we call it a "small" table

Quite common case when datapumping has stopped early with "big" table like ParcelData or PlanProgressData You need to pump first something like 1 week and then start pump the missing dates. Lets say that ParcelData has stopped around half way → start first GUI and run 1week and start second GUI and ran 6-8 weeks.