IPAM upgrade fails on IPAM_IPHistory_CS.HistoryType (timeseries schema validation)

2/10/2026 6:47 PM

2/10/2026 7:51 PM

When upgrading the SolarWinds Platform with IP Address Manager (IPAM) from 2026.1 release candidates to 2026.1 general availability, the Configuration Wizard can fail during the Configure Database step with an error similar to:

Error running task Orion.ConfigureDatabase SolarWinds Platform Database
System.ArgumentException: Table 'IPAM_IPHistory_CS', column NONE(HistoryType) tinyint NULL.
Changing from nullable to non-nullable type is not supported.
   at SolarWinds.Database.TimeSeries.SchemaManagerBase.ValidateSchemaChanges(...)
   at SolarWinds.Database.TimeSeries.SchemaManagerBase.SolarWinds.Database.TimeSeries.Contracts.ISchemaManager.UpdateSchema(...)
   at SolarWinds.Database.DatabaseConfigurator.TimeSeries.IPAMDatabaseConfigurator.UpdateTimeSeriesSchema(...)
   ...

This article explains the cause and provides a safe workaround using a SQL script.

IP Address Manager

In SolarWinds Platform 2026.1, IP Address Manager (IPAM) migrates IP history data from the legacy IPAM_IPHistory table to new time‑series tables (for example, IPAM_IPHistory_CS). In some environments that were previously upgraded to the 2026.1 release candidates, the HistoryType column in the IPAM_IPHistory_CS table was created as nullable, whereas the 2026.1 general availability expects this column to be non‑nullable and part of the primary key.

During a subsequent upgrade, the Configuration Wizard detects this mismatch and attempts to change the HistoryType column from nullable to non‑nullable on the existing time‑series table. This change is not supported by the time‑series framework, so schema validation fails and the upgrade stops with an error referencing IPAM_IPHistory_CS and HistoryType.

For environments already in the inconsistent state, use the workaround below to:

1. Remove the affected IPAM IPHistory timeseries tables.

2. Correct the timeseries metadata for HistoryType.

3. Allow the Configuration Wizard to recreate the tables with the correct schema.

 

As a workaround, the SQL SCript below needs to be executed;

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

DROP TABLE [dbo].[IPAM_IPHistory_CS_cur];
DROP TABLE [dbo].[IPAM_IPHistory_CS_Detail_hist];
UPDATE [dbo].[dbm_TimeSeriesConfig]
SET [IsNullable]=0,[IsNaturalKey]=1
WHERE [TableName]='IPAM_IPHistory_CS' AND [ColumnName]='HistoryType';