Ao usar o AWS re:Post, você concorda com os AWS re:Post Termos de uso

Why did my Amazon RDS for Oracle DB instance restart, recover, or fail over?

3 minuto de leitura
0

My Amazon Relational Database Service (Amazon RDS) for Oracle DB instance automatically restarted, recovered, or failed over.

Short description

Amazon RDS for Oracle DB instances can automatically restart, recover, or fail over for the following reasons:

Resolution

To minimize issues with automatic restarts, recoveries, or failovers on your DB instance, use the following best practices:

  • Review the complete log of Amazon RDS events from the past 24 hours. To keep event data for an extended time period, it's a best practice to forward Amazon RDS events to CloudWatch Events. Use the logs to help you identify the underlying reason for the instance restart.
  • Activate Multi-AZ deployment on your DB instance to reduce downtime during an outage.
  • Create an event subscription to Amazon RDS event notifications to notify you when your DB instance restarts.
  • Configure CloudWatch alarms for key CloudWatch metrics that show instance availability. Use metrics such as, CPUUtilization, FreeableMemory, ReadIOPS, WriteIOPS, SwapUsage, and FreeStorageSpace.
  • Make sure that your queries are correctly tuned to optimize database performance. Otherwise, you might experience performance issues and extended wait times. Use the Performance Insights dashboard to analyze Oracle Execution plans and wait events.

Related information

How do I handle low free memory or high swap usage issues in my Amazon RDS for Oracle database instance?

Why is my Amazon RDS DB instance using swap memory when I have sufficient memory?