OSM DB Crashed Due to High DB Temp Utilization
Last updated on DECEMBER 09, 2017
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
***Checked for Currency on 04-Nov-2015***
On : 7.2.0 version, Database
In a production environment, the OSM DB instance crashed due to high DB temp space utilization.
Temp space was configured to grow till 20GB with auto-extension but this was exceeded.
Due to the DB crash, the OSM cluster went to failed start. To resolve this, the DB had to be restarted and then the cluster was restarted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms