Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > The Orion database is corrupted

The Orion database is corrupted

Updated 26th October 2018

Overview

You experience different errors in SolarWinds Orion products, such as 

  • The nightly database maintenance does not complete. 
  • Database maintenance tasks access excessive numbers of Orion database structures to consolidate statistical data, defragment indexes, etc.
  • The product does not start or crashes.

Additionally, an error message asking to run DBCC CHECKDB command appears in the SQL server logs.

Msg 823, Level 24, State 2, Line 2
The operating system returned error 1(Incorrect function.) to SQL Server during a read at offset 0x00001382b14000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\NetPerfMon.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

 

Environment

  • Any Orion Platform product

Cause

  • The cause of these problems can vary from file system corruption, underlying hardware system issues, driver issues, corrupted pages in memory, or problems with the SQL Server Engine.

Resolution

  • Ask your database administrator to investigate the issue and perform a full database consistency check, such as running the DBCC CHECKDB command with appropriate options.
  • If the database cannot be repaired by your DBA, you will need to restore before the issue occurred or create a new database from scratch.
 

 

Last modified

Tags

Classifications

Public