# Ignition Historian - Error executing post-value seed query **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [April 2, 2026, 12:58am UTC](https://forum.inductiveautomation.com/t/ignition-historian-error-executing-post-value-seed-query/114846 "2026-04-02T00:58:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![chaitany.goyal](https://avatars.discourse-cdn.com/v4/letter/c/da6949/32.png) [@chaitany.goyal](https://forum.inductiveautomation.com/u/chaitany.goyal)\ **Post date:** [April 2, 2026, 12:58am UTC](https://forum.inductiveautomation.com/t/ignition-historian-error-executing-post-value-seed-query/114846/1 "2026-04-02T00:58:44Z")
I have following issues with Core Historian. The suggested solution from the error is to remove partition table but since the Historian is supposed to a black box, is there a way of fixing this issue without trying to get write access to the Historian somehow? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/0/106cafa3bfee34540683b58e827a26406e1c7108.png) Additional detail: - Current I am using Ignition 8.3.3 - Core Historian Settings are below - It is currently setup is as a Splitter with another SQL Historian - The issue started when the SQL Historian had LOG\_BACKUP full error - That issue has been rectified by setting it to RECOVERY to simple in the database - However, it seems to have cause issues to Core Historian which still persist now - I have attempted to delete/rename and recreate History\_Core historian as well as reenable Historian Module. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/1/f1829e7e4bf0db82df815816cda7d47060020157.png) Any help would be appreciated. Thanks ---
**Author:** ![chaitany.goyal](https://avatars.discourse-cdn.com/v4/letter/c/da6949/32.png) [@chaitany.goyal](https://forum.inductiveautomation.com/u/chaitany.goyal)\ **Post date:** [April 9, 2026, 4:22am UTC](https://forum.inductiveautomation.com/t/ignition-historian-error-executing-post-value-seed-query/114846/2 "2026-04-09T04:22:11Z")
**Just an update:** **Got a response from Ignition Help (very prompt).** Note these steps are best to be performed with Ignition being stopped as it means the Core Historian DB copy that is taken and adjusted for the required fix doesn't get changed during the time it takes to do the fix. Also, it is advised to take a second copy of the following mentioned 'db' folder and save to another location(temporarily to the desktop is suitable). Gain Access to a current copy of the Ignition Core Historian DB: - Download QuestDB 9.1.0 [https://github.com/questdb/questdb/releases/tag/9.1.0](https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fquestdb%2Fquestdb%2Freleases%2Ftag%2F9.1.0&data=05%7C02%7Cchaitany.goyal%40pivotal.engineering%7Cd69ce36072904a258cbb08de95ed239b%7Cc617d961ef244db5b3a7679c1b35a653%7C0%7C0%7C639113042926678585%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XpXk4E93atXk7h5UQNN40l6aGe%2BwkncrIIyiUtYwM3k%3D&reserved=0 "Original URL: https://github.com/questdb/questdb/releases/tag/9.1.0. Click or tap if you trust this link.") (as this version is compatible for 8.3.3)(needs to be the exact same version) - Extract the folder and open up an admin CMD Terminal - Navigate into the bin folder (`cd C:\Users\\Downloads\questdb-9.1.0-rt-windows-x86-64\questdb-9.1.0-rt-windows-x86-64\bin`) - Run `.\questdb.exe install` and then `.\questdb.exe start`, this will create a folder called `qdbroot` under your system32 directory (`C:\Windows\System32`) - Run `.\questdb.exe stop` - Navigate to the Core Historian's directory (`C:\Program Files\Inductive Automation\Ignition\data\var\com.inductiveautomation.historian\corehistorian`) - Copy the Core Historian's 'db' folder into `C:\Windows\System32\qdbroot` and replace all files. - Run `.\questdb.exe start` - On a web browser navigate to `localhost:9000`, you should see all tables of the Core Historian Make changes to address the issue: - Run the SQL query `wal_tables` and observe the `core.datapoints` row, where it likely appears as true on the `suspended` column and the `writerTxn` and `sequencerTxn` likely have different values. - Run `ALTER TABLE "core.datapoints" RESUME WAL FROM TXN {writerTxn}`, - Following that, Run the `SHOW PARTITIONS FROM "core.datapoints"` to see all partitions in the Core Historian. - Run the `ALTER TABLE core.datapoints FORCE DROP PARTITION LIST ''` to drop the table out of the Core Historian. - Double-check on the `wal_tables` query that the `core.datapoints` has matching `writerTxn` and `sequencerTxn` (note you **may not see false under suspended** , but that is fine\*\*).\*\* - Double-check the partitions from the `core.datapoints` table that the corrupted table has been removed. - Back on CMD, Run `.\questdb.exe stop` - Navigate to the `qdbroot` folder (`C:\Windows\System32\qdbroot`) and **copy the 'db' folder** - Paste the copied 'db' folder directly into the Core Historian's installation directory (`C:\Program Files\Inductive Automation\Ignition\data\var\com.inductiveautomation.historian\corehistorian`) and replace all the files. - Start the Ignition Gateway Service. Verify the table has reconnected as expected and data is accessible: - Open a session(Designer or Perspective) that has a Power Chart on it, - Dragged a tag onto the Power Chart and ensure data maps as expected. - Access Gateway Web Page Status\>logs to observe the loggers and confirm the pre-seed and post-seed errors are no longer being recorded.