Deleting SolarWindsOrionLog

The SolarWindsOrionLog has become so large we cannot upgrade SolarWinds. We are in the middle of the upgrade going through the configuration setup so we are unable to access the Web Console. Our solution currently is to delete the database and start over setting up safeguards in the Syslogs to prevent this problem in the future but we have been unable to do so. We keep getting an error that the file is open in another program and when we try to delete it through SQL it is being used by SolarWindsOrionDatabaseUser. How can we get past this issue? We just need to finish upgrading the product.

Find more posts tagged with

Delete Database

For the Novice

Accepted answers

dhodgson

After restarting the Server we were able to delete it. @donrobert5 I will be using the links you sent to make sure this doesn't happen again. Thank you.

All comments

donrobert5

Try this one.

Change the Retention Settings for Syslogs and Traps in Orion Platform (support.solarwinds.com)

By default it's seven. Try lowering it down. But the resolution for that is to only configure the devices to send syslog and traps that is actually needed and not all informational messages. Additionally, you can check this link below.

SQL Server configuration best practices for SolarWinds Platform products (documentation.solarwinds.com)

dhodgson

Sadly, I am unable to access the Web Console so cannot use the instructions from the first link. We plan to reconfigure the syslogs and traps once we have completed the upgrade and can access the web console again.

We configured the SQL Server accordingly when first setting up the product.

Azarel

@dhodgson

You can try stopping first the Orion services on all Polling Engine in your instance before trying to Delete the DB.

Another option is to truncate syslog / trap

Stop the Orion services on all of the Orion servers using the Orion Services Manager.
Open the Orion Database Manager.
Right-click on the SolarWindsOrionLog and select New Query.

Run the SQL query below:

SELECT 'Truncate Table [dbo].[' + table_name +']' FROM Information_Schema.tables where table_name like 'OrionLog_LogEntryMessage_%'
and table_name not like 'OrionLog_LogEntryMessageSource'
and table_type ='BASE TABLE'

Copy all the SQL query results to a Notepad.

Add the SQL query results on the SQL statements below:

Truncate Table [dbo].[OrionLog_LogEntry]
Truncate Table [dbo].[OrionLog_LogEntryFieldValue]

Copy the SQL queries and paste them back to the Orion Database Manager.
Execute all the SQL queries including the "Truncate Table [dbo].[OrionLog_LogEntry]"
and "Truncate Table [dbo].[OrionLog_LogEntryFieldValue]"

dhodgson

We just attempted this and received the following error:

-"The transaction log for database 'SolarWindsOrionLog' is full due to 'ACTIVE_TRANSACTION'."

We have also attempted the following without success:

-Changing SW Orion DB User permissions to Deny for connect

-Powered down server then tried to take it offline and detach and delete it (we were unable to even take it offline)

donrobert5

support.solarwinds.com/.../Transaction-log-for-Orion-database-is-full

NOTE: Steps specified are only applicable to databases using 'Simple' as its Recovery Model. For the Full Recovery Model, shrinking the Transaction Log requires taking a Full backup of the DB. Have DBAs perform the full backup instead

dhodgson

This was our first troubleshooting step at the beginning of the week and sadly it did not solve our specific problem. The log file is not so large but the database is taking up all of the server's memory. Currently we have resorted to trying to delete the database to no avail.

dhodgson

After restarting the Server we were able to delete it. @donrobert5 I will be using the links you sent to make sure this doesn't happen again. Thank you.