"Check interval" value is not set to 0 on customized partitions after recovering Exadata database server
(Doc ID 2320141.1)
Last updated on APRIL 12, 2022
Applies to:
Oracle Exadata Storage Server Software - Version 11.2.3.2.0 to 12.2.1.1.3 [Release 11.2 to 12.2]Linux x86-64
Symptoms
After recovering Exadata database server, the "Check interval" value was reset to 15552000 on customized partitions.
When running the exachk, the following result could be seen:
The database server file systems should have "Check interval" = "0"
/dev/VGExaDb/LVDbSys1: 0
/dev/VGExaDb/LVDbOra1: 0
/dev/VGExaDb/LVDbOra2: 15552000
/dev/VGExaDb/LVDbOra3: 15552000
/dev/VGExaDb/LVDbOra4: 15552000
/dev/VGExaDb/LVDbOra5: 15552000
/dev/VGExaDb/LVDbOra6: 15552000
/dev/VGExaDb/LVDbOra7: 15552000
/dev/VGExaDb/LVDbDiag1: 15552000
Changes
Recovered Oracle Linux database server with customized partitions
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |