Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion Database Failed (trying to update to 2022.3) JSON_MODIFY must be a string literal

chromcarx

trying to update from 2020.6 to 2022.3 failed wit the following message:

Find more posts tagged with

Accepted answers

All comments

nafeeskhan29

Is this resolved ? If yes then how ?

Have you raised a case with Solarwinds Support?

I need to upgrade the version too.

xtraspecialj

Yeah, I'm trying to upgrade our QA instance of SolarWinds from 2023.1.0 to 2023.2 and am getting this same error...

marcrobinson

I just poked around google on that json sql error and this is one for SolarWinds support. Mostly because it looks like you are getting an error on some configuration json sent to the orion db. Not sure if I would want to troubleshoot that on a whim. Good luck and please post, it sounds like this might the first big bug found. THis might an issue going from 2020.XXX to 2023.2 directly though.

bmrad

Please open a ticket with support and post the number back here.

sja

Open a ticket and update the thread we sure like to know if it safe to move to that release

RomeoG2022

I, too, would like to see an update from anyone experiencing this issue and if it was resolved or not.

RomeoG2022

I have opened a support ticket to find out if this issue is resolved, and if it's considered safe to do this update. I will report back.

RomeoG2022

This is what I got back from support. I will reply later to report my results of the upgrade.

I understood your concern regarding you would like to know if it is safe to update to 2023.2.

Regarding your concern I checked internally and found that:

First of all, this issue might be coming when updating directly from 2020.2.x to 2023.2.
and for that case, we have steps for resolution that would resolve the issue.

You may refer the following and check for its "Before you upgrade from 2020.2.x" section, to make sure what to follow already:
SolarWinds Platform 2023.2 Release Notes

So, it is safe to update to 2023.2 version.