Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Oracle RDS running out of storage
0
My RDS Oracle instance is running out of storage due to archived redo logs.
I have already set the archivelog retention hours to 0 using:
sql
Copy
Edit
BEGIN
rdsadmin.rdsadmin_util.set_configuration(
name => 'archivelog retention hours',
value => '0'
);
END;
/
I had the same issue last week, I changed the archivelog retention hours to 0, reduced the backup retention to 7 days and increased the size by 500GB and now today the space was full according with the RDS dashboard but I can't see where that space is being consumed, I have checked dba_undo_extents, v$temp_space_header, dba_data_files, dba_segments and all looks ok
This recommendation was generated using AWS Generative AI capabilities. You are responsible for evaluating the recommendation in your specific context and implementing appropriate oversight and safeguards. Learn more
It sounds like you're facing a persistent storage issue with your Oracle RDS instance, even after taking some initial steps to address it. While setting the archivelog retention hours to 0 and reducing backup retention are good first steps, there may be other factors contributing to your storage consumption.
Here are some additional areas to investigate:
Check for autoextended tablespaces: Some tablespaces might be configured to automatically extend, consuming more space than expected.
Examine Oracle file size quotas: Ensure that file size quotas are not causing unexpected storage consumption.
Review large trace files and Data Pump directories: These can take up significant space. Consider cleaning up or archiving unnecessary files.
Analyze database fragmentation: Fragmentation can lead to inefficient storage usage. You may need to address this issue.
Monitor FreeStorageSpace metric: Use Amazon CloudWatch to track this metric. A rapid drop can indicate increased usage approaching storage-full state.
Check backup storage usage: Even with reduced retention, backups might still be consuming significant space. You can verify this using AWS CLI.
Investigate hidden tables or unused schemas: There might be data structures created by applications or users that aren't regularly monitored.
If after checking these areas you still can't identify the cause of the storage consumption, it may be worthwhile to reach out to AWS Support for a deeper analysis. There could be specific settings or issues related to your instance type or configuration affecting the storage usage.
Remember, just because you've increased storage doesn't mean all of it is immediately available for your database. RDS uses some of this space for system operations and backups. Consider implementing storage auto-scaling and setting up CloudWatch alarms to notify you when free storage space reaches a specified threshold. This will allow you to take proactive measures before hitting critical storage levels again.