| Description |
The article describes how to resolve 'ERROR: column 'incidnetid' does not exist' by cleaning Up device-related records in the FortiSIEM Database and how to clean up a device entry from the FortiSIEM CMDB that is causing database-related issues. |
| Scope | FortiSIEM. |
| Solution |
This error can occur in server.log when CMDB entries are inconsistent or corrupted, possibly due to schema mismatches or failed deletions.
Server.log error:
[glassfish 5.1] [ERROR] [] [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] [tid: _ThreadID=482 _ThreadName=pool-14-thread-10] [timeMillis: 1744616645840] [levelValue: 1000] [[
The resolution requires manually clearing multiple related tables in the PostgreSQL backend database phoenixdb which are:
psql -U phoenix -d phoenixdb select * from ph_incident2device;
select from ph_incident2device where device_id=xxxxxxx;
Find the IP or the device first:
SELECT id, name, access_ip, win_machine_guid FROM ph_device WHERE access_ip = 'x.x.x.x'
After identifying Id:
SELECT id, name, access_ip, win_machine_guid FROM ph_device WHERE id = xxxxxxx;
Delete the reference:
DELETE FROM ph_device WHERE id = xxxxxxx;
Post Validation:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.